4680 Supermarket IBM

Electronic Marketing Support PRPQ:

User’s Guide

SC30-3547-01
Note:
Before using this information and the product it supports, be sure to read the general information
under “Notices” on page xv.

Second Edition (April 2000)

This is the second edition of the IBM 4680 Electronic Marketing Store Support PRPQ For The IBM 4680
Supermarket Application SC30-3547-01.
Order publications through your IBM representative or the IBM branch office serving your locality. Publications are
not stocked at the address given below.
Forms for readers’ comments appear at the front and back of this publication. If the forms have been removed,
address your comments to:
IBM Corporation, Department CJMA
PO Box 12195
Research Triangle Park, North Carolina
U. S. A.
When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any
way it believes appropriate without incurring any obligation to you.
© Copyright International Business Machines Corporation 1991 2000. All rights reserved.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . xv
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . xv

About This Book . . . . . . . . . . . . . . . . . . . . . . . xvii

About the Chapters . . . . . . . . . . . . . . . . . . . . . . . xvii
Related Publications . . . . . . . . . . . . . . . . . . . . . . xviii
IBM 4680 Supermarket Application . . . . . . . . . . . . . . . . xviii
IBM 4680 Store System Library . . . . . . . . . . . . . . . . . xviii

Summary of Changes . . . . . . . . . . . . . . . . . . . . . xix

Part 1. Planning and Installation . . . . . . . . . . . . . . . . . . . . . . . . 1

Chapter 1. Introduction . . . . . . . . . . . . . . . . . . . . . . 5
Overview and Perspective . . . . . . . . . . . . . . . . . . . . . 5
Hardware Supported . . . . . . . . . . . . . . . . . . . . . . . 6
What this Program Includes . . . . . . . . . . . . . . . . . . . . 6

Chapter 2. Concepts . . . . . . . . . . . . . . . . . . . . . . . 7
Customer Enrollment and Identification . . . . . . . . . . . . . . . . 7
Rain check Customers . . . . . . . . . . . . . . . . . . . . . 8
Customer Identification Number . . . . . . . . . . . . . . . . . . 8
Customer Recognition, Rewards, and Messages . . . . . . . . . . . . . 8
Points. . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Points-Only Items . . . . . . . . . . . . . . . . . . . . . . . 9
Electronic Marketing Coupons . . . . . . . . . . . . . . . . . . 10
Home Store Concept. . . . . . . . . . . . . . . . . . . . . . . 11
Enterprises that Use the Home Store Concept . . . . . . . . . . . . 12
Non-Home Store Concept . . . . . . . . . . . . . . . . . . . . . 13
Enterprises that Use a Non-Home Store Concept . . . . . . . . . . . 13
Activity Record Types . . . . . . . . . . . . . . . . . . . . . . 13
Primary Customer Activity Records . . . . . . . . . . . . . . . . 13
Alias Customer Activity Records for Family Members . . . . . . . . . . 13
Electronic Marketing Database . . . . . . . . . . . . . . . . . . 13
Auxiliary Functions . . . . . . . . . . . . . . . . . . . . . . . 14
Default Auxiliary Functions . . . . . . . . . . . . . . . . . . . 14
Accept Only Foodstamps After a Foodstamp Balance Due . . . . . . . . 15
Display the Weight for Sales of Weight Items . . . . . . . . . . . . . 15
Prohibit Entry of Cash Amounts When the Balance Is Negative . . . . . . 15
Weight Accumulation on Category 2 Sales . . . . . . . . . . . . . . 15
Improved End of Transaction Printing Performance . . . . . . . . . . 15
Printed Subtotals . . . . . . . . . . . . . . . . . . . . . . . 15
Add Operator Name to Cash/Performance Reports . . . . . . . . . . 15
Require an Override for Any Negative Transaction . . . . . . . . . . . 16
Store Coupon Taxability Defined Only by the Item Record and Tax Key . . . 16
Document Print Voids of Miscellaneous Items . . . . . . . . . . . . 16
Exception Logging of Data Entry on Items . . . . . . . . . . . . . . 16
Improved Terminal Monitor from the Controller . . . . . . . . . . . . 16
Document Low Memory Condition . . . . . . . . . . . . . . . . . 16

© Copyright IBM Corp. 1991 2000 iii

 Print Additional Diagnostic Data for Selected Failures. . . . . . . . . . 16
Prohibit Changing of Department Numbers from a Register . . . . . . . 16
Optional Auxiliary Functions . . . . . . . . . . . . . . . . . . . . 17
Highlighting Negative Entries . . . . . . . . . . . . . . . . . . . 17
Ignore Coupon Families for Validation . . . . . . . . . . . . . . . 17
Panel Capture of Transaction Data . . . . . . . . . . . . . . . . 17
Only Allow One Terminal to Have Negative Transactions . . . . . . . . 17
Define Which Taxes to Turn On with the Tax/NoTax Key. . . . . . . . . 17
Accumulate UPC/Department Key Rather Than Keyed/Scanned Sales . . . 18
Accumulate Keyed Versus Scan Totals by Department . . . . . . . . . 18
Weight Items Do Not Require Weight Key . . . . . . . . . . . . . . 18
Display Backup Indicator at Registers . . . . . . . . . . . . . . . 18
Allow Tax Exemption Without a Discount Key. . . . . . . . . . . . . 18
Cash Checks Using a Sales Transaction . . . . . . . . . . . . . . 18
Remind Operator to Take the Customer’s Money . . . . . . . . . . . 18
Interpret Restricted Time Periods as Unrestricted Times . . . . . . . . . 18
Support for Multiple Cash Drawers . . . . . . . . . . . . . . . . 18
Time in 12-Hour Format on the Customer Receipt . . . . . . . . . . . 19
Require Immediate Override for Transaction Cancel Limits . . . . . . . . 19
Limit the Length of the Item Descriptor Shown to the Customer . . . . . . 19
Get Tare Code Information from the Item Record for Weight Items . . . . . 19

Chapter 3. Coupon Processing Enhancements . . . . . . . . . . . . 21

Store Coupon Scanning Enhancements . . . . . . . . . . . . . . . . 21
Category 4 UPC Store Coupons . . . . . . . . . . . . . . . . . 21
Category 5 UPC Store Coupons . . . . . . . . . . . . . . . . . 21
Store Coupon Validation Enhancements . . . . . . . . . . . . . . . 23
Validation of Coupon UPCs with Invalid or No Manufacturer Number . . . . 23
Limit of Like Coupons in a Transaction . . . . . . . . . . . . . . . 24
Validation Only by Quantity of Like Coupons . . . . . . . . . . . . . 24
Validate Department Coupons by Department Subtotal Group . . . . . . 24
Minimum Purchase Requirement . . . . . . . . . . . . . . . . . 24
Minimum Purchase by Manufacturer or Department . . . . . . . . . . 24
Minimum Purchase by Department without Department Validation . . . . . 25
Require More Than One Item Per Coupon . . . . . . . . . . . . . . 25
Support Cross-Item Promotion Coupons . . . . . . . . . . . . . . 25
Coupon Expiration Based on a Sequence Number . . . . . . . . . . . 25
Support Bypass of Validation for Certain Coupons . . . . . . . . . . . 26
Promotion Code Validation . . . . . . . . . . . . . . . . . . . 26
Summary of Coupon Validation Enhancements . . . . . . . . . . . . 26
General Enhancements. . . . . . . . . . . . . . . . . . . . . . 27
Support for 7, 8, and 9 Digit UPCs on Store Coupons . . . . . . . . . 27
Coupon Provides Net Item Value Instead of Discount . . . . . . . . . . 27
Support for Training Mode . . . . . . . . . . . . . . . . . . . . 28
Item Record Data for Store Coupons . . . . . . . . . . . . . . . . . 28
Additional Coupon Record Data. . . . . . . . . . . . . . . . . . 28
Coupon Record Maintenance . . . . . . . . . . . . . . . . . . 29
Coupon Restrictions Because of Additional Data . . . . . . . . . . . 29
Coupon Restrictions Because of System Design . . . . . . . . . . . 29
Coupon Multiplication Limits . . . . . . . . . . . . . . . . . . . . 30
Limit on the Number of Coupons Doubled . . . . . . . . . . . . . . 30
Limit on the Value of Doubled Coupons (3 Options) . . . . . . . . . . 30
Minimum Purchase Requirement . . . . . . . . . . . . . . . . . 30
Limit of Coupons to Double Varies with Order Size. . . . . . . . . . . 31
Deactivate Coupon Doubling by Day of Week . . . . . . . . . . . . 31
Do Not Double MFR Coupon if Store Coupon Already Taken for Item . . . . 31

iv Electronic Marketing PRPQ

 Limit on the Number of Like Coupons to Be Doubled in an Order . . . . . 31
Prohibit Coupon Doubling Through a Key Sequence . . . . . . . . . . 31
Allow Manual Entry of Doubled Coupons . . . . . . . . . . . . . . 32
Allow Coupons to Be Marked for No Doubling . . . . . . . . . . . . 32
Operator Interface Enhancements . . . . . . . . . . . . . . . . . . 32
Allow Operator Override of User-Selected Error Conditions . . . . . . . 32
Prompt the Operator to Write Free Coupon Value on the Coupon . . . . . 32
Alter Coupon Guidance if too few Items Are Sold . . . . . . . . . . . 33
Alter Coupon Guidance to Tell if any Matching Items Are Sold . . . . . . 33
Allow Certain Coupon Entries without Matching Item Validation . . . . . . 33
Require a Single Override in a Coupon only Transaction . . . . . . . . 33
Logging of All Coupon Data . . . . . . . . . . . . . . . . . . . . 33
Coupon Tracking Options . . . . . . . . . . . . . . . . . . . . 34
Limit Coupon Tracking to a Range of Coupon UPCs . . . . . . . . . . 34
Coupon Campaign Number Capture . . . . . . . . . . . . . . . . 34
Personalization of Coupon Processing . . . . . . . . . . . . . . . . 35
System Performance Considerations of Coupon Processing . . . . . . . . 35

Chapter 4. Installation and Configuration . . . . . . . . . . . . . . 37

Installation Notes . . . . . . . . . . . . . . . . . . . . . . . . 37
Install Electronic Marketing Exit Code . . . . . . . . . . . . . . . . 38
Copying Electronic Marketing Files to Your System . . . . . . . . . . 38
Alter Terminal Sales and Checkout Support Link List . . . . . . . . . . 38
| Enhanced Manufacturer Coupon Reporting Considerations. . . . . . . . 39
Install Terminal and Controller Checkout Exit Code. . . . . . . . . . . 40
Install Report Exit Code . . . . . . . . . . . . . . . . . . . . 42
Re-Link Data Maintenance, Tender Count and Automatic Reconciliation . . . . 43
Install Background Programs . . . . . . . . . . . . . . . . . . . . 44
Install User Reports . . . . . . . . . . . . . . . . . . . . . . . 44
Install Optional User Procedures . . . . . . . . . . . . . . . . . . 45
Install the Optional Date of Last Sale Update Function . . . . . . . . . 45
Optional Source Code Changes . . . . . . . . . . . . . . . . . . 47
Optional Changes to Delayed Data Maintenance . . . . . . . . . . . 47
Optional Changes to Department Analysis Report . . . . . . . . . . . 49
Perform Configuration Changes. . . . . . . . . . . . . . . . . . . 52
Add User Logical Names . . . . . . . . . . . . . . . . . . . . 52
Configure Background Application . . . . . . . . . . . . . . . . . 53
Configure Key Sequences for Auxiliary Functions . . . . . . . . . . . 54
Configure Optional Customer Number Key. . . . . . . . . . . . . . 55
Install the In-Store Enrollment Program . . . . . . . . . . . . . . . . 60
Install the Batch Keyed File Maintenance Program . . . . . . . . . . . . 61
Install Batch Program . . . . . . . . . . . . . . . . . . . . . 61
Configure Logical Names for the Batch Program . . . . . . . . . . . 61
Use Controller Configuration to Define a New Background Program . . . . 62
Add Messages Used by the Batch Program . . . . . . . . . . . . . 62
Executing the Batch Program . . . . . . . . . . . . . . . . . . 62
Install Background Panel Filters as Needed . . . . . . . . . . . . . . 62
Install Electronic Marketing Data Files . . . . . . . . . . . . . . . . 63

Chapter 5. Personalization . . . . . . . . . . . . . . . . . . . . 65
Activate Terminal and Controller Exits . . . . . . . . . . . . . . . . 65
Personalize Terminal Sales Descriptors . . . . . . . . . . . . . . . . 65
Personalize Report Descriptors . . . . . . . . . . . . . . . . . . . 66
Personalize Electronic Marketing Report Descriptors . . . . . . . . . . . 68

Part 2. Operations and Reports . . . . . . . . . . . . . . . . . . . . . . . . 69

Contents v
 Chapter 6. Personalization of Preferred Customer Options and Messages 75
Preferred Customer Options File (EAMFBOPT) . . . . . . . . . . . . . 75
Preferred Customer Options Default . . . . . . . . . . . . . . . . 76
Preferred Customer Options Descriptions . . . . . . . . . . . . . . 76
Selective Item Record Report Options . . . . . . . . . . . . . . . 163
Preferred Customer Messages File (EAMFBMSG) . . . . . . . . . . . 169
Message Zero: Normal points message . . . . . . . . . . . . . . 171
Message One: Points message for non-home store customers . . . . . . 171
Message Two: Points message for new customers . . . . . . . . . . 171
Message Three: Prints message for customers not enrolled . . . . . . . 171
Message Four: Personalization message for receipt . . . . . . . . . . 171
Message Five: Out of store transfer message . . . . . . . . . . . . 172
Message Six: Rain check message . . . . . . . . . . . . . . . . 172
Message Seven: Bonus points message . . . . . . . . . . . . . . 172
Message Eight: Redeemed points message . . . . . . . . . . . . . 172
Message Nine: Available targeted coupons header message . . . . . . 172
When Messages Are Shown . . . . . . . . . . . . . . . . . . 172
Messages Associated with Customer Identification . . . . . . . . . . 172
Messages Associated with Other Customer Interests . . . . . . . . . 173
Data Entry Line . . . . . . . . . . . . . . . . . . . . . . . 173
How to Activate Additional Messages . . . . . . . . . . . . . . . 173
How to Make Changes to the Messages File . . . . . . . . . . . . 173
Default Preferred Customer Messages File . . . . . . . . . . . . . 174

Chapter 7. Operations . . . . . . . . . . . . . . . . . . . . . 177

How to Enter a Customer ID Number . . . . . . . . . . . . . . . . 177
Establishing a New Customer Identification Number . . . . . . . . . . . 178
When to Enter Customer ID Number with Targeted Coupons . . . . . . . 178
How to Enter Multiple Customer ID Numbers per Transaction . . . . . . . 179
Procedures for Preferred Customer Identification . . . . . . . . . . . . 179
Enrolled Preferred Customer Receipt . . . . . . . . . . . . . . . . 180
Regular Customer Receipt . . . . . . . . . . . . . . . . . . . . 180
In-Store Enrollment Procedure Screens . . . . . . . . . . . . . . . 181
Preferred Customer Enrollment . . . . . . . . . . . . . . . . . . 183
Changing a Customer Record . . . . . . . . . . . . . . . . . . . 185
Erase a Customer Record . . . . . . . . . . . . . . . . . . . . 187
Displaying a Customer Record . . . . . . . . . . . . . . . . . . 189
Redeeming an Award . . . . . . . . . . . . . . . . . . . . . . 191
Adjusting a Customer Record . . . . . . . . . . . . . . . . . . . 193
Entering a Rain check . . . . . . . . . . . . . . . . . . . . . . 195
Sample Coupons . . . . . . . . . . . . . . . . . . . . . . . 197
Bonus Point Coupons . . . . . . . . . . . . . . . . . . . . . . 197
Limit Per Transaction/Items Per Coupon . . . . . . . . . . . . . . . 199
Final Value Coupons . . . . . . . . . . . . . . . . . . . . . . 201
Linked Coupons (Discount/Redeem Points) . . . . . . . . . . . . . . 202
Linked Coupons (Multiple Items Plus Points) . . . . . . . . . . . . . 205
Linked Coupons (Multiple Items/No Points) . . . . . . . . . . . . . . 209
Coupon Linked to Department Purchase . . . . . . . . . . . . . . . 212
Coupon Linked to a Minimum Department Purchase . . . . . . . . . . 214
Coupon Linked to Minimum in Two Departments . . . . . . . . . . . . 215
Coupon Linked to Minimum by Manufacturer . . . . . . . . . . . . . 218
Coupon Linked to Items per Coupons . . . . . . . . . . . . . . . . 219
Award Points With No Performance Required . . . . . . . . . . . . . 222
Promotion Code Coupons . . . . . . . . . . . . . . . . . . . . 223
Percent Off Discount Coupons. . . . . . . . . . . . . . . . . . . 225

vi Electronic Marketing PRPQ

Chapter 8. Electronic Marketing Processing. . . . . . . . . . . . . 227
Support for Home Store Processing . . . . . . . . . . . . . . . . . 227
Home Store Concept Supported Mainly by In-Store Processing . . . . . 227
Home Store Concept Supported Mainly by Central Site Processing . . . . 227
Support for No Home Store . . . . . . . . . . . . . . . . . . . . 228
Support for Multiple Home Stores . . . . . . . . . . . . . . . . . 228
Customer Identification Number Processing . . . . . . . . . . . . . . 228
Validating a Customer Identification Number . . . . . . . . . . . . 228
Using a Customer Number as Tender Verification Number . . . . . . . 229
Alias/Primary Record Pair Processing . . . . . . . . . . . . . . . 230
Electronic Coupon Processing . . . . . . . . . . . . . . . . . . . 230
Awarding Electronic Coupons during Sales . . . . . . . . . . . . . 230
Distinguishing Electronic Coupons from Other Types . . . . . . . . . 231
Implementing Cross-Promotional Electronic Coupons . . . . . . . . . 231
Effect on Performance. . . . . . . . . . . . . . . . . . . . . 232
Effect on Taxes . . . . . . . . . . . . . . . . . . . . . . . 232
Electronic Coupon Maintenance . . . . . . . . . . . . . . . . . 232
Targeted Coupon Processing . . . . . . . . . . . . . . . . . . 234
Entering a Customer ID with Targeted Coupons . . . . . . . . . . . 235
Validating Targeted Coupons . . . . . . . . . . . . . . . . . . 235
Defining Reuse of Targeted Coupons . . . . . . . . . . . . . . . 236
Maintaining Targeted Coupons in the Customer Activity Record . . . . . 236
Defining Targeted Coupons in the Rain Check Record . . . . . . . . . 237
Redemption Coupon Processing . . . . . . . . . . . . . . . . . . 237
Point Processing . . . . . . . . . . . . . . . . . . . . . . . . 238
Linkage of Points-Only Items . . . . . . . . . . . . . . . . . . 238
Point Eligibility. . . . . . . . . . . . . . . . . . . . . . . . 239
Points Multiplication via Customer Activity Record. . . . . . . . . . . 240
Customer Point Adjustments at the Controller . . . . . . . . . . . . 240
Referenced Account Point Processing . . . . . . . . . . . . . . . . 240
Support for Periodic Points Totals . . . . . . . . . . . . . . . . . 240
Automatic Discounts via Customer Activity Record . . . . . . . . . . . 242
Provide Kiosk Support to Show Customer Their Points and Coupons . . . . 243
Totals Accumulation Processing . . . . . . . . . . . . . . . . . . 244
Using Data Base for Directed Marketing . . . . . . . . . . . . . . 244
Updating and Transferring Totals Files . . . . . . . . . . . . . . . 244
Accumulating Electronic Coupons Totals . . . . . . . . . . . . . . 245
Data Space Use Adjustments . . . . . . . . . . . . . . . . . . . 246
Date of Last Sale Update Functions. . . . . . . . . . . . . . . . . 247
Promotion Code Validation . . . . . . . . . . . . . . . . . . . . 247
Use of promotion codes is optional . . . . . . . . . . . . . . . . 247
Promotion codes are values in User Exit field 1 in item records . . . . . 247
Validation of coupons with promotion codes . . . . . . . . . . . . . 248
Minimum purchase of coupons with promotion codes . . . . . . . . . 248
Taxability and foodstampability of coupons with promotion codes . . . . . 248

Chapter 9. Reports . . . . . . . . . . . . . . . . . . . . . . 249

User Reports . . . . . . . . . . . . . . . . . . . . . . . . . 249
Selective Item Record Report . . . . . . . . . . . . . . . . . . . 250
Item Selection . . . . . . . . . . . . . . . . . . . . . . . . 250
Item Reporting . . . . . . . . . . . . . . . . . . . . . . . 252
Item Alterations . . . . . . . . . . . . . . . . . . . . . . . 254
Operator Interface . . . . . . . . . . . . . . . . . . . . . . 257
Error Handling. . . . . . . . . . . . . . . . . . . . . . . . 257
Performance . . . . . . . . . . . . . . . . . . . . . . . . 257
Selective Preferred Customer Report . . . . . . . . . . . . . . . . 258

Contents vii
 Customer Selection . . . . . . . . . . . . . . . . . . . . . . 258
Customer Reporting . . . . . . . . . . . . . . . . . . . . . 259
Customer Record Alterations . . . . . . . . . . . . . . . . . . 260
Operator Interface . . . . . . . . . . . . . . . . . . . . . . 261
Error Handling. . . . . . . . . . . . . . . . . . . . . . . . 261
Performance . . . . . . . . . . . . . . . . . . . . . . . . 261
Preferred Customer Audit Log Report . . . . . . . . . . . . . . . . 262
Preferred Customer Exception Log Report . . . . . . . . . . . . . . 262
Preferred Customer Options Report . . . . . . . . . . . . . . . . . 264
Sample Electronic Marketing Preferred Customer Options Report . . . . . . 268
Accounting Reports . . . . . . . . . . . . . . . . . . . . . . . 273

Part 3. Utilities and Programming . . . . . . . . . . . . . . . . . . . . . . 275

Chapter 10. Utilities -- Installation and Operational . . . . . . . . . . 277

Installation Utilities . . . . . . . . . . . . . . . . . . . . . . . 277
DESCADDE - Auto Install of Electronic Marketing Descriptors . . . . . . 277
DESCADDR - Auto Install of New Report Descriptors . . . . . . . . . 278
DESCADDS - Auto Install of New Sales Descriptors. . . . . . . . . . 278
FIXFILES - Keyed File Record Reformatting . . . . . . . . . . . . 279
FIXR1OPT - Convert Options Files to New Format . . . . . . . . . . 280
LOGNAMES - Install Preferred Customer Logical Names . . . . . . . . 281
Operational Utilities . . . . . . . . . . . . . . . . . . . . . . . 282
EAMUBATP - Batch Maintenance for Keyed files . . . . . . . . . . . 282
EAMUREFA - Preferred Customer Reference Processing . . . . . . . . 293
EAMUROLP - Roll Customer Period Totals Procedure . . . . . . . . . 294
EAMUPM3L - Manual Close of Points Activity Period . . . . . . . . . 294
EAMUPM4L - Maintain Targeted Coupon Messages . . . . . . . . . . 295
EAMUXFER - Process Customer Data from Other Stores. . . . . . . . 295
EAMUFILT - Filters Transaction Summary Log Data . . . . . . . . . . 295
EAMUPKUP - Automatic Pickup of Paperless Coupons . . . . . . . . 296
EAMUDOLS - Date of Last Sale Update Function . . . . . . . . . . 296

Chapter 11. Electronic Marketing Unique User Exits . . . . . . . . . 299

Electronic Marketing Unique User Exits . . . . . . . . . . . . . . . 299
Electronic Marketing Terminal User Exits . . . . . . . . . . . . . . . 300
Exit TSEMEC01 - Called After The Read Of A Customer Activity Record 300
Exit TSEMEC02 - Called After The Read Of A Customer Transfer Record 301
Exit TSEMEC03 - Called After The Read Of A Coupon Message Record 301
Exit TSEMEC04 - Called After The Input Of A Customer Number in
Response to a Prompt (Input from MSR) . . . . . . . . . . . . . 302
Exit TSEMEC05 - Called After Validation Of A Customer Number . . . . . 302
Exit TSEMEC06 - Called After Computing A Coupon Value Based On The
Value Of Matching Items . . . . . . . . . . . . . . . . . . . 303
Exit TSEMEC07 - Called Before Assuring The Minimum Purchase For A
Coupon Is Met. . . . . . . . . . . . . . . . . . . . . . . 303
Exit TSEMEC08 - Called After Computing The Points Value Of An Order 304
Exit TSEMEC09 - Called After Saving A Coupon For Total Time . . . . . 304
Exit TSEMEC10 - Called At Checking For Crossing A Points Boundary 305
Exit TSEMEC11 - Called Before Giving Automatic Coupons At The Entry Of
A Customer Number . . . . . . . . . . . . . . . . . . . . 305
Exit TSEMEC12 - Called Before Giving Automatic Coupons At Total Time 306
Electronic Marketing Controller User Exits . . . . . . . . . . . . . . 307
Exit CSEMEC01 - Called After the Read of a Customer Activity Record 307
Exit CSEMEC02 - Called After the Read of a Customer Transfer Record 308
Exit CSEMEC03 - Called Before the Write of a Customer Activity Record 309

viii Electronic Marketing PRPQ

 Exit CSEMEC04 - Called Before the Write of a Customer Transfer Record 310
Exit CSEMEC05 - Called Before the Write of an Activity Transfer Record 310
Exit CSEMEC06 - Called After The Update Of Accounting Totals . . . . . 311
Exit CSEMEC07 - Called Before The Write Of A Preferred Customer Audit
Log Record . . . . . . . . . . . . . . . . . . . . . . . . 312
Exit CSEMEC08 - Called Before the Write of a Panel Diary Record . . . . 312
Exit CSEMEC09 - Called Before The Write Of A Coupon Tracking Record 313

Part 4. Appendixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315

Appendix A. Electronic Marketing Database. . . . . . . . . . . . . 317

File and Options Support. . . . . . . . . . . . . . . . . . . . . 318
Preferred Customer Enrollment File (EAMFBCUS) . . . . . . . . . . . 320
Preferred Customer Activity File (EAMFBACT) . . . . . . . . . . . . . 322
Preferred Customer Previous Activity File (EAMFBAPP) . . . . . . . . . 324
Electronic Marketing Report Descriptors File (EAMEDESC) . . . . . . . . 325
Preferred Customer Transfer File (EAMFBXFR) . . . . . . . . . . . . 325
Preferred Customer Activity Transfer File (EAMXssss) . . . . . . . . . . 326
Preferred Customer Audit Log (EAMFBAUD) . . . . . . . . . . . . . 327
Redemption Adjustment Record Format . . . . . . . . . . . . . . 327
Preferred Customer Enrollment Change Log (EAMFBCHG) . . . . . . . 328
Preferred Customer Messages File (EAMFBMSG) . . . . . . . . . . . 330
Panel Diary File (EAMPANEX). . . . . . . . . . . . . . . . . . . 330
Period Header String . . . . . . . . . . . . . . . . . . . . . 331
Marker for Preferred Customer Transactions . . . . . . . . . . . . 331
Marker for Items to which Preferred Customer Coupons Might Apply. . . . 331
Marker for Coupon Tracking Transactions . . . . . . . . . . . . . 332
Automatic Coupon Transaction Data String . . . . . . . . . . . . . 332
Customer Identification String . . . . . . . . . . . . . . . . . . 332
Preferred Customer Transaction Data String . . . . . . . . . . . . 333
New Tender Verification Account Number String . . . . . . . . . . . 333
Alias Electronic Coupon Item Code String . . . . . . . . . . . . . 333
Coupon Tracking String . . . . . . . . . . . . . . . . . . . . 334
Bonus/Redemption Points String . . . . . . . . . . . . . . . . . 334
Redemption/Adjustment String. . . . . . . . . . . . . . . . . . 335
Period Summary String . . . . . . . . . . . . . . . . . . . . 335
Panel Filter File (EAMFBFLT) . . . . . . . . . . . . . . . . . . . 336
Targeted Coupon Messages File (EAMFBTCM) . . . . . . . . . . . . 340
Item Record File Usage (EAMITEMR) . . . . . . . . . . . . . . . . 341
Linked Coupons . . . . . . . . . . . . . . . . . . . . . . . 341
Allow Coupon Validation by Department with Minimum Purchase by
Transaction . . . . . . . . . . . . . . . . . . . . . . . . 346
Allow Minimum Purchase by Department with No Coupon Validation. . . . 347
Allow Minimum Purchase by Department with Validation by MFR . . . . . 347
Staged Item Movement File (EAMIMOV1) . . . . . . . . . . . . . . 351
Record Format – Store Record . . . . . . . . . . . . . . . . . 351
Record Format – Movement Record . . . . . . . . . . . . . . . 352
Accounting File Usage (EAMACCTC) . . . . . . . . . . . . . . . . 352
Performance File Usage (EAMPERFC) . . . . . . . . . . . . . . . 353
Department Totals File Usage (EAMDEPTC) . . . . . . . . . . . . . 353
Exception Log Usage (EAMEXCPT) . . . . . . . . . . . . . . . . 354
User Log of Data Entry = X'19' (Customer number seen multiple times) 354
Addition to 02 and 03 Log Entries . . . . . . . . . . . . . . . . 354
User Log = X'99' (Transfer activity file processed) . . . . . . . . . . 354
System Error Log Usage . . . . . . . . . . . . . . . . . . . . . 355
Preferred Customer Coupon Tracking File (EAMCOUPC) . . . . . . . . . 356

Contents ix
 Sample Coupon Record . . . . . . . . . . . . . . . . . . . . . 358
Packed Format (only demonstrable in Hex) . . . . . . . . . . . . . . 358
Exception Log Format (only demonstrable in Hex) . . . . . . . . . . . 358

Appendix B. Supermarket Application Base Coupon Processing . . . . 359

Supermarket Application Base Support . . . . . . . . . . . . . . . 359
Format of Industry Coupon Code . . . . . . . . . . . . . . . . . 359
Coupon Validation . . . . . . . . . . . . . . . . . . . . . . 359
Coupons. . . . . . . . . . . . . . . . . . . . . . . . . . 359

Appendix C. Electronic Marketing Code Glossary . . . . . . . . . . 361

Supermarket Modules modified for Electronic Marketing: . . . . . . . . . 361
Electronic Marketing Load Modules:. . . . . . . . . . . . . . . . . 361
Required Data Files: . . . . . . . . . . . . . . . . . . . . . . 362
Terminal Sales and Checkout Support EXIT Code: . . . . . . . . . . . 362
Report EXIT Code: . . . . . . . . . . . . . . . . . . . . . . . 362
Electronic Marketing File Summary: . . . . . . . . . . . . . . . . . 363
Electronic Marketing Application Summary: . . . . . . . . . . . . . . 363
Electronic Marketing Customer File Usage Summary: . . . . . . . . . . 364

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . 367

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369

Readers’ Comments — We’d Like to Hear from You . . . . . . . . . 377

x Electronic Marketing PRPQ

Figures
1. Options File with no boundary processing defined . . . . . . . . . . . . . . . . . . 127
2. Options File with one boundary defined . . . . . . . . . . . . . . . . . . . . . . 128
3. Options File with two boundaries defined. . . . . . . . . . . . . . . . . . . . . . 128
4. Options File with three boundaries defined.. . . . . . . . . . . . . . . . . . . . . 129
5. Options File with four boundaries defined. . . . . . . . . . . . . . . . . . . . . . 129
6. Weight Item Record Without Tare Code . . . . . . . . . . . . . . . . . . . . . . 146
7. Weight Item Record With Tare Code . . . . . . . . . . . . . . . . . . . . . . . 146
8. Preferred Customer Receipt . . . . . . . . . . . . . . . . . . . . . . . . . . 180
9. Regular Customer Receipt . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
10. System Main Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
11. Secondary Applications Menu - Preferred Customer Enrollment . . . . . . . . . . . . . 182
12. Preferred Customer Program Main Menu -- Option 2 -- add record . . . . . . . . . . . . 183
13. Add Customer Record Screen -- the highlighted fields are required. . . . . . . . . . . . 184
14. Alternate Add Customer Record Screen . . . . . . . . . . . . . . . . . . . . . . 185
15. Preferred Customer Program Main Menu -- Option 1 -- change record. . . . . . . . . . . 186
16. Change Customer Record Screen . . . . . . . . . . . . . . . . . . . . . . . . 186
17. Alternate Change Customer Record Screen . . . . . . . . . . . . . . . . . . . . 187
18. Preferred Customer Program Main Menu -- Option 3 -- erase record . . . . . . . . . . . 188
19. Erase Customer Record Screen . . . . . . . . . . . . . . . . . . . . . . . . . 188
20. Alternate Erase Customer Record Screen . . . . . . . . . . . . . . . . . . . . . 189
21. Preferred Customer Program Main Menu -- Option 4 -- display record . . . . . . . . . . . 189
22. Display Customer Record Screen . . . . . . . . . . . . . . . . . . . . . . . . 190
23. Alternate Display Customer Record Screen . . . . . . . . . . . . . . . . . . . . 191
24. Preferred Customer Program Main Menu -- Option 5 -- Redeem Award . . . . . . . . . . 191
25. Redemption of Point Award Screen . . . . . . . . . . . . . . . . . . . . . . . 192
26. Alternate Redemption of Point Award Screen . . . . . . . . . . . . . . . . . . . . 193
27. Preferred Customer Program Main Menu -- Option 6 -- Adjustments . . . . . . . . . . . 193
28. Adjustment of Point Award Screen . . . . . . . . . . . . . . . . . . . . . . . . 194
29. Alternate Adjustment of Point Award Screen . . . . . . . . . . . . . . . . . . . . 195
30. Preferred Customer Program Main Menu -- Option 7 -- Enter Rain check . . . . . . . . . 195
31. Rain check Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
32. Alternate Rain check Screen . . . . . . . . . . . . . . . . . . . . . . . . . . 197
33. Add a Bonus Point Coupon Item Record -- Page 1 . . . . . . . . . . . . . . . . . . 198
34. Add a Bonus Point Coupon Item Record -- Page 2 . . . . . . . . . . . . . . . . . . 199
35. Add a Limit Per Transaction/Items Per Coupon Item Record -- Page 1 . . . . . . . . . . 200
36. Add a Limit Per Transaction/Items Per Coupon Item Record -- Page 2 . . . . . . . . . . 200
37. Add a Final Value (net item value) Coupon Item Record -- Page 1 . . . . . . . . . . . . 201
38. Add a Final Value (net item value) Coupon Item Record -- Page 2 . . . . . . . . . . . . 202
39. Add a Linked Coupon (redeems points) Item Record -- Page 1 . . . . . . . . . . . . . 203
40. Add a Linked Coupon (redeems points) Item Record -- Page 2 . . . . . . . . . . . . . 203
41. Add a Linked Coupon (discount given after points redeemed) Item Record -- Page 1 . . . . . 204
42. Add a Linked Coupon (discount given after points redeemed) Item Record -- Page 2 . . . . . 205
43. Add a Linked Coupon (multiple items plus points) Item Record -- Page 1. . . . . . . . . . 206
44. Add a Linked Coupon (multiple items plus points) Item Record -- Page 2. . . . . . . . . . 206
45. Add a Linked Coupon to provide validation (no bonus points) Item Record -- Page 1 . . . . . 207
46. Add a Linked Coupon to provide validation (no bonus points) Item Record -- Page 2 . . . . . 207
47. Add a Linked Coupon (discount given if each coupon passes validation, no bonus points) Item
Record -- Page 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
48. Add a Linked Coupon (discount given if each coupon passes validation, no bonus points) Item
Record -- Page 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
49. Add a dummy validation Linked Coupon Item Record -- Page 1 . . . . . . . . . . . . . 210
50. Add a dummy validation Linked Coupon Item Record -- Page 2 . . . . . . . . . . . . . 210
51. Add a dummy validation Linked Coupon Item Record -- Page 1 . . . . . . . . . . . . . 211

© Copyright IBM Corp. 1991 2000 xi

52. Add a dummy validation Linked Coupon Item Record -- Page 2 . . . . . . . . . . . . . 211
53. Add a validation Linked Coupon (price method 4) Item Record -- Page 1. . . . . . . . . . 212
54. Add a validation Linked Coupon (price method 4) Item Record -- Page 2. . . . . . . . . . 212
55. Add a Coupon Linked to Department Purchase Item Record -- Page 1 . . . . . . . . . . 213
56. Add a Coupon Linked to Department Purchase Item Record -- Page 2 . . . . . . . . . . 213
57. Add a Coupon Linked to Minimum Department Purchase Item Record -- Page 1 . . . . . . . 214
58. Add a Coupon Linked to Minimum Department Purchase Item Record -- Page 2 . . . . . . . 215
59. Add a dummy Coupon Linked to minimum in two departments Item Record -- Page 1 . . . . . 216
60. Add a dummy Coupon Linked to minimum in two departments Item Record -- Page 2 . . . . . 216
61. Add a Linked Coupon, pricing method 3, point coupons require validation Item Record -- Page 1 217
62. Add a Linked Coupon, pricing method 3, point coupons require validation Item Record -- Page 2 217
63. Add a coupon linked to minimum by manufacturer Item Record -- Page 1 . . . . . . . . . 218
64. Add a coupon linked to minimum by manufacturer Item Record -- Page 2 . . . . . . . . . 219
65. Add a Coupon Linked to items per coupon Item Record -- Page 1 . . . . . . . . . . . . 220
66. Add a Coupon Linked to items per coupon Item Record -- Page 2 . . . . . . . . . . . . 220
67. Add a Coupon Linked to items per coupon Item Record -- Page 1 . . . . . . . . . . . . 221
68. Add a Coupon Linked to items per coupon Item Record -- Page 2 . . . . . . . . . . . . 221
69. Add an Award Points with no performance required Item Record -- Page 1 . . . . . . . . . 222
70. Add an Award Points with no performance required Item Record -- Page 2 . . . . . . . . . 223
71. Add a Promotion Code Discount Coupon Item Record -- Page 1 . . . . . . . . . . . . . 224
72. Add a Promotion Code Discount Coupon Item Record -- Page 2 . . . . . . . . . . . . . 225
73. Add a Percent Off Discount Coupon Item Record -- Page 1 . . . . . . . . . . . . . . 226
74. Add a Percent Off Discount Coupon Item Record -- Page 2 . . . . . . . . . . . . . . 226
75. Report Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
76. User Reports Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
77. Selective Item Record Search . . . . . . . . . . . . . . . . . . . . . . . . . 251
78. Selective Preferred Customer Search . . . . . . . . . . . . . . . . . . . . . . . 258
79. Preferred Customer Audit Log Report . . . . . . . . . . . . . . . . . . . . . . . 262
80. Preferred Customer Exception Log Report . . . . . . . . . . . . . . . . . . . . . 262
81. Multiple Card Use Report . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
82. Preferred Customer Exception Log Report . . . . . . . . . . . . . . . . . . . . . 263
83. Transfer Activity Report – Example . . . . . . . . . . . . . . . . . . . . . . . . 263
84. Options Report screen with invalid options . . . . . . . . . . . . . . . . . . . . . 264
85. Options Report screen one . . . . . . . . . . . . . . . . . . . . . . . . . . 266
86. Options Report screen with prompt for password . . . . . . . . . . . . . . . . . . 266
87. Options Report screen with prompt for option to change . . . . . . . . . . . . . . . . 267
88. Options Report screen with prompt new option value . . . . . . . . . . . . . . . . . 267
89. Options Report screen after an option has been altered . . . . . . . . . . . . . . . . 268

xii Electronic Marketing PRPQ

Tables
1. Preferred Customer Messages File. . . . . . . . . . . . . . . . . . . . . . . . 174
2. Targeted Coupon Data Record . . . . . . . . . . . . . . . . . . . . . . . . . 287
3. Date of Last Sale Input Options and Parameters. . . . . . . . . . . . . . . . . . . 297
4. Reading the Contents of Messages and Options Files. . . . . . . . . . . . . . . . . 319
5. Preferred Customer Enrollment File . . . . . . . . . . . . . . . . . . . . . . . 320
6. Preferred Customer Activity File . . . . . . . . . . . . . . . . . . . . . . . . . 322
7. Customer Previous Activity File Record Format . . . . . . . . . . . . . . . . . . . 324
8. Electronic Marketing Report Descriptors File Record Format . . . . . . . . . . . . . . 325
9. Customer Transfer File . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
10. Customer Activity Transfer File . . . . . . . . . . . . . . . . . . . . . . . . . 326
11. Customer Audit Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
12. Customer Audit Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
13. Preferred Customer Enrollment Change Log . . . . . . . . . . . . . . . . . . . . 328
14. Period Header String . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
15. Automatic Coupon Transaction Data String . . . . . . . . . . . . . . . . . . . . . 332
16. Customer Identification String. . . . . . . . . . . . . . . . . . . . . . . . . . 332
17. Customer Transaction Data String . . . . . . . . . . . . . . . . . . . . . . . . 333
18. New Tender Verification Account Number String . . . . . . . . . . . . . . . . . . . 333
19. Alias Electronic Coupon Item Code String . . . . . . . . . . . . . . . . . . . . . 333
20. Coupon Tracking String . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
21. Bonus Redemption Points String . . . . . . . . . . . . . . . . . . . . . . . . 334
22. Redemption/Adjustment String . . . . . . . . . . . . . . . . . . . . . . . . . 335
23. Period Summary String . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
24. Targeted Coupon Message File Record Format . . . . . . . . . . . . . . . . . . . 341
25. Staged Item Movement File – Store Record . . . . . . . . . . . . . . . . . . . . 351
26. Staged Item Movement File - Movement Record. . . . . . . . . . . . . . . . . . . 352
27. Accounting File Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
28. Performance File Usage. . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
29. Department File Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
30. Exception Log entry = X'19' . . . . . . . . . . . . . . . . . . . . . . . . . . 354
31. Exception Log entry = X'99' . . . . . . . . . . . . . . . . . . . . . . . . . . 354
32. Preferred Customer Session Number Usage . . . . . . . . . . . . . . . . . . . . 355
33. Selective Item Record Report Session Numbers . . . . . . . . . . . . . . . . . . . 356
34. Date of Last Sale and Item Movement Staging Session Numbers . . . . . . . . . . . . 356
35. Coupon Tracking File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357

© Copyright IBM Corp. 1991 2000 xiii

xiv Electronic Marketing PRPQ
Notices
References in this publication to IBM products, programs, or services do not imply
that IBM intends to make these available in all countries in which IBM operates. Any
reference to an IBM product, program, or service is not intended to state or imply
that only IBM’s product, program, or service may be used. Any functionally
equivalent product, program, or service that does not infringe any of IBM’s
intellectual property rights may be used instead of the IBM product, program, or
service. Evaluation and verification of operation in conjunction with other products,
except those expressly designated by IBM, is the user’s responsibility.

IBM may have patents or pending patent applications covering subject matter in this
document. The furnishing of this document does not give you any license to these
patents. You can send license inquiries, in writing, to the IBM Director of Licensing,
IBM Corporation, North Castle Drive, Armonk, NY 10504-1785, USA.

Trademarks
The following terms used in this publication, denoted by an asterisk (*), are
trademarks of the IBM Corporation in the United States and/or other countries:
v IBM

© Copyright IBM Corp. 1991 2000 xv

xvi Electronic Marketing PRPQ
About This Book
This manual provides a guide to those enterprises that install and use the Electronic
Marketing application (PRPQ). It describes the marketing functions provided by this
Preferred Customer Program and the code to enhance the coupon processing
functions provided in the Supermarket Application.

About the Chapters

The manual is divided into three parts and three appendixes.
v Part 1, “Planning, Processing, and Installation”
– Chapter 1. Introduction, gives an overview of the purpose and functions of the
preferred customer package, and describes hardware supported and migration
issues.
– Chapter 2. Concepts, discusses the basic principles of customer enrollment
and identification, customer recognition and rewards, and defines different
customer types.
– Chapter 3. Coupon Processing Enhancements, discusses the coupon
processing enhancements that are provided by the Electronic Marketing
application.
– Chapter 4. Installation and Configuration, explains how to install exit codes
and programs, and how to perform configuration changes.
– Chapter 5. Personalization, explains how to activate terminal and controller
exits and how to personalize terminal sales and report descriptors as well as
screen files.
– Part 2, “Operations, Processing, and Reports”
– Chapter 6. Personalization of Preferred Customer Options and Messages,
contains the coding and descriptions for the Preferred Customer Options and
the Coupon Options provided by the Electronic Marketing application.
– Chapter 7. Operations, tells an operator how and when to enter a preferred
customer identification number during a sales transaction. It also provides
screens and step-by-step instructions for many functions.
– Chapter 8. Electronic Marketing Processing, contains processing information
for support of the home store concept, validation of customer identification
numbers, coupons, and points.
– Chapter 9. Reports, describes the reports that can be produced through
Electronic Marketing. These reports include the Selective Item Record Report,
the Selective Preferred Customer Report, and others.
– Part 3, “Utilities and Programming”
– Chapter 10. Utilities -- Installation and Operational, describes the utilities
which support the Electronic Marketing application.
– Chapter 11. Electronic Marketing Unique User Exits, contains information
describing the Electronic Marketing Terminal and Controller User exits and
their impact on processing.
– Appendix A. Electronic Marketing Database, describes the files and logs
provided to support the functions offered by the Electronic Marketing
application. This appendix includes tables that show the information in each
file.
– Appendix B. Supermarket Application Base Coupon Processing, provides the
format of an industry coupon code and summarizes the characteristics of
coupon validation and coupons in the 4680 base Supermarket Application.
© Copyright IBM Corp. 1991 2000 xvii
 – Appendix C. Electronic Marketing Code Glossary, contains the following:
Supermarket modules modified for Electronic Marketing, Electronic Marketing
load modules, Terminal Sales and Checkout Support EXIT code, Report EXIT
code and Electronic Marketing files (summary, application summary, and file
usage summary).

Related Publications
The following publications provide information about related application software.

IBM 4680 Supermarket Application

IBM 4680 Supermarket Application: Planning and Installation Guide –
GC30-3371
IBM 4680 Supermarket Application: Guide to Operations – SC30-3372
IBM 4680 Supermarket Application: Programming Guide – SC30-3373

IBM 4680 Store System Library

IBM Store System: User’s Guide – SC30-3518

xviii Electronic Marketing PRPQ

Summary of Changes
Technical changes and additions to this edition are noted with vertical bars (|) in the
left margin.

This manual includes information about the following functional enhancements to

the Electronic Marketing application (PRPQ).

Customer Enrollment and Identification

v Magnetic Stripe Reader (MSR) support for the input of customer numbers has
been added.
v A Customer Key has been added for ease of keying customer numbers.
v All customers can be treated as Preferred Customers.
v User defined demographic input has been added to the enrollment procedure.
v Support for moving customer history when assigning a new number to a
customer (for replacement of a lost customer card) has been added.
Customer Recognition and Rewards

Customer Messages:
v The ″Could Have Saved″ amount shown to non-preferred customers has been
improved by taking into account:
– limits on the number of like coupons in an order
– the number of items needed per coupon
– the minimum purchase requirements for coupons
– net value and percent off coupons.
– Period points can be shown on the customer receipt.
– Transaction discounts can be shown on the customer receipt.

Electronic Coupons:
v Equal support for all automatic coupons is now provided by awarding them at
total time when required.
v A minimum purchase is allowed on non-preferred coupons.
v Electronic net value coupons will compute their value based on the value of the
linked from item regardless of coupon validation.
v An option allows paper and automatic coupons to be taken for the same item.
v An option can bypass journal printing of automatic coupon rejections.
v An order with paperless coupons can be voided without receiving a “return
coupons” guidance.
v Item scanning during a replay of automatic coupons is prohibited.
v Keyed preferred coupons (non-void) can be secured with a manager’s override.
v Automatic coupons can be tested in training mode prior to activation.
v First time or rain check coupons will be given immediately after the sale.

Targeted Coupons:
v Up to three lines of free form text describing each targeted coupon can be
printed on the receipt of customers eligible for the promotion.
v Options have been added to bypass the receipt printing of:
– fixed targeted descriptors
– targeted coupon numbers.

© Copyright IBM Corp. 1991 2000 xix

 – Up to 96 coupons can be targeted to each Preferred Customer.
– Equivalent targeted coupon support for Manufacturer/Family,
Department/Family, and promotion code validation is allowed.

Points Accumulation and Redemption:

v Customers can be allowed to redeem only recently earned points (use them or
lose them limits accumulation and liability).
v Customers can receive boundary awards based on points from the current points
period only.
v Customers can receive unique messages and coupons the first time they shop in
a new points period.
v Selected customers can be targeted for various points rates.
v Support has been added for transferring points to referenced accounts.

Other Awards and Recognition:

v Selected customers can be targeted for transaction discounts.
v Selected customers can be targeted for tax exemptions.
v A register can run in an unattended Kiosk mode so customers can scan their
card to see their points and targeted coupons.
v Customers can be allowed to use the Kiosk register to check item prices.
v An option has been added to provide coupon doubling to Preferred Customers
only.
Coupon Processing Enhancements

New Promotions:
v Coupons good for a percentage off on sales of an item or sales from a
manufacturer, department, or transaction are supported.
v Support has been added for validation of coupons by a user promotion code.
v A unique sale is required for each cross-promotional coupon validated by
promotion code.
v A coupon value against all items in a cross-promotional deal is allowed.
v A promotion valid for “each $50.00 purchased” is allowed by requiring a separate
minimum purchase for each like coupon.
v Coupon support in training mode:
– Paper coupons can be counted by scanning them
– The limits on like coupons can be bypassed
– Coupons are not doubled.

New Validations or Limits:

v A minimum purchase by department with no coupon validation is allowed.
v A minimum purchase by department with validation by manufacturer is allowed.
v Validation by department with a minimum purchase is allowed.
v Full validation support for more Barcodes on store coupons is allowed.
v Non-promotable items will be excluded from the minimum purchase for a coupon.

Reduced Limitations:
v Voids and multipriced items are processed correctly for final value coupons.
v Multiple coupons on the same item are allowed with an operator’s override.
v Weighted coupons work correctly for all coupon limits.

xx Electronic Marketing PRPQ

v A weighted coupon can require multiple packages.
v Non-validating, targeted, weight, and net value coupons work correctly with a
minimum purchase amount or as cross promotions.
v Final value coupons can work with multipriced items.
v Coupons can double up to the value of all matching items when multiple items
are required and validation is at family level.
v Pricing method 4 coupons and item voiding work the same for MFR/FAM,
DEPT/FAM, and promotion code validation.
Totals accumulation and reporting

Periodic Points Processing:

v Points can be accumulated by a customer on a periodic basis for better
promotion evaluation.
v A maximum number of unredeemed points can be defined to be carried over
from one points period to the next.
v The point periods can automatically close on the proper dates or be manually
closed through a user procedure.
v Transaction discounts can be automatically assigned to Preferred Customers
based on the points accumulated in the prior points period.

New Totals:
v A sales total (Gross Plus - Gross Minus) will be accumulated in the Customer
activity file.
v The Preferred Customer number can be saved with each coupon in the coupon
tracking file.
v The last transaction number is added to the activity file so a customer can be
credited for the same points twice in the same day.
v The Customer Activity file can be saved at each store close for host retrieval or
for additional backup.

Altered Reports:
v Electronic coupons are accounted for correctly when a Tender Count is
performed from the register.
v Doubled coupons can be optionally excluded from the store coupon totals in the
department totals file.
v Paperless coupons have been removed from the cash drawer position reports.
File maintenance and options support

Selective Item Report Enhancements:

v The linkage of promotional coupons to the promoted items has been simplified.
v The clearing of promotional coupon linkages has been simplified.
v An option has been added to print the reports with 132 characters per line to
show more item data.
v The sum of movement totals for all reported items is shown.
v Batch changes are allowed for any field in the set of reported items.
v ADDMI partial update batches or record replacement batches can be created.
v ADDMI can be started immediately from the Selective Item Report to run
batches.
v The price of a group of items by a percentage can be changed.

Summary of Changes xxi

 v The price of a group of items by a fixed increment/decrement can be changed.
v A range of items can be excluded from any found list of items.
v Search capabilities for the following have been added:
– any non-zero mix and match
– items which do not contain links
– a family independent of vendor
– a mix and match group independent of department.

Selective Customer Report Enhancements:

v You can randomly select a set of customers based on volumes in a period.
v You can add or delete a targeted coupon to/from a set of customers.
v Support for more than 5 targeted coupons (search, display, update) has been
added.
v An option has been added to print the reports with 132 characters per line to
show more item data.
v Options for fast creation of batches have been added.
v You can name the batch file created by the Selective Customer Report.
v An ″undo″ batch can be built when the alter batch is built.
v Erasing of reported customer records is supported.
v Mailing labels can be printed.
v You can graphically report on points activity by period.
v The total outstanding points for any subset of customers is shown.
v The total sales for Preferred Customers is shown.
v You can search on, report, and update new customer data by:
– discount group
– points multiplier
– periodic point totals
– preferred coupon amount
– preferred status level.
v An option has been added to prevent printing before display.

Preferred Customer Options processing:

v You can change of all Electronic Marketing options through the Options Report.
v Electronic Marketing options have been combined into a single file.
v A migration program to format the old options to the new format is provided.
v The Selective Item Report options are included in the Options report.
v A warning is provided in the options report if:
– all needed exits are not active
– the options file contains invalid (tab) characters.

Other Record Maintenance:

v The alteration of the tare field in item record data maintenance is allowed.
v New flag support is provided for validation by department.
v Larger limits are allowed on coupons per order and items per coupon.
v EAMBATCH can add, delete, or replace targeted coupons without being told
where the coupons are in the list of targeted coupons.
v A new user procedure to Maintain Targeted Coupon Messages has been added.
Auxiliary Functions
v An option to deactivate all Electronic Marketing exit processing has been added.

xxii Electronic Marketing PRPQ

v Unique exits for Electronic Marketing can be added with a controlling option.
v Deposit returns can drive a transaction total negative without requiring a
manager’s override.
v Points transfer processing, points reference processing, and BATCH
maintenance processing can automatically start once a day.
v The item descriptor length can be specified so that the end of the item record
descriptor field can be used for user data.
v Coupon only transactions can be restricted to a single register which is selected
for negative transactions.
v An option has been added to allow tare code support in item record data.
v An option has been added to allow the update of the “date of last sale” in the
item record file.
v The cash report can be altered to show whether the operator is reconciled.
Worldwide Support Enhancements
v Support for larger money fields for point ratios, coupon totals, Preferred
Customer totals, and minimum purchase amounts has been added.
v Support for EAN 20 random weight coupons like UPC 2 random weight coupons
has been added.
v National language support has been added to reports and procedures.
v Support for national requirements for selected enrollment fields such as postal
codes, telephone numbers, and national ID numbers has been added.
New Appendix

Appendix C has been added documenting the Supermarket modules modified for
Electronic Marketing, Electronic Marketing load modules, Terminal Sales and
Checkout Support EXIT code, Report EXIT code, Electronic Marketing file
(summary, application summary, and file usage summary).

Summary of Changes xxiii

xxiv Electronic Marketing PRPQ
Part 1. Planning and Installation
Chapter 1. Introduction . . . . . . . . . . . . . . . . . . . . . . 5
Overview and Perspective . . . . . . . . . . . . . . . . . . . . . 5
Hardware Supported . . . . . . . . . . . . . . . . . . . . . . . 6
What this Program Includes . . . . . . . . . . . . . . . . . . . . 6

Chapter 2. Concepts . . . . . . . . . . . . . . . . . . . . . . . 7
Customer Enrollment and Identification . . . . . . . . . . . . . . . . 7
Rain check Customers . . . . . . . . . . . . . . . . . . . . . 8
Customer Identification Number . . . . . . . . . . . . . . . . . . 8
Customer Recognition, Rewards, and Messages . . . . . . . . . . . . . 8
Points. . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Points-Only Items . . . . . . . . . . . . . . . . . . . . . . . 9
Electronic Marketing Coupons . . . . . . . . . . . . . . . . . . 10
Normal Sales Coupons . . . . . . . . . . . . . . . . . . . . 10
Net Value Coupons . . . . . . . . . . . . . . . . . . . . . 10
Points Coupons . . . . . . . . . . . . . . . . . . . . . . 10
Preferred Customer Coupons . . . . . . . . . . . . . . . . . 10
Non-Preferred Customer Coupons . . . . . . . . . . . . . . . . 10
Paper Coupons. . . . . . . . . . . . . . . . . . . . . . . 10
Electronic Coupons . . . . . . . . . . . . . . . . . . . . . 11
Home Store Concept. . . . . . . . . . . . . . . . . . . . . . . 11
Enterprises that Use the Home Store Concept . . . . . . . . . . . . 12
Non-Home Store Concept . . . . . . . . . . . . . . . . . . . . . 13
Enterprises that Use a Non-Home Store Concept . . . . . . . . . . . 13
Activity Record Types . . . . . . . . . . . . . . . . . . . . . . 13
Primary Customer Activity Records . . . . . . . . . . . . . . . . 13
Alias Customer Activity Records for Family Members . . . . . . . . . . 13
Electronic Marketing Database . . . . . . . . . . . . . . . . . . 13
Auxiliary Functions . . . . . . . . . . . . . . . . . . . . . . . 14
Default Auxiliary Functions . . . . . . . . . . . . . . . . . . . 14
Accept Only Foodstamps After a Foodstamp Balance Due . . . . . . . . 15
Display the Weight for Sales of Weight Items . . . . . . . . . . . . . 15
Prohibit Entry of Cash Amounts When the Balance Is Negative . . . . . . 15
Weight Accumulation on Category 2 Sales . . . . . . . . . . . . . . 15
Improved End of Transaction Printing Performance . . . . . . . . . . 15
Printed Subtotals . . . . . . . . . . . . . . . . . . . . . . . 15
Add Operator Name to Cash/Performance Reports . . . . . . . . . . 15
Require an Override for Any Negative Transaction . . . . . . . . . . . 16
Store Coupon Taxability Defined Only by the Item Record and Tax Key . . . 16
Document Print Voids of Miscellaneous Items . . . . . . . . . . . . 16
Exception Logging of Data Entry on Items . . . . . . . . . . . . . . 16
Improved Terminal Monitor from the Controller . . . . . . . . . . . . 16
Document Low Memory Condition . . . . . . . . . . . . . . . . . 16
Print Additional Diagnostic Data for Selected Failures. . . . . . . . . . 16
Prohibit Changing of Department Numbers from a Register . . . . . . . 16
Optional Auxiliary Functions . . . . . . . . . . . . . . . . . . . . 17
Highlighting Negative Entries . . . . . . . . . . . . . . . . . . . 17
Ignore Coupon Families for Validation . . . . . . . . . . . . . . . 17
Panel Capture of Transaction Data . . . . . . . . . . . . . . . . 17
Only Allow One Terminal to Have Negative Transactions . . . . . . . . 17
Define Which Taxes to Turn On with the Tax/NoTax Key. . . . . . . . . 17
Accumulate UPC/Department Key Rather Than Keyed/Scanned Sales . . . 18
Accumulate Keyed Versus Scan Totals by Department . . . . . . . . . 18

© Copyright IBM Corp. 1991 2000 1

 Weight Items Do Not Require Weight Key . . . . . . . . . . . . . . 18
Display Backup Indicator at Registers . . . . . . . . . . . . . . . 18
Allow Tax Exemption Without a Discount Key. . . . . . . . . . . . . 18
Cash Checks Using a Sales Transaction . . . . . . . . . . . . . . 18
Remind Operator to Take the Customer’s Money . . . . . . . . . . . 18
Interpret Restricted Time Periods as Unrestricted Times . . . . . . . . . 18
Support for Multiple Cash Drawers . . . . . . . . . . . . . . . . 18
Time in 12-Hour Format on the Customer Receipt . . . . . . . . . . . 19
Require Immediate Override for Transaction Cancel Limits . . . . . . . . 19
Limit the Length of the Item Descriptor Shown to the Customer . . . . . . 19
Get Tare Code Information from the Item Record for Weight Items . . . . . 19

Chapter 3. Coupon Processing Enhancements . . . . . . . . . . . . 21

Store Coupon Scanning Enhancements . . . . . . . . . . . . . . . . 21
Category 4 UPC Store Coupons . . . . . . . . . . . . . . . . . 21
Category 5 UPC Store Coupons . . . . . . . . . . . . . . . . . 21
Sequence Number and Velocity Code Imbedded in Coupon UPC . . . . 22
Store Coupon Scanning Alternatives . . . . . . . . . . . . . . . 22
Store Coupon Validation Enhancements . . . . . . . . . . . . . . . 23
Validation of Coupon UPCs with Invalid or No Manufacturer Number . . . . 23
Limit of Like Coupons in a Transaction . . . . . . . . . . . . . . . 24
Validation Only by Quantity of Like Coupons . . . . . . . . . . . . . 24
Validate Department Coupons by Department Subtotal Group . . . . . . 24
Force Department Validation on Keyed Coupons . . . . . . . . . . 24
Minimum Purchase Requirement . . . . . . . . . . . . . . . . . 24
Minimum Purchase by Manufacturer or Department . . . . . . . . . . 24
Minimum Purchase by Department without Department Validation . . . . . 25
Require More Than One Item Per Coupon . . . . . . . . . . . . . . 25
Support Cross-Item Promotion Coupons . . . . . . . . . . . . . . 25
Coupon Expiration Based on a Sequence Number . . . . . . . . . . . 25
Operator Guidance Management . . . . . . . . . . . . . . . . 25
Support Bypass of Validation for Certain Coupons . . . . . . . . . . . 26
Promotion Code Validation . . . . . . . . . . . . . . . . . . . 26
Summary of Coupon Validation Enhancements . . . . . . . . . . . . 26
General Enhancements. . . . . . . . . . . . . . . . . . . . . . 27
Support for 7, 8, and 9 Digit UPCs on Store Coupons . . . . . . . . . 27
Coupon Provides Net Item Value Instead of Discount . . . . . . . . . . 27
Support for Training Mode . . . . . . . . . . . . . . . . . . . . 28
Item Record Data for Store Coupons . . . . . . . . . . . . . . . . . 28
Additional Coupon Record Data. . . . . . . . . . . . . . . . . . 28
Coupon Record Maintenance . . . . . . . . . . . . . . . . . . 29
Coupon Restrictions Because of Additional Data . . . . . . . . . . . 29
Coupon Restrictions Because of System Design . . . . . . . . . . . 29
Coupon Multiplication Limits . . . . . . . . . . . . . . . . . . . . 30
Limit on the Number of Coupons Doubled . . . . . . . . . . . . . . 30
Limit on the Value of Doubled Coupons (3 Options) . . . . . . . . . . 30
Minimum Purchase Requirement . . . . . . . . . . . . . . . . . 30
Limit of Coupons to Double Varies with Order Size. . . . . . . . . . . 31
Deactivate Coupon Doubling by Day of Week . . . . . . . . . . . . 31
Do Not Double MFR Coupon if Store Coupon Already Taken for Item . . . . 31
Limit on the Number of Like Coupons to Be Doubled in an Order . . . . . 31
Prohibit Coupon Doubling Through a Key Sequence . . . . . . . . . . 31
Allow Manual Entry of Doubled Coupons . . . . . . . . . . . . . . 32
Allow Coupons to Be Marked for No Doubling . . . . . . . . . . . . 32
Operator Interface Enhancements . . . . . . . . . . . . . . . . . . 32
Allow Operator Override of User-Selected Error Conditions . . . . . . . 32

2 Electronic Marketing PRPQ

 Prompt the Operator to Write Free Coupon Value on the Coupon . . . . . 32
Alter Coupon Guidance if too few Items Are Sold . . . . . . . . . . . 33
Alter Coupon Guidance to Tell if any Matching Items Are Sold . . . . . . 33
Allow Certain Coupon Entries without Matching Item Validation . . . . . . 33
Require a Single Override in a Coupon only Transaction . . . . . . . . 33
Logging of All Coupon Data . . . . . . . . . . . . . . . . . . . . 33
Coupon Tracking Options . . . . . . . . . . . . . . . . . . . . 34
Limit Coupon Tracking to a Range of Coupon UPCs . . . . . . . . . . 34
Coupon Campaign Number Capture . . . . . . . . . . . . . . . . 34
Personalization of Coupon Processing . . . . . . . . . . . . . . . . 35
System Performance Considerations of Coupon Processing . . . . . . . . 35

Chapter 4. Installation and Configuration . . . . . . . . . . . . . . 37

Installation Notes . . . . . . . . . . . . . . . . . . . . . . . . 37
Install Electronic Marketing Exit Code . . . . . . . . . . . . . . . . 38
Copying Electronic Marketing Files to Your System . . . . . . . . . . 38
Alter Terminal Sales and Checkout Support Link List . . . . . . . . . . 38
Medium Memory Model . . . . . . . . . . . . . . . . . . . . 38
Big Memory Model . . . . . . . . . . . . . . . . . . . . . 39
| Enhanced Manufacturer Coupon Reporting Considerations. . . . . . . . 39
Install Terminal and Controller Checkout Exit Code. . . . . . . . . . . 40
Install Report Exit Code . . . . . . . . . . . . . . . . . . . . 42
Re-Link Data Maintenance, Tender Count and Automatic Reconciliation . . . . 43
Install Background Programs . . . . . . . . . . . . . . . . . . . . 44
Install User Reports . . . . . . . . . . . . . . . . . . . . . . . 44
Install Optional User Procedures . . . . . . . . . . . . . . . . . . 45
Install the Optional Date of Last Sale Update Function . . . . . . . . . 45
Optional Source Code Changes . . . . . . . . . . . . . . . . . . 47
Optional Changes to Delayed Data Maintenance . . . . . . . . . . . 47
Optional Changes to Department Analysis Report . . . . . . . . . . . 49
Perform Configuration Changes. . . . . . . . . . . . . . . . . . . 52
Add User Logical Names . . . . . . . . . . . . . . . . . . . . 52
Configure Background Application . . . . . . . . . . . . . . . . . 53
Configure Key Sequences for Auxiliary Functions . . . . . . . . . . . 54
Configure Optional Customer Number Key. . . . . . . . . . . . . . 55
Install the In-Store Enrollment Program . . . . . . . . . . . . . . . . 60
Install the Batch Keyed File Maintenance Program . . . . . . . . . . . . 61
Install Batch Program . . . . . . . . . . . . . . . . . . . . . 61
Configure Logical Names for the Batch Program . . . . . . . . . . . 61
Use Controller Configuration to Define a New Background Program . . . . 62
Add Messages Used by the Batch Program . . . . . . . . . . . . . 62
Executing the Batch Program . . . . . . . . . . . . . . . . . . 62
Install Background Panel Filters as Needed . . . . . . . . . . . . . . 62
Install Electronic Marketing Data Files . . . . . . . . . . . . . . . . 63

Chapter 5. Personalization . . . . . . . . . . . . . . . . . . . . 65
Activate Terminal and Controller Exits . . . . . . . . . . . . . . . . 65
Personalize Terminal Sales Descriptors . . . . . . . . . . . . . . . . 65
Personalize Report Descriptors . . . . . . . . . . . . . . . . . . . 66
Personalize Electronic Marketing Report Descriptors . . . . . . . . . . . 68

Part 1. Planning and Installation 3

4 Electronic Marketing PRPQ
Chapter 1. Introduction
Overview and Perspective
The 4680 Supermarket Electronic Marketing Application (ordered as Programming
Request for Price Quotation (PRPQ) P85218) can identify and selectively reward
customers, as well as collect information on their purchases.

With the Electronic Marketing application, an enterprise can gain knowledge of its
customers shopping habits. This knowledge can then be used as the basis for
direct marketing programs designed to promote customer loyalty and improve store
volumes and profits.

With the Electronic Marketing application, you can enroll a store’s customers and
provide them with a unique customer identification number. You should also provide
enrolled customers with cards that contain their customer identification numbers.
This card is the only identification that a preferred customer needs to present.
These same customer ID numbers can also be used for check verification. A
preferred customer presenting this card at checkout time can receive:
v Recognition
v Awards
v Discounts.

A store can use the demographic data obtained during customer enrollment and the
captured sales information to build the customer knowledge base necessary for
targeted marketing programs. The Electronic Marketing application includes the
functions needed to support consumer:
v Identification
v Rewards
v Marketing.

A store can select through personalization options what information to maintain,

including:
v Demographic data
v Customer privileges
v Future rewards
v Redeemed rewards
v Points earned.

The Electronic Marketing application can minimize the need for customer mailings.
You may still need to use mailings for some advertising and promotions targeted at
specific customer profiles however, with the Electronic Marketing application you
can use messages printed on the cash register’s receipt tape, (including notices of
discounts and reward totals,) as the main means of communication with preferred
customers.

Processing at the central site can be minimized by making extensive use of a home
store concept. The store where a customer enrolls becomes their home store. The
home store number can be included as part of the customer identification number if
desired.

© Copyright IBM Corp. 1991 2000 5

 A preferred customer’s shopping activities are tracked when they shop in any store
in a chain of associated stores, however some rewards and recognition can only be
given at a customer’s home store. Only the home store maintains a complete
history of a customer’s activity. The benefits of the home store alone maintaining full
customer activity data are:
v Only the information pertaining to each store’s own preferred customers needs to
be maintained at each store.
v The central site support needed for transferring preferred customer transaction
information from other stores to their home stores is reduced.

Hardware Supported
The Electronic Marketing application executes in the IBM Point of Sale Terminal and
in the store controller. Customer ID numbers can be scanned, keyed or swiped
(entered using a magnetic stripe reader).

The Electronic Marketing application installed on Version 1 of the Supermarket base

can run in a 1 megabyte 4683 Terminal however, a 2 megabyte terminal is
recommended to support a Model 1 / Model 2 pairing, and when there is extensive
customer user exit code or other Supermarket features installed.

What this Program Includes

The Electronic Marketing application provides functions to track purchases for a set
of preferred customers by using the customer identification number. It enables a
store to give discounts on items (electronic coupons) and volume-related bonuses
(points such as electronic trading stamps) to participating customers encouraging
them to identify themselves at each visit.

The Electronic Marketing application allows a store to save full transaction

information for all preferred customers. The customers benefit by receiving
recognition and discounts. The stores benefit through enhanced customer loyalty
and a better understanding of their customers to use in direct marketing.

The Electronic Marketing application provides the following additions to the coupon
processing functions provided in the Supermarket Application:
v More control over coupon doubling
v Scanning and validation of store coupons
v Limits to control store coupon redemption
v An improved operator interface to coupon processing
v Full tracking of all redeemed coupons.
v Validation by promotion codes.
The purpose of these enhancements are:
v To extend the manufacturer’s coupon processing functions to store coupons
v To improve a store’s flexibility and control over this processing
v To provide the detailed coupon tracking necessary for electronic redemption.

The Selective Item Record Report enhances coupon processing by reporting on all
store coupons active in the store. Reporting capabilities are not limited to coupon
item records but extend to generalized searches of the Item Record File based on
numerous input parameters. Department number, item code range, and the date of
last sale are included.

6 Electronic Marketing PRPQ

Chapter 2. Concepts
This chapter defines basic concepts of the Electronic Marketing application
including:
v Customer enrollment and identification
v Customer rewards and recognition (messages, coupons, and points)
v The home store and multiple store concepts
v Activity record types.

This chapter also explains auxiliary functions provided by the Electronic Marketing
application.

Customer Enrollment and Identification

By using the customer enrollment procedure provided by the Electronic Marketing
application, an enterprise assigns identification numbers to customers who
participate in the preferred customer program. A customer identification number is
the only identification a customer needs to be considered enrolled.

An enterprise should provide customer cards that contain the customer identification
number to customers who enroll in the preferred customer program.

Once a customer is enrolled, an enterprise can electronically capture information

describing each customer such as name, address and zip code. The information a
customer provides during preferred customer enrollment is contained in the
Preferred Customer Enrollment File. For additional information see “Preferred
Customer Enrollment File (EAMFBCUS)” on page 320.

Preferred customers who shop before their customer enrollment information is

entered into the system can still receive the benefits of the program. This flexibility
is provided by the on-line enrollment of the customer ID number the first time they
present their card.

An enterprise can decide where to have customer enrollment information collected

(in the store or at a different location) and how to have this information collected
(using the Electronic Marketing application or another program).

Enrollment information entered outside the store can be sent to a store and
maintained there, but it must be in the format defined for the Preferred Customer
Enrollment File.

There is no requirement to maintain customer names or enrollment information in a

store’s database. At a minimum however, you might want to maintain the
customer’s name in the activity file so the terminal can display or print the
customer’s name during checkout transactions.

To analyze customer sales data the enrollment information must reside where
processing is performed.

The enrollment process is controlled by either an in-store controller or a central site

host. The Electronic Marketing application provides an in-store enrollment
procedure that runs on the store controller. The additional software required for a
central site host to maintain this enrollment process is not supplied by the Electronic
Marketing application.

© Copyright IBM Corp. 1991 2000 7

 An enterprise can decide through personalization options which in-store enrollment
functions are active. Personalization options also enable an enterprise to run the
in-store enrollment procedure without an in-store enrollment file so that activity and
audit data can be updated even when enrollment data is not present in the store.
For additional information see “Run the Enrollment Procedure Without an
Enrollment File” on page 107.

The in-store enrollment procedure provided by the Electronic Marketing application

performs the following functions:
v Provides the ability to add, change, display, or delete a customer enrollment
record.
v Updates the Preferred Customer Activity File with a customer name.
The Preferred Customer Activity File accumulates purchase activity information in
a record for each customer.
v Provides the ability to perform adjustments and redemptions of customer
transaction points.
Like electronic trading stamps, points are the electronically accumulated totals
which reflect a customer’s history of purchase activity which can be redeemed for
other rewards.
v Displays customer activity data with enrollment data when a customer record is
displayed.
v Provides the ability to add rain check customer points to their cumulative point
total.

Rain check Customers

Rain check customers are customers who use a predefined store rain check ID
when they do not have their preferred customer ID card. By using a rain check ID
when their preferred customer ID is not available, a customer is still able to receive
some benefits and accumulate points for a transaction. When a store provides a
rain check ID to a customer, the receipt shows the transaction points. The receipt
can be used later as the basis for an adjustment. The rain check descriptor on the
receipt indicates to the manager :
v Points were accumulated by a customer identified as a preferred customer at the
point of sale.
v Points have not been credited.

Customer Identification Number

A customer identification number assigned during enrollment consists of up to 18
digits of any combination of numeric characters. An enterprise can designate
validation digits within customer numbers to provide a means of verifying whether or
not a customer number can be used in a particular store or chain. See “Validation
Digits in Customer Number” on page 101.

Customer Recognition, Rewards, and Messages

With the knowledge gained through recording customer enrollment information and
purchase activity, an enterprise can reward preferred customers for buying both
specific merchandise and categories of merchandise. An enterprise can reward
customers for purchases made during a single shopping trip or over a period of
time. The Electronic Marketing application also enables an enterprise to give
benefits, including customer messages, points, and coupons for product discounts.

8 Electronic Marketing PRPQ

 The Electronic Marketing application provides the ability to create and track
promotions targeted at specific customers, and to give customers product discounts
(or rewards) for buying specified promotional items.

A store notifies a customer of their reward (coupons or points) by printing messages

on the cash receipt and/or displaying messages at the terminal during a checkout
transaction. An enterprise can use these messages to communicate with customers
on virtually any topic.

The system maintains rewards earned by customers in the Preferred Customer

Activity File. A store has the option to allow customers to accumulate points (based
on purchase history) and to redeem these points during a sales transaction.

Points
The Electronic Marketing application provides transaction points accumulation as a
method to reward customers for continual patronage of the same store or chain. As
preferred customers shop in a store or stores in a chain, the Electronic Marketing
application accumulates a history of their purchase activity as points. Customers
may redeem points for tangible rewards at a later time.

Conceptually, points are like electronic trading stamps. The system keeps the
running total which is communicated to a customer in the form of customer
messages. Customer messages can show points for an individual transaction, total
cumulative points, and points transferred in from a transaction at another store.
Customer messages can also be designed to either show or not show points for an
individual transaction.

Points are related to the tender value of items purchased by a customer but may
differ from the tender value because they are affected by factors such as taxes,
coupons, point ratios and bonus points.

Points-Only Items
Items in the Item Record File can be designated as points-only items when the
value in the price field represents a preferred customer point value, not a monetary
value. The “sale” of a points-only item increments or decrements a preferred
customer’s total for the transaction.

A primary usage of points-only items is to provide bonus points. Bonus points can
be awarded under any of the following conditions:
v The purchase of selected items
v The purchase of selected items by selected customers
v The tendering of special coupons or points vouchers.

A points-only item provides bonus points without requiring validation as a bonus

points coupon would. A bonus points coupon provides bonus points like a
points-only item, but must be associated with a purchased item for coupon
validation purposes.

Another usage of points-only items is to give redemption coupons. When a

points-only coupon is selected to be a redemption coupon, it reduces a preferred
customer’s point total by redeeming points.

Chapter 2. Concepts 9
Electronic Marketing Coupons
The Electronic Marketing application supports several different types of coupons.
Coupons are defined in the Item Record File as:
v Normal sales coupons
v Net value coupons
v Points coupons
– Bonus points coupons
– Redemption coupons.

Coupons can be further defined and used as:

v Preferred customer coupons
v Non-preferred customer coupons
v Paper coupons
v Electronic coupons
– Targeted coupons.

Normal Sales Coupons

The price of a Normal Sales Coupon reflects the value to be subtracted from the
transaction balance due. Normal Sales coupons apply to all customers.

Net Value Coupons

The value of a net value coupon represents the final price of the discounted item
rather than the discount amount. Pricing method 4 is used to designate these net
value coupons. For more information on net value coupons, see “Coupon Provides
Net Item Value Instead of Discount” on page 27.

Points Coupons
The price of a points coupon represents the number of points to be given to or
taken away from a customer.

Bonus Point Coupons: Bonus point coupons are a subset of points coupons.
Bonus point coupons add to a preferred customer’s points total.

Redemption Coupons: Redemption coupons are also a subset of points

coupons. Usually a points coupon adds to a customer’s point total. But a
redemption coupon (also called redemption points coupon) subtracts from a
customer’s point total by redeeming points. A redemption coupon allows a preferred
customer to exchange points for something of value, such as a special discount.

Preferred Customer Coupons

The Electronic Marketing application enables you to specify coupons to be awarded
to preferred customers only. An option selects a range of UPCs for these preferred
customer coupons. The default is 300 to 399.

Non-Preferred Customer Coupons

Coupons with UPCs outside of the range defined for preferred customers are given
to all customers, including preferred and non-preferred customers.

Paper Coupons
Paper coupons are manufacturer coupons (which are considered as tender) or store
coupons (which are considered as a discount) printed on paper that a customer can
redeem for a discount on a product. They may be given to all customers or
designated for preferred customers only.

10 Electronic Marketing PRPQ

 Electronic Coupons
Electronic coupons (for preferred or non-preferred customers) have no paper
counterpart for a customer to present at the point of sale. When a customer buys a
promoted item, an electronic coupon with its discount is automatically given.
Electronic coupons serve as a primary means of providing special discounts to
customers for purchasing designated promotional items. In order for electronic
coupons to be awarded automatically to preferred customers when they purchase
designated promotional items, an item record must be created for the coupon in the
Item Record File. (See “Item Record File Usage (EAMITEMR)” on page 341.) This
item record is linked to the promoted item and is defined as either a store or
manufacturer coupon, depending on the source of the promotional funds and the
taxability of the coupon.

Items to which an electronic coupon might apply can be marked on a customer

receipt and in the transaction log and panel diary data. This enables preferred
customers to identify the exact products on which they saved money, and enables
non-preferred customers to identify the exact products on which they would have
saved.

Electronic coupons are usually the same thing as preferred customer coupons, but
this is not always the case. For exceptions, see “Electronic Coupons and Preferred
Customer Coupons” on page 231.

Electronic coupons are treated similarly to paper coupons. For differences, see
“Electronic Coupons and Paper Coupons” on page 231.

Targeted Coupons: Targeted coupons are preferred customer coupons that are
targeted to selected preferred customers. A normal preferred customer coupon is
linked to an item and applies to all preferred customers. A targeted coupon is linked
to selected preferred customers through the placement of its coupon item code in
their customer activity records. They might require purchases from a particular
category, department, manufacturer, or of a particular item to pass coupon
validation.

The intent of targeted coupons is to allow promotions to be targeted to a selected

subset of preferred customers. For example, a store may offer incentives for
customers who are not buying from a particular department by giving them $1.00 off
on the first $5.00 purchase from the department. A manufacturer may target a
promotion to customers who fit a particular profile. For example, a manufacturer
may offer to customers who do not usually buy Flavor products $1.00 off on the first
$5.00 purchase of Flavor products.

Coupons can be targeted to preferred customers at their first use of their customer
identification card. See “Coupons Targeted for the First Use of a Customer Card” on
page 81.

Home Store Concept

An enterprise using the preferred customer package may operate according to a
home store concept. This concept designates a home store for each preferred
customer. A home store is the store where a customer enrolls, usually shops,
receives recognition, and gains and redeems points. The home store concept
facilitates the tracking and combining of customers’ points activity and the targeting
of coupons when customers shop at multiple stores.

Chapter 2. Concepts 11
Enterprises that Use the Home Store Concept
Enterprises that use the home store concept distinguish between different types of
participating customers. They designate the following five customer types:

Rain check Customers are customers who use a predefined store rain check ID
when they do not have their preferred customer ID card. A rain check ID enables a
customer to receive some benefits and accumulate points for a transaction.

Primary Home Store Customers are customers shopping in the store in which
they enrolled.

Local Home Store Customers are customers shopping in a store that is in their
local area but is not the store in which they enrolled.

Visiting Preferred Customers are members of the preferred customer program

shopping in a store that is not within their local area and is not the one in which
they enrolled.

Non-participating customers are customers who are not enrolled in the preferred
customer program.

The following diagram presents a conceptual view of primary home store, local
home store, visiting preferred customers, and non-participating customers:

┌────────────────────────────────────────────────────────────┐
│ Non-participants │
│ │
│ ┌──────────────────────────────────────────────────┐ │
│ │ │ │
│ │ Visiting Preferred Customers │ │
│ │ │ │
│ │ ┌────────────────────────────────────────┐ │ │
│ │ │ │ │ │
│ │ │ Local Home Store Customers │ │ │
│ │ │ │ │ │
│ │ │ ┌────────────────────────────────┐ │ │ │
│ │ │ │ │ │ │ │
│ │ │ │ Primary Home Store Customers │ │ │ │
│ │ │ │ │ │ │ │
│ │ │ │ - Customers from this store │ │ │ │
│ │ │ │ │ │ │ │
│ │ │ └────────────────────────────────┘ │ │ │
│ │ │ │ │ │
│ │ │ - Customers not from this store, but │ │ │
│ │ │ from a store in the local area. │ │ │
│ │ │ │ │ │
│ │ └────────────────────────────────────────┘ │ │
│ │ │ │
│ │ - Members of the preferred customer program who │ │
│ │ are not from this store and not from a store │ │
│ │ within the local area. │ │
│ │ │ │
│ └──────────────────────────────────────────────────┘ │
│ │
│ - Store customers not participating in the preferred │
│ customer program. │
│ │
└────────────────────────────────────────────────────────────┘

12 Electronic Marketing PRPQ

Non-Home Store Concept
An enterprise may choose not to operate with a home store concept. If an
enterprise does not define a store number field in the customer number, all
customers are considered home customers and receive points and recognition in all
of the chain’s stores where they shop. No points are transferred out of store. Each
store maintains an activity history for each of it’s customers who shop in that store
and has no knowledge of it’s customers’ activity in other stores. Each store appears
to operate its own preferred customer program.

Enterprises that Use a Non-Home Store Concept

Enterprises that use the non-home store concept designate the following three
customer types:

Rain check customers are customers who use a predefined store rain check ID
when they do not have their preferred customer ID card. A rain check ID enables a
customer to receive some benefits and accumulate points for a transaction.

Participating customers are those customers who are enrolled in the preferred
customer program.

Non-participating customers are those customers who are not enrolled in the
preferred customer program.

Activity Record Types

At each point of sale, when a preferred customer presents an identification card, the
Terminal Sales program searches the store’s activity file to determine whether it
contains the customer’s activity record. If a customer’s activity record is in the file, it
is one of two types, primary or alias.

Primary Customer Activity Records

A primary customer activity record contains accumulated point information and
instructions for processing a customer’s transactions.

Alias Customer Activity Records for Family Members

An alias customer activity record contains an indication marking it as an alias
record. This type of record points to a primary activity record that contains
accumulated point information and processing instructions for customers and their
family members. Alias records allow multiple customer IDs to access the same
primary activity record and contribute to and redeem from the same points total.
They also enable the system to recognize each contributor individually. For more
information, see “Alias/Primary Record Pair Processing” on page 230.

Electronic Marketing Database

In addition to the Preferred Customer Enrollment File, the Preferred Customer
Activity File, and the Item Record File previously referred to in this chapter, the
Electronic Marketing Database includes files for the following functions:
v Logging changes to the Preferred Customer Enrollment File. For more
information see “Preferred Customer Enrollment Change Log (EAMFBCHG)” on
page 328.

Chapter 2. Concepts 13
 v Transferring Preferred Customer Activity Files. For more information see
“Preferred Customer Transfer File (EAMFBXFR)” on page 325 and “Preferred
Customer Activity Transfer File (EAMXssss)” on page 326.
v Logging points redemption and points adjustment events for security auditing
purposes. For more information see “Preferred Customer Audit Log
(EAMFBAUD)” on page 327.
v Logging all of the transaction summary log information for selected preferred
customers. For more information see “Panel Diary File (EAMPANEX)” on
page 330.
v Streamlining the transaction summary log information in the Panel Diary File. For
more information see “Panel Filter File (EAMFBFLT)” on page 336.
v Accumulating accounting, performance, and department totals. For more
information see “Accounting File Usage (EAMACCTC)” on page 352,
“Performance File Usage (EAMPERFC)” on page 353, and “Department Totals
File Usage (EAMDEPTC)” on page 353.
v Logging all exceptional transactions. For more information see “Exception Log
Usage (EAMEXCPT)” on page 354.
v Logging system errors. For more information see “System Error Log Usage” on
page 355.
v Tracking coupons. For more information see “Preferred Customer Coupon
Tracking File (EAMCOUPC)” on page 356.
v Previous activity file. For more information see “Preferred Customer Previous
Activity File (EAMFBAPP)” on page 324.
v Targeted coupon messages. For more information see “Targeted Coupon
Messages File (EAMFBTCM)” on page 340.

Auxiliary Functions
The following functions are included in the Electronic Marketing application either to
enhance processing or to simplify the incorporation of these auxiliary functions with
the preferred customer functions. Most of these auxiliary functions exist as user exit
functions. Many of them have been previously documented in Appendix H.
Examples of User Exits in the IBM 4680 Supermarket Application: Programming
Guide They are included in the Electronic Marketing application as defaults or as
optional functions so you no longer need them as separate user exits.

Default Auxiliary Functions

The following default auxiliary functions are included as defaults in the Electronic
Marketing application:
v Accept Only Foodstamps After a Foodstamp Balance Due
v Display the Weight for Sales of Weight Items
v Prohibit Entry of Cash Amounts when the Balance is Negative
v Weight Accumulation on Category 2 Sales
v Improved End of Transaction Printing Performance
v Printed Subtotals
v Add Operator Name to Cash/Performance Reports
v Require an Override for Any Negative Transaction
v Store Coupon Taxability Defined Only by the Item Record and Tax key
v Document Print Voids of Miscellaneous Items
v Exception Logging of Data Entry on Items

14 Electronic Marketing PRPQ

 v Improved Terminal Monitor from the Controller
v Document Low Memory Condition
v Print Additional Diagnostic Data for Selected Failures
v Prohibit Changing of Department Numbers From a Register.

Accept Only Foodstamps After a Foodstamp Balance Due

Results in a “TAKE TOTAL” operator guidance and rejects the tender entry if a
tender other than food-stamps is entered following a foodstamp balance due. Thus
a normal balance due is required between a foodstamp balance due and a
non-foodstamp tender.

Display the Weight for Sales of Weight Items

Causes the entered (scale or keyed) weight to be displayed with the sale of any
item for which a weight is entered.

Prohibit Entry of Cash Amounts When the Balance Is Negative

Rejects the entry of a non-zero cash amount as tender for a sales transaction when
the balance is negative.

Weight Accumulation on Category 2 Sales

Causes weight to be accumulated in the item movement for all category 2 item
codes which contain a unit price. The weight is computed by dividing the price per
pound into the package price. The same processing is performed for non-category
two items if a price is entered rather than a weight.

This function allows coupons which reduce the price per pound on promotional
weight items to be used to discount all packages or just the largest package of an
item that is sold using a random weight (category 2) UPC.

Improved End of Transaction Printing Performance

Completes the customer receipt sooner because:
v All receipt printing at the end of a transaction is completed before any journal
printing
v Printing of the transaction header is delayed until the start of the next transaction
v The total line is printed when the total is taken rather than when the tender is
entered.

This function is required to offset the additional preferred customer printing.

Printed Subtotals
As a result of the improved End of Transaction printing performance, a total line is
printed each time the total key is pressed and the total has changed since the last
printing. All subtotals are printed and displayed. The subtotals would only be
displayed in the base Supermarket system.

Add Operator Name to Cash/Performance Reports

The operator name is printed or displayed next to the operator number on all
Operator, and Operator Performance reports and the words “Reconciled” or “Not
Reconciled” ,( whichever is appropriate) is printed or displayed after the operator
name.

Chapter 2. Concepts 15
Require an Override for Any Negative Transaction
This function causes a manager’s override to be needed at tender time for any
credit transaction. Any transaction which ends by giving the customer money is a
credit transaction. Transactions which would not be negative if deposit returns were
excluded will not require an override. It is suggested that a limit be placed on the
amount of deposit returns allowed in a transaction through the negative entry limits
in the terminal options. Since this function is the only Preferred Customer code that
uses terminal exit 40, you can turn off this function by turning off the terminal option
which activates terminal exit 40, provided there is no user written code that uses
this terminal exit.

Store Coupon Taxability Defined Only by the Item Record and Tax Key
This user exit code causes the taxability of a store coupon to be determined only
from the tax flags in the item record for the coupon and by the usage of the Tax/No
Tax key. The base code would also look at the taxability of items which were
validated against the coupon. This function assumes that the user can better control
the taxability of store coupons than can the system. Note that the tax for a
transaction will not be allowed to go negative because of a coupon except in a
coupon only transaction.

Document Print Voids of Miscellaneous Items

This code will force all voids of miscellaneous sales to be printed on the document
insert station if voids of normal sales are being document printed.

Exception Logging of Data Entry on Items

This code causes all items entered with data to be exception logged with the
entered data. If the item is printed on the journal, then the entered data is also
printed on the journal.

Improved Terminal Monitor from the Controller

In order to clean up the controller monitor function, item sale display lines are not
monitored at the manager’s terminal. Note that this display data is redundant since
all of the same information is printed. The alteration is limited to controller
monitoring since the displays are valid when monitoring from a terminal.

Document Low Memory Condition

This function causes a low memory condition to result in journal printing at the time
of a special sign-off.

Print Additional Diagnostic Data for Selected Failures

This function causes extra diagnostic lines to be printed for severe code failures
which occur in terminal or controller checkout.

Prohibit Changing of Department Numbers from a Register

The terminal price change procedure is prevented from changing a department
number in an item record in order to save terminal data space.

16 Electronic Marketing PRPQ

Optional Auxiliary Functions
The following optional auxiliary functions are included in the Electronic Marketing
application as options:
v Highlighting Negative Entries
v Ignore Coupon Families for Validation
v Panel Capture of Transaction Data
v Only Allow One Terminal to Have Negative Transactions
v Define Which Taxes to Turn On with the Tax/NoTax Key
v Accumulate UPC/Department Key Rather Than Keyed/Scanned Sales
v Accumulate Keyed Versus Scan Totals by Department
v Weight Items Do Not Require Weight Key
v Display Backup Indicator at Registers
v Allow Tax Exemption Without a Discount Key
v Cash Checks Using a Sales Transaction
v Remind Operator to Take the Customer’s Money
v Interpret Restricted Time Periods as Unrestricted Times
v Support for Multiple Cash Drawers
v Time in 12-Hour Format on the Customer Receipt
v Require Immediate Override for Transaction Cancel Limits
v Limit the Length of the Item Descriptor Shown to the Customer
v Get Tare Code Information from the Item Record for Weight Items.

Highlighting Negative Entries

This function causes all negative entries in a sales transaction to be overprinted
and thus to be highlighted.

Ignore Coupon Families for Validation

This function causes every item to look like it has a family code of 000 and thus
gets rid of coupon validation by coupon family for these coupons. With this code
implemented, all scanned category 5 coupon are validated by manufacturer without
regard for coupon family.

Panel Capture of Transaction Data

Complete transaction data is accumulated for all preferred customers if this option
is selected. This data is in the same format as the panel data already being
processed by A.C. Nielsen and I.R.I.

Only Allow One Terminal to Have Negative Transactions

This function prevents all but a single designated terminal from returning money to
a customer due to a negative transaction. This means that all refunds, payouts, and
coupons outside of orders must be handled at the designated register.

Define Which Taxes to Turn On with the Tax/NoTax Key

This function defines which tax flags to turn on when the Tax/NoTax key is used
with a department or lookup key that has no taxes defined in the item record.

Chapter 2. Concepts 17
Accumulate UPC/Department Key Rather Than Keyed/Scanned Sales
The base system accumulates keyed versus scanned totals where a keyed UPC is
considered a keyed sale. This function makes a keyed UPC look like a scanned
sale and changes the keyed verses scanned ratios to UPC sales verses department
key sales. These ratios are shown in accounting and performance reports.

Accumulate Keyed Versus Scan Totals by Department

This function accumulates the number of keyed and scanned items by department
in the user exit field of the department totals. This allows the department analysis
report to be altered to present keyed versus scanned sales by department. Sample
code to include these new totals in this report is presented in the install section of
this document.

Weight Items Do Not Require Weight Key

This function allows weight items to be sold with a scale weight without the weight
key being pressed. Note that the weight key must still be pressed with a price
override on a weight item if the keyed price is the price per pound. If a price is
keyed on a weight item and the weight key is not pressed, then the price is taken
as the total item price and no weight is read from the scale.

Display Backup Indicator at Registers

displayed at all registers which are being serviced by a backup controller. The
indication is not displayed constantly, but only when it does not interfere with the
display contents.

Allow Tax Exemption Without a Discount Key

This user exit change causes a key sequence of VOID,TAX/NOTAX,TOTAL to be
processed as though the sequence TAX/NOTAX,DISCOUNT had been keyed. In
order for this key sequence to lead to a tax exemption, discount group 2 must be
defined as a tax exemption in the terminal options.

Cash Checks Using a Sales Transaction

This function allows a check or miscellaneous tender to be accepted in a checkout
transaction without requiring prior sales. This has the effect of providing an alternate
tender cashing function which does not require a signon or authorization and looks
just like a tender in a checkout transaction.

Remind Operator to Take the Customer’s Money

This function sounds a unique tone following a period of inactivity in an order after
an item sale or a balance due request. The purpose of this warning is to remind the
cashier to take the customer’s money.

Interpret Restricted Time Periods as Unrestricted Times

This function converts the restricted sales times from the terminal options into
unrestricted time periods. This allows a user to define a continuous restricted time
period that crosses the day boundary.

Support for Multiple Cash Drawers

This function provides for support of two cash drawers so that a terminal which has
two cash drawers attached and configured will be able to use both drawers. This

18 Electronic Marketing PRPQ

 allows an operator to reserve a cash drawer while taking a break so that the till
need not be moved to allow the register to be used.

Time in 12-Hour Format on the Customer Receipt

This function alters the time format in the store data line on the customer receipt to
be in 12-hour format (AM/PM) rather than military format. The three additional print
positions that are needed come from the operator ID field which is reduced to a
maximum of seven digits.

Require Immediate Override for Transaction Cancel Limits

The transaction cancel limit is normally checked at tender time to see if the sum of
all cancels exceeds the limit. This function causes the transaction cancel limit check
to be made prior to accepting any single cancel and thus requires an immediate
manager’s override prior to any cancel which would cause the limit to be exceeded.

Limit the Length of the Item Descriptor Shown to the Customer

This function limits the amount of the item record descriptor that is shown to the
customer so that the excess portion of this field can be used to hold user defined
data.

Get Tare Code Information from the Item Record for Weight Items
This function allows the tare code, tare weight, or tare percentage to be processed
from item record data entered in the high half of the price field for any weight item.

Chapter 2. Concepts 19
20 Electronic Marketing PRPQ
Chapter 3. Coupon Processing Enhancements
PRPQ 5799-DCB (Coupon Processing Enhancements with Selective Item Record
Report) provided four separately installable enhancement packages for the
Supermarket Application. All four of these packages are included in the Electronic
Marketing Store Support PRPQ.

The coupon processing enhancements extend the coupon processing available in

the Supermarket Application.

The coupon processing enhancements are divided into the following categories:
v Store Coupon Scanning Enhancements
v Store Coupon Validation Enhancements
v General Enhancements
v Item Record Data for Store Coupons
v Coupon Multiplication Limits
v Operator Interface Enhancements
v Logging of All Coupon Data
v Personalization of Coupon Processing
v System Performance Considerations of Coupon Processing.

Store Coupon Scanning Enhancements

The following enhancements are intended to allow store coupons to be encoded
with UPCs and scanned at the point of sale with full validation and a minimal impact
on the data base.

Category 4 UPC Store Coupons

In the base application, any UPC that contains a manufacturer number and causes
a lookup of an item record defined as a store or manufacturer coupon requires full
manufacturer and family code validation. The coupon family code is taken from the
item record in this case. A store coupon can be represented by a category 4 UPC
that contains the manufacturer number of the product against which the store
coupon is to be redeemed. In this case, the category 4 UPC must have a matching
item record that is defined as a coupon and contains the proper family code. If the
item record for such a UPC is not on file, an alternative guidance with a default
descriptor of “COUPON HAS EXPIRED” is given instead of the standard “ITEM
NOT FOUND” guidance.

Category 5 UPC Store Coupons

This function allows store coupons to be encoded and scanned as category 5
UPCs. Usage of this function requires that manufacturer numbers be maintained in
the item record file for validation purposes. In the Supermarket Application, any
category 5 UPC is considered to be a manufacturer coupon and is processed
according to UPC guideline 22. This function provides for the definition of a specific
manufacturer’s number that causes special processing when identified in a category
5 UPC. (See “Manufacturer Number to Identify UPC 5 Store Coupons” on
page 154.) A lookup is attempted against the UPC or against the velocity code if
one is imbedded in the UPC (see “Sequence Number and Velocity Code Imbedded
in Coupon UPC” on page 22). If the record is found, the system processes the item
record instead of the normal category 5 UPC processing. If the item is defined as a
coupon, this item record processing may include full coupon validation, but it is
against a manufacturer’s number from the item record rather than the number in the
UPC. All additional item record processing, including item movement and coupon
© Copyright IBM Corp. 1991 2000 21
 validation processing (see “Store Coupon Validation Enhancements” on page 23),
applies. But, none of the normal category 5 processing, such as taking the family
code and price from the UPC, applies. If the item record for such a UPC is not on
file, an alternative guidance with a default descriptor of “COUPON HAS EXPIRED”
is given instead of the standard “ITEM NOT FOUND” guidance. This option is active
only if a five digit non-zero manufacturer’s number to key in is specified in the
coupon options. Use of this option requires manufacturer’s numbers be maintained
in the item record file for validation.

A coupon record with the key 400000XXXXX must be placed in the Item Record
File for a coupon if all the following conditions apply:
v A category 5 UPC of the form 5MMMMMXXXXX is found
v MMMMM matches the target manufacturer number defined in the Coupon
Options (see “Manufacturer Number to Identify UPC 5 Store Coupons” on
page 154)
v The option for an imbedded velocity code (see “Sequence Number and Velocity
Code Imbedded in Coupon UPC”) is not chosen.
The key 400000XXXXX is the item code assigned to the UPC 5MMMMMXXXXX.
This item code translation is performed to bypass normal category 5 processing in
the base code and to allow a manufacturer number from the item record to be used
for coupon validation. Its usage requires that manufacturer’s numbers be
maintained in the item record file for validation purposes.

Sequence Number and Velocity Code Imbedded in Coupon UPC

This function causes all category 4 UPCs and any category 5 store coupons (of the
type defined in “Category 5 UPC Store Coupons” on page 21) to be uniquely
processed. The UPCs are interpreted as 4MMMMMSVVVV or 5MMMMMSVVVV
where MMMMM is a manufacturer number, S is a sequence number, and VVVV is
a velocity code. The manufacturer number is used for validation for category 4
UPCs and as a unique identifier for category 5 store coupons. The category 5
manufacturer number is replaced with a number from the item record for validation
purposes. The sequence number is used for expiration validation if the item record
is defined as a coupon. The velocity code is used as the item code for the item
record lookup. This option simplifies the coupon data base and migration to coupon
scanning. The four-digit velocity code can still be keyed to access the same coupon
record as the complete UPC. This makes migration easier for chains that have not
fully installed scanning and that currently handle velocity-coded store coupons.

To be able to key the velocity code instead of the full UPC number, you must
maintain manufacturer numbers in the coupon records for store coupon validation.
The advantage to this option is that it minimizes the number of coupon item records
by reusing a limited set of coupon velocity codes. When this option is selected, all
coupon item movement is maintained using the velocity code regardless of whether
the velocity code or the full UPC was entered.

Store Coupon Scanning Alternatives

The options to use category 4 UPCs or category five UPCs, the option to imbed
data in a coupon UPC, and the options provided by an item record lookup offer
multiple ways to do store coupon scanning. Following are several approaches:
v Select both options:
– Code store coupon UPCs as category 4.
– Key four-digit velocity codes in non-scanning stores or in cases when the
UPC cannot be scanned.

22 Electronic Marketing PRPQ

 – Maintain manufacturer numbers and sequence numbers in the item file. But,
to prevent coupon validation that would always fail, non-scanning stores
should not keep the manufacturer number in the item file.
– Select neither of the options:
– Code store coupon UPCs as category 4, including the manufacturer’s number
in the UPC.
– Key the full 11-digit UPC when the UPC does not scan.
– Do not maintain manufacturer numbers or sequence numbers in the item file.
This method works only if all stores use scanning because it causes validation
always to be performed.
– Select only the velocity code option:
– Code store coupon UPCs as category 4, including the manufacturer’s number
in the UPC.
– Maintain only sequence numbers in the item file to handle coupon expiration.
With this selection, you can key the full UPC in scanning stores to cause
validation, but key only the velocity code in non-scanning stores to prevent
validation.
– Do not select any of the options:
– Code store coupons as category zero velocity codes.
– Maintain the manufacturer number in the coupon item records in scanning
stores to cause full store coupon validation.

There are numerous other alternatives to obtain full store coupon validation. For
example, store coupon validation is performed by department even if there is not a
manufacturer’s number in the coupon UPC or coupon item record. This base code
level of validation ensures that enough of the items have been sold from a
department to allow a coupon to be redeemed against the department.

Store Coupon Validation Enhancements

The following enhancements are intended to extend the functions of store coupon
processing. This processing applies only to items flagged as either store or
manufacturer coupons and is independent of what UPC is used to access the item
record. These processing options effectively apply only to store coupons because
manufacturer coupons do not have associated item records.

Validation of Coupon UPCs with Invalid or No Manufacturer Number

In the Supermarket Application, coupons are validated only against the
manufacturer number contained in the coupon UPC. This enhancement causes an
invalid or missing manufacturer number in a coupon UPC to be replaced by the
number in the item file for validation purposes. This replacement function is not
active if a valid manufacturer number is in the coupon UPC or if no number is
maintained in the item file. When this function is used, it provides full coupon
validation for coupons, including those that are entered through velocity codes or
category 5 store coupons as defined in “Category 5 UPC Store Coupons” on
page 21. If this function is used for some coupon records but not for others, there is
no coupon validation for those records that contain a manufacturer number of all
zeroes. An option allows a valid manufacturer number in a coupon item record to
replace a valid manufacturer number in the coupon item code.

Chapter 3. Coupon Processing Enhancements 23

Limit of Like Coupons in a Transaction
This function allows a coupon to be rejected if the number of like coupons entered
in a transaction exceeds the transaction limit defined in the coupon item record. A
unique operator guidance is given, with a default descriptor of “TOO MANY
COUPONS”. The (Lmt/Tran) flag in the coupon item record is used to set this limit.

Validation Only by Quantity of Like Coupons

A coupon item record can be marked so the coupon is validated only against like
coupons by quantity. This selection causes the validation of this coupon not to be
affected by any coupons with different UPCs that might apply to the same item or
by any conflicts between the value of the coupon and the value of the matching
items. With this validation selected, a coupon will be rejected only if the quantity of
like coupons that have been tendered exceeds the quantity of matching items that
have been purchased. Only the base coupon validation is altered, so all other
validation functions provided by the Electronic Marketing application still apply when
this selection is made.

Validate Department Coupons by Department Subtotal Group

You can optionally select to validate by department subtotal group those coupons
that otherwise would validate against a single department. (See “Range of
Departments to Validate by Subtotal Group” on page 154.) The department subtotal
groups are defined in the store options for use with the Department Analysis
Report. For the coupons that validate on a group of departments, the minimum
purchase requirement is also met by the sales subtotal from the group of
departments.

Force Department Validation on Keyed Coupons

You can optionally select to validate by department those coupons that cannot
validate by manufacturer. You may choose to bypass department validation on
selected coupons based on a flag in the coupon item record. This function requires
coupon validation by department for coupons entered with a coupon key and allows
you to choose on an individual coupon basis whether department level validation
applies for coupons entered through use of a coupon item record. See “Validate All
Department Keyed Coupons by Department” on page 151.

Minimum Purchase Requirement

This function allows a coupon to be rejected if the purchase amount from the item
record is not satisfied at the time the coupon is tendered. A unique operator
guidance is given, with a default descriptor of “MINIMUM PURCHASE NOT
SATISFIED”. A flag in the item record defines whether or not the items to which the
coupon applies can contribute to the total purchase amount.

The minimum purchase requirement is only enforced at the time the coupon is
tendered. If later item voids cause a coupon to no longer be valid even though the
item which the coupon discounted is still in the order, the coupon will not be
automatically voided and the operator will not be notified that the coupon conditions
are no longer satisfied.

Minimum Purchase by Manufacturer or Department

A coupon item record can be marked so the minimum purchase amount is applied
only to sales from the designated manufacturer or department against which the
coupon is being validated. In this case, the purchase amount may be reduced by
prior matching coupons. The minimum purchase can be met by the subtotal from a

24 Electronic Marketing PRPQ

 group of departments if options are set to validate department coupons by
department subtotal group. See “Validate Department Coupons by Department
Subtotal Group” on page 24.

Minimum Purchase by Department without Department Validation

Separate flags in the coupon item record are used to define department level
validation and minimum purchase by department. Support is provided to allow a
minimum purchase requirement for a department even when the coupon is not
being validated or is being validated by manufacturer.

Require More Than One Item Per Coupon

This function allows a store coupon to require that more than one item be
purchased to validate the coupon. The quantity of items required to validate the
coupon is defined in the coupon item record. Validation processing is handled with
a quantity requirement, as for manufacturer coupons. The guidance message
“QUANTITY NOT SATISFIED” is given as defined in “Alter Coupon Guidance if too
few Items Are Sold” on page 33.

Support Cross-Item Promotion Coupons

Based on of coupon validation as defined by UPC guideline 22, each coupon
validates against a single item. You may want to allow a coupon only if multiple
items have been purchased. This support is provided by linking a one cent coupon
that validates against one item with a coupon for the full discount value that
validates against the second item. The one cent coupon will be discounted except
for validation and the real coupon will be accepted only if both coupons are
successfully validated. Up to four of these “fake” coupons can be linked to the final
coupon with real value. But each coupon must provide for full validation (by
manufacturer or department) if the function is to assure that all required items were
purchased to receive the discount. The items that match the fake coupons are only
co-requisites for the real discount coupon and are not considered discounted
themselves. For this reason, a real coupon can be taken against an item that was
matched earlier against a one cent coupon.

The requirement to purchase multiple different items before accepting a coupon is

enforced only at the time a coupon is tendered. If later item voids cause a coupon
to no longer be valid even though the item which the coupon discounted is still in
the order, the coupon will not be automatically voided and the operator will not be
notified that the coupon conditions are no longer satisfied.

Coupon Expiration Based on a Sequence Number

If the velocity code option defined in “Sequence Number and Velocity Code
Imbedded in Coupon UPC” on page 22 is selected and a non-zero sequence
number is provided in both the coupon UPC and in the coupon item record, the
coupon will be rejected if the two sequence numbers do not match. An operator
guidance is given, with a default descriptor of “COUPON HAS EXPIRED”. This
provides a technique for continually maintaining the same coupon item records on
file while allocating coupon velocity codes to new coupons and causing old coupons
to expire.

Operator Guidance Management

The operator guidance messages activated by this extra store coupon validation are
stacked with base code validation errors. This allows an operator to see all the
reasons for a failure. All the new guidances except for the “COUPON HAS
EXPIRED” guidance can be overridden through the new operator override options

Chapter 3. Coupon Processing Enhancements 25

 (see “Allow Operator Override of User-Selected Error Conditions” on page 32).
When multiple guidances are stacked, a manager’s override is required to accept
the coupon unless all of the guidances allow for an operator’s override.

Support Bypass of Validation for Certain Coupons

On coupons for which no validation is selected, use the hidden option to bypass
validation with better performance. This new function is automatic. If the coupon is
set up with no validation for example, no MFR number given and department
validation is not selected, then if this hidden option is selected the coupon validation
is automatically bypassed.

Promotion Code Validation

Promotion codes are a method for relating items to coupons for the purposes of
coupon validation. Validation by promotion code replaces validation by MFR/FAM or
DEPT/FAM for those coupons that contain a non-zero promotion code. A coupon
with a non-zero promotion code validates against any item containing the same
promotion code.

Summary of Coupon Validation Enhancements

The coupon validation enhancements give an enterprise the benefit of expanded
coupon capabilities. The additional validation (matching sales) and minimum
purchase requirements provided by the coupon processing enhancements lead to
the following validation choices for coupons.
Validation choices: Minimum purchase choices:
1 none transaction total or sales per dept
2 by dept subtotal group transaction total or sales from dept group
3 by dept transaction total or sales from dept
4 by dept and family transaction total or sales from dept
5 by mfr transaction total or sales from mfr or dept
6 by mfr and family transaction total or sales from mfr or dept
7 by promotion code transaction total or sales from promo or dept

In order for validation to succeed at one of these levels, there must be more
matching sales for the level than matching coupons. To meet the minimum
purchase requirement for the validation level requires sufficient sales in the
transaction or from the given set of matching sales. The following examples show
17 possible requirements for the awarding of a discount, price reduction, or bonus
points from a validated coupon.
1 on the next shopping visit
on any purchase of $50.00 or more
on any purchase of $10.00 or more from the deli department
2 on any purchase from the meat department (subtotal group)
on purchase of a meat item in a $50.00 transaction
on purchase of $10.00 of meat
3 on purchase from the poultry department
on purchase of a poultry in a $50.00 transaction
on purchase of $10.00 of poultry
4 on purchase of chicken parts from the poultry department
on purchase of chicken parts in a $50.00 transaction
on purchase of chicken parts with $10.00 of poultry
5 on purchase of a name brand name product
on purchase of a name brand name product in a $50.00 transaction
on purchase of a name brand product with $10.00 from the deli department
on purchase of $10.00 of name brand name products
6 on purchase of name brand name cookies
on purchase of name brand name cookies in a $50.00 transaction
on purchase of name brand cookies with $10.00 from the deli department
on purchase of name brand name cookies with $10.00 total of name brand
products

26 Electronic Marketing PRPQ

 7 on purchase of name brand name chocolate chip cookies
on purchase of name brand chocolate chip cookies in a $50.00 transaction
on purchase of name brand chocolate chip cookies with $10.00 from the
deli department
on purchase of name brand chocolate chip cookies with $10.00 total
of name brand products

The number of coupon types is further increased by use of any one or combination
of the following possibilities:
v Requirement of the purchase of more than one of the matching items
v Limit of like coupons in the transaction
v Redemption of preferred customer points
v Use of four coupon reward types: bonus points, cents off, percent off, reduced
price item
v Each occurrence of the same coupon in a transaction might optionally require
separate sales to satisfy the minimum purchase requirements
v Requirement of multiple independent validations for a single coupon when the
cross promotion capability is used (for example, on the purchase of chocolate
chip cookies with the purchase of the store brand of milk)
v Awarding of discount, reduced price, or bonus points per pound of a weighted
item.

Some of these validation possibilities cannot be combined (for example, one

coupon cannot be validated against a department subtotal group while another
coupon is validated against a single department that is within the subtotal group).
All functions are not available for all types of coupons (for example, support for
weighted coupons currently is not available for targeted or paper coupons). But, the
combination of the coupon processing enhancements and the preferred customer
code provides a level of function and flexibility that should allow an enterprise to
achieve any needed validation scheme.

General Enhancements

Support for 7, 8, and 9 Digit UPCs on Store Coupons

Before this enhancement, any category zero store coupons of more than six digits
appeared to contain a valid manufacturer number in the UPC and manufacturer
number substitution from the item record data would not be performed. This
enhancement takes into account the fact that manufacturer numbers of fewer than
ten digits contained in a category zero UPC are not valid, and allows manufacturer
number substitution for these UPCs. Significant UPC digits are overlaid by the
substituted manufacturer number and must be saved at substitution and restored at
the end of the transaction. This ensures that item movement is accumulated against
the input UPC. This enhancement allows store coupons to be coded as UPC E
labels if the first digit of the UPC code is zero.

Coupon Provides Net Item Value Instead of Discount

When Pricing Method 4 instead of Pricing Method 3 is given for a coupon, the low
price field is taken as the final price of the discounted item rather than as the
discount amount. A matching item must be found with a price greater than the
discounted price so that the actual discount amount for this coupon can be
calculated as normal item price minus the discounted price. If a matching item is
not found or the only matching items have already been priced less than the final
discounted value, this coupon will not provide any discount.

Chapter 3. Coupon Processing Enhancements 27

 Matching items for targeted or paper coupons are found through the validation
process by department or manufacturer and family code or by promotion code. If
the net value coupon is linked from a sale item, then the sale item is assumed to be
the matching item. For this reason, net value coupons must only be linked (directly
or indirectly) from the items which they are intended to discount. Since the discount
is computed against the highest value item that validates against a targeted or
paper coupon, you must be careful to assure that net value coupons validate only
against items within a limited price range. This often requires the use of unique
family codes or promotion codes since a single department or manufacturer might
provide a wide range of products.

Validation is not required for linked to (electronic) net item value coupons. This
means that when an item links to a net item value coupon, the value of the coupon
is based on the value of the linked from item regardless of validation.

Because the concept of value and points are mutually exclusive, point coupons are
never processed as net item value (pricing method 4) coupons. They will instead be
processed as a normal Electronic Marketing (pricing method 3) coupon.

Support for Training Mode

This enhancement does the following while in training mode:
1. The limits on like coupons in a coupon only transaction are bypassed.
2. Coupons are not doubled in a coupon only transaction.
3. Coupons marked not for sale are allowed to process normally, as though
marked for sale so promotions can be tested before being activated.

Item Record Data for Store Coupons

To apply the new coupon validation functions on a coupon-by-coupon basis, the
new data required by these functions is maintained in the coupon item records. This
causes item records that are flagged as coupons to be interpreted differently from
all other item records and imposes unique restrictions on the record contents.
These changes do not have an impact on any item records that are not marked as
coupons.

Additional Coupon Record Data

The item record for a coupon is interpreted to contain the following additional pieces
of information:
v A manufacturer number for the matching item
v A minimum purchase amount
v A sequence number
v The number of coupons allowed per transaction
v The number of items required by the coupon
v An indication that the items matched by the coupon can contribute to the
minimum purchase requirement
v An indication that the minimum purchase amount applies only to purchases from
the manufacturer for which the coupon is valid
v An indication that the minimum purchase amount applies only to purchases from
the department for which the coupon is valid
v An indication that the coupon is to be validated only against like coupons by
quantity

28 Electronic Marketing PRPQ

 v An indication that the coupon value given in the item record is actually the net
value of the items after the discount is applied
v An indication that the coupon is to be validated by department when some
coupons without a manufacturer number are not validated.

You can choose to maintain in an item record only the information required for the
functions that you use. For example, if you do not need coupon validation by
manufacturer or if the manufacturer number is contained in the coupon UPC, you
do not need a manufacturer number in the item record. Also, you need a sequence
number in an item record only if a sequence number is contained in the coupon
UPC and you want to have expiration processing. If you maintain only essential
coupon data in a coupon item record, the following defaults apply:
v Validation against only the manufacturer number from the coupon UPC
v No minimum purchase requirement
v No expiration check provided
v Allowance of only one of a like coupon per transaction
v Only one item required to validate the coupon.

The default for all indicator flags is off.

Coupon Record Maintenance

All additional coupon record data can be maintained from the host. Electronic
Marketing has no impact on Delayed Data Maintenance or any other maintenance
tool because it does not change the size or format of the item record.

The Electronic Marketing application provides a change to the Data Maintenance

application that allows the appropriate descriptors to be displayed for the coupon
record fields that have been redefined by this product.

The Selective Item Record Report provides a user-friendly method of reporting on

all of the data in all coupon item records. See “Selective Item Record Report” on
page 250.

Coupon Restrictions Because of Additional Data

The addition of coupon data to item record fields that are normally used for other
purposes causes certain restrictions to be imposed on coupons. All coupons are
unit-priced, regardless of the pricing method or other pricing data in coupon item
records. Also, the coupon value is limited to five digits. This allows almost all of the
additional data to be contained in the pricing fields used for items not unit-priced.
Additional data is maintained in user exit field two in the item record, so this field
cannot be used for other purposes. The date of last sale function of the Selective
Item Record Report normally uses exit field two. But when additional data is kept,
no date of last sale is maintained for coupon records. If a manufacturer number is
kept in the record and the item record is to be maintained in the store through the
controller data maintenance procedure, all coupons must be assigned a pricing
method of three or four. Without this pricing method selection, the data maintenance
procedure would fail to display, allow alteration of the manufacturer number, and
delete this number if the price were altered.

Coupon Restrictions Because of System Design

The system design causes the following coupon restrictions:
v Each item record can support only two family codes. This is adequate for most
needs, but it might restrict your ability to pair store coupons with multiple items.

Chapter 3. Coupon Processing Enhancements 29

 v To cause a store coupon to expire, you must either delete the associated coupon
item record or alter its sequence number. You can cause coupons to expire on a
specific date only by diligent control of item record maintenance.
v The translation routines in the base code for migration of PSS (Programmable
Store System) item records lack adequate information about the coupon fields in
the item record to be of any value. This function effectively requires host
maintenance of the item record file through means other than the PSS
compatible translations.
v The coupon data in the Coupon Tracking File and/or the Exception Log is in a
new format that affects any prior host processing of coupon tracking data.

Coupon Multiplication Limits

In the Supermarket Application, a store coupon can be created automatically to
multiply the value of a manufacturer coupon based on personalization options. The
value of this store coupon is a multiple of the value of a manufacturer coupon and
may be limited only by the value of the item. A terminal option personalized under
Manager’s Override Controls determines whether the value of a multiplied coupon is
allowed to exceed the value of the item. These enhancements provide additional
regulations of the number and value of doubled coupons and the transaction size in
which they are allowed. They enable a store to contain its exposure to coupon
doubling losses.

Limit on the Number of Coupons Doubled

This function provides a store limit on the number of coupons that can be doubled
in any single transaction. There is no override of this limit. Any coupons that exceed
this limit are not doubled.

Limit on the Value of Doubled Coupons (3 Options)

This function provides three ways to limit the value of a store coupon that is given
to double a manufacturer coupon. Each one is based on a single, store limit on the
value of a coupon to be doubled.
v Any coupon that exceeds the limit is not doubled.
v The value of coupons that exceed the limit can be increased, but the amount of a
store coupon that is combined with a manufacturer coupon is restricted to the
limit. Coupons that exceed the limit are not doubled, but an amount not
exceeding the limit is added to them by a store.
v A store coupon value is adjusted so that the sum of the manufacturer coupon
and the store coupon does not exceed the limit. If a manufacturer coupon
exceeds half of the limit value, the additional value provided by a store is
reduced as the value of the manufacturer coupon is increased. There is no
override to a store-wide limit. The doubling of any coupon that causes the limit to
be exceeded is automatically adjusted in value based on the technique chosen to
reduce a store’s exposure.

Minimum Purchase Requirement

This function provides a store minimum purchase requirement for the size of a
transaction in which coupons can be doubled. There is no override of this limit. Any
coupons tendered when a transaction is below this minimum value are not doubled.

30 Electronic Marketing PRPQ

 Limit of Coupons to Double Varies with Order Size
This enhancement provides an option to increase the effective limit on the number
of coupons that can be doubled for large transactions. It appears in a line added to
the end of the coupon options file.

The option causes a monetary amount to be compared with the transaction size at
the time a coupon is taken. The transaction size does not include the effects of
taxes, prior coupons, or miscellaneous transaction items. If the transaction size is
greater than or equal to twice the size of the option, the limit of coupons is doubled.
If the transaction size is greater than or equal to X times the size of the option, the
limit of coupons is multiplied by X for this transaction.

For example, if the coupon doubling policy states “three coupons doubled for every
$20.00 purchased,” the option should be set to $20.00, and the limit of coupons to
double in a transaction set to three.

If the option is set to zero or is not present, the limit of coupons to double does not
vary with the size of the order.

Deactivate Coupon Doubling by Day of Week

This enhancement provides a set of seven options that are used to deactivate
coupon doubling for any day of the week. The set includes one option for each day
of the week in a line added to the end of the options file. Coupon doubling must still
be defined through personalization.

Do Not Double MFR Coupon if Store Coupon Already Taken for Item
This enhancement provides an option to keep a manufacturer coupon from doubling
if a store coupon has already been taken for the same item. This option applies
only when store coupons have been taken for all transaction items for which there
is a manufacturer coupon.

Limit on the Number of Like Coupons to Be Doubled in an Order

This enhancement provides an optional limit to restrict the number of identical
coupons that can be doubled in an order. The coupons are considered identical if
they are validated (this implies a valid manufacturer number either in the coupon
UPC or in the coupon item record) and if their UPCs match. Once the limit is
exceeded, the like coupons cease to automatically double. No warning is given and
no override opportunity is provided.

Prohibit Coupon Doubling Through a Key Sequence

| This enhancement allows the NOSALE key to be used to manually prohibit doubling
| of a coupon at coupon entry. The key sequence NOSALE, UPC 5 coupon and
| ENTER results in the NO-Double coupon function. The key sequence NOSALE,
| STORE OR MFR coupon key, store or mfr coupon item, and ENTER results in the
| No-Double coupon function. The No-Sale Price Verify function remains valid with
| the key sequence NOSALE, item code (or store/mfr cpn item code) and
| [Link] NOSALE key cannot be used to void a coupon. It does not need to be
| used for this because a doubled coupon is voided only if it is present. If a user does
| not have a NOSALE key and does not want one, he can use terminal configuration
| to define a special NO-DOUBLE key on the keyboard as function code 89. This
| function code must be added to the input state table with all options set identically
| to those for the NOSALE key.

Chapter 3. Coupon Processing Enhancements 31

Allow Manual Entry of Doubled Coupons
This enhancement allows doubled coupons to be keyed in by one of two ways:
v Using the OVERRIDE key as the first key when entering a store coupon
v Defining a unique lookup key to be used only for entering double coupons.
In either case, the processing requires that the selected item record be marked as a
store coupon. Use of coupon modifier keys is excluded with this double coupon
keying. This exclusion means that use of this optional double coupon keying
requires selected item records and/or lookup keys to be defined as store coupons.
A doubled coupon entry is rejected with a guidance in the following cases:
v If the entry would be rejected as a normal store coupon (due to validation,
minimum purchase, or transaction count limits)
v If an equal double coupon would be rejected (due to double coupon size, count,
or minimum purchase limits).
The limit defined in the store coupon item record for the number of like coupons in
an order applies separately and equally to both manually doubled coupons and
store coupons. For example, if a user defines a store coupon lookup key (for
normal and doubled coupons) and its item record restricts doubling of coupons to
two store coupons per order, two manually doubled coupons plus two store
coupons are allowed per order. To accomplish this, the OVERRIDE key is used with
the store coupon lookup key. If a lookup key is defined exclusively as a double
coupon key, the limit of like coupons applies only to the double coupons because
they are the only coupons that can use that item record.

Allow Coupons to Be Marked for No Doubling

This enhancement causes the “COUPON MULTIPLICATION ALLOWED” flag in the
item record used for a coupon entry to allow or prevent the coupon from doubling.

Operator Interface Enhancements

The following group of enhancements is intended to improve the flexibility and
function of operator interface to coupon tendering.

Allow Operator Override of User-Selected Error Conditions

In the Supermarket Application, any coupon validation error requires a manager’s
override for the coupon to be accepted. Any limit-exceeded error in the customer’s
favor also requires a manager’s override. This enhancement provides the ability to
maintain validation and limit checks but to selectively allow some of these checks to
be overridden by an operator. This is an option in personalization. See “List of
Guidances to be Lowered to Allow Operator Override” on page 156.

Prompt the Operator to Write Free Coupon Value on the Coupon

Under UPC guideline 22, a category 5 manufacturer coupon can take the value of
the item to which it applies. In the Supermarket Application, the item’s value is
automatically applied if it can be determined. If not, an operator is prompted for the
value. In either case, this program prompts an operator to write the value of the
coupon on the “free item” or “price required” coupon. This prompt sounds the tone
and displays a guidance message that must be cleared by pressing the CLEAR
key. You can define the guidance message through personalization of sales
descriptors (with a default descriptor of “PLEASE WRITE [Link] ON THE COUPON”).
In addition to the guidance text, the message contains a guidance number and the
value of the coupon. Neither the format nor location of either of these two fields can
be personalized.

32 Electronic Marketing PRPQ

Alter Coupon Guidance if too few Items Are Sold
Under UPC guideline 22, coupon validation may require that more than one item be
purchased to validate a coupon. In the Supermarket Application, when there is no
matching item or an insufficient number of matching items to validate a coupon, a
single guidance message, with a default descriptor of “NO MATCH FOUND” is
used. This enhancement provides a separate guidance message, with a default
descriptor of “QUANTITY NOT SATISFIED” to be used in transactions with
insufficient items to validate the coupon. This enhancement can apply to a
transaction in which a coupon requires multiple items for validation but only one
item has been purchased without a prior coupon.

Alter Coupon Guidance to Tell if any Matching Items Are Sold

In the base system, a single guidance message (with a default descriptor of “NO
MATCH FOUND”) is used when no match is found for a coupon. This enhancement
provides a separate guidance message, with a default descriptor of “TOO MANY
COUPONS”, to be used when items that match this coupon are sold after coupons
have been redeemed for all such items.

Allow Certain Coupon Entries without Matching Item Validation

In the Supermarket Application, when no manufacturer number is available on a
store or manufacturer coupon, the coupon is validated based on sales from the
department assigned to the coupon. This function provides an option to bypass this
department validation when no manufacturer number is available for validation. This
causes the matching item validation requirement to be bypassed for all coupons
whose item records contain no manufacturer number that are entered using a
department key or a velocity code. Department validation is performed regardless of
the setting of this option, if the coupon item record is marked for validation by
department. Another option causes all coupons entered with a coupon key to
require department validation and those entered with a coupon item record to use
the flag in the item record to determine whether to require coupon validation.
Individual coupons can be marked to validate against sales from a department or
from a group of departments.

Require a Single Override in a Coupon only Transaction

When a customer forgets to present coupons until after paying for items, the
coupons must be handled in a separate transaction. This causes security concerns
because there are no items in the transaction against which the coupons can be
validated. In the Supermarket Application, a manager’s override and a manual store
coupon entry are required for the doubling of each coupon taken in a transaction
without sales. This function causes only one override to be required for a group of
coupons taken without sales. It also allows all coupons in such a transaction to be
doubled up to the system limit even though no sales are present to further limit the
doubling. This function overrides all minimum purchase limits for coupon-only
transactions. No minimum purchase requirements apply unless items are sold.

Logging of All Coupon Data

To enhance coupon tracking and improve the opportunity for electronic redemption,
this function creates and maintains a Coupon Tracking Log that contains all
information pertinent to manufacturer or store coupons. (see “Preferred Customer
Coupon Tracking File (EAMCOUPC)” on page 356.) Each entry in the file contains
all data on the redeemed coupon and the matching item. This file is created and
maintained by the application. At the close of each reporting period, the coupon
tracking data for the period is appended to an old period coupon tracking log and a

Chapter 3. Coupon Processing Enhancements 33

 new current period coupon tracking log is created. This cumulative old period
coupon tracking log is then transferred to the host where it is maintained without
affecting the performance of the store.

Coupon Tracking Options

An option allows a user to select whether to log store coupons in the Coupon
Tracking Log. If they are not logged there, it is possible to log store coupons in the
exception log by setting the “log all sales” flag in the coupon item record. In this
case a record of type 99 instead of the normal type 01 record is written to the
exception log. This 99 record contains the same information defined for the coupon
tracking log record. If store coupons are logged in the coupon tracking file, this 99
record is never written to the exception log regardless of the item record flag
setting. An identical option is provided for manufacturer coupons. But there is no
“log all sales” flag that can be set to log for manufacturer coupons because they
usually do not relate to item records. These options provide the ability to log both
store and manufacturer coupons, or log either or neither of them. The coupons may
be logged in the same file or separate files. An additional option determines
whether store coupons created through coupon doubling are to be logged if store
coupons are logged.

Two data formats are provided for the coupon tracking log. One format contains
printable ASCII data separated by the standard three-character PC delimiter “,”.
This format can be directly printed on a PC printer or can be converted to EBCDIC
when transferred to a host for further processing. This format is ideal for reading the
file contents, but inefficient in relation to size and transmission time. A second
format contains packed ASCII data separated by a one-character delimiter “:”. This
format is not directly readable or translatable to EBCDIC, but it requires
approximately half the space and transmission time of the larger format.

Limit Coupon Tracking to a Range of Coupon UPCs

The customer can optionally select a range of coupon UPCs which are allowed to
be logged in the coupon tracking file. This option further restricts the contents of the
coupon tracking file and can be used to stop logging of coupons outside the
specified UPC range. This range applies to both store and manufacturer coupons
alike.

Coupon Campaign Number Capture

Most manufacturer coupons contain a campaign number that the manufacturer
includes for coupon redemption. This coupon tracking enhancement allows for the
campaign number to be captured and logged when it is keyed in using the DATA
ENTRY key during coupon entry. Many manufacturers also encode the campaign
number on the UPC label in a machine-readable format, primarily by using the UPC
A supplement field. This enhancement is designed to capture and save a campaign
number that is scanned in with the UPC. The format of the incoming data is
dependent on the scanner type, and the code will probably have to be altered for
each scanner type that can capture this data. At this time, there are still label and
scanner dependencies and the automatic capture of the campaign number from a
scanned coupon remains an unresolved problem. (See “Add Customer Number to
Coupon Tracking File Records” on page 135 for another use of this field).

34 Electronic Marketing PRPQ

Personalization of Coupon Processing
The Electronic Marketing options file, EAMFBOPT, contains options to personalize
the coupon processing functions. The options are read by the Checkout Support
application at initialization and at every hourly crossing. A default file shipped with
this code can be altered with any text editor, the maintenance aid or with the
Electronic Marketing Options Report. This file is read by the terminal code at
initialization and at each operator sign-on.

System Performance Considerations of Coupon Processing

An item record lookup occurs on all store coupons regardless of whether any of
these coupon processing enhancements are installed. The enhancements do not
cause any additional disk activity in the terminal and involve negligible overhead for
the processing in the terminal. No performance degradation is expected at any
register in which these enhancements are installed.

The processing impact of these enhancements (on store controller utilization) is

slightly greater in the Checkout Support application. However, additional disk activity
occurs if the user selects the option to log coupons in the coupon tracking log. This
activity is no greater than that performed in the base product if all coupons are
logged in the exception log. This additional disk activity depends on what types of
coupons are tracked and how many of these coupons are taken at a store.

The largest checkout load, in which one of every five items is a coupon and all
coupons are logged, causes the total throughput of the checkout support process to
be reduced by a maximum of ten percent. This degradation of processing is rarely
experienced because few stores approach the upper limit for checkout support
processing. Checkout support is capable of handling the throughput of the front end
registers even with a ten percent degradation. Enterprises with very large stores
(more than 40 registers) that intend to perform additional in-store processing
functions on the same controller that runs the checkout support application can
benefit from one of the faster store controller models if logging many coupons is
anticipated.

Chapter 3. Coupon Processing Enhancements 35

36 Electronic Marketing PRPQ
Chapter 4. Installation and Configuration
Installation Notes
It is recommended that you print and read the [Link] and the
[Link] files before beginning the installation and configuration of the
Electronic Marketing application. It is also recommended that you make backup
copies of the executable programs that will be replaced during installation. See
Appendix C for this list of programs.

Before installing the Electronic Marketing application, you must have first installed
the Supermarket Application base user exit support and the CBASIC compiler.

You need to install the link programs (LINK86.286 & POSTLINK.286) and the
memory management module (ADXMEM0L.L86) from the optional diskette of the
operating system.

If you intend to install Electronic Marketing using the big memory model terminal
support, you need to install the version of the Supermarket Application that supports
the big memory model. You need the big memory model version of the memory
management module (ADXMEL0L.L86) and version 3.0 or later of the BASIC
compiler installed.

All of the Electronic Marketing code for terminal sales and checkout support resides
in the Supermarket user exits. All existing user exit code should be checked for
both compatibility with Electronic Marketing code and for functional duplication.
There are many auxiliary functions supported in Electronic Marketing that may
duplicate your existing user exit code. Any user exit code that duplicates Electronic
Marketing auxiliary functions must be removed. See “Auxiliary Functions” on
page 14 for the list of the user exit functions that are integrated into the Electronic
Marketing application.

Electronic Marketing includes all of the coupon processing enhancement exit code
from PRPQ 5799-DCB (Coupon Processing Enhancements with Selective Item
Record Report). If this PRPQ is now installed in your application, it must be
removed.

Any additional user exit code that deals with coupon processing needs to be
reviewed for possible deletion as it is probably redundant and could cause
problems.

Coupon options set in both an existing EAMUOPTS file and an existing

EAMFBOPT file, (both from the Electronic Marketing PRPQ, 1991 Release), must
be migrated to the new format Electronic Marketing options file, EAMFBOPT.

The FIXR1OPT.286 utility provided by Electronic Marketing may be used to merge

the contents of EAMUOPTS and the old EAMFBOPT, into the new version of
EAMFBOPT, which now contains all options for Electronic Marketing in a single file.
The FIXR1OPT.286 utility is discussed in the utilities section of this manual.

The Electronic Marketing install diskettes contain an install checklist,

[Link], that should be used to aid you as you perform the following
installation steps. BAT files are provided that will perform most of these installation
steps for you.

© Copyright IBM Corp. 1991 2000 37

 To execute the install BATs type, A:install from your root directory. Menu choice 11
will allow you to exit the BAT files so you can reenter them later. Type, menu to
reenter the bat files. Menu choice 12 will erase the install BATs from your hard disk
before exiting.

Install Electronic Marketing Exit Code

Copying Electronic Marketing Files to Your System

The Electronic Marketing applicationmodules are to be applied to your system by
using the Operating System Copy utility. The modules are in the ADX_UPGM and
ADX_IPGM subdirectories on these diskettes.

You may want to save a copy of the contents of these subdirectories on your
controllers before applying these diskettes. All executable programs and necessary
data files are in the ADX_IPGM subdirectory. They should be copied to your
ADX_IPGM directory as needed.

The user exit code is in the ADX_UPGM subdirectory.

You should use the following command to copy these user exit modules to your
system.

If you installed the Supermarket source base diskettes on your C: drive, then:
COPY A:\ADX_UPGM\*.* C:\ADX_UPGM\*.*

If you installed the Supermarket source base diskettes on your D: drive, then:
COPY A:\ADX_UPGM\*.* D:\ADX_UPGM\*.*

Repeat this step for each of the Electronic Marketing application diskettes.

Alter Terminal Sales and Checkout Support Link List

The following changes are needed to add preferred customer code to terminal and
controller checkout and to add memory management routines to terminal checkout.

Medium Memory Model

1. In module [Link] (on \ADX_UPGM) locate the line containing the
following:
EAMTSUPC[M,LI,LO],
2. Prior to the line just located, insert the following lines:
EAMTSFBX[M,LI,LO],
EAMTSFBY[M,LI,LO],
EAMTSFBZ[M,LI,LO],
3. In module [Link] (on \ADX_UPGM) locate the line containing the
following:
ADXUCRTL.L86[S,CODESHARED,M,LI,LO,DATA[MAX[0FFE]]]
4. Prior to the line just located, insert the following line:
ADXMEM0L.L86 [S],
5. In module [Link] (on \ADX_UPGM) locate the line containing the
following:
EAMCSUPC[M,LI,LO],
6. Prior to the line just located, insert the following lines:

38 Electronic Marketing PRPQ

 EAMCSFBX[M,LI,LO],
EAMCSFBZ[M,LI,LO],

Big Memory Model

For a big memory model installation, make the following change:
1. In module [Link] (on \ADX_UPGM) locate the line containing:
[Link][M,LI,LO],
2. Prior to the line just located, insert the following lines:
[Link][M,LI,LO],
[Link][M,LI,LO],
[Link][M,LI,LO],
3. In module [Link] (on \ADX_UPGM) locate the line containing the
following:
ADXUCLTL.L86[S,CODESHARED,M,LI,LO,DATA[MAX[0FFE]]]
4. Prior to the line just located, insert the following line:
ADXMEL0L.L86 [S],
5. In module [Link] (on \ADX_UPGM) locate the line:
EAMCSUPC[M,LI,LO],
6. Prior to the line just located, insert the following lines:
EAMCSFBX[M,LI,LO],
EAMCSFBZ[M,LI,LO],

| Enhanced Manufacturer Coupon Reporting Considerations

| When CD 9901 is installed it supports accounting for Manufacturer Coupons by
| Variety. For details, see the IBM 4680–4690 Supermarket Application Planning
| Guide. If you do not want to use the enhancement to the Manufacturer Coupon
| Reporting no changes are required for Electronic Marketing.

| If you are using Electronic Manufacturer coupons, this enhancement allows you to
| specify which variety of Electronic Manufacturer coupons are included in the
| accounting totals. The default variety is 1. To change the default variety edit module
| EAMEMCVC.J86 and change the selected variety. Valid values are 1-6. The variety
| set in this module is updated and reported for Electronic Manufacturer Coupon
| totals the same as the regular Manufacturer Coupon totals is handled without these
| modifications.

| These functions are changed by this enhancement:

| v Store Totals Recap Report
| v Cash Report
| v Tender Count Procedure
| v Automated Reconciliation
| v Automatic Pickup of Paperless Coupons
| Perform the following steps to implement the changes only if you changed file
| EAMEMCVC.J86 to use a variety other than 1.

| If you intend to perform current period tender counts on operators or previous

| period tender counts on the office:
| 1. Recompile [Link] (BASIC EAMPACC)
| 2. Recompile [Link] (BASIC EAMCSFBX)
| 3. Recompile [Link] (BASIC EAMUPKUP)
| 4. Relink EAMUPKUP.286
| LINK EAMUPKUP[|
| POSTLINK EAMUPKUP.286

Chapter 4. Installation and Configuration 39

| This enhancement assumes that all electronic manufacturer coupons are inherently
| the same and therefore are grouped under the same variety using the base options
| to derive the variety of the coupons. Note that the design of the Electronic
| Marketing PRPQ has not changed with the base Supermarket Application
| enhancement and co-requisite APAR. The Electronic Marketing software in the
| terminal creates a transaction log X'11' string (Data Entry) with the Electronic
| Manufacturer coupon count and amount for the entire order, not by individual
| coupon.

| You should personalize the base Manufacturer Coupons by Variety options so all
| Electronic Manufacturer Coupons affect the same variety. You accomplish this by
| only setting varieties for known, non-electronic ranges of coupons (such as number
| system 5, EAN-99, Catalina, or other third party generated on-file coupons and
| department keyed coupons. In this example, the Default Variety will contain totals
| for all of the retailer’s In-Ad Manufacturer Coupons whether they are paper or
| electronic.

Install Terminal and Controller Checkout Exit Code

All Electronic Marketing modules with an extension of “.J86” must be installed on
the directory that is being used to compile and link user exits. For each
EAMTSE??.J86 or EAMCSE??.J86 module there is an associated base
Supermarket module with the name EAM??U??.J86. (The “??” in the module
names indicates variable letters or numbers.) If the 1991 release of Electronic
Marketing has already been installed then this step is already complete except for
adding include statements for the two new include files, EAMCSE11.J86 and
EAMTSE57.J86.
1. In each of these J86 modules you must add a line as follows:
%INCLUDE EAMTSE??.J86 ! INCLUDE ELECTRONIC MARKETING CODE
-or-
%INCLUDE EAMCSE??.J86 ! INCLUDE ELECTRONIC MARKETING CODE

An example for EAMTSU01.J86 follows:

FUNCTION TSUPEC01 PUBLIC
! TSUPEC01 - BEFORE TX
%INCLUDE EAMTSE01.J86 Í------- THIS IS THE NEW INCLUDE
END FUNCTION

This includes the appropriate Electronic Marketing code into the proper exit
module. It is important that this new Electronic Marketing %INCLUDE
statement precede any other exit code in each of the modules where it is
inserted.

For terminal sales, the following EAMTSU??.J86 files (where ?? equals the
numbers listed below) need the include statement added. (See the previous
example for EAMTSU01.J86).
01, 02, 03, 07, 08, 14, 18, 20, 21, 23, 24, 27, 28, 30, 31, 37,
39, 40, 42, 43, 51, 53, 54

as well as EAMTSUVA.J86 and EAMTSUSU.J86 and optionally EAMTSE57.J86

if suspend/retrieve is installed.

For checkout support, the following EAMCSU??.J86 files (where ?? equals the
following numbers) need the include statement added:
01, 03, 04, 06, 11, 12, 13, 14, 15, 16, 17

as well as EAMCSUVA.J86 and EAMCSUSU.J86.

40 Electronic Marketing PRPQ

Re-compile the terminal ([Link]) and controller ([Link])
user exit modules. Then, re-link the terminal ([Link] or
[Link]) and controller ([Link]) modules.

This yields new terminal (EAMTS11L.286 or EAMTS10L.286) and controller

(EAMCSMLL.286) load modules.

The IBM Supermarket Application: Programming Guide provides detailed

instructions on how to customize code through user exits however, some
sample commands follow on the next page.

On a controller where the application user exit modules and the BASIC compiler
and linker are installed, the following commands are sufficient to implement and
install the new exit code after the EAMTSU??.J86 and EAMCSU??.J86 files
have been modified.

From the system main menu, select:

7 to get into command mode

Enter the following commands for the Medium Memory Model:

a. CD \ADX_UPGM (assuming this is the directory with the user exit code)
b. BASIC EAMTSUPC [BU]
c. LINK86 EAMTS11L [I]
d. POSTLINK EAMTS11L.286
e. BASIC EAMCSUPC [BU]
f. LINK86 EAMCSMLL [I]
g. POSTLINK EAMCSMLL.286
Enter the following commands for the Big Memory Model:
a. CD \ADX_UPGM (assuming this is the directory with the user exit code)
b. COMPBMM EAMTSUPC
c. LINK86 EAMTS10L [I]
d. POSTLINK EAMTS10L.286[I]
e. BASIC EAMCSUPC [BU]
f. LINK86 EAMCSMLL [I]
g. POSTLINK EAMCSMLL.286
It is recommended that you use version 3.0 of the BASIC compiler because a
Symbol Table Overflow error may occur in the compile step if you use an older
version. If this error does occur, go into module [Link] and comment
out the following include statements:

%INCLUDE EAMETWKG.J86 ! EFT working storage

%INCLUDE EAMOSTAT.J86 ! operator status file
%INCLUDE EAMTERMS.J86 ! terminal status file
%INCLUDE EAMTAXTB.J86 ! tax tables
%INCLUDE EAMTSVER.J86 ! totals save file
%INCLUDE EAMTOPTS.J86 ! terminal options

These INCLUDEs contain variables that are not used by the Preferred Customer
code and would not normally be used by any exit code. If this causes compile
errors with your exit code, you must add declarations back into EAMTSUVA.J86
for the missing variables using the variable declaration in the deleted .J86 file as
an example.

Chapter 4. Installation and Configuration 41

 As with any user exit modifications, this process of re-building the terminal and
controller load modules to incorporate the code from the new J86 files must be
repeated at each new maintenance level of the supermarket application. This
process need only be followed on the controller where the application user exit
modules and the BASIC compiler and linker are installed. The load modules
created by that controller can be copied to all other controllers. Copy the
modified terminal and controller load modules to the ADX_IPGM directory on the
C: drive.
2. The code becomes active in the terminals after they are reloaded.
3. The code becomes active in the controller after the file server is re-IPLed.
4. If you are on a LAN system, you need to use the system file utilities to alter the
distribution type of these two files to make them compound per update.
5. If the setting of the distribution attribute is done on the development controller
before this code is distributed to other systems, use the 4680 copy command to
copy these modules to diskette and back. The distribution attributes will be
carried to the new systems and will not need to be reset in every store.

Install Report Exit Code

To install the user exit changes in the accounting reports, all modules beginning
with “EAMRP” must be installed on the directory being used to compile and link
user exits.
1. Insert the following statement into EAMRPUVA.J86:
%INCLUDE EAMRPEVA.J86
2. Insert the following statement into EAMRPUSU.J86:
%INCLUDE EAMRPESU.J86
3. In each of these three .INP files:
v [Link]
v [Link]
v [Link]
4. Insert the following line:
EAMCSASC[M,LI,LO],
5. Save a copy of [Link]. This module will be modified by these
installation steps and your current copy must be saved now and restored in the
last step. This is to ensure that the report code is not linked into any other
reports or into the accounting programs. This can be accomplished with the
following command:

Copy To
[Link] [Link]

6. If you already have exit code in any of these reports, the Electronic Marketing
exit code must be merged with your exit code prior to compiling
[Link].
7. To install the cash report changes:

Copy To
EAMCRE01.J86 EAMRPU01.J86

Compile Link To get a new load module and then postlink

[Link] [Link] EAMRPCRL.286

42 Electronic Marketing PRPQ

 8. To install the performance report changes:

Copy To
EAMPFE01.J86 EAMRPU01.J86

Compile Link To get a new load module and then postlink

[Link] [Link] EAMRPPFL.286

9. To install the recap report changes:

Copy To
EAMPFE01.J86 EAMRPU01.J86

Compile Link To get a new load module and then postlink

[Link] [Link] EAMRPSTL.286

10. After creating these three new load modules, copy them to the ADX_IPGM
directory, and if you are on a LAN system, use the system file utilities to alter
the distribution type of these three files to make them compound per update.
11. If the setting of the distribution attribute is done on the development controller
before this code is distributed to other systems, use the 4680 copy command
to copy these modules to diskette and back. The distribution attributes will be
carried to the new systems and will not need to be reset in every store.
12. Restore the saved copy of [Link]. This can be accomplished with
the following command:

Copy To
[Link] [Link]

Re-Link Data Maintenance, Tender Count and Automatic Reconciliation

1. If you intend to perform in-store maintenance on coupon item records, you will
need an altered version of the item record data maintenance program to see
correct descriptors on the new coupon fields and to maintain fields in the item
record used by the Electronic Marketing application. These alterations are
supplied in module [Link]. This module should have been copied to
ADX_UPGM (or wherever you do your compile and links) with the rest of the
Electronic Marketing code. This module must be linked into the rest of data
maintenance as follows:
LINK86 EAMDB55L [I]
POSTLINK EAMDB55L.286
2. If you want these same changes to apply when the item record change screen
is presented by delayed data maintenance (while editing data from a batch),
then you need to also link EAMDMCBL and EAMDMDEL as follows:
LINK86 EAMDMCBL [I]
POSTLINK EAMDMCBL.286
LINK86 EAMDMDEL [I]
POSTLINK EAMDMDEL.286
3. If you intend to perform current period tender counts on operators or previous
period tender counts on the office, then you will need an altered version of the
tender count and automatic reconciliation program to correctly account for

Chapter 4. Installation and Configuration 43

 paperless coupons. These alterations are supplied in [Link]. This
module should have been copied to ADX_UPGM (or wherever you do your
compile and links) with the rest of the Electronic Marketing code. This module
must be linked to the rest of tender count and automatic reconciliation as
follows:
LINK86 EAMACTCL [I]
POSTLINK EAMACTCL.286
LINK86 EAMACARL [I]
POSTLINK EAMACARL.286
4. The resulting executable programs (EAMDB55L.286, EAMACTCL.286, and
EAMACARL.286, and optionally EAMDMCBL.286 and EAMDMDEL.286) must
be copied to the ADX_IPGM directory. If you are on a LAN system, ensure the
distribution attribute of these modules is compound per update through the
system file utilities.

Install Background Programs

To copy/install the background programs:

If you are on a LAN system, run the file utility to set

Copy To distribution to
EAMUXFER.286 ADX_IPGM Compound per update
EAMUFILT.286
EAMUPKUP.286
EAMUDOLS.286
EAMUROLP.286
EAMUREFA.286

Note: In order for the installation of background utility programs to be complete,

some of the background applications must be configured on the background
processing screen. See “Configure Background Application” on page 53

Install User Reports

To install the user reports:

If you are on a LAN system, run the file utility to set

Copy To distribution type to
EAMRPU3L.286 ADX_IPGM Compound per update
EAMRPU5L.286
EAMRPU6L.286
EAMRPU7L.286
EAMRPU8L.286

These modules can, alternatively, be renamed to EAMRPUxL.286, where x is an

unused number on the user reports menu. The programs can be found on the
Electronic Marketing application diskette in the ADX_IPGM subdirectory.

These user reports provide the ability to look at preferred customer information in
the exception log, in the Audit log, and to look at and to modify the Electronic
Marketing data files, and the Supermarket item record file.

The names of the reports are:

v EAMRPU3L.286 Selective Item Record Report
v EAMRPU5L.286 Preferred Customer Audit Log Report

44 Electronic Marketing PRPQ

 v EAMRPU6L.286 Preferred Customer Exception Log Report
v EAMRPU7L.286 Preferred Customer Options Report
v EAMRPU8L.286 Selective Preferred Customer Report.
Notes:
1. User report descriptors in the range of 3230 to 3237 must be altered through
personalization to fit the appropriate assignment of the user reports. See
“Personalize Report Descriptors” on page 66 Also file [Link] must be
copied to ADX_IPGM to provide the descriptors used within the reports.
2. EAMRPU3L.286 will not run on V1R3 of the store system operating system
unless the changes on the first delta diskette are applied. It should run fine on
all other levels of the store system operating system.

Install Optional User Procedures

If you desire to close the Preferred Customer points activity period manually in the
store rather than automatically at the store close, then copy EAMUPM3L.286 to
ADX_IPGM to install user procedure 3. (See “EAMUPM3L - Manual Close of Points
Activity Period” on page 294.) Even if the option is selected to automatically close
the Preferred Customer points activity on period intervals, it is still a good idea to
install this program (with very restricted operator authorization for it’s use) so that it
will be available as a manual backup should it be needed.

If you want to maintain targeted coupon messages in the store, then copy
EAMUPM4L.286 to ADX_IPGM to install user procedure 4. (See “EAMUPM4L -
Maintain Targeted Coupon Messages” on page 295.) It is suggested that the
enrollment procedure be installed as an optional user procedure, but its installation
is described separately because of the complexity.

If you install these user procedures, you should modify the report descriptor 3224
for EAMUPM3L.286 and 3225 for EAMUPM4L in order to name these programs on
the user procedure menu screen. This descriptor can be added by running the
program DESCADDR. Default descriptors for these programs are provided in
[Link]. (See “DESCADDR - Auto Install of New Report Descriptors” on
page 278.)

Install the Optional Date of Last Sale Update Function

If you would like to report on items based on their date of last sale, this information
must be maintained in the item record file. Electronic Marketing provides a program,
EAMUDOLS.286 to do this for you. There are two ways to accomplish this:
1. An Electronic Marketing option allows this program to be called automatically. In
this case, you can copy EAMUDOLS.286 to ADX_IPGM and optionally install it
on the background screen.
2. You can manually install the program but if you choose to manually install it, do
not use the Electronic Marketing option to execute the program.

Perform the following steps to manually install the Date of Last Sale function. These
procedures can be performed on a non-Electronic Marketing system.
1. Module EAMUDOLS.286 must be copied to the ADX_UPGM directory on the
C: drive.
2. If you are on a LAN system and you copied EAMUDOLS.286 by any copy
other than a 4680 copy, you need to use the system file utilities to alter the
distribution type of this file to make it compound per update.

Chapter 4. Installation and Configuration 45

 3. To automatically start the date of last sale updating function when item
movement data is closed, code must be installed in the controller user exit that
takes control after store close processing.
The first step in installing this code is to place the following code into module
EAMCSUSU.J86 to give access to the system routine that starts another
background task. This step is not necessary if you are installing this code on a
Electronic Marketing system.
%INCLUDE CSSUDSU1.J86
4. At this point, you select code to install into module EAMCSU*.J86 according to
the following alternatives:
5. If you want only to update the date of last sale in the item records without
staging item movement, install the following code into module EAMCSU16.J86:
%INCLUDE CS16DSU1.J86
6. If you want only to stage item movement data to native format without updating
the date of last sale in the item records, install the following code into module
EAMCSU16.J86:
%INCLUDE CS16DSU2.J86
7. If you want to update the date of last sale in the item records while staging
item movement to native format, install the following code into module
EAMCSU16.J86:
%INCLUDE CS16DSU3.J86
8. If you want to update only the date of last sale in the item records without
staging item movement and you want to wait for the process to complete so
that one of the base code translation routines can be activated, then install the
following code into modules EAMCSUSU.J86:
%INCLUDE CSSUDSU2.J86

and install the following code into module EAMCSU16.J86 before the code that
activates the base item movement staging routine:
%INCLUDE CS16DSU4.J86

These four choices of user exit code demonstrate the possibilities of

automatically starting the Date Of Sale updating routine, but they do not
exhaust the possible parameter combinations that can be passed to this
program. These parameters are described in detail in the function description
“Input Options (Parameters)” on page 297.

If you want other parameters, select one of these four Include files for exit 16
and alter the options passed to the Date of Sale program as needed.
9. If you are staging item movement data to the native format and do not want to
delete the old period item movement file after creating the staged movement
file, change the second input parameter from a “zero” to a “two” or from a
“one” to a “three” If you are not staging item movement data but still wish to
delete the old period item movement file after completion of the date of last
sale updates, then change the second input parameter from a “three” to a
“one”.
If you are staging item movement data and do not want the item movement
integers converted to binary, add another four to the second input parameter to
give a parameter in the range of “four” through “seven”.
10. The techniques required to implement this controller user exit are the same as
those needed to implement the Electronic Marketing functions (see the “Install
Terminal and Controller Checkout Exit Code” section).

46 Electronic Marketing PRPQ

 11. The utility LOGNAMES.286 (see “LOGNAMES - Install Preferred Customer
Logical Names” on page 281) can be used to add all of the necessary logical
names to the Master and Alternate (DD) store controllers. If you have run the
LOGNAMES.286 utility previously, there is no need to run it again.
As an alternative,
12. The controller configuration application can be used to add the following user
logical names:
Define: To Be:

EAMIMOV1 ADXLXACN::C:\ADX_IDT4\[Link]
EAMIMWRK ADXLXACN::C:\ADX_IDT4\[Link]

These two files must be on the same disk and directory as [Link].

Controller configuration must be activated and the controller re-IPLed for these
logical names to take effect.

Optional Source Code Changes

Optional source code changes can be made to Delayed Data Maintenance and to
the Department Analysis Report.

Optional Changes to Delayed Data Maintenance

If you have the source code and you want to prevent all item record replacements
(including adds of existing records) through Delayed Data Maintenance from the
host from altering the family code, link field, or exit fields in an item record, then
make the source code changes to module [Link] that are described
below.

If you are setting the link and/or family code fields in normal sale items to promote
them with electronic coupons, and these promotion maintenance batches are
distinguishable from price maintenance batches from the host, you may want to
implement this change to keep the price maintenance batches from overlaying the
promotion maintenance updates.

If your promotion maintenance is generated at the host in conjunction with price

maintenance or if you use price only DDM batches or field level ADDMI batches to
change prices without impacting the promotion fields in an item record, you
probably do not need this alteration. This source alteration to Delayed Data
Maintenance is optional based upon a need to isolate promotion maintenance of
electronic coupon from price maintenance and upon the use of a price maintenance
system that replaces all of the data in an item record in order to change a price.

If you need this alteration then:

1. in module [Link] locate the line:
! WRITE record read from source to target
2. Prior to the line just located, insert ONE of the following lines:
%INCLUDE EAMDMML1.J86 ! STOP ALL DDM BATCHES FROM UPDATING PROMOTION
-or-
%INCLUDE EAMDMML2.J86 ! STOP ALL HOST DDM BATCHES FROM UPDATING PROMOTIONS
-or-
%INCLUDE EAMDMML3.J86 ! STOP ALL HOST DDM BATCHES FROM UPDATING PROMOTIONS
! AND STOP IN-STORE BATCH FROM UPDATING PRICES

Chapter 4. Installation and Configuration 47

 The code in EAMDMML1.J86 stops all DDM batches from replacing the link,
family code, or exit fields in an existing item record. This code can meet your
needs if you update these promotion fields through direct data maintenance or
through ADDMI immediate batches.

The code in EAMDMML2.J86 stops all DDM batches that are in PSS or New
Host format (not controller format) from replacing the link, family code, or exit
fields in an existing item record.

This code can meet your needs if your host price maintenance is in PSS or
New Host format and you intend to update the promotion fields through
controller format batches as are created by the Selective Item Record Report.

The code in EAMDMML3.J86 stops all DDM batches that are in PSS or New
Host format (not controller format) from replacing the link, family code, or exit
fields in an existing item record. It also stops all controller formatted batches
from updating the price or descriptor data in an item record.

This code can meet your needs if your host price maintenance is in PSS or
New Host format and your promotion maintenance is in controller format and
you do not intend to change any prices or descriptor through in-store created
batches.

If none of these selections meets your needs but you still have a problem with
interaction between price and promotion maintenance, then:
3. You can alter these source changes as necessary to distinguish between
promotion and price maintenance and keep the two types of maintenance from
adversely impacting each other.
For example, you might make all price maintenance batches operator initiated
and all promotion maintenance immediate and key off of this distinction to limit
the two maintenance types to their intended changes.
4. After altering the source code with the new include file, the following .J86 files
are needed from the source code in order to successfully compile
[Link]:
EAMCFINC.J86
EAMDMMLI.J86
EAMDMPRD.J86
EAMDMPWR.J86
EAMERRNH.J86
EAMSOPTS.J86
EAMSORD1.J86
EAMTLATE.J86
EAMXXCPY.J86
5. Compile the modified source with the following command:
BASIC EAMDMMLC [BU]
6. After altering and compiling [Link], you need to link
[Link] to get a new copy of EAMDMMLL.286 that contains the
altered version of [Link]. This 286 file must be postlinked. The five
other modules needed for this link are as follows:
v [Link]
v [Link]
v EAMPSDMK.L86

48 Electronic Marketing PRPQ

 v EAMGAFMK.L86
v EAMGASCK.L86
All are provided on the application exit code diskettes.
7. Enter the following commands to link the modules:
LINK86 EAMDMMLL [I]
POSTLINK EAMDMMLL.286
8. Copy the modified delayed data maintenance load module to the ADX_IPGM
directory on the C: drive.
9. If you are on a LAN system, make the distribution type of EAMDMMLL.286
compound per update.

Optional Changes to Department Analysis Report

If the option to accumulate keyed versus scanned totals by department is selected
(see 112), you can make these changes to the department analysis report to
present keyed versus scanned sales by department.

This code is copied from Sample User Exit Code 23 of the Supermarket Program
Code, Appendix H. It is unsupported code to be used as is.

Use application personalization to alter the report descriptors in the department

analysis report.
1. To alter guidance text in personalization, from the system main menu,
Type 1 to select the SUPERMARKET application
Type 6 to select Personalization
Type 4 to alter Descriptors
Type 3 to select Report Descriptors
Type 602-605 to select text for the department analysis report
2. For proper text alignment, enter the descriptors as:
" DEPARTMENT ***** NET ITEM SA"
"LES ***** ** CUSTOMER ** KEYED DEPT."
" NO. NAME ITEMS AMOUNT"
" PERCENT COUNT PERCENT UPCS KEYS "
1234567890123456789012345678901234567890
This change will define text to be used for the next execution of the department
analysis report.

In order to print the totals that Electronic Marketing has optionally placed in the
department totals exit fields in the department analysis report, the following source
code changes should be made to the specified modules. These same changes
could be made totally through the reports user exit however, this would require the
exit to re-read the department totals file. It is simple and performance sensitive to
alter the source code.
1. In module EAMRPDTD.J86 alter the line:
DIM DEPT.D (1500,4)
to be:
DIM DEPT.D (1500,6) !! IR71139

This change provides a place to save the user exit field after it has been read
in from the file.
2. Make the following changes in module [Link]:
a. Locate the line:
\ REM!!****************** END OF VARIABLES **********************!!
b. Once the line is located, precede it with the following lines:

Chapter 4. Installation and Configuration 49

 INTEGER*4 [Link], \ ** ADDED **
[Link], \ ** ADDED **
[Link], \ ** ADDED **
[Link], \ ** ADDED **
TEMPI4, \ ** ADDED **
[Link], \ ** ADDED **
[Link], \ ** ADDED **
[Link], \ ** ADDED ** IR71139
[Link], \ ** ADDED ** IR71139
[Link] ! ** ADDED ** IR71139
STRING GLOBAL [Link]$ ! ** ADDED **
3. Locate the line:
%INCLUDE DMEXTR.J86 !Display manager external routines
4. Once the line is located, follow it with the line:
%INCLUDE EAMASMCT.J86 ! ** ADDED **
5. In subroutines [Link] and [Link] locate the line:
CALL RPCFEC01(SEN$)
6. Once the line is located, precede it with the line:
%INCLUDE USERRPD1.J86 ! ** ADDED **
7. In subroutine [Link] locate the line:
CALL RPCFEC01(SEN$)
8. Once the line is located, precede it with the line:
%INCLUDE USERRPD2.J86 ! ** ADDED **
9. Locate the line:
DEPT.D(J,NBR) = WORK
10. Once the line is located, follow it with the lines:
DEPT.D(J,5) = [Link](I + 5) ! ** ADDED **
DEPT.D(J,6) = [Link](I) ! ** IR71139
11. Locate the line:
CALL [Link]
12. Once the line is located, follow it with the lines:
[Link] = 0 ! ** ADDED **
[Link] = 0 ! ** ADDED **
[Link] = 0 ! ** ADDED **
[Link] = 0 ! ** ADDED **
[Link] = 0 ! ** ADDED **
[Link] = 0 ! ** ADDED **
[Link] = 0 ! ** ADDED **
13. Locate the line:
[Link] = [Link] + DEPT.D(J,ITM)
14. Once the line is located, follow it with the lines:
TEMP$ = "1234" ! ** ADDED **
CALL PUTN4(TEMP$,0,[Link]) ! ** ADDED **
CALL ADDIN4(TEMP$,0,DEPT.D(J,5) ! ** ADDED **
[Link] = GETN4(TEMP$,0) ! ** ADDED **
[Link] = [Link] \ ** ADDED **
+ SHIFT(DEPT.D(J,5),16) ! **
[Link] = [Link] \ ** ADDED **
+ (DEPT.D(J,5) AND 0FFFFH) ! **
[Link] = [Link] + DEPT.D(J,6) ! **
[Link] = [Link] + DEPT.D(J,6) ! **
15. Locate the line:
DEPT.D(K,ITM) = [Link]
16. Once the line is located, follow it with the lines:

50 Electronic Marketing PRPQ

 DEPT.D(K,5) = [Link] ! ** ADDED **
[Link] = 0 ! ** ADDED **
DEPT.D(K,6) = [Link] ! ** ADDED **
[Link] = 0 ! ** ADDED **
17. Locate the line:
[Link] = [Link] + DEPT.D(M,ITM)
18. Once the line is located, follow it with the lines:
TEMP$ = "1234" ! ** ADDED **
CALL PUTN4(TEMP$,0,[Link]) ! ** ADDED **
CALL ADDIN4(TEMP$,0,DEPT.D(M,5) ! ** ADDED **
[Link] = GETN4(TEMP$,0) ! ** ADDED **
[Link] = [Link] \ ** ADDED **
+ SHIFT(DEPT.D(M,5),16) ! **
[Link] = [Link] \ ** ADDED **
+ (DEPT.D(M,5) AND 0FFFFH) ! **
[Link] = [Link] + DEPT.D(M,6) ! **
[Link] = [Link] + DEPT.D(M,6) ! **
19. Locate the line:
DEPT.D(K,ITM) = [Link]
20. Once the line is located, follow it with the lines:
DEPT.D(K,5) = [Link] ! ** ADDED **
DEPT.D(K,6) = [Link] ! ** ADDED **

These source changes cause the user exit fields in the department totals file to
be read in and accumulated just like the count of items sold. These changes
also cause the user data to be accessed for formatting just before the report
user exit is to be executed.
21. Create module USERRPD1.J86 containing the following code:
!! ************ ADDED *************
TEMPI4 = SHIFT(DEPT.D(DEPT.P(I,PTR),5),16) AND 0FFFFH
[Link] = [Link](TEMPI4, DEPT.D(DEPT.P(I,PTR),6))
TEMPI4 = DEPT.D(DEPT.P(I,PTR),5) AND 0FFFFH
[Link] = [Link](TEMPI4, DEPT.D(DEPT.P(I,PTR),6))
[Link] = ON1
TEMP$ = MMCFEC06$([Link],ON1,ON1)
TEMP$ = LEFT$(TEMP$,LEN(TEMP$)-2) + "%"
[Link]$ = RPCFEC04$([Link]$,TEMP$,6)
TEMP$ = MMCFEC06$([Link],ON1,ON1)
[Link] = OFF0
TEMP$ = LEFT$(TEMP$,LEN(TEMP$)-2) + "%"
[Link]$ = RPCFEC04$([Link]$,TEMP$,13)
!! *** MOVED FROM USER EXIT INTO SOURCE ***
SEN$ = LEFT$(SEN$,28) \ 28 through item count
+ MID$(SEN$,31,14) \ 14 more for amount + 2 blanks
+ MID$(SEN$,47,08) \ 08 more for percent + 1 blank
+ MID$(SEN$,62,08) \ 08 more for customers + 2 blanks
+ MID$(SEN$,71,07) \ 07 more for percent
+ " " \ 02 more for blanks
+ [Link]$ ! 13 more for user data
[Link]$ = " " ! Only use data once
!! ************ ADDED *************

This code (which is executed just prior to calling the report user exit for a
report line) is used to format the new data which corresponds to this report line
and add it to the report line before printing.
22. Create module USERRPD2.J86 containing the following code:
!! ************ ADDED *************
[Link] = [Link]([Link], [Link])
[Link] = [Link]([Link], [Link])
[Link] = ON1

Chapter 4. Installation and Configuration 51

 TEMP$ = MMCFEC06$([Link],ON1,ON1)
TEMP$ = LEFT$(TEMP$,LEN(TEMP$)-2) + "%"
[Link]$ = RPCFEC04$([Link]$,TEMP$,6)
TEMP$ = MMCFEC06$([Link],ON1,ON1)
[Link] = OFF0
TEMP$ = LEFT$(TEMP$,LEN(TEMP$)-2) + "%"
[Link]$ = RPCFEC04$([Link]$,TEMP$,13)
!! *** MOVED FROM USER EXIT INTO SOURCE ***
SEN$ = LEFT$(SEN$,28) \ 28 through item count
+ MID$(SEN$,31,14) \ 14 more for amount + 2 blanks
+ MID$(SEN$,47,08) \ 08 more for percent + 1 blank
+ MID$(SEN$,62,08) \ 08 more for customers + 2 blanks
+ MID$(SEN$,71,07) \ 07 more for percent
+ " " \ 02 more for blanks
+ [Link]$ ! 13 more for user data
[Link]$ = " " ! Only use data once
!! ************ ADDED *************

This code (which is executed just prior to calling the report user exit for a total
line) is used to format the new data which corresponds to the report total and
add it to the report line before printing.
23. Make the following change in module [Link].
v Locate the line:
EAMRPCFC [S],
v Once the line is located, follow it with the line:
EAMCSASC[S],

In order to make these changes active, module [Link] must be

recompiled and [Link] must be relinked.

Perform Configuration Changes

Add User Logical Names

The utility LOGNAMES.286 described on page “LOGNAMES - Install Preferred
Customer Logical Names” on page 281 can be used to add all of the necessary
logical names to the Master and Alternate (DD) controllers.

Once the utility LOGNAMES.286 has been run initially, it does not have to be run
again to add other user logical names to the [Link] file.

The [Link] file can be edited so the location of the data or executable
files can be changed.

Note: Electronic Marketing makes use of its own descriptor file, [Link].
This file is used by all of the Electronic Marketing executable programs,
including LOGNAMES. Since the logical name for EAMEDESC is not created
until LOGNAMES is executed (unless you use configuration) and since
LOGNAMES needs descriptors from this file to run, execute the following
command before you run LOGNAMES the first time:
DEFINE EAMEDESC=C:\ADX_IPGM\[Link]

This will create a logical name for EAMEDESC to be used in the current
command session and allow LOGNAMES to execute.

The controller configuration application or lognames, can be used to add the

following user logical names.

52 Electronic Marketing PRPQ

 Define: To Be:
EAMFBOPT ADX_IPGM:[Link]
EAMFBMSG ADX_IPGM:[Link]
EAMEDESC ADX_IPGM:[Link]
EAMUXFER ADX_IPGM:EAMUXFER.286
EAMUREFA ADX_IPGM:EAMUREFA.286
EAMUROLP ADX_IPGM:EAMUROLP.286
EAMADDMI ADX_IPGM:EAMADDML.286
EAMBEDES ADXLXAAN::ADX_IPGM:[Link]
EAMFBNEW ADXLXAAN::ADX_IPGM:[Link]
EAMFBOLD ADXLXAAN::ADX_IPGM:[Link]
EAMFBSAV ADXLXAAN::ADX_IPGM:[Link]
EAM: ADXLXACN::C:\ADX_IDT4\EAMX
EAMPANEX ADXLXACN::C:\ADX_IDT4\[Link]
EAMPANEL ADXLXACN::C:\ADX_IDT4\[Link]
EAMFBAUD ADXLXACN::C:\ADX_IDT4\[Link]
EAMFBAUO ADXLXACN::C:\ADX_IDT4\[Link]
EAMCOUPC ADXLXACN::C:\ADX_IDT4\[Link]
EAMCOUPO ADXLXACN::C:\ADX_IDT4\[Link]
EAMFBAPP ADXLXACN::C:\ADX_IDT4\[Link]
EAMFBACT ADXLXAAN::C:\ADX_IDT1\[Link]
EAMFBXFR ADXLXAAN::C:\ADX_IDT1\[Link]
EAMFBFLT ADXLXAAN::C:\ADX_IDT1\[Link]
EAMFBTCM ADXLXAAN::C:\ADX_IDT1\[Link]
EAMFBACX ADXLXAAN::C:\ADX_IDT4\[Link]
EAMIMOV1 ADXLXACN::C:\ADX_IDT4\[Link]
EAMIMWRK ADXLXACN::C:\ADX_IDT4\[Link]

Note: The controller configuration must be activated and the controller re-IPLed for
these logical names to take effect.

The first seven logical names do not define a node name so the local copy of these
files will always be used to improve performance. These files must be created and
maintained as compound files.

Any of these files can be defined on the D: drive if it’s use is necessary for space or
performance reasons and it is available for use.

If [Link] has been moved to the D: drive then, the logical names for
EAMIMOV1 and EAMIMWRK must also be moved to the D: drive.

Configure Background Application

If you intend to start the in-store points transfer processing manually in the store
from the background processing screen, use controller configuration to define a new
background program for EAMUXFER.

If you want the range of transfer files to be different from the range of valid store
numbers, you can accomplish this by entering the low and high store number
separated by a comma as parameters. If you set these numbers to be equal, the
only transfer files to be processed are those for the given store number along with
files having numbers from zero to nine.

If you intend to have the close of the Preferred Customer points activity period
automatically started by the store close procedure, then use system configuration to
define a new background program for EAMUROLP.

Program Name EAMUXFER EAMUROLP

Selection Text or Initial Process Customer Restart Close of Activity Period
Message Transfer Data

Chapter 4. Installation and Configuration 53

 Program Name EAMUXFER EAMUROLP
Parameters N RESTART
IPL Start * Yes *** Yes ***
Start when file server ** Yes *** Yes ***

Notes:
1. * For a single Controller Environment.
2. ** For a multiple Controller Environment.
3. *** For PLD recovery reasons.
4. The controller configuration must be activated and the controller re-IPLed for the
background name to take effect.

Configure Key Sequences for Auxiliary Functions

The optional support for dual cash drawers reserves drawers using the OVERRIDE,
SIGN-OFF, SIGN-OFF key sequence.

If you intend to use the optional VOID, TAX, TOTAL key sequence to manually
enter a tax exemption without a DISCOUNT KEY, you need to alter the Input
Sequence table as follows:
1. From the system main menu,
Type 4 to select Installation and Update Aids
Press ENTER the INSTALLATION AND UPDATE AIDS menu is displayed.
Type 3 to Change Input Sequence Table Data
Press ENTER the INPUT SEQUENCE TABLE UTILITY menu is displayed.
Type 1 to select Input State information
Press ENTER the INPUT STATE TABLE menu is displayed.
Type 1 to Change a Table. The “Type the name of the
table to be processed” field appears.

Type the name of the table to be processed:

C:\ADX_IPGM\EAMS@000
-or-
C:\ADX_IPGM\EAMQ:000

Press ENTER the INPUT STATE TABLE menu is displayed.

Type 2 to select State Definitions
Press ENTER the STATES OF THE TABLE menu is displayed.
2. To allow the OVERRIDE key to be used with the SIGN-OFF key as is required
to reserve a cash drawer,
Type 1 to select Change state definition
the “Change all state definitions.
(Y=Yes/N=No)” screen appears.
Type N for N=No to change all state definitions.
the “name of the state to be processed”
field is displayed.
Type MAIN for the name of the state to be processed.
Press ENTER The STATE MAIN menu is displayed.
Press ENTER the FUNCTION CODES IN THE STATE MAIN menu appears.
Type 1 to select Change function code definition.
“Change all function code definitions
(Y/N)” appears.
Type N for N=No to Change all function code definitions.
Function code definition to be processed screen
appears.
Type 61 to select 61 as the function code definition
Press ENTER the STATE MAIN Function CODE 61 screen appears.

54 Electronic Marketing PRPQ

 This function code should be altered to be not mutually exclusive with position 8
by changing the “8” in the exclusion list to a “0”.
3. To allow the TAX/NO TAX key to be used with the TOTAL key as is required to
key a tax exemption without a DISCOUNT key,
Type 1 to select Change state definition
the “Change all state definitions
(Y=Yes/N=No)” screen appears.
Type N for N=No to change all state definitions.
the “name of the state to be processed”
field is displayed.
Type MAIN for the name of the state to be processed.
Press ENTER The STATE MAIN menu is displayed.
Press ENTER the FUNCTION CODES IN THE STATE MAIN menu appears.
Type 1 to select Change function code definition.
“Change all function code definitions
(Y/N)” appears.
Type N for N=No to Change all function code definitions.
Function code definition to be processed screen
appears.
Type 81 to select 81 as the function code definition
Press ENTER the STATE MAIN Function CODE 81 screen appears.

This function code should be altered to be not mutually exclusive with position 2 by
changing the “2” in the exclusion list to a “0”.

Note: This changed input sequence table is not used until it is activated and the
terminals are reloaded. If these changes are not needed, they need not be
made. If either change is not fully implemented and the key sequence is
attempted, then a B003 operator guidance results.

Configure Optional Customer Number Key

If you intend to use a CUSTOMER NUMBER key to identify keyed, scanned, or
magnetic stripe data as input of a customer number, then you will need to alter the
Input Sequence table.

If you do not wish to key a customer number prior to using this new key
(customer,CUSTOMER as opposed to CUSTOMER, prompt, customer,ENTER) and
you do not wish to reference this function code through the Label Format Table as a
means of identifying scanned customer numbers, then you can select to not allow
data with the CUSTOMER key. This may be desirable when customer numbers are
to be entered through the MSR, since magnetic stripe input is only allowed in
response to the prompt after the CUSTOMER key has been pressed with no data.

The new CUSTOMER key will also not be used until the function code is defined
through option 6.3 in the Preferred Customer options. This option is provided so the
user can select which function code is to be used for this new key definition. While
function code 89 is suggested, it may already be used for some other user function.
If this is the case, a different function code should be used.

Note: The changed input sequence table is not used until it is activated and the
terminals are reloaded.

From the SYSTEM MAIN MENU,

Type 4 to select INSTALLATION AND UPDATE AIDS menu.
Press ENTER the INSTALLATION AND UPDATE AIDS menu is displayed.
Type 3 to Change Input Sequence Table Data.
Press ENTER the INPUT SEQUENCE TABLE UTILITY menu is displayed.
Type 1 to select Input State information.

Chapter 4. Installation and Configuration 55

 Press ENTER the INPUT STATE TABLE menu is displayed.
Type 1 to Change a Table. The “Type the name of the
table to be processed” field appears.

Type the name of the table to be processed:

C:\ADX_IPGM\EAMS@000
-or-
C:\ADX_IPGM\EAMQ:000
Press ENTER the INPUT STATE TABLE menu is displayed.

Next,
Type 2 to select State Definitions.
Press ENTER The STATES OF THE TABLE menu is displayed.
Type 1 to select Change state definition.
The “Change all state definitions
(Y=Yes/N=No)” field is displayed.
Type N for N=No to change all state definitions.
The “name of the state to be processed”
field is displayed.
Type MAIN for the name of the state to be processed.
Press ENTER The STATE MAIN menu is displayed as shown below.

CSIIS031 THE STATE MAIN

Type the necessary information.

BEGINS SEQUENCE Y This state begins an input sequence

(Y = Yes, N = No)

INPUT DEVICE ALLOWED IN THIS STATE

Keyboard Y (Y = Yes, N = No)
Barcode scanner Y (Y = Yes, N = No)
OCR reader Y (Y = Yes, N = No)
Magnetic wand N (Y = Yes, N = No)

For next page, press PgDn.

Press ENTER to process the state's function code definitions.

F1 F2 F3QUIT F4 F5 F6 F7 F8 F9 F10

Press ENTER The FUNCTION CODES IN THE STATE MAIN menu is displayed.
Type 1 to select Change function code definition.
The “Change all function code definitions? (Y/N)”
field is displayed.
Type N for N=No to “Change all Function Code
Definitions”.
The “Function code definition to be
processed: (61-255; either a single value or
a range of values)” field is displayed.
Type 80 for the function code definition to be processed.
Press ENTER The STATE MAIN FUNCTION CODE 80 screen
is displayed as shown below.

56 Electronic Marketing PRPQ

 CSIIS006 STATE MAIN FUNCTION CODE 80

Type the necessary information.

MOTOR KEY Y Function code is a motor key

(Y = Yes, N = No)
CLEAR KEY N Function code is a clear key
(Y = Yes, N = No)
NOTIFICATION Y Notify the application program if an
error is detected (Y = Yes, N = No)

Action if function code is received with no error

MESSAGE LINE 1 ____________________
MESSAGE LINE 2 ____________________

NEXT STATE CURRENT 1-8 character symbolic name, or

CURRENT to stay in the same state,
or LOCK to lock out any more input.

For next page, press PgDn.

If this function code definition is complete, press ENTER.

F1HELP F2 F3QUIT F4 F5 F6 F7 F8 F9 F10

Press F3QUIT to avoid changing the ENTER key definition. The FUNCTION
CODES IN THE STATE MAIN screen is displayed.

Note: The Enter Key was displayed to set defaults for the following steps.

Type 2 to select Add function code definition.

The Function code definition to be processed field is highlighted.

Type 89 for the function code definition to be processed.

Press ENTER The STATE MAIN FUNCTION CODE 89 screen is displayed.

CSIIS006 STATE MAIN FUNCTION CODE 89

Type the necessary information.

MOTOR KEY Y Function code is a motor key

(Y = Yes, N = No)
CLEAR KEY N Function code is a clear key
(Y = Yes, N = No)
NOTIFICATION Y Notify the application program if an
error is detected (Y = Yes, N = No)

Action if function code is received with no error

MESSAGE LINE 1 ____________________
MESSAGE LINE 2 ____________________

NEXT STATE CURRENT 1-8 character symbolic name, or

CURRENT to stay in the same state,
or LOCK to lock out any more input.

For next page, press PgDn.

If this function code definition is complete, press ENTER.

F1HELP F2 F3QUIT F4 F5 F6 F7 F8 F9 F10

Chapter 4. Installation and Configuration 57

 Because the ENTER key was used as a default, you need only change the
NEXT STATE from CURRENT to LOCK.

Press TAB key until you reach the NEXT STATE field.
Type LOCK where CURRENT is shown to change CURRENT to LOCK
Press PgDn the DATA REQUIREMENT INFORMATION screen is displayed.
Type 3 to select Data is optional.
(3 may be there already)
Press PgDn the DATA CHARACTERISTICS OF THE FUNCTION CODE
screen is displayed as shown below.

CSIIS008 STATE MAIN FUNCTION CODE 89

DATA CHARACTERISTICS OF THE FUNCTION CODE

Type the necessary information.

KEYED LABEL Y Keyed label may precede this

function code. (Y = Yes, N = No)

DATA PRECEDE Y Data precedes the function code

(Y = Yes, N = No)

DISPLAY 1 1 = Data is displayed as keyed.

2 = Data is edited and displayed.
3 = Data is not displayed.

SAVED DATA N Data is saved prior to the previous

function code.
(Y = Yes, N = No)

For next page, press PgDn.

If this function code definition is complete, press ENTER.

F1 F2 F3QUIT F4 F5 F6 F7 F8 F9 F10

Press PgDn the DATA LENGTH CHECK INFORMATION screen is displayed.

Type 0 to select the MIN. DATA LENGTH.
(0 may be there already)
Type 50 to select the MAX. DATA LENGTH.
Press PgDn the DATA VALUE CHECK INFORMATION screen is displayed.
Type N for N=No NEED A VALUE CHECK (Y = YES, N = No)
Press PgDn the RELATIVE POSITION INFORMATION screen is displayed.

58 Electronic Marketing PRPQ

 CSIIS012 STATE MAIN FUNCTION CODE 89

RELATIVE POSITION INFORMATION

Type the necessary information.

POSITION 2 Relative position of this function

in the input sequence (0 - 10).

MUTUALLY EXCLUSIVES 1
3 List all other positions that
4 can NOT co-exist in the same
5 input sequence with this function
6 code (0 - 10).
7
8
9
10
0
For next page, press PgDn.
If this function code definition is complete, press ENTER.

Type 2 for POSITION Relative position of this function.

(2 may already be there.)
Type 1 and
3 thru 10 as MUTUALLY EXCLUSIVES as is shown in
the screen below to make them mutually
exclusive.
Press ENTER to complete this function code definition.
Press F3QUIT until the INPUT STATE TABLE menu appears.
Select 7 to activate.

Type the name of the table to be processed:

C:\ADX_IPGM\EAMS@000
-or-
C:\ADX_IPGM\EAMQ:000

Press ENTER

Along with defining the new CUSTOMER key in the Input Sequence Table, you also
need to place this function code on the keyboard through terminal configuration.

To alter the terminal keyboard layout, from the INSTALLATION AND UPDATE AIDS
menu,
Type 1 to Change Configuration Data.
Press ENTER the Configuration menu is displayed.
Type 1 to select Terminal Configuration.
Press ENTER The TERMINAL CONFIGURATION menu is displayed.
Type 2 to select keyboard layouts.
Press ENTER The KEYBOARDS LAYOUTS menu is displayed.
Type 2 to Change/Display a keyboard layout.
Press ENTER The “Type the name of the terminal
keyboard layout being processed” field appears.
Type ADXKBD02 (usually ADXKBD02 for Supermarket).
The CHANGE/DISPLAY KEYBOARD LAYOUT ADXKBD02
screen is displayed.

You can now add function code 89 (or whatever function code you have chosen for
the CUSTOMER key ) to an unused key position or overlay a key position whose
function is not required. When complete,

Press ENTER

Chapter 4. Installation and Configuration 59

 The KEYBOARD LAYOUTS screen is displayed. Press PF3 until the Configuration
screen is displayed.

Note: This change is not effective until the new terminal configuration is activated
and the new keyboard table is read into the terminals. It is not necessary to
run STC to change the keyboard layout.

The final step is to set the key definition for the customer entry key you have just
defined to 89 (or whatever number you have designated). To accomplish this, in the
Preferred Customer Options Report file, update option 6.3 KEY DEFINITION FOR
CUSTOMER ENTRY KEY. See “Preferred Customer Options Report” on page 264
for additional information.

Install the In-Store Enrollment Program

The installation instructions for the in-store enrollment program are provided
separately because there is no requirement to install this program to run the
preferred customer code. This program should be installed based upon the need to
run it in the store.
1. Module EAMENROL.286 must be copied to ADX_IPGM and, if you are on a
LAN system, the system file utilities need to be used to assure the file
distribution type is compound per update. The programs can be found on the
Electronic Marketing application diskette in the ADX_IPGM subdirectory.
2. If you wish to run this program as a user procedure in order to get the security
of sign-on authorization then, rename EAMENROL.286 to EAMUPMxL.286
(where x is the procedure number from one to eight).
3. A user procedure descriptor (in report descriptors range 3222-3229) must be
altered through personalization to say “Preferred Customer Enrollment
Procedure”.
4. If you wish to run this program as a secondary application rather than as a user
procedure, the system configuration application must be used to add a
secondary application for the enrollment procedure as:
C:\ADX_IPGM\EAMENROL.286.
5. The 19 EAMEN*.DAT modules must be copied to the ADX_IPGM directory on
the C: drive. These DAT files are screen files for the enrollment program. If you
are on a LAN system, the system file utilities need to be used to assure that the
file distribution type for each of these 19 files is compound per update.
6. The utility LOGNAMES.286 (see “LOGNAMES - Install Preferred Customer
Logical Names” on page 281.) can be used to add all of the following logical
names. If you have already run the LOGNAMES.286 utility previously, it is not
necessary to run it again. As an alternative, the controller configuration
application can be used to add the following user logical names:
Define: To Be:
EAMENSCR ADXLXAAN::C:\ADX_IPGM\[Link]
EAMENMSG ADXLXAAN::C:\ADX_IPGM\[Link]
EAMEN01S ADXLXAAN::C:\ADX_IPGM\[Link]
EAMEN02S ADXLXAAN::C:\ADX_IPGM\[Link]
EAMEN03S ADXLXAAN::C:\ADX_IPGM\[Link]
EAMEN04S ADXLXAAN::C:\ADX_IPGM\[Link]
EAMEN05S ADXLXAAN::C:\ADX_IPGM\[Link]
EAMEN06S ADXLXAAN::C:\ADX_IPGM\[Link]
EAMEN07S ADXLXAAN::C:\ADX_IPGM\[Link]
EAMEN08S ADXLXAAN::C:\ADX_IPGM\[Link]
EAMENA2S ADXLXAAN::C:\ADX_IPGM\[Link]
EAMENA3S ADXLXAAN::C:\ADX_IPGM\[Link]
EAMENA4S ADXLXAAN::C:\ADX_IPGM\[Link]

60 Electronic Marketing PRPQ

 EAMENA5S ADXLXAAN::C:\ADX_IPGM\[Link]
EAMENA6S ADXLXAAN::C:\ADX_IPGM\[Link]
EAMENA7S ADXLXAAN::C:\ADX_IPGM\[Link]
EAMENA8S ADXLXAAN::C:\ADX_IPGM\[Link]
EGHXAACF ADXLXAAN::C:\ADX_IPGM\[Link]
EGHXESGS ADXLXAAN::C:\ADX_IPGM\[Link]
EAMFBCUS ADXLXACN::C:\ADX_IDT1\[Link]
EAMFBCHG ADXLXACN::C:\ADX_IDT4\[Link]

Note: The controller configuration must be activated and the controller re-IPLed
for these logical names to take effect. The process must be repeated for
all controllers in a LAN system.

The logical names EAMEN02S to EAMEN08S are used only if the option to
support an in-store enrollment file is selected while the logical names
EAMENA2S to EAMENA8S are used only if support for an in-store enrollment
file is not selected. Thus if you know how this option will always be selected,
you only need to install one or the other of these sets of seven logical names.

If the option might change, both sets of logical names must be defined. If you
decide that you don’t really need all of these logical names because you plan to
always have or not use an in-store enrollment file, you can also delete the .DAT
files that match the deleted logical names.

Install the Batch Keyed File Maintenance Program

The installation instructions for the BATCH keyed file maintenance program are
provided separately because there is no requirement to install this program to run
the preferred customer code. This program should be installed based on the need
to use it to process host data and must be installed if the Selective Customer
Report is to be used to alter customer activity records for such things as targeting
coupons or messages.

Note: Batch provides functions similar to ADDMI for all keyed files.

Install Batch Program

Module EAMUBATP.286 must be copied to the ADX_IPGM directory on the C: drive
and, if you are on a LAN system, the module must be given the distribution attribute
of Compound per Update.

Configure Logical Names for the Batch Program

Controller configuration must be activated and the controller re-IPLed for these
logical names to take effect. The utility LOGNAMES.286 (see “LOGNAMES - Install
Preferred Customer Logical Names” on page 281) can be used to add all of the
necessary logical names to the Master and Alternate (DD) store controllers. If you
have run the LOGNAMES.286 utility previously, there is no need to run it again.

As an alternative, controller configuration can be used to add the following user

logical names:
Define: To Be:
EAMBATCH ADXLXACN::C:\ADX_IDT1\[Link]
EAMBINPR ADXLXACN::C:\ADX_IDT1\[Link]
EAMBERRD ADXLXACN::C:\ADX_IDT1\[Link]
EAMBREPT ADXLXACN::C:\ADX_IDT4\[Link]
EAMBSTAT ADXLXACN::C:\ADX_IDT4\[Link]
EAMDMERB ADXLXACN::C:\ADX_IDT4\[Link]
EAMUBATP ADX_IPGM:EAMUBATP.286

Chapter 4. Installation and Configuration 61

Use Controller Configuration to Define a New Background Program
Program Name EAMUBATP
With the Descriptor Process keyed file maintenance
Parameters N
IPL Start * Yes ***
Start when file server ** Yes ***

Notes:
1. *For a single Controller Environment.
2. **For a multiple Controller Environment.
3. ***For PLD recovery reasons.
4. The controller configuration must be activated and the controller re-IPLed for the
background name to take effect.

Add Messages Used by the Batch Program

The program EAMBATZF must be run once from the command line to add the
following messages to the file ADXCSOZF for display on the system messages
screen.
U210 ERROR IN PROCESSING BATCH KEYED FILE MAINTENANCE
U211 VITAL FILE NOT AVAILABLE, BATCH PROCESSING HALTED
U212 BAD BATCH FILE INPUT, BATCH PROCESSING HALTED
U213 BAD BATCH INPUT DATA DISCARDED, GOOD DATA PROCESSED

Executing the Batch Program

The EAMUBATP program can be started in any of four ways:
1. By a “Start User Program” command from the host
2. From the background application screen (SysRq B)
3. From a user application or an application exit using the ADXSTART system
interface
4. On a controller IPL.

It operates on the data in C:ADX_IDT1\[Link].

Install Background Panel Filters as Needed

The presence of the filter file [Link] on ADX_IDT1 satisfies the need for
filtering panel data as it is moved into the Panel file. Additional filter files can be
defined which will cause additional panel files to be created at store closing. The
additional filter files have names of the form [Link] where x is between
one and nine.

If any of these filter files are available on ADX_IDT1 at store close, they are used to
create or update a panel file with the name [Link]. The filter files and
panel files defined here have the same format as the primary filter and panel files
([Link] and [Link]), but these new panel files are created by a
separate process at store closing based upon the presence of an associated filter
file. As an alternative, the controller configuration application can be used to add the
following list of logical names as needed. Controller configuration must be activated
and the controller re-IPLed for these logical names to take effect. The utility
(LOGNAMES.286 “LOGNAMES - Install Preferred Customer Logical Names” on
page 281
62 Electronic Marketing PRPQ
 page 281) can be used to add all of the necessary logical names to any controller.
The default version of [Link] will only add the logical names for the first
two background panel filters and files. If you have run the LOGNAMES.286 utility
previously, there is not need to run it again.
Define: To Be:
EAMFBFL1 ADXLXAAN::C:\ADX_IDT1\[Link]
EAMPANL1 ADXLXACN::C:\ADX_IDT4\[Link]
EAMFBFL2 ADXLXAAN::C:\ADX_IDT1\[Link]
EAMPANL2 ADXLXACN::C:\ADX_IDT4\[Link]
EAMFBFL3 ADXLXAAN::C:\ADX_IDT1\[Link]
EAMPANL3 ADXLXACN::C:\ADX_IDT4\[Link]
EAMFBFL4 ADXLXAAN::C:\ADX_IDT1\[Link]
EAMPANL4 ADXLXACN::C:\ADX_IDT4\[Link]
EAMFBFL5 ADXLXAAN::C:\ADX_IDT1\[Link]
EAMPANL5 ADXLXACN::C:\ADX_IDT4\[Link]
EAMFBFL6 ADXLXAAN::C:\ADX_IDT1\[Link]
EAMPANL6 ADXLXACN::C:\ADX_IDT4\[Link]
EAMFBFL7 ADXLXAAN::C:\ADX_IDT1\[Link]
EAMPANL7 ADXLXACN::C:\ADX_IDT4\[Link]
EAMFBFL8 ADXLXAAN::C:\ADX_IDT1\[Link]
EAMPANL8 ADXLXACN::C:\ADX_IDT4\[Link]
EAMFBFL9 ADXLXAAN::C:\ADX_IDT1\[Link]
EAMPANL9 ADXLXACN::C:\ADX_IDT4\[Link]

Note: The presence of the filter file determines the need for additional background
creation and filtering of panel files. However, without the appropriate logical
name, the filter file will not be found.

Install Electronic Marketing Data Files

Modules [Link], [Link], and [Link] provide default
Electronic Marketing options, messages, and descriptors respectively. They must be
copied to the ADX_IPGM directory on the C: drive. Do not copy [Link]
onto your system if you have the 1991 version of Electronic Marketing installed.
Instead, use the utility program FIXR1OPT to format the two options files of the
1991 level of Electronic Marketing into the one large options file handled by the
newer code level. This allows users of the prior code level to migrate to a level of
the options file that matches their current options usage.

After you install these files, if you are on a LAN system, you can use the system file
utilities to ensure that the distribution type is compound per update.

Chapter 4. Installation and Configuration 63

64 Electronic Marketing PRPQ
Chapter 5. Personalization
Activate Terminal and Controller Exits
After the preferred customer code has been installed and terminal sales and
checkout support recompiled then the user exits used by the new code must be
activated for the new functions to be available.

To activate terminal exit functions from the Supermarket Application personalization

menu type:
1 to alter Terminal options
1 to change options and enter options number
20 to select Exit options then place a ”Y” beside the following exits:

01, 02, 03, 07, 08, 14, 18, 20, 21, 23, 24,
27, 28, 30, 31, 37, 39, 40, 42, 43, 51, 53, 54

Also if you have suspend/retrieve installed, select exit 57.

To activate controller exit functions from the personalization menu type:

2 to alter Store options
1 to change options
15 to select Exit options then place a ”Y”
beside the following exits:

01, 03, 04, 06, 11, 12, 13, 14, 15, 16, 17

These changes activate the needed user exits. The changes are not active until the
terminals go through LOADING TERMINAL OPTIONS. The Preferred Customer
Options Report provided as module EAMRPU7L.286 will verify that the correct user
exits have been activated for the default terminal (000). Note that print options for
data entry determine whether the customer name and number are printed on the
customer receipt and/or summary journal at the time the number is entered.

Personalize Terminal Sales Descriptors

The utility DESCADDS.286 described in “DESCADDS - Auto Install of New Sales
Descriptors” on page 278, can be used to add all of the necessary sales descriptors
to this file. You can alter or delete these default sales descriptors from the file
[Link] before the utility is executed. The changes are not active until the
terminals go through LOADING TERMINAL OPTIONS.

The following terminal sales descriptor numbers need to be updated with the text
provided:
1234567890123456789012345678901234567890
32 "ENTER OVERRIDE OR PRESS CLEAR "
146 "BO"
147 "PC"
148 "NP"
150 "RD"
170 "QTY NOT SATISFIED"
171 "TOO MANY COUPONS "
172 " NEGATIVE TOTAL"
315 "POINTS APPLY"
320 "POINTS ITEM "
321 "LINKS TO DPT"

926 "OVERRIDE TO ADD OR CLEAR TO REKEY "

© Copyright IBM Corp. 1991 2000 65

 927 "AM PM"
928 "*BU*"
929 " "
B600 = 930 " POINTS ENTRY REQUIRES CUSTOMER # "
B601 = 931 " HOME STORE MUST REDEEM POINTS"
B602 = 932 " MORE POINTS NEEDED FOR DISCOUNT"
B603 = 933 " NO AVAILABLE DRAWER xxxxxxxxx"
B604 = 934 "CHECK KEYED CUSTOMER NUMBER"
B605 = 935 "CHECK CUSTOMER NUMBER "
B606 = 936 " REDEMPTION MUST BE POSITIVE"
B607 = 937 " BONUS POINT LIMIT CHECK "
B608 = 938 " ASK FOR CARD CLEAR TO CONTINUE "
B609 = 939 "CHECK KEYED COUPON NUMBER "

B610 = 940 "LIMITED NUMBER OF COUPONS PER ORDER"

B611 = 941 "COUPON HAS EXPIRED "
B612 = 942 "MINIMUM SALE NOT SATISFIED "
B613 = 943 "PLEASE WRITE .XX ON COUPON "
944 " "
945 " "

946 "RESERVE DRAWER "

947 "NO SALE **"
948 " FREE SPACE = xxxxx, ARRAY SIZE = xxxx"
949 "*ERROR* USER OPTION DATA IS INCOMPLETE"
950 "ERROR ACCESSING USER OPTIONS "
951 "ERROR ACCESSING USER MESSAGES "
952 "ERROR ACCESSING ACTIVITY FILE "
953 "ERROR ALLOCATING COUPON BUFFER"
954 "ERROR SAVING USER MESSAGES "
955 " "
956 " ERROR = "
957 " TRACE INFO = "
958 " LAST LINE IN EXIT CODE = "
961 " ENTER TOTAL VALUE TO BE DISCOUNTED "
962 " ENTER PRICE PER LB FOR DISCOUNTED ITEM "
963 " ENTER CUSTOMER ID OR PRESS CLEAR "
964 " ENTER EXPIRATION DATE AS MMYY "
1234567890123456789012345678901234567890

To view or alter these descriptors using the personalization application, from the
system main menu select:
1 to select the SUPERMARKET application
6 to select Personalization
4 to alter Descriptors
1 to select Sales Descriptors

Then select the descriptor number or range of descriptor numbers as defined above
to view or alter the descriptors.

Personalize Report Descriptors

The utility DESCADDR.286 (see “DESCADDR - Auto Install of New Report
Descriptors” on page 278) can be used to add all of the necessary report
descriptors to this file. If you do not like or need all of the default report descriptors,
you can alter or delete these descriptors from the file [Link] before the
utility is executed. The default user report menu descriptors will be added through
this utility. If any of the user reports are not installed or renamed then the file
[Link] will have to be modified accordingly. The changes are not active
until the terminals go through LOADING TERMINAL OPTIONS.

The following report descriptor numbers need to be updated with the text provided:

66 Electronic Marketing PRPQ

 1234567890123456789012345678901234567890
4331 "(3 = Unit Priced Coupon) "
4332 "(4 = Coupon value is net item value) "
4333 "(Use 3 to see MFR# and SEQ#) "
4334 "MFR Number "
4335 "Coupon Value "
4336 "Lmt/Tran & Items/Cpn"
4337 "Coupon Sequence (0-20) "
4338 "Minimum by MFR "
4339 "Minimum by Dept"
4340 "Minimum Purchase Amt "
4341 "Item Not in Purchase Minimum "
4342 "Coupon Gives Bonus Points "
4343 "Points Only Item "
4344 "“Links To Deposit "
4345 "“Points Apply to Item "
4346 "Points Only Coupon "
4347 "Separate Minimum per Coupon "
4348 "Validate Dept "
4349 "(3 = Unit Priced Weight Item with Tare) "
4350 "Tare Code "
4351 "Unit Price /LB "
4352 "AUTOMATIC CLOSE OF ACTIVITY PERIOD "
4353 "AUTOMATIC PICKUP OF PAPERLESS COUPONS "
4354 "PROCESSING TRANSFERS FROM OTHER STORES "
4355 "CREATE PANEL FILE xxxxxxxx AT CLOSE "
4356 "UPDATE DOLS AFTER CLOSING ITEM MOVEMENT "
4357 "UPDATE DOLS WHILE CLOSING ITEM MOVEMENT "
4358 "STAGE ITEM MOVEMENT TO NATIVE FORMAT "
4359 "UPDATE DOLS WHILE STAGING ITEM MOVEMENT "
4360 "UPDATE DOLS AND WAIT FOR COMPLETION "
4361 " WAITING FOR EAMUDOLS TO COMPLETE "
4362 "AUTO START BATCH MAINTENANCE "
4363 "AUTO START TRANSFER PROCESSING "
4364 " ERROR = "
4365 " TRACE INFO = "
4366 " LAST ENTRY = "
4367 " LAST LINE IN EXIT = "
4368 " LINE = "
4370 "Reconciled "
4371 "Not Reconciled"

The following report descriptor numbers need to be updated to add the correct titles
to the user report menu screen. If any of the user reports are renamed to another
user report or not installed, then this information will have to be modified
accordingly.
To select text for User Report 3 menu descriptor
3232 "Selective Item Record Report"

To select text for User Report 5 menu descriptor

3234 "Preferred Customer Audit Log Report"

To select text for User Report 6 menu descriptor

3235 "Preferred Customer Exception Log Report"

To select text for User Report 7 menu descriptor

3236 "Preferred Customer Options Report"

To select text for User Report 8 menu descriptor

3237 "Selective Preferred Customer Report"

Chapter 5. Personalization 67
 The following report descriptor numbers need to be updated to add the correct titles
to the user procedure menu screen. If any of the user procedures are renamed to
another user procedure or not installed then this information will have to be
modified accordingly.
To select text for User Procedure 2 menu descriptor
3223 "Preferred Customer Enrollment Procedure "

To select text for User Procedure 3 menu descriptor

3224 "Manual Close of Points Activity Period "

To select text for User Procedure 4 menu descriptor

3225 "Targeted Coupon Message Maintenance "

To view or alter these descriptors using the personalization application, from the
system main menu select:
1 to select the SUPERMARKET application
6 to select Personalization
4 to alter Descriptors
3 to select Report Descriptors

Then select the descriptor number or range of descriptor numbers as defined above
to view or alter the descriptors.

Personalize Electronic Marketing Report Descriptors

The report descriptors for the Electronic Marketing reports and utilities are delivered
in the file named [Link]. These descriptors do not normally need to be
modified. If you find it necessary to change these descriptors you can use the
Electronic Marketing utility, DESCADDE.286 described elsewhere to do this or you
can use the following procedure. Since it is in the same format as the sales
descriptor file, [Link], you can use the personalization procedure to alter
the contents of this file if you wish. You need to save [Link] as
[Link], copy [Link] to [Link] and then select to
personalize sales descriptors. Because of the file switch, you will see the Electronic
Marketing report descriptors. Once the personalization is complete, you must
restore [Link] to [Link] and then restore [Link] to
[Link].

68 Electronic Marketing PRPQ

Part 2. Operations and Reports
Chapter 6. Personalization of Preferred Customer Options and Messages 75
Preferred Customer Options File (EAMFBOPT) . . . . . . . . . . . . . 75
Preferred Customer Options Default . . . . . . . . . . . . . . . . 76
Preferred Customer Options Descriptions . . . . . . . . . . . . . . 76
Program name . . . . . . . . . . . . . . . . . . . . . . . 76
Deactivate Preferred Customer Processing . . . . . . . . . . . . 77
Deactivate Electronic Marketing Code . . . . . . . . . . . . . . 78
Rain check ID Definition . . . . . . . . . . . . . . . . . . . 78
UPC Displacement for Preferred Customer Linked Items . . . . . . . 79
Coupons Targeted for the First Use of a Customer Card. . . . . . . . 81
Activity File Size . . . . . . . . . . . . . . . . . . . . . . 81
Activity Record Size . . . . . . . . . . . . . . . . . . . . . 82
Bytes Before the Customer Name in Activity Record . . . . . . . . . 82
Format of Customer Name in Activity Record . . . . . . . . . . . . 83
Activity Options Default . . . . . . . . . . . . . . . . . . . . 83
Deactivate Activity Options for All Preferred Customers . . . . . . . . 84
Activate Activity Options for All Preferred Customers . . . . . . . . . 84
Collect Panel Data for All Customers . . . . . . . . . . . . . . . 85
Maximum Number of Coupons Targeted Per Customer . . . . . . . . 85
Create and Access Customer Transfer File . . . . . . . . . . . . 86
Automatically Process In-Store Transfers Each Hour . . . . . . . . . 86
Store Coupons Reduce Points . . . . . . . . . . . . . . . . . 87
Taxes Increase Points . . . . . . . . . . . . . . . . . . . . 87
Keyed Customer Numbers Require a Manager’s Override . . . . . . . 88
Validate Automatic Preferred Customer Store Coupons . . . . . . . . 88
Use Coupon Families in Validation of UPC 5 Coupons . . . . . . . . 89
Manager’s Override Required for New Customers . . . . . . . . . . 90
Show Points in Whole Dollar Amounts . . . . . . . . . . . . . . 90
Personalization Message Format . . . . . . . . . . . . . . . . 91
Ratio of Points Per Cents Purchased . . . . . . . . . . . . . . . 92
Points Rounding Selection. . . . . . . . . . . . . . . . . . . 92
Bonus Item Points Limit . . . . . . . . . . . . . . . . . . . 93
Preferred Coupons Buffered in Memory . . . . . . . . . . . . . . 93
Maximum Points to Carry from One Period to Another . . . . . . . . 94
Automatic Close of the Points Activity Period . . . . . . . . . . . . 94
Automatic Execution Time for Batch Updates . . . . . . . . . . . . 95
Automatic Execution Time for Transfer Processing . . . . . . . . . . 96
Coupon Velocity Code Range for Preferred Customers . . . . . . . . 97
Velocity Code Range for Reusable Targeted Coupons . . . . . . . . 97
Valid Range of Non-Home Store Numbers . . . . . . . . . . . . . 98
Automatic Execution Time for Reference Processing . . . . . . . . . 98
Multiplier for Coupon Minimum Purchase Amounts . . . . . . . . . . 99
Key Definition for Customer Entry Key . . . . . . . . . . . . . . 99
Home Store Location in Customer Number . . . . . . . . . . . . 100
Category Number to Uniquely Identify Customer Numbers . . . . . . 101
Validation Digits in Customer Number . . . . . . . . . . . . . . 101
Count Home Store Numbers Supported by This Store . . . . . . . . 102
Count Home Store Numbers Supported Only by This Store . . . . . . 102
Home Store Numbers Supported by This Store . . . . . . . . . . 103
Modulo Check Customer Numbers During Enrollment . . . . . . . . 103
Log Enrollment Alterations to a Separate Sequential File . . . . . . . 104
Allow Erase of Customer Points . . . . . . . . . . . . . . . . 104
Form Number Required on Redemption, Adjustment, and/or Rain check 105

© Copyright IBM Corp. 1991 2000 69

 Employee Number Required on Redemption, Adjustment, and/or Rain
check . . . . . . . . . . . . . . . . . . . . . . . . . 106
Selectively Deactivate Each of the Seven Enrollment Functions . . . . 106
Run the Enrollment Procedure Without an Enrollment File . . . . . . 107
Enrollment Zip Fields Are Numeric and Packed . . . . . . . . . . 107
Only Allow One Terminal to Have Negative Transactions . . . . . . . 108
Define Which Taxes to Turn On With the Tax/NoTax Key . . . . . . . 108
KIOSK Points Message Offset . . . . . . . . . . . . . . . . . 109
Maximum Item Record Descriptor Length. . . . . . . . . . . . . 109
Length of Enrollment State Field . . . . . . . . . . . . . . . . 110
Length of Enrollment ZIP Field. . . . . . . . . . . . . . . . . 110
Length of Enrollment ZIPEXT Field . . . . . . . . . . . . . . . 111
Count of Customer Defined Demographic Fields . . . . . . . . . . 111
Length of Enrollment Social Security Field . . . . . . . . . . . . 112
Accumulate Ratio of PLU Entries to DEPT Key Entries . . . . . . . . 112
Accumulate Keyed Versus Scanned Totals by Department . . . . . . 112
Weight Items Do Not Require Weight Key . . . . . . . . . . . . 113
Display Backup Indicator at Registers . . . . . . . . . . . . . . 113
Allow Tax Exemption Without a Discount Key . . . . . . . . . . . 114
Cash Checks Using a Sales Transaction . . . . . . . . . . . . . 114
Remind Operator to Take Customer’s Money . . . . . . . . . . . 115
Interpret Restricted Time Periods as Unrestricted Times . . . . . . . 115
Support for Multiple Cash Drawers . . . . . . . . . . . . . . . 116
Show Time in 12-Hour Format . . . . . . . . . . . . . . . . . 117
Check the Sum of All Voids at Each Void Entry . . . . . . . . . . 117
Highlight the Printing of Automatic Coupons . . . . . . . . . . . . 118
Highlight Printing of All Exceptional Entries . . . . . . . . . . . . 118
Print Available Targeted Coupons on a Customer Receipt . . . . . . . 119
Remind Checker to Ask for Customer Card . . . . . . . . . . . . 119
Use Period Points for Boundary Options . . . . . . . . . . . . . 120
Only Points in This Period Are Available for Redemption . . . . . . . 120
New Customer Message Starts Each New Activity Period. . . . . . . 121
New Customer Coupons Start Each New Activity Period . . . . . . . 121
Keep Monthly Previous Points Activity for Customers . . . . . . . . 122
Tenders Using Preferred Customer Number as Account Number . . . . 122
Tenders Using Alternate Customer Number as Account Number . . . . 123
Override Is Required to Change Tender Verification Number. . . . . . 124
Operator’.s Override Is Sufficient to Change Tender Number . . . . . 124
Count of Boundary Levels Defined for Special Processing . . . . . . 125
Points Total That Defines Boundary . . . . . . . . . . . . . . . 125
Boundary Repeats at Each Multiple of the Boundary Points . . . . . . 126
Bonus Points to be Awarded at Boundary Crossing . . . . . . . . . 126
Level Increment to be Awarded at Boundary Crossing . . . . . . . . 126
Message to be Presented at Boundary Crossing . . . . . . . . . . 127
Examples of Different Boundary Processing Options Selected . . . . . 127
Keep Old Period Audit Log Data . . . . . . . . . . . . . . . . 129
Append Audit Data to Panel File . . . . . . . . . . . . . . . . 130
Keep Automatic Coupon Totals in Department File Exit Fields . . . . . 130
Exclude Automatic Coupons from Reported Coupon Counts . . . . . . 131
Add Period Summary String to Panel File . . . . . . . . . . . . 131
Deposit Automatic Coupons Into Miscellaneous Accounts . . . . . . . 132
Point Ranges for Period Close Report . . . . . . . . . . . . . . 133
Automatic Discounts for Associated Points Ranges . . . . . . . . . 134
Exclude Non-Points Items from Minimum Purchase Limits . . . . . . 134
Add Customer Number to Coupon Tracking File Records . . . . . . . 135
Always Use the Manufacturer Number From a Coupon Record. . . . . 135

70 Electronic Marketing PRPQ

 Stage Activity File at Each Close of Period . . . . . . . . . . . . 136
Treat All Non-Preferred Customers as Rain check Customers . . . . . 136
Remove Doubled Coupons from Store Coupons by Department . . . . 137
Override Needed for Keyed Preferred Customer Coupons . . . . . . 138
Accept Electronic and Paper Vendor Coupons on the Same Item . . . . 138
Accept Electronic and Paper Store Coupons on the Same Item . . . . 139
Double Coupons are Available only to Preferred Customers . . . . . . 139
Save Date of Last Sale for Items at Close of Item Movement . . . . . 140
Use Promotion Codes for Coupon Validation . . . . . . . . . . . 140
Show Only Paper Coupons in Cash Drawer Reports . . . . . . . . 142
Bypass Journal Printing of Automatic Coupon Rejections . . . . . . . 143
Bypass Receipt Printing of Targeted Coupon Numbers . . . . . . . . 143
Match Coupons Against Cross Promotional Group . . . . . . . . . 144
Automatic Tare from Weight Item Records . . . . . . . . . . . . 144
Bypass Fixed Targeted Message if Promotion Text Provided . . . . . . 146
Validate Expiration Date with MSR Entry of Customer ID . . . . . . . 147
Deactivate Unique Electronic Marketing Exit Code . . . . . . . . . 148
Use Compressed Print in the Selective Customer Report . . . . . . . 148
Use 132 Character Lines in the Selective Customer Report . . . . . . 148
Address Label Size Definitions for the Selective Customer Report . . . 149
Selectively Deactivate Selective Customer Report Functions. . . . . . 150
Line 23 is Reserved . . . . . . . . . . . . . . . . . . . . 150
All Coupons Require at Least Department Level Validation . . . . . . 150
Validate All Department Keyed Coupons by Department . . . . . . . 151
Sequence Number and Velocity Code in Store Coupon UPCs . . . . . 152
Store Coupons Logged in the Coupon Tracking File . . . . . . . . . 152
Vendor Coupons Logged in the Coupon Tracking File . . . . . . . . 152
Doubled Coupons Logged in the Coupon Tracking File. . . . . . . . 153
Coupon Tracking File Entries in Compressed Format . . . . . . . . 153
Manufacturer Number to Identify UPC 5 Store Coupons . . . . . . . 154
Range of Coupon UPCs to Log in the Coupon Tracking File . . . . . . 154
Range of Departments to Validate by Subtotal Group . . . . . . . . 154
List of Guidances to be Lowered to Allow Operator Override. . . . . . 156
Doubled Coupon Value Limit Per Coupon . . . . . . . . . . . . 158
No Doubling of Coupons Over the Value Limit . . . . . . . . . . . 158
Value Limit Applies to the Sum of the Coupon and the Double . . . . . 159
Minimum Transaction Size for Coupon Doubling . . . . . . . . . . 159
Doubled Coupon Count Limit Per Order . . . . . . . . . . . . . 160
Purchase Amount for the Coupon Doubling Count Limit . . . . . . . 160
Limit on the Number of Identical Coupons to be Doubled in an Order 161
Manual Coupon Doubling Allowed, Lookup Key Code Defined . . . . . 161
Days of Week on Which Coupon Doubling is Not Active . . . . . . . 162
Line 29 is reserved.. . . . . . . . . . . . . . . . . . . . . 162
End of Options Indicator . . . . . . . . . . . . . . . . . . . 162
Selective Item Record Report Options . . . . . . . . . . . . . . . 163
Allow Saving of Report Data to File (31.1) . . . . . . . . . . . . 163
Allow Printing of the Report with No Display (31.2) . . . . . . . . . 164
Allow Resetting of Item Movement (31.3) . . . . . . . . . . . . . 164
Allow Creation of Maintenance Batches (31.4) . . . . . . . . . . . 164
Allow Deletion of Item Records (31.5) . . . . . . . . . . . . . . 165
Allow Creation of Item Movement Lists (31.6) . . . . . . . . . . . 165
Exit Field 1 Contains Packed Decimal Data (31.7) . . . . . . . . . 165
Exit Field 2 Contains Packed Decimal Data (31.8) . . . . . . . . . 166
Report Exit 1 and Exit 2 as a Single Field (31.9) . . . . . . . . . . 166
Use a One Page Menu for All 16 Search Selections (31.10) . . . . . . 166
Printed Reports are in Compressed Mode (32.1) . . . . . . . . . . 167

Part 2. Operations and Reports 71

 Printed Reports Use 132 Character Line Formats (32.2) . . . . . . . 167
Automatically Update Item Family with the Low 3 Link Digits (32.3) . . . 167
All Batches Are Created as DDM Operator Controlled Batches (32.4) 168
All Batches Are Created as ADDMI Batches (32.5) . . . . . . . . . 168
All Batches Are Created as ADDMI Immediate Updates (32.6) . . . . . 168
Automatically Update Promotion Codes to Equal the Link Value (32.7) 169
Preferred Customer Messages File (EAMFBMSG) . . . . . . . . . . . 169
Message Zero: Normal points message . . . . . . . . . . . . . . 171
Message One: Points message for non-home store customers . . . . . . 171
Message Two: Points message for new customers . . . . . . . . . . 171
Message Three: Prints message for customers not enrolled . . . . . . . 171
Message Four: Personalization message for receipt . . . . . . . . . . 171
Message Five: Out of store transfer message . . . . . . . . . . . . 172
Message Six: Rain check message . . . . . . . . . . . . . . . . 172
Message Seven: Bonus points message . . . . . . . . . . . . . . 172
Message Eight: Redeemed points message . . . . . . . . . . . . . 172
Message Nine: Available targeted coupons header message . . . . . . 172
When Messages Are Shown . . . . . . . . . . . . . . . . . . 172
Messages Associated with Customer Identification . . . . . . . . . . 172
Messages Associated with Other Customer Interests . . . . . . . . . 173
Data Entry Line . . . . . . . . . . . . . . . . . . . . . . . 173
How to Activate Additional Messages . . . . . . . . . . . . . . . 173
How to Make Changes to the Messages File . . . . . . . . . . . . 173
Default Preferred Customer Messages File . . . . . . . . . . . . . 174

Chapter 7. Operations . . . . . . . . . . . . . . . . . . . . . 177

How to Enter a Customer ID Number . . . . . . . . . . . . . . . . 177
Establishing a New Customer Identification Number . . . . . . . . . . . 178
When to Enter Customer ID Number with Targeted Coupons . . . . . . . 178
How to Enter Multiple Customer ID Numbers per Transaction . . . . . . . 179
Procedures for Preferred Customer Identification . . . . . . . . . . . . 179
Enrolled Preferred Customer Receipt . . . . . . . . . . . . . . . . 180
Regular Customer Receipt . . . . . . . . . . . . . . . . . . . . 180
In-Store Enrollment Procedure Screens . . . . . . . . . . . . . . . 181
Preferred Customer Enrollment . . . . . . . . . . . . . . . . . . 183
Changing a Customer Record . . . . . . . . . . . . . . . . . . . 185
Erase a Customer Record . . . . . . . . . . . . . . . . . . . . 187
Displaying a Customer Record . . . . . . . . . . . . . . . . . . 189
Redeeming an Award . . . . . . . . . . . . . . . . . . . . . . 191
Adjusting a Customer Record . . . . . . . . . . . . . . . . . . . 193
Entering a Rain check . . . . . . . . . . . . . . . . . . . . . . 195
Sample Coupons . . . . . . . . . . . . . . . . . . . . . . . 197
Bonus Point Coupons . . . . . . . . . . . . . . . . . . . . . . 197
Limit Per Transaction/Items Per Coupon . . . . . . . . . . . . . . . 199
Final Value Coupons . . . . . . . . . . . . . . . . . . . . . . 201
Linked Coupons (Discount/Redeem Points) . . . . . . . . . . . . . . 202
Linked Coupons (Multiple Items Plus Points) . . . . . . . . . . . . . 205
Linked Coupons (Multiple Items/No Points) . . . . . . . . . . . . . . 209
Coupon Linked to Department Purchase . . . . . . . . . . . . . . . 212
Coupon Linked to a Minimum Department Purchase . . . . . . . . . . 214
Coupon Linked to Minimum in Two Departments . . . . . . . . . . . . 215
Coupon Linked to Minimum by Manufacturer . . . . . . . . . . . . . 218
Coupon Linked to Items per Coupons . . . . . . . . . . . . . . . . 219
Award Points With No Performance Required . . . . . . . . . . . . . 222
Promotion Code Coupons . . . . . . . . . . . . . . . . . . . . 223
Percent Off Discount Coupons. . . . . . . . . . . . . . . . . . . 225

72 Electronic Marketing PRPQ

Chapter 8. Electronic Marketing Processing. . . . . . . . . . . . . 227
Support for Home Store Processing . . . . . . . . . . . . . . . . . 227
Home Store Concept Supported Mainly by In-Store Processing . . . . . 227
Home Store Concept Supported Mainly by Central Site Processing . . . . 227
Support for No Home Store . . . . . . . . . . . . . . . . . . . . 228
Support for Multiple Home Stores . . . . . . . . . . . . . . . . . 228
Customer Identification Number Processing . . . . . . . . . . . . . . 228
Validating a Customer Identification Number . . . . . . . . . . . . 228
Searching for a Customer ID in the Customer Activity File . . . . . . 228
Using a Customer Number as Tender Verification Number . . . . . . . 229
Alias/Primary Record Pair Processing . . . . . . . . . . . . . . . 230
Electronic Coupon Processing . . . . . . . . . . . . . . . . . . . 230
Awarding Electronic Coupons during Sales . . . . . . . . . . . . . 230
Distinguishing Electronic Coupons from Other Types . . . . . . . . . 231
Electronic Coupons and Paper Coupons . . . . . . . . . . . . . 231
Electronic Coupons and Preferred Customer Coupons . . . . . . . . 231
Different Behavior of Non-Preferred Customer Electronic Coupons . . . 231
Implementing Cross-Promotional Electronic Coupons . . . . . . . . . 231
Effect on Performance. . . . . . . . . . . . . . . . . . . . . 232
Effect on Taxes . . . . . . . . . . . . . . . . . . . . . . . 232
Electronic Coupon Maintenance . . . . . . . . . . . . . . . . . 232
Processing Electronic Coupons Linked to Items with Deposits . . . . . 232
Processing Promotional Items . . . . . . . . . . . . . . . . . 233
System Considerations: Host and Controller. . . . . . . . . . . . 234
Targeted Coupon Processing . . . . . . . . . . . . . . . . . . 234
Entering a Customer ID with Targeted Coupons . . . . . . . . . . . 235
System Considerations . . . . . . . . . . . . . . . . . . . 235
Performance Impact . . . . . . . . . . . . . . . . . . . . 235
Validating Targeted Coupons . . . . . . . . . . . . . . . . . . 235
Defining Reuse of Targeted Coupons . . . . . . . . . . . . . . . 236
Maintaining Targeted Coupons in the Customer Activity Record . . . . . 236
Defining Targeted Coupons in the Rain Check Record . . . . . . . . . 237
Redemption Coupon Processing . . . . . . . . . . . . . . . . . . 237
Point Processing . . . . . . . . . . . . . . . . . . . . . . . . 238
Linkage of Points-Only Items . . . . . . . . . . . . . . . . . . 238
Point Eligibility. . . . . . . . . . . . . . . . . . . . . . . . 239
Points Multiplication via Customer Activity Record. . . . . . . . . . . 240
Customer Point Adjustments at the Controller . . . . . . . . . . . . 240
Referenced Account Point Processing . . . . . . . . . . . . . . . . 240
Support for Periodic Points Totals . . . . . . . . . . . . . . . . . 240
Automatic Discounts via Customer Activity Record . . . . . . . . . . . 242
Provide Kiosk Support to Show Customer Their Points and Coupons . . . . 243
Totals Accumulation Processing . . . . . . . . . . . . . . . . . . 244
Using Data Base for Directed Marketing . . . . . . . . . . . . . . 244
Updating and Transferring Totals Files . . . . . . . . . . . . . . . 244
Accumulating Electronic Coupons Totals . . . . . . . . . . . . . . 245
Data Space Use Adjustments . . . . . . . . . . . . . . . . . . . 246
Date of Last Sale Update Functions. . . . . . . . . . . . . . . . . 247
Promotion Code Validation . . . . . . . . . . . . . . . . . . . . 247
Use of promotion codes is optional . . . . . . . . . . . . . . . . 247
Promotion codes are values in User Exit field 1 in item records . . . . . 247
Validation of coupons with promotion codes . . . . . . . . . . . . . 248
Minimum purchase of coupons with promotion codes . . . . . . . . . 248
Taxability and foodstampability of coupons with promotion codes . . . . . 248

Chapter 9. Reports . . . . . . . . . . . . . . . . . . . . . . 249

Part 2. Operations and Reports 73

 User Reports . . . . . . . . . . . . . . . . . . . . . . . . . 249
Selective Item Record Report . . . . . . . . . . . . . . . . . . . 250
Item Selection . . . . . . . . . . . . . . . . . . . . . . . . 250
Item Reporting . . . . . . . . . . . . . . . . . . . . . . . 252
Item Alterations . . . . . . . . . . . . . . . . . . . . . . . 254
Operator Interface . . . . . . . . . . . . . . . . . . . . . . 257
Error Handling. . . . . . . . . . . . . . . . . . . . . . . . 257
Performance . . . . . . . . . . . . . . . . . . . . . . . . 257
Selective Preferred Customer Report . . . . . . . . . . . . . . . . 258
Customer Selection . . . . . . . . . . . . . . . . . . . . . . 258
Customer Reporting . . . . . . . . . . . . . . . . . . . . . 259
Customer Record Alterations . . . . . . . . . . . . . . . . . . 260
Operator Interface . . . . . . . . . . . . . . . . . . . . . . 261
Error Handling. . . . . . . . . . . . . . . . . . . . . . . . 261
Performance . . . . . . . . . . . . . . . . . . . . . . . . 261
Preferred Customer Audit Log Report . . . . . . . . . . . . . . . . 262
Preferred Customer Exception Log Report . . . . . . . . . . . . . . 262
Preferred Customer Options Report . . . . . . . . . . . . . . . . . 264
Sample Electronic Marketing Preferred Customer Options Report . . . . . . 268
Accounting Reports . . . . . . . . . . . . . . . . . . . . . . . 273

74 Electronic Marketing PRPQ

Chapter 6. Personalization of Preferred Customer Options and
Messages
Modules [Link], [Link], and [Link] provide default
Electronic Marketing options, descriptors, and messages, respectively, for the
preferred customer code. They must be copied to the ADX_IPGM directory on the
C: drive. The options file is defined in detail below. The messages file is defined in
“Preferred Customer Messages File (EAMFBMSG)” on page 169. After you install
these files, if you are on a LAN system, you can use the system file utilities to
ensure that the distribution type is compound per update.

The utility program FIXR1OPT will format the two options files of the 1991 level of
Electronic Marketing into the one large options file handled by the newer code level.
This allows users of the prior code level to migrate to a level of the options file that
matches their current options usage.

Preferred Customer Options File (EAMFBOPT)

Logical File Record LAN File
Name Description Organization Length I/O No. Dist Copies
EAMFBOPT Customer Options Sequential Var 8 Com 1/ cont

Options are provided for preferred customer processing in a file named

[Link]. A copy of this file is maintained on all controllers. A default
version of this file is provided to show the proper file format. The options should
be altered as needed to obtain the desired processing by using the Preferred
Customer Options Report (User Report 7) to display and alter the options
values. The options could also be altered by editing the [Link] file with
any available editor (for example, DREDIX) or with the maintenance tool provided
with the operating system (ADXCSJ0L), but this in not recommended as it is too
easy to create an invalid options file. The options report performs a range check on
each entry to the options file. This range check is adequate to ensure the validity of
most entries.

Options are separated on a line by commas. No decimal points or commas should

be contained in any of the numeric amounts. Most of the lines in the options file
contain 10 variables even though many of these lines have fewer options defined in
the following documentation. These excess variables are reserved for future use
and must be present for the file to be properly processed. After editing EAMFBOPT,
the contents of this file should always be reported using the “Preferred Customer
Options Report” on page 264 to verify the file contents.

© Copyright IBM Corp. 1991 2000 75

Preferred Customer Options Default
The default preferred customer options file contains the following 30 lines. These
defaults are explained in detail in “Preferred Customer Options Descriptions”. The
default option for each line is also shown.
(Line #)
1 " PREFERRED CUSTOMER","99999999999","0",0,0,0,0,0,"0","0" (Page 76)
2 10000,101,84,2,0,0,0,0,10,0 (Page 81)
3 -1,0,0,0,0,-1,0,0,0,0 (Page 86)
4 4,1,1,0,999999,20,0,0,0,0 (Page 91)
5 300,399,0,0,1,9999,0,0,0,0 (Page 97)
6 0,0,0,0,0,0,0,0,0,0 (Page 98)
7 11,2,4,9,0,0,0,1,1,0 (Page 100)
8 0 (Page 103)
9 0,0,0,0,0,0,0,0,0,0 (Page 103)
10 0,0,0,0,0,0,0,0,-1,0 (Page 106)
11 0,240,0,18,2,5,4,0,9,0 (Page 108)
12 0,0,0,0,0,0,0,0,0,0 (Page 112)
13 0,-1,0,0,0,0,0,0,0,0 (Page 117)
14 0,0,0,0,0 (Page 124)
15 0 (Page 125)
16 -1,0,0,0,0,0,0,0,0,0 (Page 129)
17 0,0,0,0,0,0,0,0,0,0 (Page 133)
18 0,0,0,0,0,0,0,0,0,0 (Page 134)
19 0,0,0,0,0,0,0,0,0,0 (Page 134)
20 0,0,0,0,0,0,0,0,0,0 (Page 140)
21 0,0,0,0,0,0,0,0,0,0 (Page 148)
22 0,0,0,0,0,0,0,0,0,0 (Page 150)
23 0,0,0,0,0,0,0,0,0,0 (Reserved)
24 0,-1,-1,0,-1,0,0,0,0,0 (Page 150)
25 "00000","0","0",0,0,0,0,0,0,0 (Page 154)
26 199 (Page 156)
27 9999,0,0,0,999,0,999,0,0,0 (Page 158)
28 0,0,0,0,0,0,0,0,0,0 (Page 162)
29 0,0,0,0,0,0,0,0,0,0 (Reserved)
30 "*END*" (Page 162)

Note that the 30 lines in the file match the 30 lines shown in the options report and
in the documentation. If the option on line 15 is set to a value other than 0 so that
boundary levels can be defined, then there will be an extra line in the file after line
15 for each boundary level. These additional lines are accounted for in the
documentation and report as a single line 15, but in the file these options take a
variable number of lines depending upon the number of boundary levels defined.
The following is an example of what these optional boundary options might look
like.
(Line 15) 3 (Page 125)
1,0,10000,0,12 (Page 125)
10000,-1,0,1,11 (Page 126)
50000,0,1000,0,10 (Page 126)

Preferred Customer Options Descriptions

Program name
LINE 1

“ PREFERRED CUSTOMER”,“99999999999”,“0”,0,0,0,0,0
______________________
↑
Program Name
Range: (0-20 Alphanumeric characters)
Location: Line 1, Option 1

76 Electronic Marketing PRPQ

Default: “ PREFERRED CUSTOMER”
Change Activation:
Re-enter selected report.

This option provides a text field to be used to describe the totals associated with
the preferred customer program. This name is used in reports at the manager’s
terminal. It must be right justified into a 20-character field.

Deactivate Preferred Customer Processing

LINE 1

“ PREFERRED CUSTOMER”,“99999999999”,“0”,0,0,0,0,0
_____________________
↑
Program Name or Deactivate Processing
Range:
(0-2 Alphanumeric characters)
Location:
Line 1, Option 1
Default:
“ PREFERRED CUSTOMER” (Set to “!!!PREFERRED CUSTOMER” to set
option.)
Change Activation:
Force all registers to “RELOAD OPTIONS”, stop and restart checkout
support.

This option is selected by setting the first two characters in the program name to
exclamation points to “comment out” preferred customer processing. When
!!PREFERRED CUSTOMER is selected, the following functions are turned off:
v Transfer processing for non-home store points
v Background filtering of panel data
v Panel capturing of data, but this function remains active if the option is for
paneling all customers
v Prompting for a preferred customer number at the register
v Entering of preferred customer numbers
v Printing of preferred customer messages
v Marking of preferred customer items
v Processing of all preferred customer coupons for all customers. This allows item
maintenance for preferred customer coupons to precede the activation of
preferred customer processing.
Only the processes defined above are deactivated. All report programs and file
maintenance procedures are fully active to allow the data base for Preferred
Customer processing to be set up while the processing of customers is inactive.

When this option is set to deactivate preferred customer processing, you must set
the option “Coupon Velocity Code Range for Preferred Customers” on page 97 to
include all electronic coupons, whether preferred or non-preferred, and to exclude
all linked deposits. All linked records within this preferred customer range are
deactivated by this deactivate option. If the preferred customer velocity range is not
set properly, you may inadvertently deactivate other linked records, such as
automatic bottle deposits, or you might mistakenly process an Electronic Marketing
coupon as a regular supermarket coupon, causing errors.

Chapter 6. Personalization of Preferred Customer Options and Messages 77

 Deactivate Electronic Marketing Code
LINE 1

“ PREFERRED CUSTOMER”,“99999999999”,“0”,0,0,0,0,0
____________________
↑
Program Name or Deactivate Processing
Range:
(0-2 Alphanumeric characters)
Location:
Line 1, Option 1
Default:
“ PREFERRED CUSTOMER” (set to “\\PREFERRED CUSTOMER” to set
option)
Change Activation:
Sign-off all registers. Stop and Restart Checkout Support.

This option provides a simple single change which can be used to turn ALL
electronic marketing functions on and off in the register, in the checkout support
background task, and in the accounting reports. When this option is selected, these
programs behave as if the Electronic Marketing were not installed. This option is
selected by setting the first two characters in the program name to “\\” to “comment
out” ALL preferred customer processing.

When \\PREFERRED CUSTOMER is selected, all preferred customer processing is

stopped in terminal sales, checkout support and in the accounting reports.

Rain check ID Definition

LINE 1

“ PREFERRED CUSTOMER”,“99999999999”,“0”,0,0,0,0,0
______________
↑
Rain check ID definition
Range:
(0-18 Numeric characters)
Location:
Line 1, Option 2
Default:
“99999999999”
Change Activation:
Sign off all registers, Stop and Restart Checkout Support.

This option defines a customer number to be used as a rain check ID. This rain
check ID number must have an associated enrollment record and activity record,
such as a customer ID number does. But the use of a rain check number differs
from a customer ID number in the following ways:
v A special Rain check message is printed on the receipt to show that a customer
identified himself/herself as a preferred customer and asked for a rain check.
v Each use of this number is entered in the Exception Log file, so that all uses can
be reported and tracked. This provides additional security against fraudulent rain
check claims.
v A special rain check adjustments procedure, provided as part of the enrollment
procedure, allows the original rain check transaction to be identified as a
customer is given the rain check points. This transaction data is logged.
v Totals for this ID are never transferred out of store.

78 Electronic Marketing PRPQ

v Any coupons targeted to the rain check ID are available to all Preferred
Customers eligible for coupons in addition to any coupons targeted specifically to
individual customers. Thus you may want to define this ID just for targeting
coupons to all Preferred Customers even if you never expect the ID to be
entered to identify a rain check customer. A points multiplier or discount group
defined for the Rain check ID applies to all Preferred Customers who do not
have these promotions selected individually in their own activity records and are
eligible for discounts or points through their activity options. For performance
reasons, the Rain check record is read into each terminal at sign-on and used
directly from memory. This means that all registers must be signed off to activate
a change in the Rain check record. In Stand-alone, all Preferred Customers are
treated as Rain check customers in that they use the status, messages, and
options associated with this ID as well as the targeted coupons, discount group,
and points multiplier if the Rain check ID is eligible for coupons, discounts, and
points through the activity options. An option allows all non-preferred customers
to be treated as Preferred Rain check customers. Thus there are many good
reasons to define a Rain check ID and initialize a Rain check activity record as
the default way of treating Preferred Customers whose individual IDs are
unknown.

UPC Displacement for Preferred Customer Linked Items

LINE 1

” Preferred Customer“,”99999999999“,“0”,0,0,0,0,0
___
↑
UPC Displacement for Preferred Customer Linked Items
Range:
(0-8 Numeric characters) (xx00000x if validation is selected)
Location:
Line 1, Option 3
Default:
“0”
Change Activation:
Sign off all registers.

This option concatenates UPC displacement digits to the front of any linked item
code within the preferred customer coupon range (defined in “Coupon Velocity
Code Range for Preferred Customers” on page 97). The item code of the record is
looked up to resolve the linkage, and it is enlarged by the extra digits. The terminal
searches for the item code of the linked item’s record to resolve the linkage, and
adds the extra digits to it. For example, a UPC displacement of 99 combines with a
preferred customer linked item code of 0123, causing a lookup of item 990123. This
displacement allows the linked preferred customer item records to be moved out of
the range of velocity codes that might be needed for other purposes. In the
example above, item code 123 can be used as a produce velocity code if another
item record is never linked to it. In order to void a preferred customer coupon using
the number 123 printed on the receipt tape, an operator must key in the displaced
item code 990123.

This option displaces only the preferred customer item records and their associated
item movement data.

If you select validation of preferred customer coupons (defined in “Validate

Automatic Preferred Customer Store Coupons” on page 88), specify this option as
either one digit or as two digits followed by six zeroes. This is required to avoid the
appearance of a manufacturer number in the resulting UPC code.

Chapter 6. Personalization of Preferred Customer Options and Messages 79

| For example, a UPC displacement of 9 combines with a preferred customer linked
| item code of 0123, causing a lookup of item 90123.

80 Electronic Marketing PRPQ

Coupons Targeted for the First Use of a Customer Card
LINE 1

“ Preferred Customer”,“99999999999”,“0”,0,0,0,0,0
_________
↑
Coupons targeted for the first use of customer card
Range:
(0 or within the preferred coupon UPC range)
Location:
Line 1, Options 4-8
Default:
0,0,0,0,0
Change Activation:
Sign off all registers.

This option set allows up to five coupons to be targeted uniquely to preferred

customers during their first use of their customer identification cards. Preferred
customers are eligible to receive these targeted coupons only if they have no other
targeted coupons in their activity record and no activity history associated with
either them or a family member’s customer number. If customers are added to the
activity file with targeted coupons before they first use their card, they do not
receive the coupons targeted only for first-time users. You can also require that they
purchase a selected item prior to receiving any coupons.

The coupons available to first-time customers are identified through a velocity code
within the range of automatic preferred customer coupon codes specified in
“Coupon Velocity Code Range for Preferred Customers” on page 97. Any value
outside the range of automatic preferred coupons is ignored. You must define all
five options fields with either the velocity code of the coupon or a value of zero to
denote no coupon.

These first-time coupons are available only at the first time a customer’s card is
presented. They are never printed on the customer receipt as available. The
purpose of this option is to provide a special incentive for new preferred customers
to identify themselves on their next store visit. If preferred customers do not take
advantage of these coupons at the first use of their customer ID card, they cannot
use them in any subsequent transactions.

Activity File Size

LINE 2

10000,101,84,2,0,0,0,0,10,0
_____
↑
Activity file size
Range:
(1,000 - 1,000,000)
Location:
Line 2, Option 1
Default:
10,000 (.83 MB of disk space)
Change Activation:
Stop checkout support; delete EAMFBACT; then restart checkout support.
(See FIXFILES utility if EAMFBACT contains good data and cannot simply
be deleted.)

Chapter 6. Personalization of Preferred Customer Options and Messages 81

 Checkout support creates a Preferred Customer Activity File ([Link]) if
one is not present at program initialization. The enrollment procedure creates a
Preferred Customer Enrollment File ([Link]) if the procedure is used and
a customer enrollment file does not exist. This option is used to determine the size
of these two files.

The option should be defined as the maximum number of expected preferred

customers plus 20 percent. You must ensure that there is adequate disk space to
create these files. For more information on file sizes, see “Preferred Customer
Activity File (EAMFBACT)” on page 322 and “Preferred Customer Enrollment File
(EAMFBCUS)” on page 320.

Activity Record Size

LINE 2

10000,101,84,2,0,0,0,0,10,0
___
↑
Activity Record Size
| Range:
| (31 - 508)
Location:
Line 2, Option 2
Default:
101 bytes
Change Activation:
Sign off all registers; stop checkout support delete EAMFBACT; then restart
checkout support. (See FIXFILES utility if EAMFBACT contains good data
and cannot simply be deleted.)

| This option is used to determine the size of an activity record in the Preferred
| Customer Activity File. These records can range from 31 to 508 bytes, depending
| on the needed contents. For more information on record size, see “Preferred
| Customer Activity File (EAMFBACT)” on page 322.

Bytes Before the Customer Name in Activity Record

LINE 2

10000,101,84,2,0,0,0,0,10,0
__
↑
Bytes before the customer name in activity record
Range:
(31 - 254)
Location:
Line 2, Option 3
Default:
84 bytes (17-character customer name)
Change Activation:
Sign off all registers; stop checkout support delete EAMFBACT; then restart
checkout support. (See FIXFILES utility if EAMFBACT contains good data
and cannot simply be deleted.)

This option defines the location of the customer name field in the activity record.
The customer name field is the last field in the record. This option and the Activity
Record Size option (see 82) define the length of the customer name field. If a
customer name is present, it is optionally displayed and printed on the customer
receipt.

82 Electronic Marketing PRPQ

Format of Customer Name in Activity Record
LINE 2

10000,101,84,2,0,0,0,0,10,0
__
↑
Format of customer name in activity record
Range:
(0 - 3)
Location:
Line 2, Option 4
Default:
2 (Last name only)
Change Activation:
Restart enrollment procedure.

You must use this option if you use an in-store procedure that transfers a
customer’s name from the Preferred Customer Enrollment File to the Preferred
Customer Activity File. This option defines what portion of the name goes into the
activity file as follows:

0 = No name in activity record

1 = First name only in activity record (13 bytes from enrollment)
2 = Last name only in activity record (17 bytes from enrollment)
3 = Full name in activity record (30 bytes from enrollment)

If you select option three, one blank is placed between the first and last names and
any excess blanks are removed.

Activity Options Default

LINE 2

10000,101,84,2,0,0,0,0,10
__
↑
Activity options default
Range:
(0 - 255)
Location:
Line 2, Option 5
Default:
0
Change Activation:
Sign off all registers; stop checkout support then restart checkout support.

An options field in each record of the Preferred Customer Activity File determines
the processing that applies to each preferred customer who has an activity record
on file. This option provides a default value for all preferred customers who do not
have a record on file (new or non-home store customers). This default value is also
used if the required record cannot be successfully accessed.

Any combination of options in the following list can be set as the default. Add up the
values to the left of the options and place the sum in line 2, option 5. For example,
to choose “Do not give points to all preferred customers,” “Do not collect panel on
all preferred customers,” and “Do not personalize trailer message”, place 11
(8+2+1) in this option.

Chapter 6. Personalization of Preferred Customer Options and Messages 83

 1 = Do not personalize trailer messages for all preferred customers
2 = Do not collect panel data on all preferred customers
4 = Do not give automatic coupons to all preferred customers
8 = Do not give points to all preferred customers
16 = Read the Customer Transfer file for all customers
128 = Do not give automatic discounts to any preferred customers

Deactivate Activity Options for All Preferred Customers

LINE 2

10000,101,84,2,0,0,0,0,10,0
__
↑
Deactivate activity options for all preferred customers
Range:
(0 - 255)
Location:
Line 2, Option 6
Default:
0 (All processing options taken from file data)
Change Activation:
Sign off all registers; stop checkout support then restart checkout support.

An options field in each record of the Preferred Customer Activity File determines
the processing that applies to each preferred customer who has an activity record
on file. This option selectively overrides (deactivates) these processing options for
all customers. The inverse of this option is logically ANDed with the option byte
from the file.

Any combination of options in the following list can be deactivated. Add up the
values to the left of the options and place the sum in this option.

For example, to choose “Give points to all preferred customers, ” “Collect panel
data for all shoppers,” and “Personalize trailer message for all customers”, place 11
(8+2+1) in this option.

1 = Personalize trailer messages for all preferred customers

2 = Collect panel data on all preferred customers
4 = Give automatic coupons to all preferred customers
8 = Give points to all preferred customers.
16 = Do not process points transferred from another store
128 = Give automatic discounts to all preferred customers

Activate Activity Options for All Preferred Customers

LINE 2

10000,101,84,2,0,0,0,0,10,0
__
↑
Activate activity options for all preferred customers
Range:
(0 - 255)
Location:
Line 2, Option 7
Default:
0 (All processing options taken from file data)
Change Activation:
Sign off all registers; stop checkout support then restart checkout support.

84 Electronic Marketing PRPQ

 An options field in each record of the Preferred Customer Activity file determines
the processing that applies to each preferred customer who has an activity record
on file. This option selectively overrides (activates) these processing options for all
customers. Note that this option is logically ORed with the option byte from the file.

Any combination of options in the following list can be activated. Add up the values
to the left of the options and place the sum in this option. For example, to choose
“Do not give points to all preferred customers,” “Do not collect panel data on
preferred customers,” and “Do not personalize trailer message”, place 11 (8+2+1) in
this option.

1 = Do not personalize trailer messages for any preferred customers

2 = Do not collect panel data on any preferred customers
4 = Do not give automatic coupons to any preferred customers
8 = Do not give points to any preferred customers
16 = Read the Customer Transfer file for all customers
128 = Do not give automatic discounts to any preferred customers

Collect Panel Data for All Customers

LINE 2

10000,101,84,2,0,0,0,0,10,0
__
↑
Collect panel data for customers
Range:
Yes (-1), No (0)
Location:
Line 2, Option 8
Default:
No (0) (Capture panel data only for preferred customers.)
Change Activation:
Stop then Restart Checkout Support.

This Yes/No option determines whether data is accumulated in the Panel Diary file
for all customers or for preferred customers only. A value of No (0) causes panel
data to be captured only for transactions that customers identify themselves as
preferred customers.

A value of Yes (-1) causes data to be captured in the Panel Diary file for all
transactions regardless of whether the identity of the customer is known.

Maximum Number of Coupons Targeted Per Customer

LINE 2

10000,101,84,2,0,0,0,0,10,0
___
↑
Maximum number of coupons targeted per customer
| Range:
| (5 - 223)
Location:
Line 2, Option 9
Default:
10 (5 coupons in user data)
Change Activation:
Stop then Restart Checkout Support. Sign off all registers.

Chapter 6. Personalization of Preferred Customer Options and Messages 85

 This numeric option notifies the code how much of the user area in the customer
activity record is to be used for targeted coupons. Space for five unique targeted
coupons per customer is reserved in this record, and if more are needed, they can
be placed at the front of the user area in the record. If there is not enough space in
the user area of the record to accommodate this definition, this maximum is
automatically reduced to fit the available space. Note that if the activity record is not
defined large enough, it may not contain any user area.

Create and Access Customer Transfer File

LINE 3

-1,0,0,0,0,-1,0,0,0,0
___
↑
Create and access customer transfer file
Range:
Yes (-1), No (0)
Location:
Line 3, Option 1
Default:
Yes (-1) (File is created and used)
Change Activation:
Stop then Restart Checkout Support.

This Yes/No option determines whether a Customer Transfer File is used in the
system. This file is used to store points data for customers who shop in a store
other than their home store. The data from this file can be transferred to the proper
home store to allow points to be accrued from any store.

A value of No (0) prevents the transfer file from being created or used and thus
prevents the delayed transfer of points from a non-home store to a home store. A
value of Yes (-1) causes the customer transfer file to be created and used as
needed. Note that transfer processing for immediate updates (from a host or from
activity update errors) is possible even when transfer files are not created. When
points totals are updated locally and transferred, for example, another store is also
a customer’s home store, the transfer can be assured to avoid a double bonus
possibility. This is accomplished by setting the immediate activity update flag in the
transfer file (EAMXssss). If the immediate activity update flag within the transfer file
is set, then the file will be processed and the activity file will be immediately
updated regardless of the setting of this option.

Automatically Process In-Store Transfers Each Hour

LINE 3

-1,0,0,0,0,-1,0,0,0,0
__
↑
Automatically process in store transfers each hour
Range:
Yes (-1), No (0)
Location:
Line 3, Option 2
Default:
No (0) (No automatic processing)
Change Activation:
Stop then Restart Checkout Support.

86 Electronic Marketing PRPQ

This Yes/No option causes in-store transfer files to be automatically searched for
and processed once each hour. This processing depends upon the transferal of files
with the proper names and formats to the system. After they are processed, the
transfer files are deleted. This processing can be started alternatively by a request
from a host or as a manual request from the background control screen.

A value of No (0) allows transfer data to go unprocessed until requested from a

host or an operator. A value of Yes (-1) causes any transfer files present to be
processed at each hour as checkout support processes the hourly crossing.

Note: Checkout support only processes an hourly crossing. When sales are
detected in a new hour, this option will not cause transfer processing to
occur when the store is closed. Transfer files transmitted during the night will
be processed at the first sales transaction of the next day.

Store Coupons Reduce Points

LINE 3

-1,0,0,0,0,-1,0,0,0,0
__
↑
Store coupons reduce points
Range:
Yes (-1), No (0)
Location:
Line 3, Option 3
Default:
No (0) (Store coupons do not reduce points.)
Change Activation:
Sign off all registers.

This Yes/No option determines whether the value of store coupons reduces the
transaction amount upon which point calculation is based. Store coupons are often
interpreted as discounts, so enterprises may not wish to award both a coupon for
an item and points for the amount of the item that the coupon reduced.

A value of No (0) causes store coupons to have no impact on transaction points. A

value of Yes (-1) causes store coupons to reduce the points according to the size of
the discount given by the store coupon.

Taxes Increase Points

LINE 3

-1,0,0,0,0,-1,0,0,0,0
__
↑
Taxes increase points
Range:
Yes (-1), No (0)
Location:
Line 3, Option 4
Default:
No (0) (Taxes do not increase points)
Change Activation:
Sign off all registers.

This Yes/No option determines whether the amount of taxes is included in the
transaction amount upon which the point calculation is based.

Chapter 6. Personalization of Preferred Customer Options and Messages 87

 A value of No (0) causes taxes to be excluded from transaction points. A value of
Yes (-1) causes taxes to be included and to increase the points given for a
transaction that is taxed.

Keyed Customer Numbers Require a Manager’s Override

LINE 3

-1,0,0,0,0,-1,0,0,0,0
__
↑
Keyed customer numbers require a manager’s override
Range:
Yes (-1), No (0)
Location:
Line 3, Option 5
Default:
No (0) (Keyed customer numbers do not require an override)
Change Activation:
Sign off all registers.

This Yes/No option determines whether a manager’s override is required for keyed
customer numbers.

A value of No (0) allows customer numbers to be keyed. A value of Yes (-1) causes
a manager’s override to be required before a keyed customer number will be
accepted.

Use of this option helps an enterprise to prevent fraud when all preferred customers
are expected to have a scannable card.

Validate Automatic Preferred Customer Store Coupons

LINE 3

-1,0,0,0,0,-1,0,0,0,0
___
↑
Validate automatic preferred customer coupons
Range:
Yes (-1), No (0)
Location:
Line 3, Option 6
Default:
Yes (-1) (Validation of automatic coupons)
Change Activation:
Sign off all registers.

This Yes/No option determines whether the automatic coupons that are given to
preferred customers are validated or not. Automatic coupons are linked to items and
it is known that the customer purchased the item(s) to which the coupon applies. A
customer does not receive automatic coupons until he/she has purchased the
item(s) to which the coupons apply. If you are using only simple coupons, validation
may not be necessary. If this option is selected, the taxability of the coupon is
derived only from the tax flags in the item record, because the taxability of the
matching items is not known.

If you select this option, the only requirement is that the coupon item records
contain the needed information (such as manufacturer number or promotion code)

88 Electronic Marketing PRPQ

to allow them to be paired with the matching items. With this ability to link the
preferred customer coupons back to the items to which they apply, the following
functions are available:
v The ability to avoid giving paper and electronic coupons for the same item
v The ability to require sales of multiple like items or different items before a
coupon is given
v The ability to require the purchase of selected items in order to award coupons
that are targeted to selected customers
v The ability to require a minimum purchase in a department or for a manufacturer
before awarding the benefits of a coupon
v The ability to pair matching items with the coupons in the coupon tracking file
v The ability to first void non-couponed sales when voiding an item for which some
sales received a coupon and others did not
v The ability to exclude matching items from a coupon’s minimum purchase
requirement.

Each of these cases depends upon the ability of the system to pair all coupons with
the corresponding sales by department or by manufacturer number and perhaps
coupon family or promotion code. An automatic coupon does not normally have an
associated manufacturer number, so this pairing of coupons to items occurs only if
the Coupon Processing Enhancements are used to associate a manufacturer with
the coupon.

You can also select to validate coupons by department only by setting this option to
Yes (-1). This requires that all coupons (automatic and other types) be paired with
sales from the same department as defined in the coupon item record. See “Linked
Coupons” on page 341 for more information on the coupon item record.

There is a similar option in the Coupon Processing Enhancements (see “All

Coupons Require at Least Department Level Validation” on page 150) that pertains
to all coupons that can only be validated by department for lack of an associated
manufacturer number. These two validation options are independent of each other
and have a similar impact. To provide validation for automatic preferred customer
coupons at a department level, you must either select the validate by department
option in the Coupon Processing Enhancements or override this option by setting
the department validation flag in the coupon item record.

A value of No (0) causes automatic coupons to be accepted without validation. A

value of Yes (-1) causes normal coupon validation to occur on automatic coupons
and requires that coupons be paired with associated sales either by manufacturer,
department, or promotion code. The functions listed above are not available unless
this option is set to Yes (-1). It is suggested that this option be selected.

Use Coupon Families in Validation of UPC 5 Coupons

LINE 3

-1,0,0,0,0,-1,0,0,0,0
__
↑
Use coupon families in validation of UPC 5 coupons
Range:
Yes (-1), No (0)
Location:
Line 3, Option 7

Chapter 6. Personalization of Preferred Customer Options and Messages 89

 Default:
No (0) (No family validation)
Change Activation:
Sign off all registers.

This Yes/No option determines whether the coupon families in a UPC 5 coupon are
used for validation of the coupon. A value of Yes (-1) causes the UPC 5 coupon
families to be used in the validation process and provides item level validation. This
selection requires that coupon families be accurately maintained in the item record
file. A value of No (0) causes every UPC 5 manufacturer coupon to look like it has a
family code of zero, and coupon validation by family code to be bypassed. With this
selection, all coupon validation is done by manufacturer without regard for coupon
family. This allows UPC 5 coupons to be validated at a manufacturer level without
requiring any maintenance of coupon families in the item record file. Any coupons
on file can contain family numbers that can be defined by the store. The same
family numbers can be placed in selected item records to provide for item level
validation of electronic coupons.

Manager’s Override Required for New Customers

LINE 3

-1,0,0,0,0,-1,0,0,0,0
__
↑
Managers’s override required for new customers
Range:
Yes (-1), No (0)
Location:
Line 3, Option 8
Default:
No (0) (Operator‘s override validates a new customer.)
Change Activation:
Sign off all registers.

This Yes/No option determines whether a manager’s override or an operator’s

override is required to accept a new customer number that has not been included in
the Preferred Customer Enrollment File. The procedure used to enroll a new
customer causes a record for this customer to be added to the activity file. But if a
store is first enrolling a large number of preferred customers, it is possible that new
customers with new identification numbers may engage in checkout transactions
before their enrollment data has been entered into the system.

A value of No (0) causes the validation of a new customer number to be satisfied

with an operator’s override. A value of Yes (-1) requires a manager’s override to
validate the entry of a new customer number.

When the number of customer enrollments is high, use an operator’s override.

When the number of customer enrollments is low, use a manager’s override.

Show Points in Whole Dollar Amounts

LINE 3

-1,0,0,0,0,-1,0,0,0,0
__
↑
Show points in whole dollar amounts
Range:
Yes (-1), No (0)

90 Electronic Marketing PRPQ

Location:
Line 3, Option 9
Default:
No (0) (Show points in dollars and cents.)
Change Activation:
Sign off all registers.

This Yes/No option determines whether the points values shown on a customer
receipt or register display are presented with dollars and cents or with dollars only.
This has meaning only if points are equivalent to cents as defined in a option “Ratio
of Points Per Cents Purchased” on page 92. When points are shown in whole dollar
amounts only, the cents portion is just truncated, and the points are effectively
rounded down.

A value of No (0) causes the point values shown on a receipt or register display to
be shown with two decimal places. A value of Yes (-1) causes the same points
values to be shown without the decimal portion.

Personalization Message Format

LINE 4

4,1,1,0,999999,20,0,0,0,0
__
↑
Personalization message format
Range:
0-6
Location:
Line 4, Option 1
Default:
4 (Replace standard message line 2.)
Change Activation:
Sign off all registers.

A store personalizes the messages in the store’s controller for Terminal Sales to use
them to communicate with customers during transactions. For example, a message
may show customers their current activity record, inform them of an award they
have earned, or remind them to update their enrollment information. The purpose of
these messages is to reduce the need for expensive mailings to communicate with
customers.

The Supermarket application provides for a one or two line personalization

message (THANK YOU - COME AGAIN) to be printed at the end of each
customer’s receipt. The preferred customer code allows a unique message to be
printed for preferred customers in addition to or in place of the normal message
printed for all other customers. This option determines the format of the preferred
customer personalization message as follows:
0 = No unique personalization message for preferred customers
1 = Insert preferred customer message before standard message
2 = Replace standard message line 1 with preferred customer message
3 = Insert preferred customer message after standard message line 1
4 = Replace standard message line 2 with preferred customer message
5 = Insert preferred customer message after standard message line 2
6 = Replace standard message with preferred customer message.

The text of the preferred customer personalization message is defined in the

message file [Link] and can contain information such as the customer
name and points total.

Chapter 6. Personalization of Preferred Customer Options and Messages 91

 Ratio of Points Per Cents Purchased
LINE 4

4,1,1,0,999999,20,0,0,0,0
___
↑
Ratio of points per cents purchased
Range:
(1 - 100), (1 - 100000)
Location:
Line 4, Options 2 and 3
Default:
1,1 (Points = Cents)
Change Activation:
Sign off all registers.

These two options define the value of a point and the way points are accumulated
by providing a ratio of points to cents. The points value is specified first, followed by
the number of cents required to receive these points. Points accumulated in a
transaction are always a multiple of the point option. The point option must NOT be
set higher than the cent option.

Ratio Explanation
1,1 1 point for each cent tendered.
1,100 1 point for each 100 cents tendered.
10,1000 10 points for each 1000 cents tendered. Same proportion as
1,100 except points awarded only in increments of 10.

For a transaction with a $123.44 value of purchases to which points apply, ratio
options of 1,100 would give 123 or 124 points (see 92 for rounding selections). But
ratio options of 10,1000 would give 120 or 130 points for the same transaction. If
you want to establish a ratio of five points per dollar, it will make a difference
whether you specify the option as five points per dollar or as one point for 20 cents.

Points Rounding Selection

LINE 4

4,1,1,0,999999,20,0,0,0,0
__
↑
Points rounding selection
Range:
(-1, 0, or +1)
Location:
Line 4, Option 4
Default:
0 (Conventional rounding)
Change Activation:
Sign off all registers.

This option determines how points are rounded in the points calculation at the end
of each preferred customer transaction as follows:

Value Explanation
-1 Round down
0 Half adjust
+1 Round up

92 Electronic Marketing PRPQ

 This rounding is done to the nearest points multiple as defined in “Ratio of Points
Per Cents Purchased” on page 92.

Bonus Item Points Limit

LINE 4

4,1,1,0,999999,20,0,0,0,0
_______
↑
Bonus item points limit
Range:
(0 - 999999)
Location:
Line 4, Option 5
Default:
999999 (no real limit)
Change Activation:
Sign off all registers.

This option determines the maximum number of bonus points (excluding boundary
points) that a customer can receive in a single transaction without a manager’s
override. These bonus points are accumulated through bonus point items or bonus
point coupons. Boundary points are awarded as the customer’s purchases cross
thresholds set in “Bonus Points to be Awarded at Boundary Crossing” on page 126.

Preferred Coupons Buffered in Memory

LINE 4

4,1,1,0,999999,20,0,0,0,0
__
↑
Preferred coupons buffered in memory
| Range:
| (0 - 199)
Location:
Line 4, Option 6
Default:
20 (20 Coupons buffered)
Change Activation:
Sign off all registers.

This option allows preferred customer coupons to be buffered in terminal memory

so that frequently used coupons need not cause a lookup from the Item Record
File. The option is specified as a single numeric value that defines the number of
coupon records to be buffered in memory. A value of zero prevents coupon
buffering.

The buffer is in extended terminal memory and does not use terminal data space.
Each buffer entry requires approximately 50 bytes of terminal memory. The default
value of 20 uses about 1K of terminal memory.

Only preferred customer coupons are buffered with this option. They are
automatically saved in the buffer as they are seen at the terminal. When the buffer
is full, it wraps around to always keep the most recently used coupons. The buffer
is cleared at each operator sign-on. This option requires all registers to sign-off in
order to pick up a change to a preferred customer coupon item record. The benefit

Chapter 6. Personalization of Preferred Customer Options and Messages 93

 of this function is particularly evident when coupons targeted to individual customers
are used, and the customer number is entered at the start of a transaction. This
option assures that the targeted coupon item records are read from file only once
for any customer though they might be processed multiple times.

Maximum Points to Carry from One Period to Another

LINE 4

4,1,1,0,999999,20,0,0,0,0
__
↑
Maximum Points to Carry from One Period to Another
Range:
(0 - 999999999)
Location:
Line 4, Option 7
Default:
0 (each new period starts with all points reset)
Change Activation:
None.

This option has meaning only if period points are being used for redemption and the
period close procedure EAMUROLP is being used to close a points activity period.
When these conditions are met, this value option determines the maximum amount
of points that can be carried from one period into another. A value of 0 for this
option causes all points totals to be reset for a new period while a value of
999999999 allows all points to carry forward into the new points activity period. The
option can be set between these two extremes to allow the customer a reasonable
time to redeem earned points while still limiting the stores liability by forcing the
customers with points above this limit to use them or lose them. Upon execution,
the activity period close procedure reduces all period point totals above this limit
down to the limit.

Automatic Close of the Points Activity Period

LINE 4

4,1,1,0,999999,20,0,0,0,0
__
↑
Automatic Close of the Points Activity Period
Range: (-7 to 6)
Location: Line 4, Option 8
Default: 0 (No automatic close of activity totals)
Change Activation:
Stop and Restart Checkout Support.

You can cause the close of the Preferred Customer points activity period to proceed
automatically at the correct day and time through this option. The alternative to this
automatic close of the period is a manual close of the period through the provided
user procedure, but it is anticipated that most users will want to select the automatic
close through this value option. This value option defines the time for the automatic
close as follows:

6= Close Annually (Jan. 1)

5= Close Twice a year (Jan. 1, July 1)

94 Electronic Marketing PRPQ

4= Close Every 4 Months (Jan. 1, May 1, Sept. 1)
3= Close Quarterly (Jan. 1, April 1, July 1, Oct. 1
2= Close Every 2 Months (Jan. 1, March 1, ... Nov. 1)
1= Close Monthly (1st of each month)
0= NO automatic close of the activity period
-1 = Close every Sunday night (Monday morning)
-2 = Close every Monday night (Tuesday morning)
-3 = Close every Tuesday night (Wednesday morning)
-4 = Close every Wednesday night (Thursday morning)
-5 = Close every Thursday night (Friday morning)
-6 = Close every Friday night (Saturday morning)
-7 = Close every Saturday night (Sunday morning)

The close of the activity period is always performed just after midnight or just after
an early morning close of the reporting period whichever comes last. This assumes
that the close of the reporting period occurs at night or in the morning and that only
one close of the reporting period will ever occur between Noon and Noon of the
following day. If the reporting period is closed daily, then any of these options are
available, but if the reporting period is closed weekly, then this option can be used
only to close the activity period on the same weekly schedule as the store close.
Note that an activity period close on the first of a month occurs as early as possible
(just after midnight) on the first of the month so that each activity period spans the
fewest possible months.

If this option is chosen, then the program EAMUROLP must be configured as a

background program to be started at IPL so that the close program will be restarted
if a controller failure occurs between the store close and the completion of an
activity period close. This program will do no harm if it is started by an IPL that is
not on the night of an expected close or if it is started multiple times on the night of
an expected close. This program can be manually activated on the night of an
expected close through the background activation screen as an alternative to using
the manual user procedure if no store close is performed on the night that the
activity close is desired.

Automatic Execution Time for Batch Updates

LINE 4

4,1,1,0,999999,20,0,0,0,0
__
↑
Automatic Execution Time for Batch Updates
Range:
(0 to 24)
Location:
Line 4, Option 9
Default:
0 (No automatic start of BATCH processing)
Change Activation:
Stop and Restart Checkout Support.

This value option provides the hour after which to automatically start the BATCH
maintenance program EAMUBATP each day. A value of 1 says the start BATCH

Chapter 6. Personalization of Preferred Customer Options and Messages 95

 processing after 1:00 AM each day, 2 says to start BATCH processing after 2:00 AM
each day, ... , 23 says to start BATCH processing after 11:00 PM each day, and 24
says to start BATCH processing anytime after midnight. A value of 0 means to
never automatically start BATCH processing. BATCH processing will not be started
more than once a day unless file access errors occur.

The BATCH program EAMUBATP is a file maintenance utility that applies

maintenance updates to the Preferred Customer keyed files from the input file
[Link]. If this program is started when no maintenance input is present,
the program stops. It is normal for keyed file maintenance updates to be sent from
a central site to the EAMBATCH input file after which the host would normally issue
a “Start User Program” command to start the BATCH maintenance processing. This
option provides an alternative and/or a backup to the “Start User Program” interface
from the host to assure that BATCH maintenance updates are processed at least
once a day. The option on when to start the program is provided so that all
maintenance updates can be expected to be present when the processing is done.
BATCH processing is not started right on the designated hour, but rather as soon
after that activity in the store triggers the checkout support process. An operator
sign-on or sign-off at a register, the first transaction that ends in a new hour, any
close of reporting totals, or any restart of checkout support can trigger the start of
BATCH processing after the start of the designated hour. If this option is set to 4:00
AM because all host transmissions are normally completed by then, but the store
does not open until 7:00 AM, then BATCH processing will not likely start until the
first operator signs on to a register around 7:00 AM.

Automatic Execution Time for Transfer Processing

LINE 4

4,1,1,0,999999,20,0,0,0,0
__
↑
Automatic Execution Time for Transfer Processing
Range:
(0 to 24)
Location:
Line 4, Option 10
Default:
0 (No automatic start of transfer processing)
Change Activation:
Stop and Restart Checkout Support.

This value option provides the hour after which to automatically start the points
transfer program EAMUXFER each day. The value selected for this option has the
same meaning as for the prior option which starts Batch processing. The only
difference between this option and the prior option is the background program
which is started. The transfer program EAMUXFER is a file maintenance program
that applies points updates to the Preferred Customer Activity file or the Preferred
Customer Transfer file using Preferred Activity Transfer files as input. If this program
is started when no activity transfer input is present, the program just stops. Activity
transfer data is normally pulled from various stores and then sent from a central site
after which a “Start User Program” command is sent to start the transfer
processing. This option provides an alternative and/or a backup to the “Start User
Program” interface from the host to assure that transfer updates are processed at
least once a day. The option on when to start the program is provided so that all
transfer updates can be expected to be present when the processing is done.

96 Electronic Marketing PRPQ

Coupon Velocity Code Range for Preferred Customers
LINE 5

300,399,0,0,1,9999,0,0,0,0
_______
↑
Coupon velocity code range for preferred customers
Range:
(0 - 9999)
Location:
Line 5, Options 1 and 2
Default:
300,399 (Preferred customer UPCs are between 299 and 400)
Change Activation:
Sign off all registers.

This option defines the range of velocity codes reserved exclusively for preferred
customers. The option consists of two numbers separated by a comma. The first
number defines the lowest preferred customer item code and the second number
defines the highest preferred customer item code. Any linked-to item code within
this range is processed only for preferred customers; any linked-to item code
outside of this range is processed for all customers.

One function of this option is to provide automatic discounts to preferred customers

by giving automatic coupons for selected items. These automatic coupons are
defined through links to item records. This unique processing applies not only to
coupons, but also to any item including bonus point items. Any keyed UPCs within
this defined range will also be valid only for preferred customers to allow for paper
coupons that are limited to identified preferred customers. Preferred customer totals
are accumulated only for coupons within this range.

Velocity Code Range for Reusable Targeted Coupons

LINE 5

300,399,0,0,1,9999,0,0,0,0
____
↑
Velocity code range for reusable targeted coupons
Range:
(0 - 9999 and within the coupon velocity code range for preferred
customers. See “Velocity Code Range for Reusable Targeted Coupons”.)
Location:
Line 5, Options 3 and 4
Default:
0,0 (No targeted coupons are reusable.)
Change Activation:
Sign off all registers; stop checkout support then restart checkout support.

This option determines which targeted coupons can be used in more than one
transaction. The first number defines the lowest reusable coupon item code and the
second number defines the highest reusable coupon item code. A targeted coupon
with a velocity code outside the range specified by this option is good only in one
transaction. It is automatically deleted from the customer activity record after the
first transaction in which it is used. A targeted coupon with a velocity code inside
the range specified by this option remains available in the customer‘s activity record
until it is removed by an in-store or host update of the record.

Chapter 6. Personalization of Preferred Customer Options and Messages 97

 The quantity allowed flag in the coupon item record determines whether a targeted
coupon can be used more than once in a transaction. This option and the quantity
allowed flag enables an enterprise to specify the following options for targeted
preferred customer coupons:
v Available only once
v Available for all matching items in one transaction
v Available once per transaction until removed
v Available for all matching items in all transaction until removed.

Valid Range of Non-Home Store Numbers

LINE 5

300,399,0,0,1,9999,0,0,0,0
______
↑
Valid range of non-home store numbers
Range:
(0 - 9999)
Location:
Line 5, Options 5 and 6
Default:
1,9999 (Valid store numbers range from 1 to 9999)
Change Activation:
Sign off all registers.

All entered customer numbers are validated first against the customer activity file
and then against the list of valid home store numbers. If an entered number is not
on file and its imbedded store number is not a home store number, the store
number is validated to against the range specified by this option. This option
consists of two numbers separated by a comma. The first number defines the
lowest valid store number and the second number defines the highest valid store
number. This option provides a sanity check so that the preferred customer
processing cannot be activated by any entered customer number. Customer
numbers that are added through the in-store enrollment procedure are also
validated against this store number range. If they do not validate properly, a
warning message is given. In order to add to the activity file store numbers outside
of the normal range, an operator must re-key the invalid numbers or an operator or
manager must perform an override.

Automatic Execution Time for Reference Processing

LINE 6

0,0,0,0,0,0,0,0,0,0
__
↑
Automatic Execution Time for Reference Processing
Range:
(0 to 24)
Location:
Line 6, Option 1
Default:
0 (No automatic start of reference processing)
Change Activation:
Stop and Restart Checkout Support.

This option provides the hour after which to automatically start the points reference
program EAMUREFA each day. A value of 1 starts reference processing after 1:00
AM each day, 2 starts reference processing after 2:00 AM each day, ... , 23 starts

98 Electronic Marketing PRPQ

reference processing after 11:00 PM each day, and 24 starts reference processing
anytime after midnight. A value of 0 cancels automatic execution of reference
processing. Reference processing is not started more than once a day unless file
access errors occur. These option values have the same meaning as the values for
the other two options which automatically start background programs.

For more information on the EAMUREFA program, see “EAMUREFA - Preferred

Customer Reference Processing” on page 293.

Multiplier for Coupon Minimum Purchase Amounts

LINE 6

0,0,0,0,0,0,0,0,0,0
__
↑
Multiplier for coupon minimum purchase amounts
Range:
(1, 10, 100, or 1000)
Location:
Line 6, Option 2
Default:
0 (Use minimum purchase amount from file)
Change Activation:
Sign-off all registers.

This option provides a means to shift the range of minimum purchase amounts for
coupons in the item record file. Each coupon record can require a minimum
purchase for the coupon to be valid. The minimum purchase amount is contained in
a 2-byte integer field in the item record and ranges from 0 to 32767. While 327.67
dollars is an adequate upper limit for a minimum purchase requirement in U.S.
dollars, this upper limit is restrictive for other currencies that have less purchasing
power per monetary unit. This option provides a multiplier which is used to shift the
range of minimum purchase values from the item record file.

The only valid values for this option are 1, 10, 100, and 1000. Any other value is
treated as 1. A value of 1 uses the amounts from the item record field without value
shifting. A value of 100 multiplies the value from the item record by 100 and thus
shift the range of minimum purchase requirements so that the smallest non-zero
value is 100 and the largest value is 3276700.

Key Definition for Customer Entry Key

LINE 6

0,0,0,0,0,0,0,0,0,0
__
↑
Key definition for customer entry key
Range:
(0, 61-199 excluding previously used codes)
Location:
Line 6, Option 3
Default:
0 (No CUSTOMER key is defined)
Change Activation:
Sign-off all registers.

This option defines the function code of a CUSTOMER key to be used to identify
input data as a customer number. Option 7.4 identifies a category number to

Chapter 6. Personalization of Preferred Customer Options and Messages 99

 identify scannable customer numbers and the key sequence NOSALE, DATA
ENTRY, customer, ENTER can be used to identify non-scannable keyed customer
numbers. This option provides another alternative method for identifying customer
numbers at a terminal. After this new CUSTOMER key has been defined and
configured (see Configuring a CUSTOMER key), the new key can be used in the
following input sequences:
customer,CUSTOMER
CUSTOMER, (prompt), customer, ENTER
CUSTOMER, (prompt), expiration date, “/”, customer, ENTER
where the “customer, ENTER” in response to the prompt can be
replaced by scanning a UPC or swiping a magnetic card.

This option does not provide any new function. The same input can be made using
the NOSALE, DATA ENTRY, ENTER key sequence, but the new sequence is
preferable when used very often such as with magnetic stripe reader (MSR) input.
Note that the MSR can be used for entering customer numbers only in response to
the “Enter Customer Number” prompt that results from using a customer entry
sequence without an associated customer number.

The new function code can also be referenced in the Label Format Table as an
alternative method of identifying scanned customer numbers other than through the
category number.

Any valid unique function code that has been correctly configured for a
CUSTOMER key can be entered for this option, however, a value of 89 is
suggested and is used in the configuration instructions. Function codes from 200 up
are reserved for department and lookup keys and many of the function codes
between 61 and 199 are already used by the supermarket application and therefore
are not available for this option value. A value of 0 indicates that no CUSTOMER
key is defined.

Home Store Location in Customer Number

LINE 7

11,2,4,9,0,0,0,1,1,0
_______
↑
Home store location in customer number
Range:
(5 - 18, 0 - 18, 0 - 4)
Location:
Line 7, Options 1, 2, and 3
Default:
11,2,4 (4-digit store number follows UPC category digit)
Change Activation:
Sign off all registers; stop checkout support then restart checkout support.

In order to support multiple stores with the preferred customer program, this code
supports the concept of a home store for each customer. Preferred customers
receive discounts in any participating store, however they can only see their status
or collect preferred customer bonuses only in their home store. The totals for
preferred customers need only to reside only in their home store. A preferred
customer‘s home store number is normally imbedded in their customer ID number.
This option defines the offset for home store numbers imbedded in customer ID
numbers.

The option consists of the following three numeric values:

100 Electronic Marketing PRPQ

v The first value defines the maximum length of a customer number. This number
is only used to reference the offsets of the store number and the validation digits
in a customer number.
v The second value in this option defines the offset of the start of a store number
within a customer number of maximum length (the leftmost digit is the first digit
and the rightmost digit is the maximum digit). Even if your customer numbers are
of fewer digits than the defined maximum, this offset must to be specified as
though there were enough leading zeroes to form a maximum-sized number.
v The third number in this option defines the number of digits in an imbedded store
number. There is no requirement that a store number be included in the
customer number. If there is no store number in a customer number, you must
specify both the offset and the length as zero.

Category Number to Uniquely Identify Customer Numbers

LINE 7

11,2,4,9,0,0,0,1,1,0
__
↑
Category number to uniquely identify customer number
Range:
(0 - 99)
Location:
Line 7, Option 4
Default:
9 (Category 9 uniquely identifies customer numbers.)
Change Activation:
Sign off all registers.

This option enables an enterprise to specify a UPC/EAN category number to

uniquely identify customer ID numbers. The category number is the first digit in an
11-digit UPC number or the first 2 digits in a 12-digit EAN number. A value of No (0)
in this option means that no category uniquely identifies customer numbers. If the
category number of the scanned UPC is unique and is defined in this option,
function keys are not required for scanned customer numbers. Customer numbers
can always be keyed in the sequence NOSALE, DATA ENTRY, customer number,
ENTER or be scanned following the NOSALE and DATA ENTRY keys. For more
information, see “How to Enter a Customer ID Number” on page 177.

Validation Digits in Customer Number

LINE 7

11,2,4,9,0,0,0,1,1,0
_____
↑
Validation digits in customer number
Range:
(0 - 18, 0 - 4, 0 - 9999)
Location:
Line 7, Options 5, 6, and 7
Default:
0,0,0 (No validation digits)
Change Activation:
Sign off all registers.

Selected digits in the customer number can be required to have a defined value in
order for the customer number to be accepted as a non-home or new customer

Chapter 6. Personalization of Preferred Customer Options and Messages 101

 number when there is no record in the activity file for the customer number. The
purpose of these validation digits in the customer number is to allow one chain’s
preferred customer card to be distinguished from another’s when both chains use
the same category number and have a similar range of valid non-home store
numbers.

If an enterprise uses validation digits, a customer number that is not on file and
does not contain the correct validation digits in the selected location is rejected as
an invalid customer number and an operator guidance is given.

This option consists of the following three numeric values:

v The first value in this option defines the offset of the start of the validation digits
within a customer ID number of maximum length as defined by option 7.1. (The
leftmost digit is the first digit and the rightmost digit is the maximum digit). Even if
your customer numbers are of fewer digits than the defined maximum, this offset
needs to be specified as though there were enough leading zeroes to form a
maximum-sized number.
v The second number in this option defines the number of consecutive digits to be
used for validation.
v The third number in this option defines the expected value for the validation
digits. There is no requirement that validation digits be included in the customer
number. If no validation digits are needed in the customer number, you must
specify both the offset and the length as zero.

Count Home Store Numbers Supported by This Store

LINE 7

11,2,4,9,0,0,0,1,1,0
__
↑
Count home numbers supported by this store
Range:
(0 - 9)
Location:
Line 7, Option 8
Default:
1 (Single supported home store number)
Change Activation:
Sign off all registers; stop checkout support; then restart checkout support.

A store normally supports only one home store number. But, it is possible to support
more than one so that several stores located close together can provide a zone of
support. Each store would support the others’ home store number as well as its
own. If a customer has a record in a store’s customer activity file, the count of
home stores with the associated store numbers is not referenced because the file
defines a home store account for in-store processing purposes. But the count of
home stores is referenced when a customer activity record is not in a store’s activity
file or when the system must determine which activity updates to send out of store.
If home store numbers are not defined, this option must be set to zero.

Count Home Store Numbers Supported Only by This Store

LINE 7

11,2,4,9,0,0,0,1,1,0
__
↑
Count home numbers supported only by this store

102 Electronic Marketing PRPQ

Range:
(0 - 9)
Location:
Line 7, Option 9
Default:
1 (Single number supported only in store)
Change Activation:
Sign off all registers; stop checkout support then restart checkout support.

It is possible to support a given store number from multiple physical stores. This
support is provided so that several stores located close together can provide a zone
of support with each store supporting the others’ home store number as well as its
own. This option defines the count of home store numbers supported only by this
store. This count is applied to the list of home store numbers supported by this
store (see “Home Store Numbers Supported by This Store”), beginning with the first
number in the list. If this count is less than the count of store numbers supported by
this store, the store numbers provided at the end of the list are supported with both
in-store updates and out-of-store updates. That is, the customers from the selected
store numbers have their totals updated in the customer activity file (like home-store
support) and also have their totals updated in the activity transfer file (like
non-home store support). This option must be less than or equal to the total count
of home store numbers supported by this store.

Home Store Numbers Supported by This Store

LINE 8

0
__
↑
Home numbers supported by this store
Range:
(0 - 9 entries separated by commas, each from 0 to 9999)
Location:
Line 8, Options 1 to 9 (Number of entries depends on count of home store
numbers supported by this store as defined by Line 7 Option 8.)
Default:
Single value of 0 (Use configured store number)
Change Activation:
Sign off all registers; stop checkout support then restart checkout support.

This option provides a list of supported home store numbers. There must be as
many store numbers defined as are called for by the count of home store numbers
defined in “Count Home Store Numbers Supported by This Store” on page 102.
Each store number can range from 0 to 9999. Any store number of zero that is
defined in the list is replaced by the store number defined in system configuration.
The store number is printed on the receipt and journal tapes. The store numbers
are provided as a set of numeric characters separated by commas. If you specified
four in Line 7 Option 8, you would enter the four store numbers here. For example,
store numbers 21,22,23, 24 could be added here, separated by commas. If the
count of home store numbers is zero, line 8 should be deleted from the options file
altogether such that line 9 follows line 7. See “Non-Home Store Concept” on
page 13 for information on the implication of defining no home stores.

Modulo Check Customer Numbers During Enrollment

LINE 9

0,0,0,0,0,0,0,0,0,0

Chapter 6. Personalization of Preferred Customer Options and Messages 103

 __
↑
Modulo check customer numbers during enrollment
Range:
Yes (-1), No (0)
Location:
Line 9, Option 1
Default:
No (0) (No modulo checking)
Change Activation:
Enter the enrollment procedure.

This Yes/No option determines whether customer numbers entered in the in-store
enrollment procedure are modulo checked or not. The modulo checking assumes a
standard UPC (11 digits) with a trailing modulo check character. This option usually
applies to scannable customer numbers.

A value of No (0) prevents modulo checking and a value of Yes (-1) assures modulo
checking. At the time that this option is selected, the modulo check digit is not
included in the customer number on file. The referenced account number is modulo
checked if this option is selected, and the referenced number stored on the file
contains the modulo check digit as the last character.

Log Enrollment Alterations to a Separate Sequential File

LINE 9

0,0,0,0,0,0,0,0,0,0
___
↑
Log alterations to enrollment file to separate sequential file
Range:
Yes (-1), No (0)
Location:
Line 9, Options 2 and 3
Default:
0,0 (No logging to Enrollment Change file)
Change Activation:
Enter the enrollment procedure.

This set of two 0 or -1 options determines if changed enrollment records are written
to the Enrollment Change File. The first option determines if additions, changes or
deletions to customer enrollment records are logged. The second option determines
if redemptions and adjustments made through the enrollment procedure are logged.

A value of No (0) in either of the options prevents logging of the enrollment record.
A value of Yes (-1) assures logging of the changed enrollment record. Redemptions
and adjustments do not change any of the demographic data in the enrollment
record, but they do cause fields defining the last redemption or adjustment to
change.

Allow Erase of Customer Points

LINE 9

0,0,0,0,0,0,0,0,0,0
__
↑
Allow erase of customer points

104 Electronic Marketing PRPQ

Range:
Yes (-1), No (0)
Location:
Line 9, Option 4
Default:
No (0) (No erasure of customer points)
Change Activation:
Enter the enrollment procedure.

This Yes/No option determines whether the customer activity record containing
points history is erased when the enrollment record is erased during the enrollment
procedure.

A value of No (0) prevents deletion of customer points through erasure of the

enrollment record. A value of Yes (-1) assures deletion of the activity record and all
associated customer history with the erasure of the enrollment record.

If there is no points history for a customer number being erased (the number has
not been used in a sales transaction), the activity record is always erased with the
enrollment record. If this option is set, and the enrollment record for an active
customer is deleted and re-added through the enrollment procedure, all customer
history is maintained.

Form Number Required on Redemption, Adjustment, and/or Rain

check
LINE 9

0,0,0,0,0,0,0,0,0,0
_____
↑
Form number required on redemption, adjustment, and/or Rain check
Range:
Yes (-1), No (0)
Location:
Line 9, Options 5, 6, and 7
Default:
No (0), No (0), No (0) (Form numbers are not required.)
Change Activation:
Enter the enrollment procedure.

An optional form number can be entered and saved for a redemption, an

adjustment, or a rain check adjustment made through the in-store enrollment
procedure. This set of three Yes/No options determines whether the form number is
required for any of these functions. The first option applies to redemptions
performed through enrollment procedure five. The second option applies to
adjustments performed through enrollment procedure six. The third option applies to
rain check adjustment performed through enrollment procedure seven.

A value of Yes (-1) in any of these three options requires that a form number be
entered with the specified enrollment procedure. A value of No (0) in the any of
these three options leaves the entry of a form number on a specified enrollment
procedure to the discretion of the operator.

Chapter 6. Personalization of Preferred Customer Options and Messages 105

 Employee Number Required on Redemption, Adjustment, and/or
Rain check
LINE 9

0,0,0,0,0,0,0,0,0,0
_____
↑
Employee number required on redemption, adjustment, and/or Rain check
Range:
Yes (-1), No (0)
Location:
Line 9, Options 8, 9, and 10
Default:
No (0), No (0), No (0) (Employee numbers are not required.)
Change Activation:
Enter the enrollment procedure.

An optional employee number can be entered and saved for a redemption, an

adjustment, or a rain check adjustment made through the in-store enrollment
procedure. This set of three Yes/No options determines whether the employee
number is required for any of these functions. The first option applies to
redemptions performed through enrollment procedure five. The second option
applies to adjustments performed through enrollment procedure six. The third option
applies to rain check adjustment performed through enrollment procedure seven. A
value of Yes (-1) in any of these three options requires that an employee number be
entered with the specified enrollment procedure. A value of No (0) in the any of
these three options leaves the entry of an employee number in the specified
enrollment procedure at the discretion of the operator.

Selectively Deactivate Each of the Seven Enrollment Functions

LINE 10

0,0,0,0,0,0,0,0,-1,0
_____________
↑
Selectively deactivate each of the seven enrollment procedure functions
Range:
Yes (-1), No (0)
Location:
Line 10, Options 1 through 7
Default:
No (0), No (0), No (0), No (0), No (0), No (0), No (0) (All functions are
active.)
Change Activation:
Enter the enrollment procedure.

The main menu of the in-store enrollment procedure allows for seven function
selections as follows:
1. Change a customer record
2. Add a customer record
3. Erase a customer record
4. Display a customer record
5. Redeem award
6. Make adjustments
7. Enter rain checks.

106 Electronic Marketing PRPQ

This line of seven Yes/No options allows each of these seven functions to be
selectively deactivated. The options apply to the functions in the order in which they
appear above.

A value of Yes (-1) in any of these options deactivates the selected function such
that an operator guidance message will be given if the function is chosen. A value
of No (0) in any of these options lets any operator select and execute the target
function.

Run the Enrollment Procedure Without an Enrollment File

LINE 10

0,0,0,0,0,0,0,0,-1,0
__
↑
Run the enrollment procedure without an enrollment file
Range:
Yes (-1), No (0)
Location:
Line 10, Option 8
Default:
No (0) (Create and use enrollment file.)
Change Activation:
Enter the enrollment procedure.

The enrollment procedure uses the in-store enrollment file. Supporting an in-store
enrollment file is optional. You may choose to maintain the demographic data on
your customers on another system. This Yes/No option allows the enrollment
procedure to run without an enrollment file, and prevents this procedure from
creating an enrollment file. This allows an enterprise to use the enrollment
procedure to add, update, display, or delete activity data, adjust points balances,
and record rain check adjustments when enrollment data is not present in a store. A
value of Yes (-1) causes the enrollment procedure to bypass all accesses to the
enrollment file and present only activity data on the screens. A value of No (0)
causes the enrollment procedure to create and access an in-store enrollment file
and present both enrollment and activity data on the display screens.

Enrollment Zip Fields Are Numeric and Packed

LINE 10

0,0,0,0,0,0,0,0,-1,0
__
↑
Enrollment zip fields are numeric and packed
Range:
Yes (-1), No (0)
Location:
Line 10, Option 9
Default:
Yes (-1) (Zip fields are numeric and packed)
Change Activation:
Enter the enrollment procedure.

This Yes/No option defines the format of the two enrollment ZIP fields (ZIP and
ZIPEXT). They can be either all numeric and stored as packed decimal fields or
alphanumeric and stored as ASCII fields. If the option has a value of Yes (-1), they
are numeric fields and are stored as packed decimal numbers in the enrollment file,
EAMFBCUS, at offset 112 and 115. If the option has a value of No (0), then these

Chapter 6. Personalization of Preferred Customer Options and Messages 107

 fields are alphanumeric fields and they are stored in ASCII format at offset 224,
length 5 for the ZIP field and offset 229, length 4 for the ZIPEXT field. Any change
to this option requires a corresponding change to the enrollment data files
([Link] and [Link]).

Only Allow One Terminal to Have Negative Transactions

LINE 11

0,240,0,18,2,5,4,0,9,0
__
↑
Only allow one terminal to have negative transactions
Range:
(0 to 999)
Location:
Line 11, Option 1
Default:
0 (Any terminal can complete a negative transaction.)
Change Activation:
Sign off all registers.

This option prevents all but a single designated terminal from returning money to a
customer due to a negative transaction. This means that all refunds, payouts, and
coupons outside of orders must be handled at the designated register. A manager’s
override is still required for a negative transaction. A value of 0 will allow any
terminal to have a negative transaction with a manager’s override. Any non-zero
value is used as the terminal number of the single register at which negative
transactions are allowed. If the option is set to a nonzero value that does not match
a valid register number, no terminal is allowed to complete a transaction that returns
money to a customer.

Define Which Taxes to Turn On With the Tax/NoTax Key

LINE 11

0,240,0,18,2,5,4,0,9,0
___
↑
Define which taxes to turn on with the Tax/NoTax key
Range:
(0 to 240 in increments of 16)
Location:
Line 11, Option 2
Default:
240 (Tax key turns on all taxes.)
Change Activation:
Sign off all registers.

This option defines which tax options to set when the Tax/NoTax key is used with a
department or lookup key and no taxes are defined in the item record. The option
defaults to all four taxes to initiate the application. If this option is set to zero, the
Tax/NoTax key becomes a NoTax key only.

A value of 128 selects Tax A, 64 selects Tax B, 32 selects Tax C and 16 selects Tax
D. The option must be specified as zero or a sum of the values for the selected tax
options. If you wish the Tax key to turn on only Tax A and Tax B, you must set the
option value to 192 (128 + 64).

108 Electronic Marketing PRPQ

KIOSK Points Message Offset
LINE 11

0,240,0,18,2,5,4,0,9,0
__
↑
Kiosk points message offset
Range:
(0, 10 - 47)
Location:
Line 11, Option 3
Default:
0 (Use standard points messages in Kiosk mode)
Change Activation:
Sign-off all registers.

When a customer scans his card at a Kiosk terminal, he will normally see the same
points message (display and print) that he would see in sales transaction. The three
messages for a home store customer, a non-home store customer, and a new
home store customer are defined at the top (messages 0, 1, and 2) of the Preferred
Customer Message file. This option provides a displacement offset within the
Preferred Customer Message file at which to find the three comparable messages
for use at the Kiosk Terminal. This allows for different points messages to be used
at a self-service Kiosk than during a sales transaction. If you wish the home store
points message to be used in Kiosk mode to be message 20 in the Preferred
Customer Message file (note that this is the 21st message because of message 0),
then you would set this option to a value of 20. This value would define the 22nd
and 23rd messages in the file to be the non-home customer and new home
customer messages for use at any Kiosk register. A value of 0 for this option leaves
the Kiosk points messages the same as the points messages at a normal checkout
lane. A non-zero value for this option defines the offset (10 - 47) at which a special
Kiosk points message will be defined in the Preferred Customer Message file.

Maximum Item Record Descriptor Length

LINE 11

0,240,0,18,2,5,4,0,9,0
___
↑
Maximum item record descriptor length
Range:
(12 - 18)
Location:
Line 11, Option 4
Default:
18 Use full descriptor length)
Change Activation:
Sign-off all registers.

The item record file allows for an 18-character item descriptor. Many users support
only descriptors of a shorter length. This option allows the maximum length of the
item descriptor to be defined as less than 18 characters so that the unused portion
of the item descriptor field is available for user defined purposes. For example, if
this option is set to 12, then only the first 12 characters of the item record descriptor
field are printed on the customer receipt or shown on the customer display and the
excess 6 characters can be used to hold user data. The characters defined as
excess by this option are truncated from the item descriptor when the item record is
read into the terminal and are saved in the variable [Link]$, which is

Chapter 6. Personalization of Preferred Customer Options and Messages 109

 available to user exits. This option only truncates the item descriptor shown by
terminal sales. All item record maintenance and reporting procedures still show the
full 18 character descriptor field so that they can be used to maintain and report
characters in the user portion of this field.

Length of Enrollment State Field

LINE 11

0,240,0,18,2,5,4,0,9,0
___
↑
Length of enrollment state field
Range:
(0 - 3)
Location:
Line 11, Option 5
Default:
2 (State field is two bytes long)
Change Activation:
Enter the enrollment procedure.

This option, which has a range of 0 to 3, defines the length of the STATE field. If
option is set to 2 or less, then the data is stored in the original location, i.e offset
110 in EAMFBCUS. If the option has a value of 3, then the first two digits are
stored at offset 110, with the last digit being stored at offset 223. Any change to this
option requires a corresponding change to the enrollment data files
([Link] and [Link]).

Length of Enrollment ZIP Field

LINE 11

0,240,0,18,2,5,4,0,9,0
__
↑
Length of enrollment zip field
Range:
(0 - 5)
Location:
Line 11, Option 6
Default:
5 (ZIP field is five bytes long)
Change Activation:
Enter the enrollment procedure.

This option, which has a range of 0 to 5, defines the length of the ZIP field that is
displayed on the enrollment screen. When the field is stored within the enrollment
record the full width of the field is always used. If the ZIP field is a numeric field, it
is padded to the left with enough zeros to make its length five before it is packed
and saved. If the field is an alphanumeric field it is padded on the right with enough
spaces to make its length five before it is saved. When read from the file, this
option is used to determine the correct number of digits or letters to display. Any
change to this option requires a corresponding change to the enrollment data files
([Link] and [Link]).

110 Electronic Marketing PRPQ

Length of Enrollment ZIPEXT Field
LINE 11

0,240,0,0,2,5,4,0,9,0
__
↑
Length of enrollment zipext field
Range:
(0 - 4)
Location:
Line 11, Option 7
Default:
4 (ZIPEXT field is four bytes long)
Change Activation:
Enter the enrollment procedure.

This option, which has a range of 0 to 4, defines the length of the ZIPEXT field that
is displayed on the enrollment screen. When the field is stored within the enrollment
record, the full width of the field is always used. If the ZIPEXT field is a numeric
field, it is padded to the left with enough zeros to make its length four before it is
packed and saved. If the field is an alphanumeric field, it is padded on the right with
enough spaces to make its length four before it is saved. When read from the file,
this option is used to determine the correct number of digits or letters to display.
Any change to this option requires a corresponding change to the enrollment data
files ([Link] and [Link]).

Count of Customer Defined Demographic Fields

LINE 11

0,240,0,0,2,5,0,0,9,0
__
↑
Count of customer defined demographic fields
Range:
(0 - 6)
Location:
Line 11, Option 8
Default:
0 (No customer defined fields are being used)
Change Activation:
Enter the enrollment procedure.

This option, which has a range of 0 to 6, defines the number of customer defined
demographic fields, and their matching descriptor, that are to be displayed on the
enrollment screens of the enrollment procedure. Each field is one digit long,
allowing for the entry of a single number, 0-9. The customer defines what this
number means. Six descriptors, 1132-1137 in [Link] (the Electronic
Marketing descriptor file), are displayed next to these 6 input fields. These
descriptors can be modified as needed to assign a meaning to these fields. The
default for this option is 0, that is no fields or descriptors are visible on the screen.
All of these invisible fields are still present on the screen and can be tabbed
through. As these are the last fields on the enrollment screen, it is a simple matter
to press the HOME key when an invisible field is reached and you will be returned
to the top of the screen. This demographic data is stored in packed format, two
demographic fields per byte, starting at offset 152 for 1/2, 153 for 3/4 and 154 for
5/6.

Chapter 6. Personalization of Preferred Customer Options and Messages 111

 Length of Enrollment Social Security Field
LINE 11

0,240,0,0,2,5,4,0,9,0
__
↑
Length of enrollment social security field
Range:
(0 - 14)
Location:
Line 11, Option 9
Default:
9 (The social security field is 9 digits long)
Change Activation:
Enter the enrollment procedure.

This option, which has a range of 0 to 14, defines the length of the social security
field that is displayed on the enrollment screen. When the field is stored within the
enrollment record, the full width of the field is always used. It is padded to the right
with enough zeros to make it length 14 before it is packed and saved. The first five
bytes at offset 158 of EAMFBCUS. The last two bytes are stored at offset 156. Any
change to this option requires a corresponding change to the enrollment data files
([Link] and [Link]).

Accumulate Ratio of PLU Entries to DEPT Key Entries

LINE 12

0,0,0,0,0,0,0,0,0,0
__
↑
Accumulate ratio of plu entries to dept key entries
Range:
Yes (-1), No (0)
Location:
Line 12, Option 1
Default:
No (0) (Keyed UPCs are considered keyed sales.)
Change Activation:
Stop and Restart Checkout support.

The Supermarket Application accumulates a ratio of keyed to scanned totals. A

keyed UPC is considered a keyed sale. This Yes/No option determines whether a
keyed UPC is considered a keyed sale or a scanned sale. A value of No (0) leaves
the count of keyed UPCs in the keyed sales totals and a value of Yes (-1) moves
the count of keyed UPC sales into the scanned sales totals. This option changes
ratios of keyed to scanned totals to ratios of PLU sales to department key sales.
These ratios are shown in accounting and performance reports.

Accumulate Keyed Versus Scanned Totals by Department

LINE 12

0,0,0,0,0,0,0,0,0,0
__
↑
Accumulate keyed versus scanned totals by department
Range:
Yes (-1), No (0)

112 Electronic Marketing PRPQ

Location:
Line 12, Option 2
Default:
No (0) (No new totals by department)
Change Activation:
Stop and Restart Checkout support.

This Yes/No option accumulates two new totals in the user exit field in the
department totals records. The number of keyed UPC sales for a department and
the number of keyed department sales for a department are accumulated as two
two-byte positive integers in the user exit field. These new totals and the total count
of sales for a department allow the department analysis report to be altered to
present a ratio of keyed to scanned sales by department. Sample code to include
these new totals in this report is presented in “Chapter 4. Installation and
Configuration” on page 37. The report alterations determine whether keyed UPCs
are considered keyed sales or scanned sales.

A value of No (0) does not accumulate new department totals. A value of Yes (-1)
accumulates the two new totals for each department.

Weight Items Do Not Require Weight Key

LINE 12

0,0,0,0,0,0,0,0,0,0
__
↑
Weight items do not require weight key
Range:
Yes (-1), No (0)
Location:
Line 12, Option 3
Default:
No (0) (Weight key is required.)
Change Activation:
Sign off all registers.

The Supermarket Application requires an operator to press the Weight key to read
the scale for a weight item or to press the Clear key in response to a weight
prompt. This option allows weight items to be sold with a scale weight without the
Weight key or the Clear key being hit. The Weight key must still be pressed with a
price override on a weight item if the keyed price is the price per pound. If a price is
keyed on a weight item and the Weight key is not pressed, the price is taken as the
total item price and weight is not read from the scale.

A value of No (0) leaves the Weight and Clear key requirement intact. A value of
Yes (-1) removes the need to press this additional key in order to sell a weighted
item.

Display Backup Indicator at Registers

LINE 12

0,0,0,0,0,0,0,0,0,0
__
↑
Display backup indicators at registers
Range:
Yes (-1), No (0)

Chapter 6. Personalization of Preferred Customer Options and Messages 113

 Location:
Line 12, Option 4
Default:
No (0) (No backup indication)
Change Activation:
Sign off all registers.

This Yes/No option determines a backup indication of “*BU*” is displayed at all

registers serviced by a backup controller. The indication is not displayed constantly,
but only when it does not interfere with the display contents.

A value of No (0) does not cause the a new indication to be displayed. A value of
Yes (-1) causes the backup indication to be displayed.

Allow Tax Exemption Without a Discount Key

LINE 12

0,0,0,0,0,0,0,0,0,0
__
↑
Allow tax exemption without a discount key
Range:
Yes (-1), No (0)
Location:
Line 12, Option 5
Default:
No (0) (Tax exemption requires discount key.)
Change Activation:
Sign off all registers.

This Yes/No option determines whether a key sequence of

VOID,TAX/NOTAX,TOTAL is processed as though the sequence
TAX/NOTAX,DISCOUNT had been keyed. In order for this key sequence to lead to
a tax exemption, discount group two must be defined as a tax exemption in the
terminal options. See “Define Which Taxes to Turn On With the Tax/NoTax Key” on
page 108.

Also, the Input Sequence Table for all terminals that use this function must be
altered through the system configuration facilities. Function code 81 in the MAIN
state must be changed so that it is not mutually exclusive with position two. The
changed table(s) must be activated and the terminals reloaded in order to make the
change effective. If this change is not fully implemented, the new key sequence will
lead to a B003 operator guidance.

A value of No (0) requires the DISCOUNT key to be pressed for a tax exemption. A
value of Yes (-1) allows the new key sequence to cause a tax exemption.

Cash Checks Using a Sales Transaction

LINE 12

0,0,0,0,0,0,0,0,0,0
__
↑
Cash checks using a sales transaction
Range:
Yes (-1), No (0)
Location:
Line 12, Option 6

114 Electronic Marketing PRPQ

Default:
No (0) (Tender cashing procedure must be used.)
Change Activation:
Sign off all registers.

This Yes/No option determines whether a check or miscellaneous tender can be

accepted in a checkout transaction without requiring prior sales. This option
effectively provides an alternate tender cashing function that does not require a
signon or authorization and looks like a tender in a checkout transaction.

A value of No (0) requires that the check cashing procedure be used to cash a
check. A value of Yes (-1) allows a normal check tendering sequence to be used to
cash a check.

Remind Operator to Take Customer’s Money

LINE 12

0,0,0,0,0,0,0,0,0,0
__
↑
Remind operator to take a customer’s money
Range:
Yes (-1), No (0)
Location:
Line 12, Option 7
Default:
No (0) (No warning of inactivity in a transaction)
Change Activation:
Sign off all registers.

This Yes/No option determines whether a unique tone sounds following a period of
inactivity in an order after an item sale or a balance due request. The warning
sound reminds an operator to take a customer’s money. The duration of this period
is defined by the hidden option for the automatic balance due timeout. You can
change the hidden option [Link] using the EAMHIDOL program. This alarm
will continue through successive inactivity periods until the transaction is tendered
out or another sale is made. The CLEAR key resets the inactivity period.

A value of No (0) causes the inactivity alarm not to sound. A value of Yes (-1)
activates the inactivity alarm.

Interpret Restricted Time Periods as Unrestricted Times

LINE 12

0,0,0,0,0,0,0,0,0,0
__
↑
Interpret restricted time periods as unrestricted times
Range:
Yes (-1), No (0)
Location:
Line 12, Option 8
Default:
No (0) (Time periods define restricted periods.)
Change Activation:
Sign off all registers.

Chapter 6. Personalization of Preferred Customer Options and Messages 115

 This Yes/No option determines whether the restricted sales times in the terminal
options can be determined by unrestricted time periods. This allows a user to define
a continuous restricted time period that crosses the day boundary. For example, a
restricted time of 11 PM to 7 AM can be expressed as an unrestricted time of 7:00
to 23:00.

Note: In the Supermarket Application, the single restricted time definition per day
prevents this type of restricted time from being defined. If time periods are
not defined in the options for any given day, the whole day is presumed to
be unrestricted. To make the whole day restricted, one must define the start
and end of the unrestricted period to be the same nonzero value. This
requires a manual update of the store options because personalization does
not allow the start and end of a time period to be specified as the same
value.

A value of No (0) leaves the time periods defined in the options as restricted times.
A value of Yes (-1) causes the time periods defined in the options to be viewed as
unrestricted times.

Support for Multiple Cash Drawers

LINE 12

0,0,0,0,0,0,0,0,0,0
__
↑
Support for multiple cash drawers
Range:
Yes (-1), No (0)
Location:
Line 12, Option 9
Default:
No (0) (Only one cash drawer is supported.)
Change Activation:
Sign off all registers.

This Yes/No option provides support for two cash drawers so that a terminal with
two cash drawers attached and configured can use both drawers. With no manual
override, each successive operator sign-on will switch to the next cash drawer. By
signing off with the sequence OVERRIDE, SIGN-OFF, SIGN-OFF, operators
reserves their drawers so that they cannot be used until they return. (The code is
designed to allow operators to reserve a cash drawer during a break so that the
other cash drawer can be used and their till does not need to be moved.)

Either drawer can be reserved in this manner as long as both drawers are
operational and neither drawer is already reserved. Only one drawer at a time can
be reserved so that the register always has a cash drawer available. If only one
cash drawer is configured or only one cash drawer is attached and working, this
option uses that available drawer and does not allow it to be reserved.

The Input Sequence Table for all terminals that use this function must be altered
through the system configuration facilities. Function code 61 in the MAIN state must
be changed so that it is not mutually exclusive with position eight. The changed
table(s) must be activated and the terminals reloaded to make the change effective.
If this change is not fully implemented, the key sequence to reserve a drawer will
lead to a B003 operator guidance.

116 Electronic Marketing PRPQ

A value of No (0) allows only one cash drawer to be supported. A value of Yes (-1)
allows two cash drawers to be supported.

Show Time in 12-Hour Format

LINE 12

0,0,0,0,0,0,0,0,0,0
__
↑
Show time in 12-hour format
Range:
Yes (-1), No (0)
Location:
Line 12, Option 10
Default:
No (0) (Time printed in 24-hour format.)
Change Activation:
Sign off all registers.

This Yes/No option alters the time format in the store data line on the customer
receipt to be in 12-hour format (AM/PM) rather than 24-hour format. The three
additional print positions that are needed come from the operator ID field that is
reduced to a maximum of seven digits. The old and new line formats are as follows:
OLD mm/dd/yy hh:mm ssss tt xxxx yyyyyyyyyy
12345678901234567890123456789012345678
NEW mm/dd/yy hh:mm XM ssss tt xxxx yyyyyyy

The printing of time on the summary journal may or may not be impacted by this
function, depending upon the print options that are selected for end of transaction
printing. See “Highlight the Printing of Automatic Coupons” on page 118 and
“Highlight Printing of All Exceptional Entries” on page 118.

A value of No (0) leaves time printing in 24-hour format. A value of Yes (-1) alters
time printing to 12-hour format.

Check the Sum of All Voids at Each Void Entry

LINE 13

0,-1,0,0,0,0,0,0,0,0
__
↑
Check the sum of all voids at each void entry
Range:
Yes (-1), No (0)
Location:
Line 13, Option 1
Default:
No (0) (Cancel limit checked at tender time.)
Change Activation:
Sign off all registers.

The transaction cancel limit is checked at tender time to determine whether the sum
of all cancels exceeds the limit. This Yes/No option determines whether the
transaction cancel limit check is made prior to the acceptance of any item sale
cancel. It requires an immediate manager’s override to cancel a transaction that
exceeds the limit.

Chapter 6. Personalization of Preferred Customer Options and Messages 117

 A value of No (0) causes the transaction cancel limit check to be performed only at
tender time. A value of Yes (-1) causes the transaction cancel limit to be checked
prior to each cancel entry.

Highlight the Printing of Automatic Coupons

LINE 13

0,-1,0,0,0,0,0,0,0,0
__
↑
Highlight the printing of automatic coupons
Range:
Yes (-1), No (0)
Location:
Line 13, Option 2
Default:
Yes (-1) (Automatic coupons are highlighted.)
Change Activation:
Sign off all registers.

This Yes/No option highlights the receipt printing of any automatic (linked-to)
coupon or any points-only entry by overprinting.

A value of No (0) leaves the receipt printing of preferred customer bonuses and
discounts the same as all other print lines. A value of Yes (-1) highlights the receipt
printing of preferred customer bonuses and discounts.

The bonuses and discounts appear on the customer receipt as separate highlighted
lines with unique user-definable descriptors and values per bonus or coupon. The
print line for each automatic coupon shows the velocity code used to access that
coupon in case the linked-to coupon record needs to be directly accessed to
manually correct a problem (for example, to void the automatic coupon).

Highlight Printing of All Exceptional Entries

LINE 13

0,-1,0,0,0,0,0,0,0,0
__
↑
Highlight printing of all exceptional entries
Range:
Yes (-1), No (0)
Location:
Line 13, Option 3
Default:
No (0) (No highlighting of exceptional entries)
Change Activation:
Sign off all registers.

This Yes/No option highlights the receipt printing of exceptional items by

overprinting. Exceptional entries include all voids of item entries, any item entry that
returns money to a customer, and any item entry that requires an override. For the
purposes of this definition, coupons, refunds, deposits, and miscellaneous
transaction items are considered item entries as are normal sales.

A value of No (0) leaves the receipt printing of exceptional item entries the same as
all other print lines. A value of Yes (-1) highlights the receipt printing of exceptional
item entries.

118 Electronic Marketing PRPQ

Print Available Targeted Coupons on a Customer Receipt
LINE 13

0,-1,0,0,0,0,0,0,0,0
__
↑
Print available targeted coupons on a customer receipt
Range:
Yes (-1), No (0)
Location:
Line 13, Option 4
Default:
No (0) (No printing of available targeted coupons)
Change Activation:
Sign off all registers.

Electronic coupons can be made available to all customers, to all identified

preferred customers, or to selected (targeted) preferred customers. This Yes/No
option prints all available coupons that are targeted to a particular customer on the
customer receipt at the end of a transaction. A single line preceded by a
user-defined header message is printed for each available coupon. A print line
includes a unique coupon identification number (the velocity code), the coupon
value, the coupon type (discount, reduced price, or bonus point), and the coupon
descriptor from the item record. The coupon’s identification number can be used to
reference additional information on the coupon. The amount of printing depends
upon the number of coupons targeted per customer and varies for different
customers who have different sets of available targeted coupons. The maximum
number of coupons targeted to a customer defaults to five but can be increased
through an option in this file if the activity records are made large enough to hold
the data. (See “Maximum Number of Coupons Targeted Per Customer” on
page 85.) If a targeted coupon is not reusable, it will not be printed. Targeted
coupons for first-time users are never printed on a customer’s receipt as available
for future use because they are valid only during a customer’s first transaction. Free
form message text can also be optionally made available to describe each targeted
coupon. Up to three 38-character free form print lines can be defined in the
Targeted Coupon Message file through the Targeted Coupon Message (See
“Targeted Coupon Messages File (EAMFBTCM)” on page 340). Maintenance
procedure. These lines are printed following the associated coupon print line
described above. This message text allows the conditions of the targeted promotion
to be described in greater detail. The purpose of this printing is to offer an
alternative to expensive mailings that informs customers of the promotions available
uniquely to them.

A value of No (0) bypasses any receipt printing of targeted coupons. A value of Yes
(-1) causes the available targeted coupons to be printed on a customer’s receipt.

Remind Checker to Ask for Customer Card

LINE 13

0,-1,0,0,0,0,0,0,0,0
__
↑
Remind checker to ask for customer card
Range:
Yes (-1), No (0)
Location:
Line 13, Option 5

Chapter 6. Personalization of Preferred Customer Options and Messages 119

 Default:
No (0) (No prompting for entry of customer number)
Change Activation:
Sign off all registers.

This Yes/No option determines whether a customer number is prompted for at the
first total in a transaction if a customer number has not been entered. A value of No
(0) bypasses the customer card prompt. A value of Yes (-1) causes this prompt to
remind an operator to ask for a customer card. The Clear key removes the prompt.
The text for the prompt is definable through personalization and defaults to “ASK
FOR CARD CLEAR TO CONTINUE.” After the prompt is cleared, the transaction
total is displayed and an operator may either enter a customer number or proceed
with the transaction.

Use Period Points for Boundary Options

LINE 13

0,-1,0,0,0,0,0,0,0,0
__
↑
Use period points for boundary options
Range:
Yes (-1), No (0)
Location:
Line 13, Option 6
Default:
No (0) (Use total points for boundary processing)
Change Activation:
Sign-off all registers. Stop and Restart Checkout Support.

Boundary options provide for special processing when a customer’s point total
crosses specified boundaries. This processing normally uses a customer’s point
total since he became a Preferred Customer. This Yes/No option causes boundary
processing to use the points accumulated in this time period rather than the points
earned over the life of the Preferred Customer program. The length of the time
period is defined by how often the program that rolls over period totals is run. A
value of No (0) (No) causes boundary processing to be based on points earned
over the life of the Preferred Customer program, while value of Yes (-1) causes this
processing to look only at the points earned in (or rolled into) the current activity
period.

Only Points in This Period Are Available for Redemption

LINE 13

0,-1,0,0,0,0,0,0,0,0
__
↑
Only points in this period are available for redemption
Range:
Yes (-1), No (0)
Location:
Line 13, Option 7
Default:
No (0) (All earned points are available for redemption)
Change Activation:
Sign-off all registers.

120 Electronic Marketing PRPQ

When a customer attempts to redeem points through a points redemption coupon,
he must have accumulated enough points. This processing normally uses a
customer’s point total since he became a Preferred Customer. This Yes/No option
causes points redemption to use the points accumulated in this time period rather
than the points earned over the life of the Preferred Customer program. The length
of the time period is defined by how often the program that rolls over period totals is
run. A value of No (0) allows all points earned over the life of the Preferred
Customer program to be redeemed, while value of Yes (-1) causes only points
earned in (or rolled into) the current activity period to be available for redemption.

New Customer Message Starts Each New Activity Period

LINE 13

0,-1,0,0,0,0,0,0,0,0
__
↑
New customer message starts each new activity period
Range:
Yes (-1), No (0)
Location:
Line 13, Option 8
Default:
No (0) (New customer message given only once per customer)
Change Activation:
Sign-off all registers.

A special points message is printed on the receipt tape for a new Preferred
Customer. This Yes/No option causes the new customer message to be printed the
first time each customer shops in a new activity period, regardless past activity. The
length of the time period is defined by how often the program that rolls over period
totals is run. A value of No (0) causes the new customer message to be used only
the first time that a new Preferred Customer shops, while value of Yes (-1) causes
the new customer message to be given the first time that each Preferred Customer
shops in a new activity period.

New Customer Coupons Start Each New Activity Period

LINE 13

0,-1,0,0,0,0,0,0,0,0
__
õÍ │Í New customer coupons start each
new activity periodÍ
Range: Yes (-1), No (0)
Location: Line 13, Option 9
Default: No (0) (New customer coupons given only once per customer)
Change Activation:
Sign-off all registers.

Special coupons can be targeted to the first shopping trip for a new Preferred
Customer. This Yes/No option causes the new customer coupons to be available
the first time each customer shops in a new activity period, regardless past activity.
The length of the time period is defined by how often the program that rolls over
period totals is run. A value of No (0) causes the new customer coupons to be
available only the first time that a new Preferred Customer shops, while value of
Yes (-1) causes the new customer coupons to be given the first time that each
Preferred Customer shops in a new activity period.

Chapter 6. Personalization of Preferred Customer Options and Messages 121

 Keep Monthly Previous Points Activity for Customers
LINE 13

0,-1,0,0,0,0,0,0,0,0
__
↑
Keep monthly previous points activity for customers
Range:
Yes (-1), No (0)
Location:
Line 13, Option 10
Default:
No (0) (One previous activity record per customer)
Change Activation:
Erase file EAMFBAPP after this option has been changed and before
closing the activity period.

When the close activity procedure resets the periodic point totals for all customers,
it saves the totals from the prior period in a previous period activity file. Normally
only a single record for the prior period would be kept in the previous activity file
per customer. This Yes/No option causes the period starting month to be included in
the record key along with the customer number so that a record is kept for each
customer for each month in which a period close is done. If the activity period is
closed monthly, then the file can contain up to 12 records for each customer with
each record containing the points totals for the customer for a month. If the activity
period is close quarterly, then the file will contain only the records for the last four
quarters. A value of No (0) causes only the activity for the most recent points period
to be saved for each customer in the previous activity file. A value of Yes (-1) (Yes)
causes a new record to be added to the previous activity file for each customer and
monthly period within a 12 month span. Records that are a year old are overlayed
by new records that contain the same starting month.

If this option is chosen, then the points activity period should be closed no more
than once a month. It is suggested that the points activity period be closed on the
first day of the month (after midnight) so that the period starting month will be
correct. If this option is selected and the points activity period is accidentally closed
more than once in a particular month then the points activity for that month will be
incomplete in the previous period activity file. That is, data will be lost.

Tenders Using Preferred Customer Number as Account Number

LINE 14

0,0,0,0,0,0,0,0,0,0
__
↑
Tenders using preferred customer number as account number
Range:
0, 2x, 4x, 5x, or 6x (where x is between 1 and 6)
Location:
Line 14, Option 1
Default:
0 (Preferred customer number not used for tender verification)
Change Activation:
Sign off all registers.

The Electronic Marketing PRPQ is intended to require customers to identify

themselves only once by presenting their preferred customer number at total time.
In order to have the same number used for tender verification purposes, this option

122 Electronic Marketing PRPQ

defines the tender types and varieties for which a preferred customer number is
also the tender verification account number. For these selected tenders, preferred
customers need only present their card once and the number is automatically used
multiple times as needed.

You should not select a tender through this option if the tender does not have
account number verification defined through the tender definitions in the terminal
options. This option is selected by defining the tender type/variety to which it
applies. Checks are defined by the value 2x (0<x<7) where x is the variety as
defined in the tender definitions options. The three possible miscellaneous tenders
are specified as 4x, 5x, or 6x where x is the variety.

This option is selected by defining the tender type/variety to which it applies.

Multiple tenders can be specified for this option. The options report will only report
and alter the first 20 entries.

To specify multiple tenders, the tender values are all entered as a single option but
are separated by colons as shown below:
21:23,0,0,0,0,0,0,0,0,0

Tenders Using Alternate Customer Number as Account Number

LINE 14

0,0,0,0,0,0,0,0,0,0
__
↑
Tenders using alternate customer number as account number
Range:
(0, 2x, 4x, 5x, or 6x where x is between 1 and 6)
Location:
Line 14, Option 2
Default:
0 (Preferred customer number not used for tender verification)
Change Activation:
Sign off all registers.

This option allows a customer to use an existing credit card account number or
courtesy card number for an alternate account number. This option is similar to the
option “Tenders Using Preferred Customer Number as Account Number” on
page 122. But an alternate customer number associated with the preferred
customer number is used as the tender verification account number instead of the
preferred customer number. The alternate number is captured when it is first used
by a preferred customer and is saved with the preferred customer number in the
primary activity record for automatic use later. If check tenders are selected by this
option and a preferred customer presents a courtesy card for check verification, this
courtesy card number is saved. It is presented automatically the next time that the
customer presents their preferred customer card and tenders a check. This option is
consistent with the goal of requiring a single customer card only when a customer
has an existing tender verification number.

This option is selected by defining the tender type/variety to which it applies.

Multiple tenders can be specified for this option. The options report will only report
and alter the first 20 entries.

To specify multiple tenders, the tender values are all entered as a single option but
are separated by colons as shown below:
0,21:23,0,0,0,0,0,0,0,0

Chapter 6. Personalization of Preferred Customer Options and Messages 123

 The same tenders can be specified for both this option and option “Tenders Using
Preferred Customer Number as Account Number” on page 122 to provide a
migration path between using existing numbers and the new preferred customer
numbers for tender verification.

The following rules guide the behavior of the terminal in determining which number
to use:
v If the tender type appears only in the list of tenders that use a customer ID
number, the customer’s ID number is substituted for an account number during
tender verification.
v If the tender type appears in both options lists, the alternate number is
substituted unless it is zero (in which case the customer ID number is
substituted). The customer’s alternate number remains zero until one is manually
entered.
v If the tender type appears only in the list of tenders that use alternate customer
ID numbers and the alternate number is zero, the terminal prompts for the
alternate number to be used. This number is saved in the customer’s activity
record to be used automatically the next time the customer visits the store and
uses an applicable tender type.

Override Is Required to Change Tender Verification Number

LINE 14

0,0,0,0,0,0,0,0,0,0
__
↑
Override is required to change tender verification number
Range:
Yes (-1), No (0)
Location:
Line 14, Option 3
Default:
No (0) (No override is required.)
Change Activation:
Sign off all registers.

When a tender is selected by either or both of the options “Tenders Using Preferred
Customer Number as Account Number” on page 122 and “Tenders Using Alternate
Customer Number as Account Number” on page 123 for automatic account number
substitution, the operator can still manually override this substitution by using the
VERIFY key to enter an account number. This Yes/No option determines whether a
manual override of a preferred customer’s tender verification account number
requires a manager’s or operator’s override sequence for addition security. If the
use of an alternate account number is manually overridden, this override also
causes the alternate account number to be changed to the newly entered account
number. Also, the first entry of an alternate account number does not require an
override. This manual entry does not replace any previously defined number.

A value of No (0) allows a manual entry to replace a preferred customer tender

verification account number without an override. A value of Yes (-1) requires a
manager’s or operator’s override to manually substitute an entered tender account
number for that previously defined for a preferred customer.

Operator’.s Override Is Sufficient to Change Tender Number

LINE 14

0,0,0,0,0,0,0,0,0,0

124 Electronic Marketing PRPQ

 __
↑
Operator’s override is sufficient to change tender number
Range:
Yes (-1), No (0)
Location:
Line 14, Option 4
Default:
No (0) (Manager’s override if any required)
Change Activation:
Sign off all registers.

When the option “Override Is Required to Change Tender Verification Number” on

page 124 is set to require an override for the manual entry of a tender verification
account number that replaces a previously defined preferred customer tender
verification account number, this Yes/No option determines whether an operator’s
override is sufficient or whether a manager’s override is required.

A value of No (0) requires a manager’s override with a manual account number

entry that replaces a preferred customer’s tender verification account number. A
value of Yes (-1) allows an operator’s override for a manual replacement of a
preferred customer’s tender verification account number.

Count of Boundary Levels Defined for Special Processing

LINE 15
0
__
↑
Count of boundary levels defined for special processing
Range:
(0 - 20)
Location:
Line 15, Option 1
Default:
0 (No Boundaries defined)
Change Activation:
Sign off all registers; stop checkout support then restart checkout support.

Special processing is provided when the total of a preferred customer’s points

reaches specified boundary levels. Special processing can include any combination
of the following:
v Awarding bonus points
v Incrementing a customer’s boundary level
v Providing a customer with a unique message on the receipt tape and/or display
that informs him/her of the boundary crossing and of any associated awards.
This option defines the number of boundary levels that are defined. The definition of
each boundary level requires an additional line in the options file containing five
boundary options. Each of the five boundary options defined for line “n’ is repeated
for each defined boundary. This option defines the number of lines containing these
five boundary options.

Points Total That Defines Boundary

Range:
(1 - 99999999) = (.01 - 999,999.99)
Location:
Line 15.1

Chapter 6. Personalization of Preferred Customer Options and Messages 125

 Default:
None.
Change Activation:
Sign off all registers; stop checkout support then restart checkout support.

This secondary option defines the number of points that must be met or exceeded
in order for the associated boundary processing to occur. These points are
expressed in cent values (if points = pennies). The boundary processing occurs
once as the boundary is crossed. If more than one boundary is crossed in the same
transaction, only the processing for the last defined boundary is performed. For
example, if the boundary definitions are sorted from smallest to largest, the largest
boundary crossed will determine the processing. If boundary crossing involves
awarding bonus points, these points are added to any accumulated points a
customer has earned for the transaction.

Boundary Repeats at Each Multiple of the Boundary Points

Range:
Yes (-1), No (0)
Location:
Line 15.2
Default:
None.
Change Activation:
Sign off all registers; stop checkout support then restart checkout support.

This Yes/No option determines whether the boundary processing occurs once as
the points boundary is crossed or whether it occurs each time that a multiple of the
points boundary is crossed. This option allows you to provide a bonus for each
[Link] dollars of points with only a single boundary level definition.

A value of No (0) causes the boundary processing to occur just once per customer
as a customer crosses the boundary threshold. A value of Yes (-1) causes the
boundary processing to occur each time a customer crosses any multiple of the
points boundary.

Bonus Points to be Awarded at Boundary Crossing

Range:
(0 - 32500)
Location:
Line 15.3
Default:
None.
Change Activation:
Sign off all registers.

This option defines a points amount (in cents) to be awarded as a customer

crosses the points boundary. These points are added to the points normally
accumulated in the transaction.

Level Increment to be Awarded at Boundary Crossing

Range:
(0 - 99)
Location:
Line 15.4
Default:
0

126 Electronic Marketing PRPQ

Change Activation:
Sign off all registers; stop checkout support then restart checkout support.

This option defines a value by which to increment the customer status level as a
customer crosses the points boundary. This status level is a simple indicator of the
degree of privilege a customer has earned at a store, based on her past transaction
history. The customer level ranges from 0 to 99. Any increment that raises the level
above 99 leaves the level at 99.

Message to be Presented at Boundary Crossing

Range:
(0, 7 - 49)
Location:
Line 15.5
Default:
0
Change Activation:
Sign off all registers.

This option defines the message number of a message to be given to a customer at

the end of a transaction that crosses the points boundary. The message is defined
in the message file. This is the same type of message number that can be
referenced from the customer activity file. The boundary message is displayed
and/or printed on the receipt tape with any points message or customer activity
message for the transaction. A message number of zero is used to denote that
there is no message.

Examples of Different Boundary Processing Options Selected

The screens from the Preferred Customer Options Report on the following pages
show some example option files. Five different options files are shown, each with
different levels of boundary processing defined.

Preferred Customer Options Report - STORE 0445 Page 7 of 20

Electronic Marketing Test Store 01/18/93 13:07

13.6 USE PERIOD POINTS FOR BOUNDARY OPTIONS NO

13.7 ONLY POINTS IN THIS PERIOD ARE AVAILABLE FOR REDEMPTION NO
13.8 NEW CUSTOMER MESSAGE STARTS EACH NEW ACTIVITY PERIOD NO
13.9 NEW CUSTOMER COUPONS START EACH NEW ACTIVITY PERIOD NO
13.0 KEEP MONTHLY PREVIOUS POINTS ACTIVITY FOR CUSTOMERS NO

14.1 TENDERS USING PREFERRED CUSTOMER NUMBER AS ACCOUNT NUMBER = NONE

14.2 TENDERS USING ALTERNATE CUSTOMER NUMBER AS ACCOUNT NUMBER = NONE
14.3 OVERRIDE IS REQUIRED TO CHANGE TENDER VERIFICATION NUMBER NO
14.4 OPERATOR’S OVERRIDE IS SUFFICIENT TO CHANGE TENDER NUMBER NO

15.1 POINT BOUNDARY OPTIONS NOT DEFINED

16.1 KEEP OLD PERIOD AUDIT LOG DATA YES

16.2 APPEND AUDIT DATA TO EAMPANEL AT CLOSE NO
16.3 KEEP AUTO STORE COUPONS IN DEPT TOTALS EXIT FIELD NO
16.4 KEEP MULTIPLIED COUPONS IN DEPT TOTALS EXIT FIELD NO

1 2 3 QUIT 4 5 6 7 ALTER 8 9 10 PRINT

Time=13:09 Current Window=3 Number of Windows=4 SYSTEM MESSAGE AVAILABLE

Figure 1. Options File with no boundary processing defined

Chapter 6. Personalization of Preferred Customer Options and Messages 127

 Preferred Customer Options Report - STORE 0445 Page 7 of 21

Electronic Marketing Test Store 01/18/93 13:07

13.6 USE PERIOD POINTS FOR BOUNDARY OPTIONS NO

13.7 ONLY POINTS IN THIS PERIOD ARE AVAILABLE FOR REDEMPTION NO
13.8 NEW CUSTOMER MESSAGE STARTS EACH NEW ACTIVITY PERIOD NO
13.9 NEW CUSTOMER COUPONS START EACH NEW ACTIVITY PERIOD NO
13.0 KEEP MONTHLY PREVIOUS POINTS ACTIVITY FOR CUSTOMERS NO

14.1 TENDERS USING PREFERRED CUSTOMER NUMBER AS ACCOUNT NUMBER = NONE

14.2 TENDERS USING ALTERNATE CUSTOMER NUMBER AS ACCOUNT NUMBER = NONE
14.3 OVERRIDE IS REQUIRED TO CHANGE TENDER VERIFICATION NUMBER NO
14.4 OPERATOR’S OVERRIDE IS SUFFICIENT TO CHANGE TENDER NUMBER NO

BOUNDARY POINTS REPEAT BONUS INCREMENT MESSAGE

15.1 .01 NO 100.00 0 12

16.1 KEEP OLD PERIOD AUDIT LOG DATA YES

16.2 APPEND AUDIT DATA TO EAMPANEL AT CLOSE NO
16.3 KEEP AUTO STORE COUPONS IN DEPT TOTALS EXIT FIELD NO

1 2 3 QUIT 4 5 6 SAVE 7 ALTER 8 9 10PRINT

Time=13:13 Current Window=3 Number of Windows=4 SYSTEM MESSAGE AVAILABLE

Figure 2. Options File with one boundary defined

Preferred Customer Options Report - STORE 0445 Page 7 of 21

Electronic Marketing Test Store 01/18/93 13:07

13.6 USE PERIOD POINTS FOR BOUNDARY OPTIONS NO

13.7 ONLY POINTS IN THIS PERIOD ARE AVAILABLE FOR REDEMPTION NO
13.8 NEW CUSTOMER MESSAGE STARTS EACH NEW ACTIVITY PERIOD NO
13.9 NEW CUSTOMER COUPONS START EACH NEW ACTIVITY PERIOD NO
13.0 KEEP MONTHLY PREVIOUS POINTS ACTIVITY FOR CUSTOMERS NO

14.1 TENDERS USING PREFERRED CUSTOMER NUMBER AS ACCOUNT NUMBER = NONE

14.2 TENDERS USING ALTERNATE CUSTOMER NUMBER AS ACCOUNT NUMBER = NONE
14.3 OVERRIDE IS REQUIRED TO CHANGE TENDER VERIFICATION NUMBER NO
14.4 OPERATOR’S OVERRIDE IS SUFFICIENT TO CHANGE TENDER NUMBER NO

BOUNDARY POINTS REPEAT BONUS INCREMENT MESSAGE

15.1 .01 NO 100.00 0 12
15.2 100.00 YES .00 1 11

16.1 KEEP OLD PERIOD AUDIT LOG DATA YES

16.2 APPEND AUDIT DATA TO EAMPANEL AT CLOSE NO

1 2 3 QUIT 4 5 6 SAVE 7 ALTER 8 9 10 PRINT

Time=13:14 Current Window=3 Number of Windows=4 SYSTEM MESSAGE AVAILABLE

Figure 3. Options File with two boundaries defined.

128 Electronic Marketing PRPQ

 Preferred Customer Options Report - STORE 0445 Page 7 of 21

Electronic Marketing Test Store 01/18/93 13:07

13.6 USE PERIOD POINTS FOR BOUNDARY OPTIONS NO

13.7 ONLY POINTS IN THIS PERIOD ARE AVAILABLE FOR REDEMPTION NO
13.8 NEW CUSTOMER MESSAGE STARTS EACH NEW ACTIVITY PERIOD NO
13.9 NEW CUSTOMER COUPONS START EACH NEW ACTIVITY PERIOD NO
13.0 KEEP MONTHLY PREVIOUS POINTS ACTIVITY FOR CUSTOMERS NO

14.1 TENDERS USING PREFERRED CUSTOMER NUMBER AS ACCOUNT NUMBER = NONE

14.2 TENDERS USING ALTERNATE CUSTOMER NUMBER AS ACCOUNT NUMBER = NONE
14.3 OVERRIDE IS REQUIRED TO CHANGE TENDER VERIFICATION NUMBER NO
14.4 OPERATOR’S OVERRIDE IS SUFFICIENT TO CHANGE TENDER NUMBER NO

BOUNDARY POINTS REPEAT BONUS INCREMENT MESSAGE

15.1 .01 NO 100.00 0 12
15.2 100.00 YES .00 1 11
15.3 500.00 NO 10.00 0 10

16.1 KEEP OLD PERIOD AUDIT LOG DATA YES

1 2 3 QUIT 4 5 6 SAVE 7 ALTER 8 9 10 PRINT

Figure 4. Options File with three boundaries defined.

Preferred Customer Options Report - STORE 0445 Page 7 of 21

Electronic Marketing Test Store 01/18/93 13:07

13.6 USE PERIOD POINTS FOR BOUNDARY OPTIONS NO

13.7 ONLY POINTS IN THIS PERIOD ARE AVAILABLE FOR REDEMPTION NO
13.8 NEW CUSTOMER MESSAGE STARTS EACH NEW ACTIVITY PERIOD NO
13.9 NEW CUSTOMER COUPONS START EACH NEW ACTIVITY PERIOD NO
13.0 KEEP MONTHLY PREVIOUS POINTS ACTIVITY FOR CUSTOMERS NO

14.1 TENDERS USING PREFERRED CUSTOMER NUMBER AS ACCOUNT NUMBER = NONE

14.2 TENDERS USING ALTERNATE CUSTOMER NUMBER AS ACCOUNT NUMBER = NONE
14.3 OVERRIDE IS REQUIRED TO CHANGE TENDER VERIFICATION NUMBER NO
14.4 OPERATOR'S OVERRIDE IS SUFFICIENT TO CHANGE TENDER NUMBER NO

BOUNDARY POINTS REPEAT BONUS INCREMENT MESSAGE

15.1 .01 NO 100.00 0 12
15.2 100.00 YES .00 1 11
15.3 200.00 NO 10.00 0 10
15.4 500.00 NO 10.00 0 13

1 2 3 QUIT 4 5 6SAVE 7ALTER 8 9 10PRINT

Figure 5. Options File with four boundaries defined.

Keep Old Period Audit Log Data

LINE 16

-1,0,0,0,0,0,0,0,0,0
___
↑
Keep old period audit log data
Range:
Yes (-1), No (0)

Chapter 6. Personalization of Preferred Customer Options and Messages 129

 Location:
Line 16, Option 1
Default:
Yes (-1) (Keep old period Audit Log data.)
Change Activation:
Stop then Restart Checkout Support.

This option determines whether old period totals are kept for the
Redemption/Adjustments Audit Log file.

A value of No (0) causes current period Audit Log data to be discarded after the
close of a reporting period. A value of Yes (-1) causes current period Audit log data
to be appended to an old period Audit Log file at the close of a reporting period.

If old period Audit Log data is kept, then the old period Audit Log file
[Link] must be purged occasionally by a host or manual in-store process
to keep the file from growing to fill all available disk space. If you keep the old
period Audit Log data, you can obtain reports on any redemptions or adjustments
made in a prior period.

Append Audit Data to Panel File

LINE 16

-1,0,0,0,0,0,0,0,0,0
___
↑
Append audit data to panel file
Range:
Yes (-1), No (0)
Location:
Line 16, Option 2
Default:
No (0) (No Audit data in the Panel file)
Change Activation:
Stop then Restart Checkout Support.

This Yes/No option reformats and appends the records in the current period
Redemption/Adjustments Audit Log file to the real time Panel Diary file
[Link] at the close of a reporting period. The format of this optional
Panel data is defined with the other Panel Diary File record definitions. (See “Panel
Diary File (EAMPANEX)” on page 330.) If adjustments or redemptions of points are
performed from the enrollment procedure, you must select this option for the Panel
file to contain a record of all events that impact the points history of a preferred
customer.

A value of No (0) excludes the Audit Log data from the Panel Diary File. A value of
Yes (-1) causes current period Audit Log data to be appended to the Panel Diary
File at each close of a reporting period.

Keep Automatic Coupon Totals in Department File Exit Fields

LINE 16

-1,0,0,0,0,0,0,0,0,0
_____
↑
Keep automatic coupon totals in department file exit fields
Range:
(0 - 5)

130 Electronic Marketing PRPQ

Location:
Line 16, Options 3, 4, and 5
Default:
0,0,0 (No automatic coupon totals in the Department file)
Change Activation:
Stop then Restart Checkout Support.

This set of three options values allows amounts for automatic store coupons,
automatic manufacturer coupons, and doubled coupons to be accumulated in the
first five four-byte exit fields in the Department Totals File. This allows for the totals
for paperless coupons to be available to the Department Totals Report. Each value
of these three option’s values has a range of zero to five. Zero does not accumulate
the total; one accumulates the total in the first exit field (72 bytes into the file); five
accumulates the total in the fifth exit field (88 bytes into the file).
v The first option value applies to automatic store coupons
v The second option value applies to multiplied (doubled) coupons
v The third value applies to automatic manufacturer coupons.

You can give all of the options the same nonzero value (one through five) to
accumulate the total amount of all paperless coupons in a single value.
Alternatively, you can give each of the options a separate value to accumulate a
separate total for each of the three types of automatic coupons. Or you can keep
any subset of the three totals.

Exclude Automatic Coupons from Reported Coupon Counts

LINE 16

-1,0,0,0,0,0,0,0,0,0
__
↑
Exclude automatic coupons from reported coupon counts
Range:
Yes (-1), No (0)
Location:
Line 16, Option 6
Default:
No (0) (Coupon counts include all coupons.)
Change Activation:
Stop then Restart Checkout Support.

This Yes/No option excludes all automatic coupons from the store and manufacturer
coupon counts in the accounting and performance files. With automatic coupons
excluded, the coupon counts reported in the cash reports, performance reports, and
store recap report will represent the paper coupons that are counted from the tills.

A value of No (0) causes the coupon counts to include both automatic and paper
coupons. A value of Yes (-1) causes the coupon counts to contain only paper
coupons.

Add Period Summary String to Panel File

LINE 16

-1,0,0,0,0,0,0,0,0,0
__
↑

Range:
Yes (-1), No (0)

Chapter 6. Personalization of Preferred Customer Options and Messages 131

 Location:
Line 16, Option 7
Default:
No (0) (No Period Summary Panel Record)
Change Activation:
Stop then Restart Checkout Support.

This Yes/No option causes an additional Period Summary record to be added to the
foreground panel file EAMPANEX at the close of a reporting period. This record
contains preferred customer totals for the accounting period to be compared to the
rest of the panel data. A value of No (0) leaves the Period Summary Record out of
the Panel file. A value of Yes (-1) causes the Period Summary Record to be
included in the Panel file.

Deposit Automatic Coupons Into Miscellaneous Accounts

LINE 16

-1,0,0,0,0,0,0,0,0,0
______
↑
Deposit Automatic Coupons Into Miscellaneous Accounts
Range:
(-999 to 999)
Location:
Line 16, Options 8, 9, and 10
Default:
0,0,0 (No automatic coupon totals in miscellaneous transactions)
Change Activation:
Close the Reporting Period.

This set of three options values allows amounts for automatic store coupons,
automatic manufacturer coupons, and doubled coupons to be automatically
deposited into miscellaneous transaction accounts from the previous period store
office at the close of a reporting period. This allows the automatic coupon amounts
to be reported with the Miscellaneous Transaction Report. It also prevents the store
office accounting record from lacking the automatic coupon amounts when viewed
by a host report. These options have no significant impact on the in-store
accounting reports. These options are ignored if no store office record is defined in
the system.

Each of these three options values has a range of -999 to 999. Values are given
the following meanings:
0 Does not accumulate a miscellaneous transaction total
A positive number
Provides an account to be credited
A negative number
Provides an account to be debited

If, on manual deposits of money to the Miscellaneous Transaction File, you credit a
paid amount or debit a received amount, you should provide the accounts for
automatic coupons as negative numbers for consistency in the sign of the
miscellaneous deposits. The first option value applies to automatic manufacturer
coupons, the second option value applies to automatic store coupons, and the third
value applies to multiplied (doubled) coupons. You may use the options in the
following ways:

132 Electronic Marketing PRPQ

v Give all of the options the same nonzero value to accumulate the total amount of
all paperless coupons in a single miscellaneous account
v Give each of the options a separate value to accumulate a separate total for
each of the three types of automatic coupons
v Keep any subset of the three totals.

Point Ranges for Period Close Report

LINE 17

0,0,0,0,0,0,0,0,0,0
___________________
↑
Point ranges for period close report
Range:
(0 to 999999999)
Location:
Line 17, Options 1 to 10
Default:
0,0,0,0,0,0,0,0,0,0 (No reporting by points ranges)
Change Activation:
None.

When the period close procedure is run to reset the points activity period, this
procedure produces a status report in the managers message file for the activity
period. This set of 10 point value options defines point ranges that are used in the
status report to show how many customers ended the activity period in each
defined point range. Up to 10 different point values can be defined as the low end
of a point range. An additional range is automatically defined for all customers with
points below the value of the first point boundary. Thus if point boundaries are
defined by the values 100, 200, ... 500, the count of customers in the point ranges
1-99, 100-199, ... 500-99999999, will be included in the activity period status report.
The values for this option must be defined in ascending order starting with the first
option. Any unused options must have a value of zero. If the first option is given a
value of zero, then all of these options are ignored and customer ranges are not
reported in the activity status. The following shows what this report would look like
with some boundary values defined.
Date/Time PREFERRED CUSTOMER Points Activity Period
Closed for store 0445 on 08/16
Total PREFERRED CUSTOMER Activity in this period
1395 points earned in 4 transactions.
100 points redeemed leaving 1295 available

Records found in the Activity file: 1000

Records not allowed to collect points: 1
Active records with no period points: 996
Active records with period points: 3

POINT RANGE CUSTOMERS DISCOUNT

1 - 99 0 N/A
100 - 199 1 N/A
200 - 299 0 N/A
300 - 399 0 N/A
400 - 499 1 N/A
500 - 99999999 1 N/A
Total: 3

Prior points available for redemption: 1295

Total excess points discarded: 195
Current points available for redemption: 1100

Chapter 6. Personalization of Preferred Customer Options and Messages 133

 Records with less points in new period: 1
Records with no points in new period: 997
Records with redeemable points: 3

Number of errors logged during close: 25

Last error code logged during close: DW

Automatic Discounts for Associated Points Ranges

LINE 18

0,0,0,0,0,0,0,0,0,0
___________________
↑
Automatic discounts for associated points ranges
Range:
(0 to 99)
Location:
Line 18, Options 1 to 10
Default:
0,0,0,0,0,0,0,0,0,0 (No automatic earning of discounts)
Change Activation:
None.

Automatic transaction discount groups can be assigned to Preferred Customers by

the period close procedure based upon the points earned in the prior activity period.
This set of 10 value options defines discount groups to be associated with Preferred
Customers in the 10 point ranges defined by the option “POINT RANGES FOR
PERIOD CLOSE REPORT”. A value of zero defines that a discount group of zero
(no discount) is to be assigned to a given point range. If any non-zero discount
group is defined for a valid point range, then the discount group assigned to each
Preferred Customer will be reset to either a group defined by this option set or to
zero. Note that all customers who earned less points than defined by the first point
boundary will be assigned a discount group of zero and thus will receive no
transaction discounts. If the points close procedure is empowered by this option to
automatically assign transaction discount groups to Preferred Customers, the
procedure will assign a discount group to each Preferred Customer and thus will
overlay any discount group previously assigned by any means to any Preferred
Customer. Individual customer records can be marked to not receive any
transaction discounts, but they cannot be marked to maintain their current discount
regardless of points earned if the period close procedure is assigning discounts
based on earned points. The EAMBATCH procedure can be used if needed to
restore a selected set of customers to designated discount groups if these discount
groups are not based on earned points.

Exclude Non-Points Items from Minimum Purchase Limits

LINE 19

0,0,0,0,0,0,0,0,0,0,0
__
↑
Exclude non-points items from minimum purchase limits
Range:
Yes (-1), No (0)
Location:
Line 19, Option 1
Default:
No (0) (All items contribute to minimum purchase amount)
Change Activation:
Sign-off all registers.

134 Electronic Marketing PRPQ

This Yes/No option determines whether items for which no points are given will
contribute to the minimum purchase requirement of coupons. Individual items are
marked in their item records as to whether points apply and individual coupons can
contain a minimum purchase requirement in their item records. A minimum
purchase requirement can also be defined for coupon doubling. Non-point items can
be excluded only from a minimum transaction size requirement. If a coupon
requires a minimum purchase from a particular department or manufacturer, then
non-points items will not be excluded from the purchase amount for the department
or manufacturer. A value of Yes (-1) causes all items which are not eligible for
points to be excluded from the purchase total that is compared to the minimum
transaction size required for a coupon or for coupon doubling. A value of No (0)
causes all items to be included in the transaction total that is compared to a
minimum purchase requirement for a coupon.

Add Customer Number to Coupon Tracking File Records

LINE 19

0,0,0,0,0,0,0,0,0,0
___
↑
Add customer number to coupon tracking file records
Range:
Yes (-1), No (0)
Location:
Line 19, Option 2
Default:
No (0) (Customer numbers are not logged with coupons)
Change Activation:
Stop and Restart Checkout Support.

This Yes/No option determines whether each coupon entry logged in the Coupon
Tracking file should contain the Preferred Customer account number if this coupon
was redeemed by a Preferred Customer. If this option is selected then all coupons
logged for Preferred Customer transactions will contain the customer number in the
field reserved for the coupon campaign number. This field will be empty for coupons
redeemed by non-preferred customers unless a campaign number is key entered.
Note that the campaign number field was created in the hope that this number
could be read from a paper coupon when it was scanned, but this has never
become possible. A value of Yes (-1) causes all coupons logged in the coupon
tracking file from Preferred Customer transactions to contain the customer number
in place of the campaign number. A value of No (0) causes the campaign number
field in the coupon tracking file to be empty unless a campaign number is keyed in
at the register with the entry of a coupon.

Always Use the Manufacturer Number From a Coupon Record

LINE 19

0,0,0,0,0,0,0,0,0,0
__
↑
Always use the manufacturer number from a coupon record
Range:
Yes (-1), No (0)
Location:
Line 19, Option 3
Default:
No (0) (Valid MFR always taken from item code)

Chapter 6. Personalization of Preferred Customer Options and Messages 135

 Change Activation:
Sign-off all registers.

The coupon processing enhancements allow the manufacturer number to be used

for validation of a coupon to come from the coupon item record rather than from the
coupon item code. If a valid manufacturer number is included in the coupon item
code as well as in the coupon item record, then the value from the coupon item
code is normally used for coupon validation. This Yes/No option causes the
manufacturer number from a coupon item record to be used for coupon validation
whenever it is present and the coupon item code is not a category 4 UPC code.
This option is useful for validation of Catalina, EAN, or any other coupons that
contain digits in the manufacturer portion of the item code that do not match the
manufacturer number of the promoted items. A value of Yes (-1) causes all
manufacturer numbers in coupon item records to be used for coupon validation
unless a valid manufacturer number is provided in a category 4 (4MMMMMxxxxx)
UPC coded coupon. A value of No (0) causes the manufacturer numbers in coupon
item record to be used only when no valid manufacturer number is provided in the
coupon item code. Note that a coupon item code of the form CCMMMMMxxxxx is
considered to contain a valid manufacturer number unless CCM = 000 or the first
four digits of MMMMM are all zero. Thus this option does not impact any linked
coupon unless the option to displace preferred linked codes is selected with a value
that places non-zero digits in the manufacturer field.

Stage Activity File at Each Close of Period

LINE 19

0,0,0,0,0,0,0,0,0,0
__
↑
Stage activity file at each close of period
Range:
Yes (-1), No (0)
Location:
Line 19, Option 4
Default:
No (0) (No staging of Customer Activity file)
Change Activation:
Stop and Restart Checkout Support.

This Yes/No option causes a copy of the Preferred Customer Activity file to be
made at the close of a reporting period. The copy named [Link] is
located on the ADX_IDT4 directory and is identical to [Link] as it existed
when the period was closed. This checkpoint version of the activity data is
overlayed at each successive close of the reporting period. Note that the copy is
made before any resetting of periodic points totals that might occur at the end of
this period. This snapshot of the Preferred Customer Activity file can be use for host
retrieval or simply as a backup copy. It will be needed for host retrieval in a 24-hour
store since the primary file will always be open for updates and thus cannot be
dumped to a host. A value of Yes (-1) causes a copy of the activity file to be staged
at each close of a reporting period while a value of No (0) prevents this copy from
being made.

Treat All Non-Preferred Customers as Rain check Customers

LINE 19

0,0,0,0,0,0,0,0,0,0

136 Electronic Marketing PRPQ

 __
↑
Treat all non-preferred customers as rain check customers
Range:
Yes (-1), No (0)
Location:
Line 19, Option 5
Default:
No (0) (No preferred promotions to non-preferred customers
Change Activation:
Stop Checkout Support and sign-off all registers.

This Yes/No option allows all non-preferred customers to be treated a Preferred

Rain check customers. This causes all non-preferred customers to receive the
messages and promotions available to the Rain check ID. Note that the Rain check
ID contains default points multiplier, discount group, and targeted coupons for all
Preferred Customers, but these promotions may not be available to Rain check
customers depending upon the options set in the Rain check record. These activity
record options also determine whether panel data is collected or personalized
messages are printed for Rain check customers. When this option is selected, the
use of the Rain check ID will not cause an exception log entry as is usually the
case. This options does not stop a real Preferred Customer ID from being entered
anywhere in the transaction nor does it stop the optional prompting for this ID. The
option just causes each transaction to start out as a Rain check transaction, so that
if Preferred coupons are given to Rain check customers, there may be no additional
promotions due when a Preferred Customer number is entered. If preferred
coupons are targeted to rain check customers and this option is selected, you must
be careful not to target different size discounts on the same item to different
customers because the discount received as a rain check customer prior to entry of
the real customer ID might prevent a Preferred Customer from receiving the larger
discount that he is due. A value of Yes (-1) causes all non-preferred customers to
be treated as Preferred Rain check customers while a value of No (0) prevents
preferred promotions to non-preferred customers. This option is useful for
temporarily showing non-preferred customers the benefits of becoming a Preferred
Customer.

Remove Doubled Coupons from Store Coupons by Department

LINE 19

0,0,0,0,0,0,0,0,0,0
__
↑
Remove doubled coupons from store coupons by department
Range:
Yes (-1), No (0)
Location:
Line 19, Option 6
Default:
No (0) (Include doubled coupons in Department Totals)
Change Activation:
Stop and Restart Checkout Support.

This Yes/No option causes doubled (multiplied) coupon totals to be excluded from
the store coupon totals in the department totals file. This causes the store coupon
total shown in the Department Analysis Report to match the store coupon total in
the Summary Cash Report. If the hidden option is selected to include (deduct) store
coupons in the (from) net sales figures by department, then this option will keep the

Chapter 6. Personalization of Preferred Customer Options and Messages 137

 double coupons from being charged against the department net like the other store
coupons. Note that option 16.4 provides the ability to accumulate the double
coupon total in an exit field in the department totals file so that the totals removed
by this option can be accumulated elsewhere if they are needed. A value of Yes (-1)
causes the doubled coupon counts and amounts to be excluded from the store
coupon counts and amounts in department totals. A value of No (0) leaves the
doubled coupon totals included within the department store coupon totals.

Override Needed for Keyed Preferred Customer Coupons

LINE 19

0,0,0,0,0,0,0,0,0,0
__
↑
Override needed for keyed preferred customer coupons
Range:
Yes (-1), No (0)
Location:
Line 19, Option 7
Default:
No (0) (Allow keyed preferred coupons)
Change Activation:
Sign-off all registers.

This Yes/No option causes a manager’s override to be required with any keyed
entry of a preferred customer coupon other than a void. The range of item codes for
preferred coupons is defined by options 5.1 and 5.2. The item code for each
automatic preferred coupon is printed on the customer receipt tape so that the
coupon can be manually voided if this is required to accept a better paper coupon.
This option provides for the manual void requirement while assuring that targeted
coupons are not manually given to preferred customers without a manager’s
override. A value of Yes (-1) causes an override to be required for any manual entry
of a preferred coupon other than a void entry. A value of No (0) allows for manual
entry of (paper) preferred coupons for any preferred customer. This option should
be set to No (0) if paper preferred coupons are issued to preferred customers.

Accept Electronic and Paper Vendor Coupons on the Same Item

LINE 19

0,0,0,0,0,0,0,0,0,0
__
↑
Accept electronic and paper vendor coupons on the same item
Range:
Yes (-1), No (0)
Location:
Line 19, Option 8
Default:
No (0) (Only one vendor coupon per item)
Change Activation:
Sign-off all registers.

This Yes/No option causes automatic (linked to) manufacturer coupons to be

validated separately from paper manufacturer coupons. This allows a paper vendor
coupon and an automatic vendor coupon to both be accepted against the same
item sale. A value of Yes (-1) allows both a paper and an electronic manufacturer
coupon to be accepted for the same item. A value of No (0) causes paper and

138 Electronic Marketing PRPQ

electronic vendor coupons to be validated against each other so that only 1 vendor
coupon will be accepted against any single item.

Note: This option is dependent on APAR 98274.

Accept Electronic and Paper Store Coupons on the Same Item

LINE 19

0,0,0,0,0,0,0,0,0,0
__
↑
Accept electronic and paper store coupons on the same item
Range:
Yes (-1), No (0)
Location:
Line 19, Option 9
Default:
No (0) (Only one store coupon per item)
Change Activation:
Sign-off all registers.

This Yes/No option causes automatic (linked to) store coupons to be validated
separately from paper store coupons. This allows a paper store coupon and an
automatic store coupon to both be accepted against the same item sale. A value of
Yes (-1) allows both a paper and an electronic store coupon to be accepted for the
same item. A value of No (0) causes paper and electronic store coupons to be
validated against each other so that only 1 store coupon will be accepted against
any single item.

Note: This option is dependent on APAR 98274.

Double Coupons are Available only to Preferred Customers

LINE 19

0,0,0,0,0,0,0,0,0,0
__
↑
Double coupons are available only to preferred customers
Range:
Yes (-1), No (0)
Location:
Line 19, Option 10
Default:
No (0) (Coupon multiplication applies to all customers)
Change Activation:
Sign-off all registers.

This Yes/No option causes coupon multiplication to be available only to Preferred

Customers. Because no coupons are doubled for non-preferred customers, this
option requires that a Preferred Customer number be entered prior to the entry of
any paper coupons that are to be doubled. The entry of a Preferred Customer
number after vendor coupons have already been entered will not cause the earlier
coupons to be doubled. In order to double coupons entered prior to a Preferred
Customer number, the coupons must be voided and re-entered or multiplied through
the manual doubling key sequence. When this option is selected, the manual
doubling key sequence (see Electronic Marketing option “MANUAL COUPON
DOUBLING ALLOWED, LOOKUP KEY CODE DEFINED”) can also be used to
multiply coupons for non-preferred customers. A value of Yes (-1) restricts coupon

Chapter 6. Personalization of Preferred Customer Options and Messages 139

 multiplication to those coupons entered after a valid Preferred Customer number. A
value of No (0) allows coupon multiplication to apply equally to all customers.

Save Date of Last Sale for Items at Close of Item Movement

LINE 20

0,0,0,0,0,0,0,0,0,0
__
↑
Save date of last sale for items at close of item movement
Range:
Yes (-1), No (0)
Location:
Line 20, Option 1
Default:
No (0) (No sale date stored in item records)
Change Activation:
Stop and Restart Checkout Support.

This Yes/No option causes each close of an item movement period to update with
the date each item record for which movement was recorded. When the close of an
item movement period is completed, the background program EAMUDOLS updates
the item record for each associated record in the item movement file with the date
of the store close. This date is placed into user exit field 2 of the item record in the
format required for a Selective Item Record report search (Month * 100 + Day) No
date is placed into coupon records since coupon records use exit field 2 to store the
minimum purchase amount. A value of Yes (-1) causes the date of last sale to be
saved in user exit field 2 of each non-coupon item record. A value of No (0) avoids
any processing to update the date of last sale in any item records.

The installation instructions present several different ways in which the program
EAMUDOLS can be installed; however, this option just selects the function of
updating the date of last sale without any staging of item movement. If EAMUDOLS
is installed to perform a different set of functions, then this option should not be
selected. If this option is selected, then EAMUDOLS should not be activated
through the optional installation instructions, except, to set the two needed logical
names, EAMIMOV1 and EAMIMWRK. If EAMUDOLS was installed in one of these
alternate ways and you now wish to use this option then the exit code in the
checkout support exits you installed previously must be removed.

Use Promotion Codes for Coupon Validation

LINE 20

0,0,0,0,0,0,0,0,0,0
__
↑
Use Promotion Codes for Coupon Validation
Range:
Yes (-1), No (0)
Location:
Line 20, Option 2
Default:
No (0) (No promotion code support)
Change Activation:
Sign-off all registers.

This Yes/No option determines if the first exit field (User Data 1) in the item record
file should be used as a promotion code for coupon validation. Promotion codes are

140 Electronic Marketing PRPQ

a method for relating items to coupons. A coupon with a non-zero promotion code
validates against any item containing the same promotion code. This validation by
promotion code replaces validation by manufacturer and family or by department
and family for those coupons that contain a non-zero promotion code. A value of
Yes (-1) causes User Data field 1 to be interpreted and processed as a promotion
code for all items and coupons that contain a value in this item record field. A value
of No (0) prevents any promotion code validation and thereby leaves the first user
exit field in the item record available for other uses.

When this option is selected, only those coupons that contain a promotion code are
validated by the promotion code. All other coupons are validated by the standard
methods. Category 5 scannable coupons do not have an associated promotion
code and therefore continue to be validated by manufacturer and family. Coupons
entered with department keys will continue to be validated by department as long
as no promotion code is put into the department item record. Promotion code
validation is expected to be used for coupons that are created and managed by the
retailer, while external coupons will continue to be validated by manufacturer and
family or by department. The two separate methods of validation are intended to
minimize conflicts between promotions that are internal and external to the retailer.

Since there is no relationship between promotion code validation and the other
forms of coupon validation, a single item can validate one coupon by promotion
code and a second coupon by manufacturer or department. Thus a single sale
might validate 2 manufacturer coupons (1 internal and 1 external) and 2 store
coupons. Likewise, the void of a sale may require the return of multiple coupons. An
item sale may be associated with a promotion code, a manufacturer and family, and
a department number and any of these associations can be used for coupon
validation. Any coupon uses only one method of validation. If promotion code
support is selected and a coupon contains a promotion code, then promotion code
validation will take place regardless of other option settings or item record flags or
fields. If a coupon contains a manufacturer number and no promotion code, then
validation will be by manufacturer. Thus any coupon to be validated by department
or not to be validated at all must not be associated with a promotion code or a
manufacturer number.

Since promotion codes apply to both items and coupons, this option can be
selected only if item record exit field 1 is not being used for any other purpose. The
single exception is that this user data field can be used for a different purpose with
item records defined as refunds, deposits, or deposit returns since these items will
never participate in promotion code validation. Use of promotion codes cost over 1K
in terminal data space usage, so adequate data space must be available to select
this option. If you have not moved the log of the current transaction into extended
memory and are not using the big memory model compiler in the terminal, then
selection of this option will reduce your maximum transaction size by approximately
25 items. When the promotion code option is turned off, the terminals must go
through “Loading Options” before this data space is released.

Any coupon with an item record can be validated by promotion code. This includes
paper coupons, points coupons, weight coupons, cross promotional coupons and
net value coupons. Coupons validated by promotion code have some properties
unique to this validation method. Coupons validated by promotion code are not
eligible to be doubled. Coupons validated by promotion code can be tracked in the
Coupon Tracking file, but the entries for these coupons will not show a matching
item. If a minimum purchase requirement is defined for a coupon validated by
promotion code and the item record flag is set for minimum by manufacturer, then
the minimum purchase requirement will be applied to all matching promotion code

Chapter 6. Personalization of Preferred Customer Options and Messages 141

 sales rather than sales from the coupon manufacturer. Minimum purchase
requirements by department are still applicable to coupons validated by promotion
code.

Unlike standard store coupons, the taxability and foodstampability for all coupons
validated by promotion code will come directly from the flags in the coupon item
record. These coupons will not cause taxes to go negative for the order, but they
can reduce the taxes paid in an order even though all coupons do not match
taxable items. It is the retailer’s responsibility to assure that all items in the same
promotion group have the same taxability and foodstampability if concerned with the
taxability or foodstampability of the coupon. Also, cross promotional coupons
(coupons for validation only with no value) will behave differently with promotion
code validation in that a unique item will be required to validate each valueless
coupon. Thus with promotion code validation, a customer will have to buy two of
each item in a cross promotional chain before the discount will be given a second
time. A customer will also not be allowed to keep a discount if he voids an item that
was required for the cross promotional discount but was not actually discounted.

When this option is selected, the Selective Item Record report will change the
descriptors used with exit field 1 to show that this field is being used for promotion
codes. When the Options Report is used to select this option, it will change the
descriptors used by the Data Maintenance application from “User Data 1” to
“Promotion Code” or “Promo Code”. When the report is used to turn off this option,
the old descriptors for item record maintenance will be restored. If you do not use
the Options Report to activate this option or if you do not like the default Data
Maintenance descriptors for promotion codes, then you can alter the printed
descriptor by using Personalization to change report descriptor 348 and you can
alter the displayed descriptor by using the Display Manager Editor (DMED) to alter
the descriptor on screen 4 of file EAMDBM1S.

Show Only Paper Coupons in Cash Drawer Reports

LINE 20

0,0,0,0,0,0,0,0,0,0
__
↑
Show Only Paper Coupons in Cash Drawer Reports
Range:
Yes (-1), No (0)
Location:
Line 20, Option 3
Default:
No (0) (All coupons in current period till reports)
Change Activation:
Sign-off all registers after closing the reporting period.

This Yes/No option determines whether paperless coupons are included in the till
contents shown by a till status report at the register or by a current period cash
drawer position report. The cash drawer position report for the previous period
never contains paperless coupons since these coupons are automatically picked up
at the close of the period. A value of No (0) leaves all coupon amounts in the till
status and current cash drawer position reports. A value of Yes (-1) removes the
automatic (paperless) coupon amounts from these two reports so that the reports
reflect only the total value of the paper coupons in the till. In order for the coupon
values in these reports to have any meaning, this option must be changed before
any sales activity in a new reporting period. If this option is changed at any time

142 Electronic Marketing PRPQ

other than the start of a new reporting period, then the till status and cash drawer
position reports may show odd coupon amounts for the reporting period in process
when the option is changed.

Bypass Journal Printing of Automatic Coupon Rejections

LINE 20

0,0,0,0,0,0,0,0,0,0
__
↑
Bypass Journal Printing of Automatic Coupon Rejections
Range:
Yes (-1), No (0)
Location:
Line 20, Option 4
Default:
No (0) (Journal print automatic coupon rejections)
Change Activation:
Sign-off all registers.

This Yes/No option determines whether the rejection of an automatic coupon after
an item sale leads to a print line on the journal to define why the coupon was not
given. Journal printing of the rejection of automatic coupons will never occur when
the coupon is rejected at total time or after the entry of a Preferred Customer
number. When an automatic coupon could have been given immediately following
an item sale but was rejected for some reason other than a missed minimum
purchase requirement and this option has a value of 0 (No), then a line will print on
the journal to show why the discount was not awarded. When this option is set to
Yes (-1), then no journal printing will ever occur to detail the rejection reason for
automatic coupons. Note that the journal printing of automatic coupon rejections is
a valuable tool when testing new electronic coupons, however, the journal print lines
may have little value in a store unless most coupons are awarded immediately after
the purchase of the promoted item and the cashiers are aware to look at the journal
to answer customer questions.

Bypass Receipt Printing of Targeted Coupon Numbers

LINE 20

0,0,0,0,0,0,0,0,0,0
__
↑
Bypass Receipt Printing of Targeted Coupon Numbers
Range:
Yes (-1), No (0)
Location:
Line 20, Option 5
Default:
No (0) (Targeted coupon codes are printed)
Change Activation:
Sign-off all registers.

This Yes/No option determines whether the UPC number for a targeted coupon is
printed on the customer receipt when the customer is awarded the coupon or
informed of the coupons available to him. This number is printed so that it can be
used to manually void the coupon if necessary. Option 19.7 prevents keyed entry of
targeted coupons except in the case of voids to prevent manual awarding of
targeted coupons to non-targeted customers. This option goes a step further by
restricting the information needed to manually award or void a targeted coupon.

Chapter 6. Personalization of Preferred Customer Options and Messages 143

 When this option is selected, it is the responsibility of the user to handle those
cases where a targeted coupon needs to be manually awarded or manually voided.
A value of No (0) causes the targeted coupon velocity codes to print on the
customer receipt while a value of Yes (-1) prevents all printing of targeted coupon
item codes. The four digit code that is printed is insufficient by itself for keying in the
coupon when option 1.3 is used to displace the item code for automatic preferred
coupons.

Match Coupons Against Cross Promotional Group

LINE 20

0,0,0,0,0,0,0,0,0,0
__
↑
Match Coupons Against Cross Promotional Group
Range:
Yes (-1), No (0)
Location:
Line 20, Option 6
Default:
No (0) (Match coupons only against a single item)
Change Activation:
Sign-off all registers.

This Yes/No option determines whether the final (real) coupon in a group of linked
cross promotional (1-cent, fake) coupons should discount a single item or the entire
set of matching items. With this option set to 0 (No), the final coupon in a set of
linked cross promotional coupons is matched only against items which it validates
and discounts only these items. The other coupons in the set require sales of
additional items in order to get the discount, but these items are not actually
discounted. Thus a promotion such as “buy ham and cheese and get .20 off on
bread” is limited to discounting the value of the bread. With this option set to Yes
(-1), the value of matching sales for the final coupon is the sum of all matching
sales for the entire promotion. This allows the value of the discount to exceed the
value of any single item required for the discount.

This option applies only to promotions that require multiple different items through
the use of linked valueless coupons (specified by a value of 1) which are linked
finally to a coupon with real value. Since this option causes the value of matching
items for the real coupon to be the sum of all values of matching items for the fake
coupons, the guidance “Coupon Value Exceeds Item Value” is received only if the
value of the coupon is greater than the value of all items required for promotion.
This total matching value is also used for pricing method 4 coupons (net value or
percent off) so that promotions such as “buy ham, cheese, and bread for a net of
1.00” or “get 10% off on the combination of ham, cheese, and bread” are possible.
If the final coupon in a group promotion has a minimum purchase requirement for
matching items (minimum by manufacturer), then all matching sales for the group
are used to satisfy this minimum.

Automatic Tare from Weight Item Records

LINE 20

0,0,0,0,0,0,0,0,0,0
__
↑
Automatic Tare from Weight Item Records
Range:
Yes (-1), No (0)

144 Electronic Marketing PRPQ

Location:
Line 20, Option 7
Default:
No (0) (No Tare weights from the item file)
Change Activation:
Sign-off all registers.

This Yes/No option determines whether tare values will be included in the item
record data for a weight item. A value of No (0) requires either a keyed tare code or
an auto tare value to be used with weight items. A value of Yes (-1) allows for a tare
code, tare weight, or tare percentage to come from the high half of the price field
from the item record for a weight item. Using the high half of the price field for tare
information limits the price per pound of weight items to five digit values and
requires that pricing method 3 be entered if data maintenance is used to update the
tare field. With this option selected, all weight items use pricing method zero
regardless of the pricing method in the item record. Without this option, any weight
item with a pricing method other than zero results in an operator guidance of
“Check Item Data”. With this option selected, the values and processing for the tare
field in the item record are just like those in the user exit example 11 in the IBM
Supermarket Application: Programming Guide The only major difference between
this option and that user exit is the position of the tare field in the item record. This
option provides the tare field in the unused high half of the price field while the exit
example provides the same information in the second user exit field in the item
record.

If the tare field contains a value of 1 to 9, then the value is used as a tare code and
the actual tare weight comes from the options table which associates tare codes
with tare weights. If the tare field contains a value of 10 to 9999 then a guidance of
“Check Item Data” is given. If the tare field contains a value of 1xxxx, then xxxx is
used directly as the tare weight as though it had come from the options. Thus this
value is in hundreds of a pound or in grams depending upon the weight options
used. When actual tare weights are used in the item record, then tare code 9
cannot be used since the weight from the item record replaces the option value for
tare code 9. If the tare field contains a value of 2xxxx, then the xxxx is use to define
the percentage of the input weight that should be subtracted out as tare weight.
This value is in hundredths of a percent so a value of 20500 says that 5 percent of
the item weight is due to the package. If the tare field contains a value of 0, then
the tare value must either be keyed or come from the automatic tare or there will be
no tare weight subtracted from the weight of the item.

Note: When the pricing method of a weight item record is changed to a 3 within
data maintenance, the “Unit Price” descriptor is changed to “Tare Code” and
the location where you might normally see “Deal/Reduced Price”, you will
now see “Unit Price/Lb”. Any price that had been entered in the unit price
field should now be moved to the “Unit Price/Lb” field and the tare
information should be placed in the “Tare Code” field as shown on the
screens on the following pages.

Chapter 6. Personalization of Preferred Customer Options and Messages 145

 DBM1S003 CHANGE AN ITEM RECORD Page 1 of 2

Item Code 89100000000

Description Ground Beef
Department Number (1-999) 300

PRICING METHOD (0-5)

Keep Item Movement (Y/N) Y
Unit Price 1.98 Price Required (Y/N) N
Weight/Price Required (Y/N) Y
Deal Quantity 0

ITEM TYPE (0-7) 0 0=Normal Sale Item 4=Misc. Sale Item

1=Deposit Item 5=Misc. Refund Item
2=Refund Item 6=Manufac. Coupon Item
3=Deposit Return Item 7=Store Coupon Item

Coupon Family Numbers (0-999): Current Period 0 Previous Period 0

For next page, press PgDn.

If complete, press ENTER.

F1 F2 F3QUIT F4 F5 F6 F7 F8 F9 F10

Figure 6. Weight Item Record Without Tare Code

DBM1S003 CHANGE AN ITEM RECORD Page 1 of 2

Item Code 89100000000

Description Ground Beef
Department Number (1-999) 300

PRICING METHOD (0-5) 3

(3 = Priced Weight Item with Tare)
Keep Item Movement (Y/N) Y
Tare Code 10002 Price Required (Y/N) N
Unit Price /LB 1.98 Weight/Price Required (Y/N) Y
Deal Quantity (0-99) 0 Multipricing Group (0-99) 0

ITEM TYPE (0-7) 0 0=Normal Sale Item 4=Misc. Sale Item

1=Deposit Item 5=Misc. Refund Item
2=Refund Item 6=Manufac. Coupon Item
3=Deposit Return Item 7=Store Coupon Item

Coupon Family Numbers (0-999): Current Period 0 Previous Period 0

For next page, press PgDn.

If complete, press ENTER.

F1 F2 F3QUIT F4 F5 F6 F7 F8 F9 F10

Figure 7. Weight Item Record With Tare Code

Bypass Fixed Targeted Message if Promotion Text Provided

LINE 20

0,0,0,0,0,0,0,0,0,0
__
↑
Bypass Fixed Targeted Message if Promotion Text Provided
Range:
Yes (-1), No (0)

146 Electronic Marketing PRPQ

Location:
Line 20, Option 8
Default:
No (0) (Print all targeted coupon descriptors)
Change Activation:
Sign-off all registers.

This Yes/No option determines whether the fixed targeted coupon descriptor is
printed on the customer receipt or Kiosk receipt when promotional text for the
coupon has been provided in the Targeted Coupon Messages file. Option 13.4
allows a list of available targeted coupons to be printed on the customer receipt. In
printing the list of available coupons, a single fixed message is created using the
coupon descriptor and value, and this fixed line may be followed by free form text
which describes the promotion. The free form text is user defined in the Targeted
Coupon Messages file through the Targeted Coupon Message Maintenance
procedure. This option prevents the printing of the fixed descriptor for those
coupons for which free form text has been provided. This option has meaning only
if option 13.4 is selected since this option only impacts the printing of the list of
available targeted coupons on the customer or Kiosk receipt.

A value of No (0) causes both the fixed targeted coupon descriptor and any
available promotion text to be printed in the listing of available targeted coupons. A
value of Yes (-1) causes only the free form promotion text to be printed in the listing
of available targeted coupons for those coupons for which promotion text is
provided. Even with this option selected, the fixed targeted coupon descriptor will
print for any available targeted coupons for which no free form promotion text is
provided in the Targeted Coupon Messages file.

Validate Expiration Date with MSR Entry of Customer ID

LINE 20

0,0,0,0,0,0,0,0,0,0
__
↑
Validate Expiration Date with MSR Entry of Customer ID
Range:
Yes (-1), No (0)
Location:
Line 20, Option 9
Default:
No (0) (No validation of expiration dates)
Change Activation:
Sign-off all registers.

This Yes/No option determines whether the expiration date associated with a
magnetic entry of a customer number is to be validated. It also determines whether
a keyed expiration date is required with a customer number keyed using the
CUSTOMER key defined by option 6.3. A value of No (0) causes the expiration date
from a magnetic customer card to be ignored. The expiration date is logged, but not
validated. This value also allows a customer number to be keyed with the
CUSTOMER key without requiring a keyed expiration date. A value of Yes (-1)
causes guidance B100 CARD HAS EXPIRED to be given whenever the expiration
date on a magnetic customer card has passed. This selection also causes a prompt
for expiration date to be provided whenever a customer number is keyed with the
CUSTOMER key and the expiration date was not entered with the “/” key.

Chapter 6. Personalization of Preferred Customer Options and Messages 147

 Deactivate Unique Electronic Marketing Exit Code
LINE 20

0,0,0,0,0,0,0,0,0,0
__
↑
Deactivate Unique Electronic Marketing Exit Code
Range:
Yes (-1), No (0)
Location:
Line 20, Option 10
Default:
No (0) (All Electronic Marketing exits are active)
Change Activation:
Sign-off all registers. Restart Checkout Support.

This Yes/No option determines whether the code in the electronic marketing exits is
active or not. Option 1.1 turns off all electronic marketing processing while this
option only impacts the user exits written in modules EAMTSESU.J86 and
EAMCSESU.J86 to alter the electronic marketing processing. A value of No (0)
allows all code in the exits in EAMTSESU and EAMCSESU to be executed. A value
of Yes (-1) prevents any of the user exit code in EAMTSESU and EAMCSESU from
executing. This option is provided primarily to isolate problems which are caused by
code added in the electronic marketing user exits.

Use Compressed Print in the Selective Customer Report

LINE 21

0,0,0,0,0,0,0,0,0,0
__
↑
Use compressed print in the selective customer report
Range:
Yes (-1), No (0)
Location:
Line 21, Option 1
Default:
No (0) (causes normal printing of Selective Customer Reports)
Change Activation:
Enter the Selective Customer Report procedure.

This Yes/No option determines whether reports printed by the Selective Customer
Report function are printed in compressed mode or normal mode. Compressed
mode is required to print 132 characters per line on 8.5 inch wide forms. A wide
carriage printer can print 132 characters per line on wide forms without compressed
mode. A value of No (0) causes normal printing of Selective Customer Reports
while a value of Yes (-1) causes compressed mode printing of these reports.

Use 132 Character Lines in the Selective Customer Report

LINE 21

0,0,0,0,0,0,0,0,0,0
__
↑
Use 132 character lines in the selective customer report
Range:
Yes (-1), No (0)

148 Electronic Marketing PRPQ

Location:
Line 21, Option 2
Default:
No (0) (80 characters per printed line)
Change Activation:
Enter the Selective Customer Report procedure.

This Yes/No option determines whether reports printed by the Selective Customer
Report function are formatted with 80 characters per line or with 132 characters per
line. More data can be shown on each line using 132 characters, however, the use
of 132 character print lines requires either a wide carriage printer or usage of
compressed print which is smaller and harder to read. There is no information
printed in 132 character mode that cannot also be printed in 80 character mode, but
the information is formatted more efficiently in 132 character mode. A value of No
(0) causes normal 80 character per line printing of Selective Customer Reports
while a value of Yes (-1) causes these reports to be printed with 132 characters per
line.

Address Label Size Definitions for the Selective Customer Report

LINE 21

0,0,0,0,0,0,0,0,0,0
______________
↑
Address label size definitions for the selective customer report
Range:
(0 or 5 - 20 for the first entry in each pair) (0 or 34 - 79 for the second entry
in each pair)
Location:
Line 21, Options 3 - 8
Default:
0,0,0,0,0,0 (No label formats defined)
Change Activation:
Enter the Selective Customer Report procedure.

These six value options define the height and width for up to three different sizes of
address labels to be used by the Selective Customer Report. When printing
address labels, the Selective Customer Report needs to know the height and width
of the label stock so that the address can be centered on the label. If multiple label
formats are defined with these options, then the report will allow the user to select
which of the defined label sizes is being used. If only one label size is defined in
these options, then all address printing is automatically formatted for that label. If no
label formats are defined in these options, then the user will be prompted to input
the label height and width each time that labels are printed.

The six options are entered as three pairs of height followed by width. The height of
a label is expressed as the number of print lines from the top of one label to the top
of the next. The width of a label is expressed as the number of print characters that
will fit in a single line across the label. The 3 label heights in options 21.3, 21.5, an
21.7 can range in value from 5 to 20 lines or can be set to 0. The 3 label widths in
options 21.4, 21.6, and 21.8 can range in value from 34 to 79 characters or can be
set to 0. If any pair of height-width options contains invalid data, then the definition
for that label size is ignored just as though it were specified as 0,0.

Chapter 6. Personalization of Preferred Customer Options and Messages 149

 Selectively Deactivate Selective Customer Report Functions
LINE 22

0,0,0,0,0,0,0,0,0,0
___________________
↑
Selectively deactivate selective customer report functions
Range:
Yes (-1), No (0)
Location:
Line 22, Options 1 through 9
Default:
0,0,0,0,0,0,0,0,0 (All functions are active)
Change Activation:
Enter the Selective Customer Report procedure.

The Selective Customer Report allows for functions such as erasing, printing,
saving to file, or altering the information stored on a selected set of customers.
Since this valuable information needs to be protected, each one of these functions
can be deactivated for all users to provide additional security beyond the
authorization needed to use the report. Other function can be deactivated to
streamline the input necessary to create a report or to create a batch of changes.
This line of nine Yes/No options allows each of the following nine functions to be
selectively deactivated:
v 22.1 Erase customer records
v 22.2 Print customer reports
v 22.3 Save customer reports to file
v 22.4 Create customer maintenance batches
v 22.5 Print customer address labels
v 22.6 Print report without prior display
v 22.7 Verify targeted coupons when creating a batch
v 22.8 Prompt for a restore batch when creating a batch
v 22.9 Prompt for file copy when creating a batch
The first option applies to the erase function while the fifth option applies to the
printing of address labels. A value of -1 (Yes) in any of the first five of these options
deactivates the selected function such that an operator guidance message will be
given if the function is chosen. A value of 0 (No) in any of these options lets any
operator select and execute the chosen function. The sixth through ninth options
deactivate functions by bypassing a request for operator input. A value of -1 (Yes) in
any of these options prevents the prompt for input from ever appearing. A value of 0
(No) in any of these options requires the operator to respond to the prompt for
additional input.

Line 23 is Reserved
0,0,0,0,0,0,0,0,0,0
____________________
↑
Reserved

All Coupons Require at Least Department Level Validation

LINE 24

0,-1,-1,0,-1,0,0,0,0,0
__
↑
All coupons require at least department level validation
Range:
Yes (-1), No (0)

150 Electronic Marketing PRPQ

Location:
Line 24, Option 1
Default:
No (0) (Individual coupon records select validation)
Change Activation:
Sign-off all registers.

This Yes/No option causes coupons to always be validated by department (assure

more sales than coupons for the department) when a coupon contains no
manufacturer number or a manufacturer number of “00000”. When this option is set
to not require department level validation, individual coupon item records determine
whether a specific coupon is to be validated by department or not validated at all.
Any coupon with a promotion code in the item record will be validated based on
that promotion code. In the absence of an active promotion code, any coupon which
has an associated manufacturer number (in the input UPC or in the coupon record)
will be validated based on that manufacturer number.

A value of No (0) allows individual coupon item records to determine the level of
coupon validation while a value of Yes (-1) assures that all coupons are validated at
least at a department level. If it is desired that some coupons not be validated
against any prior sales, then this option must be set to No (0).

Validate All Department Keyed Coupons by Department

LINE 24

0,-1,-1,0,-1,0,0,0,0
__
↑
Validate all department keyed coupons by department
Range:
Yes (-1), No (0)
Location:
Line 24, Option 2
Default:
Yes (-1) (Validate department keyed coupons)
Change Activation:
Sign-off all registers.

This Yes/No option defines whether coupon entries made with a coupon key against
a non-coupon item record should be validated by department. This option has no
meaning unless the prior option is set to 0 so that validation by department is not
required. In this case, this option can be used to insure department validation for
coupons entered with a department key while all other coupons determine their
level of validation from their item record flags. For all coupons that are entered in a
way that does not provide a coupon manufacturer number and does not cause the
lookup of a coupon item record, this option effectively replaces the item record flags
that determine coupon validation. A value of No (0) causes all coupons entered with
a coupon key and no manufacturer number to be accepted without validation. A
value of Yes (-1) causes all coupons entered with a coupon key to be validated by
department if there is no manufacturer to validate against.

This option is needed only for customers who want department validation when
coupons are entered with a department key, but do not want any validation for
selected coupon item records (i.e. a coupon based only on meeting a minimum
purchase amount). These customers must set the prior option to 0 to allow selected
coupon item records to bypass department validation. A flag is set in individual
coupon item records to force validation by department as needed. This option

Chapter 6. Personalization of Preferred Customer Options and Messages 151

 selects department validation for those coupons which are entered without a
coupon item record since only coupon item records have the flag needed to select
department validation.

Sequence Number and Velocity Code in Store Coupon UPCs

LINE 24

0,-1,-1,0,-1,0,0,0,0
__
↑
Sequence number and velocity code in store coupon UPCs
Range:
Yes (-1), No (0)
Location:
Line 24, Option 3
Default:
Yes (-1) (Store coupon UPCs contain velocity code)
Change Activation:
Sign-off all registers.

This Yes/No option determines whether Category 4 and 5 coupon UPCs contain a
velocity code and sequence number to be used for accessing and validating a
coupon item record. A value of Yes (-1) causes only the last 4 digits of an 11 digit
category 4 or 5 UPC to be used to access the item record file. A value of No (0)
causes the full 11 digits of a category 4 UPC or an item code of the form
400000XXXXX derived from the last 5 digits of a category 5 UPC to be used to
access the item file. The sequence number in the input UPC allows the same item
record to be reused for a new coupon while assuring that the prior coupon that
accessed this record is now rejected.

Store Coupons Logged in the Coupon Tracking File

LINE 24

0,-1,-1,0,-1,0,0,0,0
__
↑
Store coupons logged in the coupon tracking file
Range:
Yes (-1), No (0)
Location:
Line 24, Option 4
Default:
No (0) (Store coupons are not tracked)
Change Activation:
Sign-off all registers. Stop then Restart Checkout Support.

This Yes/No option determines whether store coupons are logged in the coupon
tracking file. A value of No (0) prevents store coupons from being saved in the
coupon tracking file while a value of Yes (-1) causes store coupons to be saved in
the coupon tracking file.

Vendor Coupons Logged in the Coupon Tracking File

LINE 24

0,-1,-1,0,-1,0,0,0,0
__
↑
Vendor Coupons Logged in the Coupon Tracking File

152 Electronic Marketing PRPQ

Range:
Yes (-1), No (0)
Location:
Line 24, Option 5
Default:
Yes (-1) (Vendor coupons are tracked)
Change Activation:
Sign-off all registers. Stop then Restart Checkout Support.

This Yes/No option determines whether vendor coupons are logged in the coupon
tracking file. A value of No (0) prevents vendor coupons from being saved in the
coupon tracking file while a value of Yes (-1) causes vendor coupons to be saved in
the coupon tracking file.

Doubled Coupons Logged in the Coupon Tracking File

LINE 24

0,-1,-1,0,-1,0,0,0,0,0
__
↑
Doubled coupons logged in the coupon tracing file
Range:
Yes (-1), No (0)
Location:
Line 24, Option 6
Default:
No (0) (Doubled coupons are not tracked)
Change Activation:
Sign-off all registers. Stop then Restart Checkout Support.

This Yes/No option determines whether store coupons created by doubling are
logged in the coupon tracking file if other store coupons are also logged. A value of
No (0) prevents double coupons from being saved in the coupon tracking file while
a value of Yes (-1) causes double coupons to be saved in the coupon tracking file.

Coupon Tracking File Entries in Compressed Format

LINE 24

0,-1,-1,0,-1,0,0,0,0,0
__
↑
Coupon tracking file entries in compressed format
Range:
Yes (-1), No (0)
Location:
Line 24, Option 7
Default:
No (0) (Coupon tracking data is in ASCII)
Change Activation:
Stop then Restart Checkout Support.

The coupon tracking file data can be formatted as ASCII data or as packed decimal
data. The ASCII data is easier to process and translate, but it takes nearly twice the
disk space and transmission time of the packed decimal data. This Yes/No option
determines whether coupon tracking file data is formatted in ASCII or is
compressed to packed decimal. A value of No (0) causes coupon data to be saved
in ASCII in the coupon tracking file while value of Yes (-1) compresses this coupon
data to a packed decimal format.

Chapter 6. Personalization of Preferred Customer Options and Messages 153

 Manufacturer Number to Identify UPC 5 Store Coupons
LINE 25

“00000”,“0”,“0”,0,0,0,0,0,0,0
_______
↑
Manufacturer number to identify UPC 5 store coupons
Range:
(“00000” - “99999”)
Location:
Line 25, Option 1
Default:
“00000” (All category 5 UPCs are vendor coupons)
Change Activation:
Sign-off all registers.

Category 5 UPCs are normally used on vendor coupons with the first five digits in
the UPC after the category number being the manufacturer number to relate the
coupon to matching items. This package allows a store to create its own category 5
store coupons if the store owns a manufacturer number (perhaps obtained for
house brand items). This option value contains the manufacturer number to be used
to recognize category 5 UPCs which are store coupons. This value only needs to
be altered if you plan to use category 5 UPCs on your store coupons. This option is
a character string that must contain of 5 numeric characters. A value of “00000”
prevents any category 5 UPC from being recognized as a store coupon and thus
causes all category 5 UPCs to be processed as vendor coupons.

Range of Coupon UPCs to Log in the Coupon Tracking File

LINE 25

“00000”,“0”,“0”,0,0,0,0,0,0,0
_______
↑
Range of coupon UPCs to log in the coupon tracking file
Range:
(“0” - “999999999999”)
Location:
Line 25, Options 2 and 3
Default:
“0”,“0” (Log any coupon UPC)
Change Activation:
Sign-off all registers. Stop then Restart Checkout Support.

This pair of value options defines a range of coupon UPC numbers to save in the
coupon tracking file. This range further restricts the coupon tracking file contents
beyond the restriction defined by prior options. Thus while the prior options might
be used to restrict coupon tracking to vendor coupons, this option might be used to
restrict coupon tracking to category 5 vendor coupons or even to category 5
coupons from a particular manufacturer. It might also be used to restrict coupon
tracking to the range of codes defined for preferred customer coupons. If this range
is provided, it should contain a low UPC followed by a high UPC. If the second
value is not higher than the first value, then there will be no restrictions on the
UPCs that are logged in coupon tracking file.

Range of Departments to Validate by Subtotal Group

LINE 25

“00000”,“0”,“0”,0,0,0,0,0,0,0

154 Electronic Marketing PRPQ

 ____
↑
Range of departments to validate by subtotal group
Range:
(0-999)
Location:
Line 25, Options 4 and 5
Default:
0,0 (No validation by department subtotal groups
Change Activation:
Force all register through LOADING OPTIONS Stop then Restart Checkout
Support.

This pair of value options defines a range of departments for which coupons are to
be validated by department subtotal group rather than by department. The first
value defines the lowest department number to be validated by subtotal group and
the second value defines the highest department number to be validated by subtotal
group. If either department number is invalid (< 1 or > 999), or the low department
number is not less than the high department number, then all department validation
will be against the specific department numbers for the coupons.

Coupons are validated by department by assuring there are more sales for the
department than coupons against the department. This department level validation
occurs for coupons with no associated manufacturer number or promotion code
only if the options are not set to bypass department level validation or the coupon is
flagged specifically for department validation. When a valid department number
range is specified in this option, then any coupons which meet the conditions for
department level validation and contain a department number in the specified range
will be validated by department subtotal group rather than by department. This
means that there must be more sales from the group of departments to which this
coupon belongs than coupons against the group of departments. A coupon which
meets the requirements for department level validation but contains a department
number outside of the specified range will be validated against its specific
department. The department lookup item codes must be defined without a valid
manufacturer number (xx00000xxxxx) for department keyed coupons to validate by
department subtotal group. For the coupons that validate on a group of
departments, the minimum purchase requirement specified in the coupon item
record is also met by all sales from the group of departments. While the purchase
amount for a specific department is reduced by associated coupons for purposes of
the minimum purchase requirement, the purchase amount for a group of
departments is compared against the minimum purchase requirement without
regard for prior coupons. Another difference from the base system is that coupons
which are validated by manufacturer are counted against the department group.
Coupon family codes are ignored for coupons which are validated by department
subtotal group. Department subtotal groups are defined in the store options and are
shown in the department analysis and operator performance reports. The
department group validated for a coupon is the group which contains the
department number specified for the coupon. If the department range specified in
this option includes only a part of a subtotal group used by the reports, then only
those departments specified in this option will be considered in the subtotal group
for the purposes of coupon validation. Thus items which are in the subtotal group
but not in the validation range will not match against coupons which are in the
subtotal group and in the validation range.

Chapter 6. Personalization of Preferred Customer Options and Messages 155

 List of Guidances to be Lowered to Allow Operator Override
LINE 26

199
↑
List of Guidances to be Lowered to Allow Operator Override
Range:
(0-999)
Location:
Line 26, Options 1 to n
Default:
199 (Partial coupon match)
Change Activation:
Sign-off all registers.

This set of value options defines a set of operator guidances to be altered from
requiring a manager’s override to requiring an operator’s override. This list can
contain as many entries as needed, but the entries must be chosen from the
following lists of valid values. If you have more than one, this set of options should
be entered on Line 26, separated by commas. The options report will only report
and alter the first 20 entries. Only operator guidances that normally require a
manager’s override can be selected by this option.

The operator guidances lowered from a manager’s override to an operator’s

override are selected through one of the following ways:
v The operator guidance code, as defined in Appendix A of IBM 4680 Supermarket
Application: Guide to Operations (For example, 9 = ITEM LIMIT CHECK.)
v The two-character override identifier in the guidance or override prompt, as
defined by the terminal sales descriptors 114 to 145. (For example, 115 = “RF”.)
v The manager’s override reason code, as shown in the definition of the type 10
record in the Transaction Summary Log in the IBM 4680 Supermarket
Application: Programming Guide

A special entry also is provided to request an operator’s override for coupons that
validate partially (MANUFACTURER VALID) but still require a manager’s override
for a coupon for which no match is found. These override controls enable you to
select all of the possible override conditions or to select only one condition for
which a given guidance might occur. When multiple selections overlap, the
conditions are logically ORed instead of being ANDed. Use of multiple redundant
override codes must be avoided to prevent adverse performance implications.

The value of guidance codes in the override list equals the value of the numeric
guidance indicator, and ranges between 1 and 120. The table impacts guidances
that require a manager’s override. The only valid guidance codes to appear in the
table are listed below:
1 - NO COUPON ON (lookup key)
8 - TRANSACTION LIMIT CHECK
9 - ITEM LIMIT CHECK
42 - KEYED WEIGHT LIMIT CHECK
43 - NO REFUND ON (lookup key)
45 - DISCOUNT LIMIT CHECK
51-58 - TENDER VERIFICATION REJECTION
60 - CHANGE AMOUNT LIMIT CHECK
62 - KEYED PRICE LIMIT CHECK
64 - COUPON MUST MATCH PREVIOUS SALE
65 - COUPON VALUE EXCEEDS ITEM VALUE
67 - CANCEL MUST MATCH PREVIOUS ENTRY

156 Electronic Marketing PRPQ

 100-109 - USER DEFINED
610 - LIMITED NUMBER OF COUPONS PER ORDER
611 - COUPON HAS EXPIRED
612 - MINIMUM SALE NOT SATISFIED

A value of 199 as the first entry in the override table defines to allow an operator’s
override on any coupon validation error where the coupon is partially validated. A
manager’s override will still be required if no match at all is found. A value of 198 as
the first entry in the override tables behaves just like a value of 199 with a single
exception. A value of 198 also allows the “TOO MANY COUPONS” guidance to be
bypassed with an operator override so that multiple coupons can be taken for the
same item.

The value of override identifiers in the override list equals the position of the two
characters in the sales descriptors plus 87, and range between 202 and 232. For
example, an RF that appears at position 115 in the sales descriptors is entered in
the override list as 202. A TL that appears at position 145 in the sales descriptors is
entered in the override table as 232. The only valid override indicators to appear in
the table are listed below.
202 - "RF" refund limit
203 - "DR" deposit return limit
204 - "MR" [Link]. receipt limit
205 - "MP" [Link]. payout limit
206 - "MC" manufacturer coupon limit
207 - "SC" store coupon limit
208 - "CL" item sale cancel limit
209 - "DC" deposit cancel limit
210 - "WT" weight limit
211 - "VF" tender verification limit
212 - "LO" loan limit
213 - "PC" pickup limit
215 - "PR" price limit
216 - "SV" store coupon validation
217 - "TR" transaction limit
218 - "CHG" change limit
219 - "FEE" fee correction limit
220 - "QUANTITY" quantity limit
221 - "DI" discount amount limit
222 - "RT" discount rate limit
223 - "TX" tax exemption limit
224 - "VT" void transaction limit
225 - "FS" foodstamp change limit
226 - "PE" pending item entry override
227 - "CV" cancel validation
228 - "TN" tender amount limit
229 - "MV" manufacturer coupon validation
230 - "EX" tender exchange limit

Override reason codes go into the override table with the value of the reason code
plus 400. Since the reason codes range from 1 to 56, the table entries range from
401 to 456. A distinction for the reason code entires in the override table is that they
MUST appear in ascending order at the end of the table. The valid override reason
code entries in the table are:
401 - Exceed price override limit
402 - Fall short of minimum price limit
403 - Exceed negative entry limit
404 - Fall short of minimum Misc. item limit
405 - Exceed misc. item refund limit
406 - Cancel item not sold in transaction
407 - Accept coupon for item not sold
408 - Enter coupon or refund with dept. key
409 - Exceed weight override limit

Chapter 6. Personalization of Preferred Customer Options and Messages 157

 410 - coupon value exceeds item value
412 - coupon sequence number mismatch
413 - coupon minimum purchase not satisfied
414 - coupon limit in transaction exceeded
415 - Exceed discount rate limit
416 - Exceed discount amount limit
417 - Exceed tax exemption limit
419 - Not enough points to redeem for discount
421 - Exceed negative entry limit for trans.
422 - Exceed negative total limit for trans.
423 - Exceed foodstamp change limit
424 - Exceed tender type amount limit
425 - Exceed tender type change limit
426 - Bypass tender verification
427 - Bypass tender verification rejection
428 - Perform delayed override
429 - Bypass tender verification access failure
430 - Keyed Preferred coupon accepted
431 - Keyed Preferred Customer number accepted
432 - Add Preferred Customer who is not on file
433 - Entry of new tender verification number
434 - Bonus point limit exceeded
435 - Exceed void transaction limit
440 - Exceed tender exchange limit
441 - Bypass tender exchange ranking
442 - Exceed tender fee refund limit
445 - Exit special signoff without password
446 - Open cash drawer inside of transaction
447 - Exceed till exchange limit
450 - Sign-on when already signed on
451 - Bypass operator auth. access failure
452 - Re-initialize transferred terminal
455 - Exceed cashier loan limit
456 - Exceed cashier pickup limit

Doubled Coupon Value Limit Per Coupon

LINE 27

9999,0,0,0,999,0,999,0,0,0
_____
↑
Doubled coupon value limit per coupon
Range:
(0 - 32767)
Location:
Line 27, Option 1
Default:
9999 (Coupons can double up to 99.99)
Change Activation:
Sign off all registers.

This (monetary) value option contains the coupon multiplication limit to be used to
restrict the size of multiplied coupons. The value is compared against either the
multiplied portion of the coupon or the sum of the coupon and the double. If the
limit is exceeded, then either the double is not given or its value is reduced. The
following two options determine the use of this limit. This option needs to be altered
only if coupon doubling has been selected in the base terminal options. This option
applies equally well to coupon tripling.

No Doubling of Coupons Over the Value Limit

LINE 27

9999,0,0,0,999,0,999,0,0

158 Electronic Marketing PRPQ

 __
↑
No doubling of coupons over the value limit
Range:
Yes (-1), No (0)
Location:
Line 27, Option 2
Default:
No (0) (Coupons over the limit double to the limit)
Change Activation:
Sign-off all registers.

This Yes/No option determines if a coupon over the limit is doubled up to the limit or
is not doubled at all. A value of No (0) causes the coupon to double up to the limit
while a value of Yes (-1) prevents the coupon from doubling at all if it is over the
limit. With the limit at $.50 and this option set to No (0), any vendor coupon more
than $.50 will cause a double coupon of $.50. If this option is set to Yes (-1) with
the same limit, any vendor coupon over $.50 will not double. This option needs to
be altered only if coupon doubling has been selected through the base terminal
options. This option applies equally well to coupon tripling.

Value Limit Applies to the Sum of the Coupon and the Double
LINE 27

9999,0,0,0,999,0,999,0,0,0
__
↑
Value limit applies to the sum of the coupon and the double
Range:
Yes (-1), No (0)
Location:
Line 27, Option 3
Default:
No (0) (Limit applies only to the size of the double)
Change Activation:
Sign-off all registers.

This Yes/No option determines whether the coupon value limit applies to just the
doubled coupon value or to the sum of the vendor coupon and the doubled coupon
values. A value of No (0) causes the limit to apply to only the multiplied coupon. A
value of Yes (-1) causes the limit to apply to the sum of both coupons, and if the
limit is exceeded, causes the doubled coupon to be reduced so that the sum will
equal the limit. With the limit at $.50 and this option set to No (0), any vendor
coupon less than $.50 will be doubled at face value. If this option is set to Yes (-1)
with the same limit, any vendor coupon over $.25 will multiply such that the total
coupon value is $.50. Thus a $.35 coupon would cause a $.15 double. This option
needs to be altered only if coupon doubling has been selected through the base
terminal options. This option applies equally well to coupon tripling.

Minimum Transaction Size for Coupon Doubling

LINE 27

9999,0,0,0,999,0,999,0,0,0
__
↑
Minimum transaction size for coupon doubling
Range:
(0 - 32767)

Chapter 6. Personalization of Preferred Customer Options and Messages 159

 Location:
Line 27, Option 4
Default:
No (0) (No minimum purchase required for doubling)
Change Activation:
Sign off all registers.

This numeric (monetary) value option contains the minimum transaction size
required for coupon doubling. When the total value of the transaction is less than
this limit, then no coupons will be doubled in the transaction. A minimum value of 0
allows any size order to contain doubled coupons. Note that if the minimum
transaction limit is exceeded after coupons have already been tendered (coupons
taken before all items), the coupons are not retroactively doubled. This option
needs to be altered only if coupon doubling has been selected through the base
terminal options. This option applies equally well to coupon tripling.

Doubled Coupon Count Limit Per Order

LINE 27

9999,0,0,0,999,0,999,0,0,0
__
↑
Doubled coupon count limit per order
Range:
(0 - 32767)
Location:
Line 27, Option 5
Default:
999 (No limit on doubled coupons per order)
Change Activation:
Sign off all registers.

This numeric value option provides a limit on the number of coupons to be doubled
in a transaction. When this limit is exceeded, no more coupons in the transaction
will be doubled. This option needs to be altered only if coupon doubling has been
selected through the base terminal options. The option applies equally well to
coupon tripling.

Purchase Amount for the Coupon Doubling Count Limit

Line 27

9999,0,0,0,999,0,999,0,0,0
__
↑
Purchase amount for the coupon doubling count limit
Range:
(0 - 32767)
Location:
Line 27, Option 6
Default:
0 (Count limit is independent of order size )
Change Activation:
Sign off all registers.

This numeric (monetary) value option defines a purchase amount to which the
doubled coupon count limit applies. If a transaction size is multiple times larger than
the specified purchase amount, then the limit of coupons to be doubled for this
transaction is multiplied accordingly. Thus this option allows the limit of coupons to

160 Electronic Marketing PRPQ

be doubled in a transaction to vary with the size of the transaction. If this option is
0, then the maximum number of coupons to be doubled in a transaction will not
vary with the size of the transaction. With the prior options set to allow one coupon
to be doubled in a $10.00 transaction and this option set for a new double limit for
each $5.00 purchased, then no coupons would be doubled for a $7.50 transaction,
up to 2 coupons could be doubled for a $14.00 transaction, and up to 3 coupons
could be doubled for a $15.00 transaction. If the options were set to allow 5
coupons to be doubled for each $50.00 purchased, then:
v Up to five coupons could be doubled for a transaction under $100.00
v Up to 10 coupons could be doubled for a transaction greater than $100.00
v Up to 15 coupons could be doubled for a transaction greater than $150.00.
Note that with this option in use, the maximum number of coupons to be doubled in
a transaction is limited only by the maximum transaction size. This option needs to
be altered only if coupon doubling has been selected through the base terminal
options. This option applies equally well to coupon tripling.

Limit on the Number of Identical Coupons to be Doubled in an

Order
Line 27

9999,0,0,0,999,0,999,0,0,0
___
↑
Limit on the number of identical coupons to be doubled in an order
Range:
(0 - 32767)
Location:
Line 27, Option 7
Default:
999 (No limit on like coupons doubled in an order)
Change Activation:
Sign off all registers.

This numeric value option defines a limit on the number of identical coupons that
can be doubled in an order. The coupons are considered identical if they are
validated and if their UPCs match. Once the limit is exceeded, the like coupons just
cease to automatically double with no warning or override opportunity. Any value
less than 1 will be converted to 9999. This option needs to be altered only if coupon
doubling has been selected through the base terminal options. This option applies
equally well to coupon tripling.

Manual Coupon Doubling Allowed, Lookup Key Code Defined

Line 27

9999,0,0,0,999,0,999,0,0,0
__
↑
Manual coupon doubling allowed, lookup key code definedÍ
Range:
(0, -1, or 200 - 255)
Location:
Line 27, Option 8
Default:
0 (No manual coupon doubling)
Change Activation:
Sign off all registers.

Chapter 6. Personalization of Preferred Customer Options and Messages 161

 This option can contain either a 0 or -1 value to define whether manual entry of
doubled coupons is allowed or a numeric value to define the lookup key to be used
for manual entry of doubled coupons. A value of 0 for this option does not allow any
manual entry of doubled coupons. Any non-zero value for this option defines that
manual entry of doubled coupons is allowed through use of the OVERRIDE key as
the first key in any key sequence that accesses an item record defined as a store
coupon. If the non-zero value is in the range of 200 to 255, then it also defines the
function code of a lookup key that is to be used exclusively as a double coupon
key. This lookup key can be used to enter doubled coupons without using the
OVERRIDE key, but it must access an item record defined as a store coupon for
this definition as a double coupon key to have any meaning. Note that if this option
is selected with the intent to use the OVERRIDE key, you might also wish to alter
the terminal input state table to make function code 79 in the MAIN state not be
mutually exclusive with position 1. This will allow the VOID key to precede the
OVERRIDE key when voiding a manual double coupon entry, which seems more
natural than requiring that the OVERRIDE key precede the Void key. This option
needs to be altered only if coupon doubling has been selected through the base
terminal options. This option applies equally well to coupon tripling.

Days of Week on Which Coupon Doubling is Not Active

Line 28

0,0,0,0,0,0,0,0,0,0
_____________
↑
Days of week on which coupon doubling is not active
Range:
Yes (-1), No (0)
Location:
Line 28, Options 1 to 7
Default:
0,0,0,0,0,0,0 (Doubling active each day of the week)
Change Activation:
Sign-off all registers.

This set of Yes (-1), or No (0) options defines the days of the week when coupon
doubling is active. A value of No (0) allows coupon doubling while a value of Yes
(-1) prevents coupon doubling on the specified day of the week. The first option is
for Sunday, the second for Monday, and the seventh is for Saturday. If all seven
options are No (0), then coupon doubling is not sensitive to the day of week. This
option needs to be altered only if coupon doubling has been selected through the
base terminal options. This option applies equally to coupon tripling.

Line 29 is reserved.
0,0,0,0,0,0,0,0,0,0
____________________
↑
Reserved

End of Options Indicator

LINE 30
*END* (Required line that indicates end of options file)

162 Electronic Marketing PRPQ

Selective Item Record Report Options
Processing options for the Selective Item Record Report are provided through flags
in a special item record, “888888888888”. This item record is created by the report
if it is not present and is marked so that it cannot be used for an item sale at a
register.

The options in the record are defaulted to minimize use of the report to alter the
item record data base. The options can be altered as needed by using the
Preferred Customer Options Report (User Report 7) to display and alter the options
values. These options can also be altered by using Data Maintenance to alter the
option flags in the item record. Since these options apply only to the Selective Item
Record Report, changes become active the next time the report is run. If the report
is active when the options are changed, it must be exited and re-entered to make
the new option setting active.

While the Preferred Customer Options Report makes these Selective Item Record
Report options appear to be no different than the options in file [Link],
the options are actually stored in the special item record for compatibility with and
migration from earlier levels of the Selective Item Record Report that were provided
with the Coupon Processing PRPQ.

The relationship between the item record flags in item “888888888888” and the
options described below and seen in the Preferred Customer Options report are
defined by the following chart:
Item Record Flag Option Description Options Report ID

TAX A NO DIRECT PRINTING OF REPORT 31.2

TAX B EXIT FIELD 1 CONTAINS PACKED DATA 31.7
TAX C EXIT FIELD 2 CONTAINS PACKED DATA 31.8
TAX D REPORT EXIT 1 + EXIT 2 AS A SINGLE FIELD 31.9
FOODSTAMP NO SAVING OF REPORT DATA 31.1
TRADE STAMP USE A 1 PAGE MENU SEARCH SELECTIONS 31.0
DISCOUNT REPORT USES COMPRESSED PRINT 32.1
COUPON MULT REPORT USES 132 CHARACTER PRINT LINES 32.2

SHELF LABEL FAMILY EQUALS LOW 3 DIGITS OF LINK 32.3

TOF ITEM ALL BATCHES ARE DDM OPERATOR CONTROLLED 32.4
POINT ONLY ALL BATCHES ARE ADDMI BATCHES 32.5
LINK DEPOSIT ALL BATCHES ARE ADDMI IMMEDIATE 32.6
USER FLAG 1 NO RESETTING OF ITEM MOVEMENT 31.3
USER FLAG 2 NO CREATION OF MAINTENANCE BATCHES 31.4
USER FLAG 3 NO DELETION OF ITEM RECORDS 31.5
USER FLAG 4 NO CREATION OF ITEM MOVEMENT LISTS 31.6

Note that the options definitions are given relative to the setting of the item record
flag. Thus if USER FLAG 1 is on (set to “Y”), then resetting of item movement is
NOT allowed. Many of the options definitions given below are inverted to a positive
statement to match the options as presented by the Options Report. The following
options definitions are also ordered as they are presented in the options report.

Allow Saving of Report Data to File (31.1)

Range:
Yes, No
Location:
Line 31, Option 1
Default:
Yes (report data can be saved)
Change Activation:
Re-enter selective item report.

Chapter 6. Personalization of Preferred Customer Options and Messages 163

 This Yes/No option determines whether item record report data can be saved to file
for further processing or later reporting. The user is given the option of saving just
the item codes of the listed items, the item record data for the items in sequential
keyed file utility format, or the actual report lines for later printing. A value of Yes in
the options report allows saving of report data to file while a value of no prohibits
saving of report data to file. This option is provided because of the security
implications of moving a subset of the item record data into a portable file.

Allow Printing of the Report with No Display (31.2)

Range:
Yes, No
Location:
Line 31, Option 2
Default:
No (No prompt to print before displaying)
Change Activation:
Re-enter selective item report.

This Yes/No option determines whether the user is given the choice of immediately
printing a report at the conclusion of an item record search rather than displaying
the report. A value of “Yes” in the options report requires the user of the item report
to define prior to each search whether the search should result in a printed or a
displayed report. A value of “No” in the options report avoids this extra user prompt
prior to each item record search and causes the found items to be displayed at the
conclusion of the search. The report can then be printed by pressing the F10PRINT
key while the report is being displayed. The user should normally view the
displayed report before printing in order to assure that the right items are reported
and to select the proper report format.

Allow Resetting of Item Movement (31.3)

Range:
Yes, No
Location:
Line 31, Option 3
Default:
No (Resetting of item movement not allowed)
Change Activation:
Re-enter selective item report.

This Yes/No option determines whether item movement data can be reset for a list
of items on which movement was just reported. A value of “Yes” in the options
report allows the user to delete the current period item movement records for a list
of reported items. A value of “No” in the options report prevents all users from
resetting any item movement data using the item report. Note that when this option
is selected, a user must still be individually authorized to reset item movement and
must enter his password to confirm his identity.

Allow Creation of Maintenance Batches (31.4)

Range:
Yes, No
Location:
Line 31, Option 4
Default:
No (Creation of maintenance batches not allowed)
Change Activation:
Re-enter selective item report.

164 Electronic Marketing PRPQ

This Yes/No option determines whether an item record maintenance batch can be
created for a list of reported items. A value of “Yes” in the options report allows the
user to create an ADDMI or DDM item record maintenance batch to add, delete, or
alter the item records for a list of reported items. A value of “No” in the options
report prevents all users from creating item record maintenance batches using the
item report. Note that when this option is selected, a user must still be individually
authorized to build a maintenance batch through the Delayed Data Maintenance
function and must enter his password to confirm his identity. The batch can be used
to alter item records only if the user is individually authorized to change item record
data through Data Maintenance.

Allow Deletion of Item Records (31.5)

Range:
Yes, No
Location:
Line 31, Option 5
Default:
No (Deletion of records not allowed)
Change Activation:
Re-enter selective item report.

This Yes/No option determines whether a list of reported item records can be
deleted from the item record file. A value of “Yes” in the options report allows the
user to delete the item records for a list of reported items. A value of “No” in the
options report prevents all users from deleting any item records using the item
report. Note that when this option is selected, a user must still be individually
authorized to delete item records through Data Maintenance and must enter his
password to confirm his identity. A value of “No” in the options report for this option
also prevents the building of maintenance batches to delete item records.

Allow Creation of Item Movement Lists (31.6)

Range:
Yes, No
Location:
Line 31, Option 6
Default:
No (Creation of item movement lists not allowed)
Change Activation:
Re-enter selective item report.

This Yes/No option determines whether an item movement list can be created for a
list of reported items. A value of “Yes” in the options report allows the user to build
an item movement list to be used to report the movement for the selected set of
items. A value of “No” in the options report prevents all users from building item
movement lists using the item report. Note that when this option is selected, a user
must still be individually authorized to build movement lists through Data
Maintenance and must enter his password to confirm his identity.

Exit Field 1 Contains Packed Decimal Data (31.7)

Range:
Yes, No
Location:
Line 31, Option 7
Default:
No (Exit field 1 is a two byte integer field.)
Change Activation:
Re-enter selective item report.

Chapter 6. Personalization of Preferred Customer Options and Messages 165

 This Yes/No option determines whether the first user exit field in the item record is
treated as packed decimal or integer data when it is reported or updated. A value of
“Yes” in the options report causes this 2-byte exit field to be treated as 4 packed
decimal digits. A value of “No” in the options report causes this exit field to be
treated as a 2-byte integer.

Exit Field 2 Contains Packed Decimal Data (31.8)

Range:
Yes, No
Location:
Line 31, Option 8
Default:
No (Exit field 2 is a two byte integer field.)
Change Activation:
Re-enter selective item report.

This Yes/No option determines whether the second user exit field in the item record
is treated as packed decimal or integer data when it is reported or updated. A value
of “Yes” in the options report causes this 2-byte exit field to be treated as four
packed decimal digits. A value of “No” in the options report causes this exit field to
be treated as a 2-byte integer.

Report Exit 1 and Exit 2 as a Single Field (31.9)

Range:
Yes, No
Location:
Line 31, Option 9
Default:
No (Exit fields reported as separate fields.)
Change Activation:
Re-enter selective item report.

This Yes/No option determines whether the contents of the two exit fields in the
item record are reported as a single 4-byte field or as two separate 2-byte fields. A
value of “Yes” in the options report causes the exit data to be reported as a single
4-byte integer or 4-byte packed decimal value. A value of “No” in the options report
causes the exit data to be reported as two separate 2-byte integer or packed
decimal values.

Use a One Page Menu for All 16 Search Selections (31.10)

Range:
Yes, No
Location:
Line 31, Option 10
Default:
Yes (All menu selections are on one page.)
Change Activation:
Re-enter selective item report.

This Yes/No option determines whether a one page or two page menu is used to
present the 16 item record search selections. A value of “Yes” in the options report
causes all 16 search criteria to be presented on a single one-page menu with two
selections on each of eight lines. With this selection, the Enter key is required
following selection 1, since two digit selections beginning with 1 are also available
on the same page. A value of “No” in the options report causes the first eight
search criteria to be presented on the first menu page and the second eight criteria
to be presented on the second menu page. The PgUp and PgDn keys are used to

166 Electronic Marketing PRPQ

move between menu pages. All selections are assumed to come from the current
menu page so only one digit is needed on the first page while a second digit or the
Enter key are needed after a 1 that is entered on the second page.

Printed Reports are in Compressed Mode (32.1)

Range:
Yes, No
Location:
Line 32, Option 1
Default:
No (Report printers are in normal mode.)
Change Activation:
Re-enter selective item report.

This Yes/No option determines whether printed reports use standard character sizes
(10 characters per inch) or condensed character sizes (17.1 characters per inch). At
10 characters per inch, a wide carriage printer and wide forms are needed to print
reports with 132 characters per line. With condensed characters, reports can be
printed with 132 characters per line on a standard printer with 8.5 inch wide forms,
but the reports are less legible. A value of “Yes” in the options report causes reports
to be printed in compressed mode while a value of “No” causes reports to be
printed in normal mode. This option should be selected only if you need to print 132
character per line reports on a standard 8.5 inch wide form.

Printed Reports Use 132 Character Line Formats (32.2)

Range:
Yes, No
Location in options report:
Line 32, Option 2
Default:
No (Printed reports use 80 character format.)
Change Activation:
Re-enter selective item report.

This Yes/No option determines whether reports are printed using 132-character line
formats or 80-character line formats. Three possible formats of the item record data
are available in 132-character mode while six possible formats are needed to show
the same information in 80-character mode. A value of “Yes” in the options report
causes reports to be printed with 132-characters per line while a value of “No”
causes reports to be printed with 80-characters per line.

Automatically Update Item Family with the Low 3 Link Digits

(32.3)
Range:
Yes, No
Location:
Line 32, Option 3
Default:
No (Item family code not updated)
Change Activation:
Re-enter selective item report.

This Yes/No option determines whether a promotions batch built with the PROMO
function updates the family code of the items being put on promotion as it updates
the link field. For coupon validation purposes, it is advantageous for all items which
link to an electronic coupon to contain a family code that matches the family code
of the coupon. This option automatically updates the family code with the low three

Chapter 6. Personalization of Preferred Customer Options and Messages 167

 digits of the four-digit link (promotion) number. A value of “Yes” in the options report
causes the PROMO function to always update a family code as it updates the item
link field. If family codes are not used in the validation of UPC 5 coupons (option
3.7), then the current family is replaced by the low 3 digits of the promotion code. If
family codes are used for validating scanned manufacturer coupons, then the
previous family is updated rather than the current family. When the PROMO
function is used to clear a promotion and this option is selected, then the
appropriate family code is set to 0 as well as the link field. A value of “No” in the
options report causes the PROMO function to update only the link value and leave
the family codes alone. Note that if the BATCH function is used to update the item
link field to put items on promotion, then the family code must be manually altered
through the BATCH function and the user gets to select which family code to alter
and its new value. It is the users responsibility to assure that the current family
code in the promotion coupon is set to the low three digits of the coupon item code
so that it matches the family of the linked items.

All Batches Are Created as DDM Operator Controlled Batches

(32.4)
Range:
Yes, No
Location:
Line 32, Option 4
Default:
No (User is prompted for type of batch to create.)
Change Activation:
Re-enter selective item report.

This Yes/No option limits the type of batches that a user can create with the BATCH
function to only DDM operator controlled batches. A value of “Yes” in the options
report causes the prompt for batch process to be bypassed as the batch is
automatically made a DDM batch. A value of “No” in the options report requires the
user to select for each item maintenance batch whether the batch should be
created as an ADDMI immediate, ADDMI operator, or DDM operator batch.

All Batches Are Created as ADDMI Batches (32.5)

Range:
Yes, No
Location:
Line 32, Option 5
Default:
No (User is prompted for type of batch to create.)
Change Activation:
Re-enter selective item report.

This Yes/No option limits the type of batches that a user can create with the BATCH
function to only ADDMI immediate or ADDMI operator controlled batches. A value of
“Yes” in the options report causes the prompt for batch process to present only the
two ADDMI selections and thus prohibits creation of direct DDM batches. Note that
ADDMI operator controlled batches become DDM operator controlled batches after
they are processed by the ADDMI program. A value of “No” in the options report
requires the user to select for each item maintenance batch whether the batch
should be created as an ADDMI immediate, ADDMI operator, or DDM operator
batch.

All Batches Are Created as ADDMI Immediate Updates (32.6)

Range:
Yes, No

168 Electronic Marketing PRPQ

 Location:
Line 32, Option 6
Default:
No (User is prompted fro type of batch to create.)
Change Activation:
Re-enter selective item report.

This Yes/No option limits the type of batches that a user can create with the BATCH
function to only ADDMI immediate batches. A value of “Yes” in the options report
causes the prompt for batch process to be bypassed as the batch is automatically
made an ADDMI immediate batch. A value of “No” in the options report requires the
user to select for each item maintenance batch whether the batch should be
created as an ADDMI immediate, ADDMI operator, or DDM operator batch.

Automatically Update Promotion Codes to Equal the Link Value

(32.7)
Range:
Yes, No
Location:
Line 32, Option 6
Default:
No (promotion code not automatically updated)
Change Activation:
Re-enter selective item report.

This Yes/No option determines whether a promotions batch built with the PROMO
function updates the promotion code of the items being put on promotion as it
updates the link field. This option is ignored unless option 20.2 is selected to
activate promotion code support. For coupon validation purposes, it is
advantageous for all items which link to an electronic coupon to contain a promotion
code that matches the promotion code of the coupon. This option automatically
updates the promotion code with the same value as the link (promotion) number. A
value of ″Yes″ in the options report causes the PROMO function to always update a
promotion code as it updates the item link field. When the PROMO function is used
to clear a promotion and this option is selected, then the promotion code is set to 0
as well as the link field. A value of ″No″ in the options report causes the PROMO
function to update only the link value and leave the promotion codes alone. Note
that if the BATCH function is used to update the item link field to put items on
promotion, then the promotion code must be manually altered through the BATCH
function and the user gets to select the new value of the promotion code. It is the
users responsibility to assure that the promotion code in the promotion coupon is
set to the value of the coupon item code so that it matches the promotion code of
the linked items.

Preferred Customer Messages File (EAMFBMSG)

Filename: EAMFBMSG I/O Session: 8
Organization: Sequential File Copies: 1 per controller
Record Length: 44 bytes Distribution class: Compound

The Preferred Customer Messages File is a sequential file that contains the unique
message text to be displayed or printed for preferred customers. Each message
contains up to 40 characters of text enclosed in quotes and followed by a carriage
return and line feed. Each message should contain the full 40 characters of text, but

Chapter 6. Personalization of Preferred Customer Options and Messages 169

 shorter messages will be processed correctly. A copy of the file is maintained on
every controller both for backup and to allow every terminal to access a local copy
of the file.

The message file can contain up to 200 of these 40-byte text messages which
make up 50 four-line logical messages. To decrease the impact to terminal memory
that the addition of 200 40-byte messages would cause, Terminal Sales stores
these messages in extended memory where they do not affect the limited amount
of data space.

Each logical message consists of three print lines preceded by a display line. Any
null lines or all blank lines are not printed or displayed. Each print line consists of
38 bytes of text followed by a comma and a numeric line feed indicator. Any print
line without a numeric line feed indicator is assumed to need a single line feed. All
display messages that begin or end with a “*” will sound a tone and require a clear
key. Any “*” that starts or ends a display message will be replaced by a blank. You
can modify the Preferred Customer Messages File with a text editor. Any of the
messages can contain variable data which is to be replaced by data pertaining to
the transaction or customer. The following variables can be defined:
@nnnn = customer name from activity file
@aaaa = account number
@tppp = transaction points (items + bonus) (or @tttt)
@tiii = transaction item points
@tbbb = transaction bonus points
@trrr = transaction redeemed points
@txxx = transaction transfer points
@pppp = net total points (prior net total + trans + xfer - redeemed)
@rrrr = net redeemed points
@gggg = grand total of points (total + xfer + trans)
@cggg = preferred coupon gross total (total + trans) (or @kkkk)
@cccc = preferred coupon total for transaction
@cnzz = preferred coupon total for transaction - blank line if total is zero
@cnv = blank line if no coupons, blank variable if coupon total
@cqqq = total quantity of coupons in the transaction
@cttt = total amount of coupons in the transaction
@dppp = date of last purchase (or @dddd)
@dxxx = date when transferred transaction occurred
@drrr = date of last redemption coupon entry
@ll = customer level
@lsss = status descriptor
@qx = quantity of transferred transactions
@oooo = operator’s full name from authorization file
@offf = operator’s first name from authorization file
@olll = operator’s last name from authorization file
@ffff = transaction discount amount
@fnzz = transaction discount amount - blank line if total is zero.
@fnv = blank line of no discount, blank variable if discount
@fppp = transaction discount percentage, blank line if no discount
@pmmm = net total period points (like @pppp but for period points)
@rmmm = net period redeemed points (like @rrrr but for period points)
@gmmm = grand total of period points (like @gggg but for period points)

To have the variables for the operator’s first or last name work correctly, the names
in the operator authorization file must be in one of the following six formats:

FIRSTNAME LASTNAME
FIRSTNAME I LASTNAME
FIRSTNAME I. LASTNAME
LASTNAME, FIRSTNAME
LASTNAME, FIRSTNAME I
LASTNAME, FIRSTNAME I.

170 Electronic Marketing PRPQ

 The length of the variable definition determines the amount of space used to
contain the variable data. If the customer name is shorter than the space allocated
to it, then the data after the name is moved closer to leave only a single blank
between the name and the following data. All substitutions except for the customer
name will be right justified into the defined field. The fields should be defined long
enough to contain the expected data. The data is allowed to overwrite the blank
preceding the “@” if it is that large, but larger data will be truncated from the right.

Of the 50 available messages, the first ten in the Preferred Customer Messages
File have defined meanings. The remaining 40 messages can be defined and used
as a store chooses. Electronic Marketing employs the first ten messages according
to the following definitions:

Message Zero: Normal points message

v Communicates with primary and local home store customers (who have an
activity record in a store’s activity file)
v Demonstrates that their customer ID number is accepted
v Tells point totals at the end of a transaction (if not modified not to give points
totals).

Message One: Points message for non-home store customers

v Communicates with visiting preferred customers
v Demonstrates that a customer ID is accepted
v Tells total points to be credited (transferred) to a customer’s home store point
total.

Message Two: Points message for new customers

v Communicates with new preferred customers
v Welcomes them to a store during their first visit.

Message Three: Prints message for customers not enrolled

v Communicates with customers not participating in the program
v Informs customers (not enrolled) about the preferred customer program
v Perhaps includes enticement to enroll in the program, such as a statement about
savings gained were they preferred customers.

Message Four: Personalization message for receipt

Contains a display message and a printed additional transaction trailer for preferred
customers only. A store defines how this additional transaction trailer prints in
relation to the Supermarket Application (SA) terminal option transaction trailer
through the Message Format option. This message augments or replaces the SA
terminal option transaction trailer, by printing in one of the following ways:
v Before the first Supermarket Application base transaction trailer line
v By replacing the first Supermarket Application base transaction trailer line, but
leaving the second intact
v Between the two Supermarket Application base trailer lines
v By replacing the second Supermarket Application base transaction trailer line, but
leaving the first intact
v After the second Supermarket Application trailer line
v Instead of the Supermarket Application trailer in total.

Chapter 6. Personalization of Preferred Customer Options and Messages 171

 Each customer’s activity record contains a flag indicating whether o not this
personalized message appears on their receipt. If the flag is off, this means that the
message should appear; if the flag is on, this means that the message should not
appear. In this latter case, the standard Supermarket Application base transaction
trailer will print independently and the system will bypass the feature display
message.

Message Five: Out of store transfer message

v Presents the out of store message
v Is executed only if a customer had points transferred into their account from
another store in the chain.

Message Six: Rain check message

Communicates with rain check customers, greeting them with the same
message used for primary and local home store customers.

Message Seven: Bonus points message

v Presents the bonus points message
v Is executed only if customers have any bonus points awarded to them during a
transaction.

Message Eight: Redeemed points message

v Presents the redeemed points message
v Is executed only if any redemptions are made during the transaction through
redemption coupons (defined on page 10).

Message Nine: Available targeted coupons header message

v Presents the targeted coupon message
v Prints on a customer’s receipt preceding a list of targeted coupons available to a
customer
v Prints for each preferred customer who has any targeted coupons in their activity
record if the option to print the available targeted coupons on a customer’s
receipt is set on.

When Messages Are Shown

For messages zero through two, the display portion of the message is shown at
customer identification, while the print portion is executed at the end of a sales
transaction. For message three, the display portion of the message is not shown
(because a nonparticipant does not present a customer ID), while the print portion
is executed at the end of a sales transaction. For messages four through nine, both
the display and print portions are executed at the end of the sales transaction.

Messages Associated with Customer Identification

Every time a customer presents their customer identification number at the point of
sale in a non-void checkout transaction, the system will display a user-personalized
message selected from messages zero through three and six (if six is used),
according to the customer’s type. New and rain check customers receive unique
messages (two and six, respectively) only in certain circumstances. For example,
primary home store customers would be greeted with the new or rain check
customer message on their first visit or the visit that they forget their customer
identification numbers. But they would receive a primary home store message on

172 Electronic Marketing PRPQ

 subsequent visits (assuming rain check customers have their customer IDs.) A store
must use messages zero through three. It can also use messages four through
nine, as well as the 40 other messages available.

Messages Associated with Other Customer Interests

Terminal Sales will print the following messages at the end of a sales transaction
(following the time/date line) in the following order, as appropriate:
1. 5 — Out of store transferred points
2. 7 — Bonus points awarded
3. 8 — Redeemed points during transaction
4. 0, 1, 2, 3, OR 6 — Customer identification print messages
5. X — Boundary-crossing message (user-defined)
6. Y — Activity record message (user-defined)
7. 9 — Targeted coupon message (if coupons are available and optioned to print)
8. 4 — Additional transaction trailer.

A customer who goes through checkout receives a minimum of one message (for a
nonparticipating customer) and can receive a maximum of eight messages, as
follows:
v Home store customer
v Incoming transfer points
v Bonus points
v Boundary crossing
v Coupon redemption at point of sale
v Message in activity file
v Targeted coupons available
v Transaction trailer allowed.

Data Entry Line

In addition to printing any customer message, Terminal Sales prints a Data Entry
Print line on a receipt at the time of customer identification because it receives all
customer IDs through Data Entry. This line contains a customer’s name and
identification number. If a customer’s name is not available, as is the case for
nonparticipating customers, a default name is substituted. Although you cannot
define the format of this data entry line through personalization, you can change it
through Supermarket Application standard user exits. You can also determine,
through base Supermarket Application options, whether the data line prints or not.

How to Activate Additional Messages

Additional messages in the file can be activated based on customer activity records
or on point boundary conditions. These messages are pointed to by message
numbers in the range of 10 to 49 which are user defined in the options and/or
activity files.

How to Make Changes to the Messages File

To make changes to the preferred customer message file, you must go into
Command Mode from the master menu. Change directories to ADX_IPGM and type
DREDIX [Link] to display the current message file. Make your changes
but stay within the quotes and if you leave the line blank, always leave two
quotation marks at the beginning of the line. After the changes are complete, hold
the control key down and press K and S (save Changes), then hold the control key
down and press K and Q (quit). Exit Command Mode by typing EXIT and you will
return to the Master Menu.

Chapter 6. Personalization of Preferred Customer Options and Messages 173

 A register must go through “LOADING OPTIONS” to make changes in the
messages file be loaded and thus become active. This can be accomplished most
easily by signing all registers off after personalization has been used to enter a
store or terminal option value (the value need not change).

Default Preferred Customer Messages File

The following table is the default messages file.
Table 1. Preferred Customer Messages File
Message Record Description Length
0 1 “ GOOD CUSTOMER @nnnnnnnnnnnnnnnnnnnnnn” 40

2 “THIS ORDER ADDED @ccc OF COUPONS AND ,1” 40

3 “@ttttt VALUE POINTS TO BRING YOUR NEW ,1” 40

4 “TOTAL TO @kkkk SAVED AND @ppppp POINTS,3” 40

1 5 “WELCOME TO OUR STORE @nnnnnnnnnnnnnnnnnn” 40

6 “LOOK FOR @ttttt POINTS TO BE ,1” 40

7 “TRANSFERRED TO YOUR HOME STORE ,1” 40

8 “” 40

2 9 “WELCOME NEW MEMBER @aaaaaaaaaaaa ” 40

10 “PRESENT YOUR CARD WITH EVERY ORDER ” 40

11 “AND RECEIVE PROMOTIONAL DISCOUNTS ” 40

12 “**** YOU SAVED @cnz ON THIS ORDER **** ” 40

3 13 “ VALUED CUSTOMER ” 40

14 “ ASK THE MANAGER HOW OUR NEW FREQUENT ,1” 40

15 “ BUYER PROGRAM CAN SAVE YOU MONEY ,1” 40

16 “ YOU COULD HAVE SAVED @ccnz TODAY ,3” 40

4 17 “ WE RECOGNIZE CUSTOMER LOYALTY ” 40

18 “ WE APPRECIATE YOUR LOYAL PATRONAGE ,1” 40

19 “ @nnnnnnnnnnnnnnnnnnnnnnnnnnn ,6” 40

20 “” 40

5 21 “* TRANSFERRED IN @txxxx POINTS ” 40

22 “ @txxxx POINTS FROM @qx TRANSACTIONS ,1” 40

23 “ THROUGH @dxxxxxx TRANSFERRED IN ,2” 40

24 “ ,1” 40

6 25 “” 40

26 “TO RECEIVE THE @ttttt POINTS FOR THIS ,1” 40

27 “ORDER, YOU MUST PRESENT THIS RECEIPT ,1” 40

28 “TO THE MANAGER WITH YOUR ID CARD ,1” 40

174 Electronic Marketing PRPQ

Table 1. Preferred Customer Messages File (continued)
Message Record Description Length
7 29 “” 40

30 “@tiiii ITEM POINTS, @tbbb BONUS POINTS,1” 40

31 “” 40

32 “” 40

8 33 “” 40

34 “@trrrr REDEEMED, @rrrrr TOTAL REDEEMED,1” 40

35 “” 40

36 “” 40

9 37 “” 40

38 “THE FOLLOWING COUPONS ARE STILL ,1” 40

39 “AVAILABLE TO YOU UNTIL NEXT MONTH ,2” 40

40 “” 40

10 41 “ BONUS AWARD ” 40

42 “PRESENT THIS TO THE MANAGER TO RECEIVE,1” 40

43 “A COUPON FOR A DOZEN FREE EGGS AS A ,1” 40

44 “REWARD FOR ANOTHER $500.00 PURCHASED. ,2” 40

11 45 “ BONUS AWARD ” 40

46 “PRESENT THIS TO THE MANAGER TO RECEIVE,1” 40

47 “A COUPON FOR 1/2 DOZEN FREE EGGS AS A ,1” 40

48 “REWARD FOR ANOTHER $100.00 PURCHASED. ,2” 40

12 49 “ ” 40

50 “YOU HAVE BEEN AWARDED $100.00 OF ,1” 40

51 “BONUS POINTS FOR THE FIRST USAGE OF ,1” 40

52 “YOUR PREFERRED CUSTOMER CARD ,2” 40

13 53 “* NOTE MESSAGE ON CUSTOMER RECEIPT ” 40

54 “PLEASE SEE THE MANAGER TO UPDATE YOUR ,1” 40

55 “ENROLLMENT DATA. OUR ADDRESS FOR YOU ,1” 40

56 “IS NO LONGER CURRENT. ,2” 40

14 57 “DISPLAY MESSAGE 14 ” 40

58 “PRINT MESSAGE 14 - LINE 1 ,1” 40

59 “ - LINE 2 ,1” 40

60 “ - LINE 3 ,1” 40

Chapter 6. Personalization of Preferred Customer Options and Messages 175

Table 1. Preferred Customer Messages File (continued)
Message Record Description Length
15 61 “DISPLAY MESSAGE 15 ” 40

62 “PRINT MESSAGE 15 - LINE 1 ,1” 40

63 “ - LINE 2 ,1” 40

64 “ - LINE 3 ,1” 40

16 65 “DISPLAY MESSAGE 16 ” 40

66 “PRINT MESSAGE 16 - LINE 1 ,1” 40

67 “ - LINE 2 ,1” 40

68 “ - LINE 3 ,1” 40

17 69 “DISPLAY MESSAGE 17 ” 40

70 “PRINT MESSAGE 17 - LINE 1 ,1” 40

71 “ - LINE 2 ,1” 40

72 “ - LINE 3 ,1” 40

18 73 “DISPLAY MESSAGE 18 ” 40

74 “PRINT MESSAGE 18 - LINE 1 ,1” 40

75 “ - LINE 2 ,1” 40

76 “ - LINE 3 ,1” 40

176 Electronic Marketing PRPQ

Chapter 7. Operations
This chapter provides instructions on how to perform many in-store procedures of
Electronic Marketing, including how to process preferred customer identification
numbers, various types of coupons, and points. Descriptions of many procedures
include screens that show steps for an operator to follow.

How to Enter a Customer ID Number

The application supports three methods of entering a customer ID number. An
enterprise may use the Category Number for Customer IDs option, provided by the
package, to specify a UPC/EAN category number to uniquely identify customer ID
numbers. (See “Category Number to Uniquely Identify Customer Numbers” on
page 101.) If an enterprise does not use this option, an operator enters a customer
ID number by keying the following sequence before keying or scanning the
customer ID number.

NO SALE - - DATA ENTRY

This key sequence indicates to Terminal Sales that the number associated with it
should be processed as a customer ID number.

If an enterprise uses a category number to uniquely identify customer numbers (see

“Category Number to Uniquely Identify Customer Numbers” on page 101), and an
operator enters a customer number that begins with the specified category number
for customer IDs, Terminal Sales processes the entered number as a customer ID
by emulating the NO SALE -- DATA ENTRY key sequence. The category number
option allows a store’s operators to directly scan or key, a customer ID without
entering the NO SALE -- DATA ENTRY keyed sequence. But the keyed sequence is
still available for use. A third method of customer identification involves the use of a
unique CUSTOMER NUMBER key. A unique CUSTOMER NUMBER key can
(optionally) be defined to identify keyed, scanned or magnetic stripe data as input of
a customer number. When the CUSTOMER NUMBER key or the DATA ENTRY,
NOSALE, and ENTER keys are used with no input data, the system will prompt for
entry of a customer number. At this prompt, the customer number can be keyed,
scanned, or read with a magnetic stripe reader. An expiration date can optionally be
keyed with the keyed entry of a customer number.

The Terminal Sales program accepts entry of a customer ID number at any point
during the item entry or tendering phases of a checkout transaction. But, the point
at which the ID is entered can affect the outcome of the transaction. It is suggested
that the number be entered immediately after paper coupons are entered and
before a tender is entered. This prevents conflict between paper and electronic
coupons and ensures that the minimum purchase requirement for electronic
coupons is compared to the final transaction balance. System performance for
targeted coupons is improved if a customer number is entered after completion of
sales. Customers can consider their customer numbers as entitlement to coupons
and give it to an operator when presenting coupons.

If a customer ID number is entered at the start of a transaction, all promotional

coupons print lines immediately follow the items to which they apply on the
customer receipt. If a customer ID number is entered at the tender time in a
transaction that contains promotional items, the promotional item print lines follow
the customer identification number on the receipt and can be matched to the
appropriate items through the coupon descriptor.
© Copyright IBM Corp. 1991 2000 177
 If a customer ID number is entered at the start of a transaction and a preferred
electronic coupon is rejected at the time a promoted item is sold, the preferred
electronic coupon is automatically retried at total time. This function assures that the
order in which a preferred electronic coupon is given in relation to when a customer
identification number is entered does not cause a preferred electronic coupon to be
rejected.

If a customer number is entered before any sales, a terminal may switch

automatically to the “Secured” state if it has timed out between the last transaction
and entry of this customer ID number. If this occurs, the terminal discards and an
operator must reenter it after the terminal is taken out of the “Secured” state. This
process prevents a preferred customer ID number entered between transactions
from applying to a non-preferred customer who is processed at checkout later. If a
customer ID number is entered as the first item of a sale without entering any other
items, the operator may manually discard this number in one of two ways:
v Key in a sign off sequence:

SIGN ON/OFF - - SIGN ON/OFF

to sign off the terminal

v Key in a nested sign on sequence:

<0> - - SIGN ON/OFF

to begin a new customer checkout transaction.

A customer ID number that has been manually discarded also requires reentry to be
processed.

Multiple customer numbers may be entered during the transaction. The last valid
customer number entered receives the benefits of the transaction. A customer
number can be entered at any point in the transaction however, a total is required
prior to the entry of a customer number if sales have occurred since the earlier
entry of a valid customer number in the same transaction.

Establishing a New Customer Identification Number

If an entered customer identification number is not found in a store’s activity file,
and either no store number is imbedded in the customer ID number or the
imbedded store number matches this store, this is a new customer. The system
prompts the operator to verify a new customer number to assure that it was not
simply incorrectly entered. After this operator override, the system automatically
adds this new customer identification number to the store’s activity file and
processes it. A user-definable option allows an enterprise to require a manager’s
override instead of an operator’s override for the system to accept a new customer
number.

When to Enter Customer ID Number with Targeted Coupons

Like normal preferred customer coupons, targeted coupons usually appear after the
matching item(s) if a customer ID number is entered at the start of the transaction,
or they appear after customer identification if the customer ID number is entered
after sale of the matching item(s). An exception to this occurs if a customer ID
number is entered before the sale of the matching item(s) and all the condition for

178 Electronic Marketing PRPQ

 accepting a targeted coupon are not met at the point of sale of the matching
item(s). This circumstance may cause the following results:
v The targeted coupon may appear after a total is taken if the minimum purchase
is met by total time.
v The operator may be required to take a manual total before tendering, even
though the results of an automatic total are being displayed because the system
has timed out.

How to Enter Multiple Customer ID Numbers per Transaction

Terminal Sales will accept more than one customer ID number entered during one
checkout transaction. Each valid number is saved in the logged data and any valid
number activates preferred customer discounts, but only the last valid number is
used for activity processing and is given credit for the sale. If an operator enters an
invalid customer ID number after having entered a valid number, Terminal Sales
uses the last valid number for the sale.

Procedures for Preferred Customer Identification

When a customer number is entered at the point of sale, the display will greet a
preferred customers with a message each time their customer number is entered.
Special messages can be displayed at the end of the transaction and printed on the
customer receipt.

The following message is displayed:

GOOD CUSTOMER
MISS LAURA SHOPPER

The following message is displayed when a new customer has not been enrolled:

B605 CHECK CUSTOMER

NUMBER 90001000001

For a new customer with a card but not enrolled, do the following:
v Press CLEAR
v Press OVERRIDE, then ENTER.
The new customer number is now on file in the activity file. When information is
added later from the enrollment application, the customer’s name will be added to
their activity record.

The following message is displayed when preferred customers use their card for the
first time:

WELCOME NEW MEMBER

90001000001

Chapter 7. Operations 179

Enrolled Preferred Customer Receipt

┌────────────────────────────────────────┐
│ │
│ THANK YOU FOR SHOPPING FAMILY MARKET │
│ NEIGHBORHOOD STORE #001 ANYTOWN, USA │
│ │
│ CIGARETTES NP 1.59 │
│ BUBBLE GUM 1.59 │
│ DETERGENT PC 2.19 │
│ BLEACH .99 │
│ GREEN BEANS PC .59 │
│ GREEN BEANS PC .59 │
│ LETTUCE .99 │
│ │
│ MISS LAURA SHOPPER 90001000001 │
│ │
│ SC DETERGENT 1.00 │
│ BO 50 POINTS .50 │
│ │
│ TAX .38 BAL 7.91 │
│ CASH 7.91 │
│ 7/08/91 13:55 0001 01 0039 1 │
│ │
│ 6.94 ITEM POINTS, .50 BONUS POINTS │
│ THIS ORDER ADDED 1.00 COUPONS AND │
│ 7.44 VALUE POINTS TO BRING YOUR NEW │
│ TOTAL TO 16.00 SAVED AND 143.27 PTS │
│ │
│ **THANK YOU - COME AGAIN** │
│ WE APPRECIATE YOUR LOYAL PATRONAGE │
│ MISS LAURA SHOPPER │
│ │
└────────────────────────────────────────┘

Figure 8. Preferred Customer Receipt

This receipt shows the SC (store coupon) for the detergent and the BO (bonus
points) coupons for the green beans. If you are redeeming points instead of
awarding, the descriptor (RD) shows that points are redeemed. The cigarettes do
not get points in the store and the descriptor is NP (no points) to the left of the
price.

Customers who are enrolled in the Preferred Customer Program and have their
cards scanned at checkout see their name on the display. They see special
messages on their receipt. Point totals and savings from Preferred Customer
coupons are displayed on the bottom of the customer receipt.

Regular Customer Receipt

The receipt for regular customers contains a message prompting them to enroll and
a statement of savings they could have made through Preferred Customer coupons.

180 Electronic Marketing PRPQ

 ┌────────────────────────────────────────┐
│ │
│ THANK YOU FOR SHOPPING FAMILY MARKET │
│ NEIGHBORHOOD STORE #001 ANYTOWN, US │
│ │
│ │
│ BUBBLE GUM 1.59 │
│ DETERGENT PC 2.19 │
│ BLEACH .99 │
│ GREEN BEANS PC .59 │
│ GREEN BEANS PC .59 │
│ LETTUCE .99 │
│ │
│ TAX .35 7.29 │
│ CASH 7.29 │
│ 7/08/91 13:55 0001 01 0040 1 │
│ │
│ │
│ ASK THE MGR ABOUT OUR PREFERRED │
│ CUSTOMER PROGRAM. YOU COULD │
│ HAVE SAVED 1.00 TODAY │
│ │
│ │
│ │
│ │
│ ** THANK YOU - COME AGAIN ** │
│ │
│ │
└────────────────────────────────────────┘

Figure 9. Regular Customer Receipt

This order had potential preferred customer coupons on the detergent and green
beans. The “PC” to the left of the price on the customer receipt shows that these
items are linked to an electronic coupon. A preferred customer would have received
these coupons.

In-Store Enrollment Procedure Screens

The optional Preferred Customer Enrollment procedure provides a method of
changing, adding, deleting, or displaying a preferred customer’s profile data in the
store. It can also be used to perform redemptions or adjustments of points or to
enter rain checks. The following eight screens appear as the procedure is used.
The initial screen allows you to select one of the seven functions provided by the
procedure.

The menu screen is the same for all users, but option 10.8 causes all other screens
to vary based on how it is set.

If the option (10.8) “Run the enrollment procedure without an in-store enrollment
file” is selected, alternate screens are used that do not show enrollment data.

Chapter 7. Operations 181

 CSO1S000 SYSTEM MAIN MENU

SELECT ONE OF THE FOLLOWING:

1 CHECKOUT MAIN MENU

2 Secondary Applications
3 File Utilities
4 Installation and Update Aids
5 Problem Analysis Data Collection
6 Problem Analysis Reports
7 Command Mode

Type your selection number, then press ENTER. 2

F1HELP F2 F3 F4 F5 F6 F7 F8 F9Signoff

Figure 10. System Main Menu

From the SYSTEM MAIN MENU, type 2 to select Secondary Applications, then
press ENTER.

CSO1S002 Secondary Applications

Select one of the following:

1 Preferred Customer Enrollment

2
3
4
5

Type your selection number, then press ENTER. 1

F1HELP F2 F3 F4 F5 F6 F7 F8 F9Signoff

Figure 11. Secondary Applications Menu - Preferred Customer Enrollment

From Secondary Applications, type 1 to select Preferred Customer Enrollment, then

press ENTER. (Your screen may differ if you have additional secondary applications
defined).

The Preferred Customer Enrollment Program Main Menu will be displayed as

shown on the next page.

182 Electronic Marketing PRPQ

Preferred Customer Enrollment
Purpose: To enroll a customer in the Preferred Customer Program and assign a
customer number that will provide the benefits of the program.

EAMEN01S PREFERRED CUSTOMER PROGRAM Date/Time field

MAIN MENU VERSION field

Select the function you wish to perform:

1. Change a customer record

2. Add a customer record
3. Erase a customer record
4. Display a customer record
5. Redeem Award
6. Adjustments
7. Enter Rain check

Type your selection 2

Type the customer number XXXXXXXXXXX

When complete, press ENTER.

F1 HELP F2 F3 END F4 F5 F6 F7 F8 F9 F10

Figure 12. Preferred Customer Program Main Menu -- Option 2 -- add record

Keying Sequence:
1. From the Preferred Customer Program Main Menu, type 2 to select “Add a
customer record”.
2. Type the 11 digit customer number from the enrollment application or Preferred
Customer Card. (The example assumes an 11 digit number.)
3. When complete, press ENTER. The “Add a customer record” screen appears
as shown on the next page.

Chapter 7. Operations 183

 EAMEN02S PREFERRED CUSTOMER PROGRAM Date/Time field
ADD CUSTOMER VERSION field

Card Number:

Last Name ....... First Name ..

Address Line 1 ..
Address Line 2 ..
City ............ State . Zip . -

Birthdate (MM/DD/YY) . / / Gender (M/F) .

Home Phone # ........ ( ) - SS # .........
Business Phone # .... ( ) -
Reference Number .... Reference is Family .
Driver License # ....

DEMOGRAPHIC INFORMATION

Size . Children Ages . Annual Income .

Authorization . CUST1 CUST2 CUST3 CUST4 CUST5 CUST6
When complete, press ENTER.
Press END to cancel.

F1 HELP F2 F3 END F4 F5 F6 F7 F8 F9 F10

Figure 13. Add Customer Record Screen -- the highlighted fields are required.

4. Type the customer’s last name and press TAB.

5. Type the customer’s first name, press TAB.
6. Type the street address, press TAB.
7. An additional address can be added on the second address line. Type the
information if available, then press TAB.
8. Type city, press TAB.
9. Type state of residence.
10. Type zip code.

Note: At this point you have filled out all the required fields and you can press
ENTER to create a new customer record and exit, or press TAB to continue.
The following information is optional. At any point, you can press ENTER to
end the input session. You can tab through any field you choose to skip.
11. Type zip code extension.
12. Type birth date (mm/dd/yy).
13. Type home telephone number starting with area code.
14. Type in business telephone number starting with area code.
15. Type M or F (male or female).
16. Type social security number (9 digit).
17. Type in reference number, press TAB.

Note: The reference number is a one digit number which belongs to the head of
the household for a group of family members or to an organization to whom
the customer is donating their points.
18. Type Y or N (yes or no) if the customer is a family member of the referenced
account.
19. Type driver’s license number (25 digit), press TAB.
20. Type number of family members (two digit), press TAB.
21. Type age of each child (if single digit, enter age and tab to next field).

184 Electronic Marketing PRPQ

 22. Type single digit for annual income (such as, 50,000 = 5), press TAB.
23. Authorization - - This field can be used to indicate that the customers do not
want their names included on mailing lists that are sold or given to other
organizations. Your programming could check this field in the record to
determine whether to include the name, press TAB
24. Type in your optional demographic numbers if you have defined them in option
11.8, “COUNT OF CUSTOMER DEFINED DEMOGRAPHIC FIELDS”.

Note: If you need to make a correction or missed a field, tab through to the
appropriate field.
25. Press ENTER to complete the enrollment process or press F3 to cancel the
enrollment and exit the screen.
26. When the enrollment is complete, the Preferred Customer Program Main Menu
will be displayed.
The following information is used when the option to select no enrollment file is
used. This information is located only in the Preferred Customer Activity file.

EAMENA2S PREFERRED CUSTOMER PROGRAM Date/Time field

ADD CUSTOMER VERSION field

Card Number:

Last Name ....... First Name ..

Reference Number ....

Reference is Family .

When complete, press ENTER.

Press END to cancel.

F1 HELP F2 F3 END F4 F5 F6 F7 F8 F9 F10

Figure 14. Alternate Add Customer Record Screen

Changing a Customer Record

Purpose: To update a customers existing record with changes or additional
information.

Chapter 7. Operations 185

 EAMEN01S PREFERRED CUSTOMER PROGRAM Date/Time field
MAIN MENU VERSION field

Select the function you wish to perform:

1. Change a customer record

2. Add a customer record
3. Erase a customer record
4. Display a customer record
5. Redeem Award
6. Adjustments
7. Enter Rain check

Type your selection 1

Type the customer number XXXXXXXXXXX

When complete, press ENTER.

F1 HELP F2 F3 END F4 F5 F6 F7 F8 F9 F10

Figure 15. Preferred Customer Program Main Menu -- Option 1 -- change record

Note: The highlighted fields on figure 7-6 are the required fields.

Keying Sequence:
1. From the Preferred Customer Program Main Menu type 1 to select “Change a
customer record.”
2. Type the customer number to display the record to be changed, press ENTER.

EAMEN03S PREFERRED CUSTOMER PROGRAM Date/Time field

CHANGE CUSTOMER VERSION field

Card Number: Last Change / /

Last Name ....... First Name ..

Address Line 1 ..
Address Line 2 ..
City ............ State . Zip . -

Birthdate (MM/DD/YY) . / / Gender (M/F) .

Home Phone # ........ ( ) - SS # .........
Business Phone # .... ( ) -
Reference Number .... Reference is Family .
Driver License # ....

DEMOGRAPHIC INFORMATION

Size . Children Ages . Annual Income .

Authorization . CUST1 CUST2 CUST3 CUST4 CUST5 CUST6
When complete, press ENTER.
Press END to cancel.

F1 HELP F2 F3 END F4 F5 F6 F7 F8 F9 F10

Figure 16. Change Customer Record Screen

3. Starting at the last name, tab to the field that will be changed or added.

186 Electronic Marketing PRPQ

 4. Type the changes, then press ENTER when complete.
5. When complete, the Preferred Customer Program Main Menu will be displayed.

The following information is used when the option to select no enrollment file is
used. This information is located only in the Preferred Customer Activity file.

EAMENA3S PREFERRED CUSTOMER PROGRAM Date/Time field

CHANGE CUSTOMER VERSION field

Card Number: Last Change / /

Last Name ....... First Name ..

Reference Number ....
Reference is Family .

When complete, press ENTER.

Press END to cancel.

F1 HELP F2 F3 END F4 F5 F6 F7 F8 F9 F10

Figure 17. Alternate Change Customer Record Screen

Erase a Customer Record

Purpose: To remove a customer number from the Preferred Customer Program
Enrollment File or to erase an incorrect number.

Chapter 7. Operations 187

 EAMEN01S PREFERRED CUSTOMER PROGRAM Date/Time field
MAIN MENU VERSION field

Select the function you wish to perform:

1. Change a customer record

2. Add a customer record
3. Erase a customer record
4. Display a customer record
5. Redeem Award
6. Adjustments
7. Enter Rain check

Type your selection 3

Type the customer number XXXXXXXXXXX

When complete, press ENTER.

F1 HELP F2 F3 END F4 F5 F6 F7 F8 F9 F10

Figure 18. Preferred Customer Program Main Menu -- Option 3 -- erase record

Keying Sequence:
1. From the Preferred Customer Program Main Menu, type 3 to select “Erase a
customer record.”
2. Type the customer number for the record to be erased, then press ENTER.

EAMEN04S PREFERRED CUSTOMER PROGRAM Date/Time field

ERASE CUSTOMER VERSION field

Card Number:

Last Name ....... First Name ..

Address Line 1 ..
Address Line 2 ..
City ............ State . Zip -

Birthdate (MM/DD/YY) . / / Gender (M/F) .

Home Phone # ........ ( ) - SS # .........
Business Phone # .... ( ) -

Date Form Number Period

Points Earned: / /
Points Adjusted: / /
Points Redeemed: / /
Total points available:

Do you want to erase this customer (Y/N)? N

To process, press ENTER.

F1 HELP F2 F3 END F4 F5 F6 F7 F8 F9 F10

Figure 19. Erase Customer Record Screen

3. The customer’ record will be displayed with the following message:

Do you want to erase this customer (Y/N)?
4. Type Y or N (yes or no), press ENTER to process.

188 Electronic Marketing PRPQ

 5. When complete, the Preferred Customer Program Main Menu will be displayed.

The following information is used when the option to select no enrollment file is
used. This information is located only in the Preferred Customer Activity file.

EAMENA4S PREFERRED CUSTOMER PROGRAM Date/Time field

ERASE CUSTOMER VERSION field

Card Number:

Last Name ....... First Name ..

Date
Points Earned: / /
Points Redeemed: / /
Total points available:

Do you want to erase this customer (Y/N)? N

To process, press ENTER.

F1 HELP F2 F3 END F4 F5 F6 F7 F8 F9 F10

Figure 20. Alternate Erase Customer Record Screen

Displaying a Customer Record

Purpose: To view a customer record to verify information and/or points.

EAMEN01S PREFERRED CUSTOMER PROGRAM Date/Time field

MAIN MENU VERSION field

Select the function you wish to perform:

1. Change a customer record

2. Add a customer record
3. Erase a customer record
4. Display a customer record
5. Redeem Award
6. Adjustments
7. Enter Rain check

Type your selection 4

Type the customer number XXXXXXXXXXX

When complete, press ENTER.

F1 HELP F2 F3 END F4 F5 F6 F7 F8 F9 F10

Figure 21. Preferred Customer Program Main Menu -- Option 4 -- display record

Keying Sequence:

Chapter 7. Operations 189

 1. From the Preferred Customer Program Main Menu, type 4 to select “Display a
customer record.”
2. Type the customer number for the record to be displayed, then press ENTER.

EAMEN05S PREFERRED CUSTOMER PROGRAM Date/Time field

DISPLAY CUSTOMER VERSION field

Card Number:

Last Name ....... First Name ..

Address Line 1 ..
Address Line 2 ..
City ............ State . Zip -

Birthdate (MM/DD/YY) . / / Gender (M/F) .

Home Phone # ........ ( ) - SS # .........
Business Phone # .... ( ) -

Date Form Number Period

Points Earned: / /
Points Adjusted: / /
Points Redeemed: / /
Total points available:

When finished viewing, press ENTER.

F1 HELP F2 F3 END F4 F5 F6 F7 F8 F9 F10

Figure 22. Display Customer Record Screen

3. The customer record is displayed with the following message:

When finished viewing, press ENTER.
4. Press ENTER when completed and return to the Preferred Customer Program
Main Menu.

The following information is used when the option to select no enrollment file is
used. This information is located only in the Preferred Customer Activity file.

190 Electronic Marketing PRPQ

 EAMENA5S PREFERRED CUSTOMER PROGRAM Date/Time field
DISPLAY CUSTOMER VERSION field

Card Number:

Last Name ....... First Name ..

Date
Points Earned: / /
Points Redeemed: / /
Total points available:

When finished viewing, press ENTER.

F1 HELP F2 F3 END F4 F5 F6 F7 F8 F9 F10

Figure 23. Alternate Display Customer Record Screen

Redeeming an Award
Purpose: To redeem an award from the office for a gift or other special award.

EAMEN01S PREFERRED CUSTOMER PROGRAM Date/Time field

MAIN MENU VERSION field

Select the function you wish to perform:

1. Change a customer record

2. Add a customer record
3. Erase a customer record
4. Display a customer record
5. Redeem Award
6. Adjustments
7. Enter Rain check

Type your selection 5

Type the customer number XXXXXXXXXXX

When complete, press ENTER.

F1 HELP F2 F3 END F4 F5 F6 F7 F8 F9 F10

Figure 24. Preferred Customer Program Main Menu -- Option 5 -- Redeem Award

Keying Sequence:
1. From the Preferred Customer Program Main Menu, type 5 to select “Redeem
award”.

Chapter 7. Operations 191

 2. Type the customer number to display the record entitled to an award, then press
enter.

EAMEN06S PREFERRED CUSTOMER PROGRAM Date/Time field

REDEMPTION VERSION field

Card Number:

Last Name ....... First Name ..

Address Line 1 ..
Address Line 2 ..
City ............ State . Zip -

Birthdate (MM/DD/YY) . / / Gender (M/F) .

Home Phone # ........ ( ) - SS # .........
Business Phone # .... ( ) -

Date Form Number Employee #

Points Earned: / /
Points Adjusted: / /
Points Redeemed: / /
Total points available:
Points to be redeemed:

When complete, press ENTER.

F1 HELP F2 F3 END F4 F5 F6 F7 F8 F9 F10

Figure 25. Redemption of Point Award Screen

3. Type in the value of points to be redeemed, press TAB.

4. Type in the form number for which you are posting the redeemed points, press
TAB.

Note: This is an optional field for accountability if a form with a form number is
used the record the redemption.
5. Type in your employee number if these numbers are for a supervisory function
at your store.
6. When complete, press ENTER.

The following information is used when the option to select no enrollment file is
used. This information is located only in the Preferred Customer Activity file.

192 Electronic Marketing PRPQ

 EAMENA6S PREFERRED CUSTOMER PROGRAM Date/Time field
REDEMPTION VERSION field

Card Number:

Last Name ....... First Name ..

Date Form Number Employee #

Points Earned: / /
Points Redeemed: / /
Total points available:
Points to be redeemed:

When complete, press ENTER.

F1 HELP F2 F3 END F4 F5 F6 F7 F8 F9 F10

Figure 26. Alternate Redemption of Point Award Screen

Adjusting a Customer Record

Purpose: For an authorized person to adjust points for an existing record.

EAMEN01S PREFERRED CUSTOMER PROGRAM Date/Time field

MAIN MENU VERSION field

Select the function you wish to perform:

1. Change a customer record

2. Add a customer record
3. Erase a customer record
4. Display a customer record
5. Redeem Award
6. Adjustments
7. Enter Rain check

Type your selection 6

Type the customer number XXXXXXXXXXX

When complete, press ENTER.

F1 HELP F2 F3 END F4 F5 F6 F7 F8 F9 F10

Figure 27. Preferred Customer Program Main Menu -- Option 6 -- Adjustments

Keying Sequence:
1. From the Preferred Customer Program Main Menu, type 6 to select
“Adjustments”.
2. Type the customer number to adjust the points, then press enter.

Chapter 7. Operations 193

 EAMEN07S PREFERRED CUSTOMER PROGRAM Date/Time field
ADJUSTMENTS VERSION field

Card Number:

Last Name ....... First Name ..

Address Line 1 ..
Address Line 2 ..
City ............ State . Zip -

Birthdate (MM/DD/YY) . / / Gender (M/F) .

Home Phone # ........ ( ) - SS # .........
Business Phone # .... ( ) -

Date Form Number Employee #

Points Earned: / /
Points Adjusted: / /
Points Redeemed: / /
Total points available:
Points to be adjusted:

When complete, press ENTER.

F1 HELP F2 F3 END F4 F5 F6 F7 F8 F9 F10

Figure 28. Adjustment of Point Award Screen

3. Type the point adjustment amount (+ or −), press TAB.

4. Type the office form number if you are using one for accountability, then press
TAB.
5. Type in employee number if employee numbers are used for supervisory
functions.
6. When complete, press ENTER.

The following information is used when the option to select no enrollment file is
used. This information is located only in the Preferred Customer Activity file.

194 Electronic Marketing PRPQ

 EAMENA7S PREFERRED CUSTOMER PROGRAM Date/Time field
ADJUSTMENTS VERSION field

Card Number:

Last Name ....... First Name ..

Date Form Number Employee #

Points Earned: / /
Points Redeemed: / /
Total points available:
Points to be adjusted:

When complete, press ENTER.

F1 HELP F2 F3 END F4 F5 F6 F7 F8 F9 F10

Figure 29. Alternate Adjustment of Point Award Screen

Entering a Rain check

Purpose: To adjust points for a customer who shopped previously but forgot her
Preferred Customer Card. Customers must have a rain check receipt provided by
the previous operator to identify rain check points to which they are entitled.

EAMEN01S PREFERRED CUSTOMER PROGRAM Date/Time field

MAIN MENU VERSION field

Select the function you wish to perform:

1. Change a customer record

2. Add a customer record
3. Erase a customer record
4. Display a customer record
5. Redeem Award
6. Adjustments
7. Enter Rain check

Type your selection 7

Type the customer number XXXXXXXXXXX

When complete, press ENTER.

F1 HELP F2 F3 END F4 F5 F6 F7 F8 F9 F10

Figure 30. Preferred Customer Program Main Menu -- Option 7 -- Enter Rain check

Keying Sequence:

Chapter 7. Operations 195

 1. From the Preferred Customer Program Main Menu, type 7 to select “Enter
Rain check”.
2. Type the customer number to display the record entitled to the rain check
points, then press ENTER.

EAMEN08S PREFERRED CUSTOMER PROGRAM Date/Time field

RAIN CHECKS VERSION field

Card Number:

Last Name ....... First Name ..

Address Line 1 ..
Address Line 2 ..
City ............ State . Zip -

Birthdate (MM/DD/YY) . / / Gender (M/F) .

Home Phone # ........ ( ) - SS # .........
Business Phone # .... ( ) -

Last Rain check: / / Total points available:

Rain check Points: Form # Employee #

Receipt Tape Identification Date Time Store Lane Order Checker

/ / :

When complete, press ENTER.

F1 HELP F2 F3 END F4 F5 F6 F7 F8 F9 F10

Figure 31. Rain check Screen

3. Type the points to be credited from the rain check receipt; press TAB.
4. Type the office form number for posting the rain check adjustments, if one is
being used for accountability; press TAB.
5. Type the employee number if employee numbers are used for supervisory
functions; press TAB.

Note: The following information is taken from the customer’s register receipt.
6. Type date (mm/dd/yy), press TAB.
7. Type time (military: 1pm = 13:00), press TAB.
8. Type store number, press TAB.
9. Type lane number, press TAB.
10. Type transaction number, press TAB.
11. Type checker number, press TAB.
12. When complete, press ENTER.

The following information is used when the option to select no enrollment file is
used. This information is located only in the Preferred Customer Activity file.

196 Electronic Marketing PRPQ

 EAMENA8S PREFERRED CUSTOMER PROGRAM Date/Time field
RAIN CHECKS VERSION field

Card Number:

Last Name ....... First Name ..

Total points available:

Rain check Points: Form # Employee #

Receipt Tape Identification Date Time Store Lane Order Checker

/ / :

When complete, press ENTER.

F1 HELP F2 F3 END F4 F5 F6 F7 F8 F9 F10

Figure 32. Alternate Rain check Screen

Sample Coupons
The following section presents examples of how several different types of coupon
item records can be established.

Bonus Point Coupons

An example of a bonus point coupon follows:

COUPON #301 BUY 6oz BLACK CHERRY GELATIN

RECEIVE 100 BONUS POINTS
1. Change the family code for the current period for 6oz black cherry gelatin to 001
for family code validation. If this is an electronic coupon, put the coupon number
301 in the link field of the 6oz black cherry gelatin.
2. Build a store coupon record number 301. Use pricing method 3 for all points
coupons that require validation.

Chapter 7. Operations 197

 DBM1S003 CHANGE AN ITEM RECORD Page 1 of 2

Item Code 301

Description 100 Points
Department Number (1-999) 100

PRICING METHOD (0-5) 3 (3 = Unit Priced Coupon)

Keep Item Movement (Y/N) Y
MFR Number 43000 Price Required (Y/N) N
Coupon Value 1.00 Weight/Price Required (Y/N) N
Lmt/Tran & Items/Cpn 00 Coupon Sequence (0-20) 0

ITEM TYPE (0-7) 6 0=Normal Sale Item 4=Misc. Sale Item

1=Deposit Item 5=Misc. Refund Item
2=Refund Item 6=Manufac. Coupon Item
3=Deposit Return Item 7=Store Coupon Item

Coupon Family Numbers (0-999): Current Period 1 Previous Period 0

For next page, press PgDn.

If complete, press ENTER.

F1 F2 F3QUIT F4 F5 F6 F7 F8 F9 F10

Figure 33. Add a Bonus Point Coupon Item Record -- Page 1

3. Change the description if needed and ensure the department number is

identical to the black cherry gelatin (dept 100).
4. Enter the manufacturer number for black cherry gelatin (43000).

Note: The manufacturer number is usually the first five digits of the UPC
number. For example, the manufacturer number for gelatin, item
4300030052, is 43000. However, for number system 3 items (that is
those items with a 11 digit UPC number beginning with 30 or 38) the
manufacturer number is created by adding a leading zero (0) to the
second - fifth digit of the UPC. For example, if the UPC is 30521261000,
the manufacturer number is 00521. For further information, see the UPC
Guidelines manual.
5. Enter the value of the bonus points in the field for coupon value (100).
6. Change the coupon family number to 001 for the current period to match the
family code of 6oz black cherry gelatin.

198 Electronic Marketing PRPQ

 DBM1S004 CHANGE AN ITEM RECORD Page 2 of 2

Item Code 301

Description 100 Points
Linked Item Code (0-9999) 0

TAX PLANS: (Type Y=yes if Tax Plan applies, N=no).

Tax Plan A Y Tax Plan B N Minimum by MFR N Minimum by Dept N

USER OPTIONS: (Type Y=yes if Option applies, N=no).

User Option 1 N User Option 2 N User Option 3 N User Option 4 N
User Data 1 (0-32767) 0 Minimum Purchase Amt 1

For the following, type Y=yes, or N=no.

Food Stamp Item Y Quantity Allowed Y

Item Not in Purchase Minimum N Quantity Required N
Coupon Gives Bonus Points Y Authorized for Sale Y
Coupon Value Multiplication Y Restricted Sale Hours N
Exception Log Item Sale N Shelf Label Print Allowed Y
Points Only Coupon Y Separate Minimum per Coupon N
If complete, press ENTER.

F1 F2 F3QUIT F4 F5 F6 F7 F8 F9 F10

Figure 34. Add a Bonus Point Coupon Item Record -- Page 2

7. Enter “Y” for “Points-Only Item.”

8. For point coupons, the line that previously displayed “Discountable Item” now
displays “Coupon Gives Bonus Points”. Enter “Y” for yes on this line. If this were
a coupon for point redemption, an “N” should be entered in the field to indicate
points subtracted from a customer’s total.

Limit Per Transaction/Items Per Coupon

A coupon can be limited to the number of times it can be given in a transaction. A
limit can also be set on the number of matching items that must be purchased to
activate the coupon.

COUPON #302 BUY ANY 6oz GELATIN

RECEIVE 100 POINTS (LIMIT ONE)
1. Change the family code for the current period for all 6oz flavors of gelatin to 002
for family code validation. If this is an electronic coupon, enter the coupon
number 302 in the link field of all flavors of 6oz gelatin.
2. Build a store coupon record number 302. Use pricing method 3 for all point
coupons that require validation.

Chapter 7. Operations 199

 DBM1S003 CHANGE AN ITEM RECORD Page 1 of 2

Item Code 302

Description 100 Points
Department Number (1-999) 100

PRICING METHOD (0-5) 3 (3 = Unit Priced Coupon)

Keep Item Movement (Y/N) Y
MFR Number 43000 Price Required (Y/N) N
Coupon Value 1.00 Weight/Price Required (Y/N) N
Lmt/Tran & Items/Cpn 11 Coupon Sequence (0-20) 0

ITEM TYPE (0-7) 7 0=Normal Sale Item 4=Misc. Sale Item

1=Deposit Item 5=Misc. Refund Item
2=Refund Item 6=Manufac. Coupon Item
3=Deposit Return Item 7=Store Coupon Item

Coupon Family Numbers (0-999): Current Period 2 Previous Period 0

For next page, press PgDn.

If complete, press ENTER.

F1 F2 F3QUIT F4 F5 F6 F7 F8 F9 F10

Figure 35. Add a Limit Per Transaction/Items Per Coupon Item Record -- Page 1

3. There are two sub-fields in the ″Lmt/Tran & Items/Cpn″ field. The first sub-field
(Lmt/Tran or limit per transaction) limits the number of times the coupon can be
honored in a transaction. The second sub-field (Items/Cpn or items per coupon)
defines the number of matching items that must be purchased to use the
coupon. Enter 11 in this field. This will limit the coupon to one per transaction
and will require that only one item (the Gelatin) must be bought to receive this
coupon.
4. Change the family code to 002 to validate any flavor of 6oz gelatin.

DBM1S004 CHANGE AN ITEM RECORD Page 2 of 2

Item Code 302

Description 100 Points
Linked Item Code (0-9999) 0

TAX PLANS: (Type Y=yes if Tax Plan applies, N=no).

Tax Plan A Y Tax Plan B N Tax Plan C N Tax Plan D N

USER OPTIONS: (Type Y=yes if Option applies, N=no).

User Option 1 N User Option 2 N User Option 3 N User Option 4 N
User Data 1 (0-32767) 0 Minimum Purchase Amt 0

For the following, type Y=yes, or N=no.

Food Stamp Item Y Quantity Allowed Y

Item Not in Purchase Minimum Y Quantity Required N
Coupon Gives Bonus Points Y Authorized for Sale Y
Coupon Value Multiplication Y Restricted Sale Hours N
Exception Log Item Sale N Shelf Label Print Allowed Y
Points Only Coupon Y Separate Minimum per Coupon N
If complete, press ENTER

F1 F2 F3QUIT F4 F5 F6 F7 F8 F9 F10

Figure 36. Add a Limit Per Transaction/Items Per Coupon Item Record -- Page 2

200 Electronic Marketing PRPQ

 5. Enter “Y” for “Points-Only Item.”
6. For point coupons, the line that previously displayed “Discountable Item” now
displays “Coupon Gives Bonus Points”. Enter “Y” for yes on this line.

Final Value Coupons

COUPON #303 BUY MILK, 1 GAL
PAY ONLY 19 CENTS
1. Build a store coupon record 303 for milk. Use pricing method 4, as this converts
the coupon value to the final price. You can use pricing method 3, but you must
know the price of the milk and enter the difference between the regular price
and the final price in the coupon value field. Preferred customer coupons may
last more than one week. If you use pricing method 3, you must change the
coupon value if there is a retail change on the milk. However, if you use pricing
method 4, it is not necessary to change the coupon value if the price of milk is
changed.
2. Enter the department and manufacturer number of the milk, the coupon value,
and any limit that might apply. Change the family code to 003.
3. The coupon 303 for milk is not a point coupon. Verify that the ″Points Only
Coupon″ flag is set to ″N″.

DBM1S003 CHANGE AN ITEM RECORD Page 1 of 2

Item Code 303

Description Milk @0.19
Department Number (1-999) 500

Pricing Method (0-5) 4(4 = Coupon value is net item value)

Keep Item Movement (Y/N) Y
MFR Number 11141 Price Required (Y/N) N
Coupon Value .19 Weight/Price Required (Y/N) N
Lmt/Tran & Items/Cpn 00 Coupon Sequence (0-20) 0

ITEM TYPE (0-7) 7 0=Normal Sale Item 4=Misc. Sale Item

1=Deposit Item 5=Misc. Refund Item
2=Refund Item 6=Manufac. Coupon Item
3=Deposit Return Item 7=Store Coupon Item

Coupon Family Numbers (0-999): Current Period 3 Previous Period 0

For next page, press PgDn.

If complete, press ENTER.

F1 F2 F3QUIT F4 F5 F6 F7 F8 F9 F10

Figure 37. Add a Final Value (net item value) Coupon Item Record -- Page 1

Chapter 7. Operations 201

 DBM1S004 CHANGE AN ITEM RECORD Page 2 of 2

Item Code 303

Description Milk @0.19
Linked Item Code (0-9999) 0

TAX PLANS: (Type Y=yes if Tax Plan applies, N=no).

Tax Plan A Y Tax Plan B N Tax Plan C N Tax Plan D N

USER OPTIONS: (Type Y=yes if Option applies, N=no).

User Option 1 N User Option 2 N User Option 3 N User Option 4 N
User Data 1 (0-32767) 0 Minimum Purchase Amt 0

For the following, type Y=yes, or N=no.

Food Stamp Item Y Quantity Allowed Y

Item Not in Purchase Minimum N Quantity Required N
Discountable Item Y Authorized for Sale Y
Coupon Value Multiplication Y Restricted Sale Hours N
Exception Log Item Sale N Shelf Label Print Allowed Y
Points Only Coupon N Separate Minimum per Coupon N
If complete, press ENTER.

F1 F2 F3QUIT F4 F5 F6 F7 F8 F9 F10

Figure 38. Add a Final Value (net item value) Coupon Item Record -- Page 2

4. The coupon is linked to milk to provide validation. Change the family code to
003 on the milk. If this is an electronic coupon, put the coupon number 303 in
the link field for the milk.

Linked Coupons (Discount/Redeem Points)

The linkage of one item record to another is a tool that is critical to preferred
customer coupons. The order of linked coupons and the number of items in a link
chain follow a few simple rules which must be understood by the operator. The first
coupon in the chain that is rejected breaks the chain. If the first coupon calls for
points to be redeemed from the customer and their point balance is insufficient then
the chain is broken. If the first coupon calls for a discount and the coupon fails to
validate (no match found) then the chain is also broken.

When you build a chain of linked coupons involving a coupon that calls for
redemption of points from a customer, the redemption coupon should be built first to
validate that there is enough points in the customer’s balance to proceed.
COUPON #304 BUY 4oz INSTANT COFFEE
REDEEM 50 POINTS
PAY ONLY 7 CENTS FOR COFFEE
1. Change the family code for the current period for 4oz instant coffee to 004 for
family code validations. If this is an electronic coupon, put the coupon number
304 in the link field of 4oz instant coffee.
2. Build a coupon record number 304. Use pricing method 3 for all point coupons
that require validation.

202 Electronic Marketing PRPQ

 DBM1S003 CHANGE AN ITEM RECORD Page 1 of 2

Item Code 304

Description -50 points
Department Number (1-999) 100

PRICING METHOD (0-5) 3 (3 = Unit Priced Coupon)

Keep Item Movement (Y/N) Y
MFR Number 43000 Price Required (Y/N) N
Coupon Value .50 Weight/Price Required (Y/N) N
Lmt/Tran & Items/Cpn 00 Coupon Sequence (0-20) 0

ITEM TYPE (0-7) 7 0=Normal Sale Item 4=Misc. Sale Item

1=Deposit Item 5=Misc. Refund Item
2=Refund Item 6=Manufac. Coupon Item
3=Deposit Return Item 7=Store Coupon Item

Coupon Family Numbers (0-999): Current Period 4 Previous Period 0

For next page, press PgDn.

If complete, press ENTER.

F1 F2 F3QUIT F4 F5 F6 F7 F8 F9 F10

Figure 39. Add a Linked Coupon (redeems points) Item Record -- Page 1

3. Change the description to show this is a redemption coupon. Enter the

department and manufacturer number of the coffee and the points to be
redeemed in the coupon value field. Change the family code number to 004 to
provide additional validation.

DBM1S004 CHANGE AN ITEM RECORD Page 2 of 2

Item Code 304

Description -50 points
Linked Item Code (0-9999) 377

TAX PLANS: (Type Y=yes if Tax Plan applies, N=no).

Tax Plan A Y Tax Plan B N Tax Plan C N Tax Plan D N

USER OPTIONS: (Type Y=yes if Option applies, N=no).

User Option 1 N User Option 2 N User Option 3 N User Option 4 N
User Data 1 (0-32767) 0 Minimum Purchase Amt 0

For the following, type Y=yes, or N=no.

Food Stamp Item Y Quantity Allowed Y

Item Not in Purchase Minimum N Quantity Required N
Coupon Gives Bonus Points N Authorized for Sale Y
Coupon Value Multiplication Y Restricted Sale Hours N
Exception Log Item Sale N Shelf Label Print Allowed Y
Points Only Coupon Y Separate Minimum per Coupon N
If complete, press ENTER.

F1 F2 F3QUIT F4 F5 F6 F7 F8 F9 F10

Figure 40. Add a Linked Coupon (redeems points) Item Record -- Page 2

4. Add the coupon number 377 to the link field. Coupon number 377 will be built
next to give a discount.
5. Enter “Y” for “Points-Only Item.”

Chapter 7. Operations 203

 6. For point coupons, the line that previously displayed “Discountable Item” now
displays “Coupon Gives Bonus Points”. Enter “N” on this line to redeem points
instead of giving points.
7. Build a coupon record number 377 to give a discount on instant coffee after the
points have been redeemed. Do not model this coupon record number after a
points coupon, this coupon does not deal with points.

DBM1S003 CHANGE AN ITEM RECORD Page 1 of 2

Item Code 377

Description Instant Coffee @07
Department Number (1-999) 100

PRICING METHOD (0-5) 4 (4 = Coupon value is net item value)

Keep Item Movement (Y/N) Y
MFR Number 43000 Price Required (Y/N) N
Coupon Value .07 Weight/Price Required (Y/N) N
Lmt/Tran & Items/Cpn 00 Coupon Sequence (0-20) 0

ITEM TYPE (0-7) 7 0=Normal Sale Item 4=Misc. Sale Item

1=Deposit Item 5=Misc. Refund Item
2=Refund Item 6=Manufac. Coupon Item
3=Deposit Return Item 7=Store Coupon Item

Coupon Family Numbers (0-999): Current Period 4 Previous Period 0

For next page, press PgDn.

If complete, press ENTER.

F1 F2 F3QUIT F4 F5 F6 F7 F8 F9 F10

Figure 41. Add a Linked Coupon (discount given after points redeemed) Item Record -- Page
1

8. Enter coupon description, the department and manufacturer number of the

coffee, the coupon value and family code 004 to provide for validation.

204 Electronic Marketing PRPQ

 DBM1S004 CHANGE AN ITEM RECORD Page 2 of 2

Item Code 377

Description Instant Coffee @07
Linked Item Code (0-9999) 0

TAX PLANS: (Type Y=yes if Tax Plan applies, N=no).

Tax Plan A Y Tax Plan B N Tax Plan C N Tax Plan D N

USER OPTIONS: (Type Y=yes if Option applies, N=no).

User Option 1 N User Option 2 N User Option 3 N User Option 4 N
User Data 1 (0-32767) 0 Minimum Purchase Amt 0

For the following, type Y=yes, or N=no.

Food Stamp Item Y Quantity Allowed Y

Item Not in Purchase Minimum N Quantity Required N
Discountable Item Y Authorized for Sale Y
Coupon Value Multiplication Y Restricted Sale Hours N
Exception Log Item Sale N Shelf Label Print Allowed Y
Points Only Coupon N Separate Minimum per Coupon N
If complete, press ENTER.

F1 F2 F3QUIT F4 F5 F6 F7 F8 F9 F10

Figure 42. Add a Linked Coupon (discount given after points redeemed) Item Record -- Page
2

9. There is no coupon number in the link field, this is the last coupon in the chain.
Make any changes to tax fields and other unique fields that affect your area.

Linked Coupons (Multiple Items Plus Points)

Product validation on multiple items within an order can be achieved by building
“dummy coupons” within the chain of coupons. These cannot be built as bonus
point coupons, but rather as regular store coupons with a coupon value of .01. Up
to four of these dummy coupons can be built in a linked chain to validate all the
criteria of the coupon has been met.
COUPON #305 BUY HOT DOGS, HOT DOG ROLLS
AND MUSTARD
REDEEM 200 POINTS
RECEIVE MUSTARD FOR 5 CENTS
1. Change the family code for the current period for hot dogs, hot dog rolls, and
mustard to 005 for family code validation. If this is an electronic coupon, put
the coupon number 305 in the link field of mustard.
2. Build a coupon record number 305. Use pricing method 3 for all point coupons
requiring validation.

Chapter 7. Operations 205

 DBM1S003 CHANGE AN ITEM RECORD Page 1 of 2

Item Code 305

Description -200 points
Department Number (1-999) 300

PRICING METHOD (0-5) 3 (3 = Unit Priced Coupon)

Keep Item Movement (Y/N) Y
MFR Number 27000 Price Required (Y/N) N
Coupon Value 2.00 Weight/Price Required (Y/N) N
Lmt/Tran & Items/Cpn 00 Coupon Sequence (0-20) 0

ITEM TYPE (0-7) 7 0=Normal Sale Item 4=Misc. Sale Item

1=Deposit Item 5=Misc. Refund Item
2=Refund Item 6=Manufac. Coupon Item
3=Deposit Return Item 7=Store Coupon Item

Coupon Family Numbers (0-999): Current Period 5 Previous Period 0

For next page, press PgDn.

If complete, press ENTER.

F1 F2 F3QUIT F4 F5 F6 F7 F8 F9 F10

Figure 43. Add a Linked Coupon (multiple items plus points) Item Record -- Page 1

DBM1S004 CHANGE AN ITEM RECORD Page 2 of 2

Item Code 305

Description -200 points
Linked Item Code (0-9999) 379

TAX PLANS: (Type Y=yes if Tax Plan applies, N=no).

Tax Plan A Y Tax Plan B N Tax Plan C N Tax Plan D N

USER OPTIONS: (Type Y=yes if Option applies, N=no).

User Option 1 N User Option 2 N User Option 3 N User Option 4 N
User Data 1 (0-32767) 0 Minimum Purchase Amt 0

For the following, type Y=yes, or N=no.

Food Stamp Item Y Quantity Allowed Y

Item Not in Purchase Minimum N Quantity Required N
Coupon Gives Bonus Points N Authorized for Sale Y
Coupon Value Multiplication Y Restricted Sale Hours N
Exception Log Item Sale N Shelf Label Print Allowed Y
Points Only Coupon Y Separate Minimum per Coupon N
If complete, press ENTER.

F1 F2 F3QUIT F4 F5 F6 F7 F8 F9 F10

Figure 44. Add a Linked Coupon (multiple items plus points) Item Record -- Page 2

3. Enter the coupon description and the department and manufacturer number of
the hot dogs. Enter the coupon value (points to be redeemed - 200). This
coupon will provide redemption of 200 points from a customer’s point balance.
If the customer balance is below 200 points, the chain is then broken. Note:
This coupon both validates that the hot dogs have been sold and redeems the
points.
4. Change the family code 005.
5. Enter “Y” for “Points-Only Item.”

206 Electronic Marketing PRPQ

 6. For point coupons, the line that previously displayed “Discountable Item” now
displays “Coupon Gives Bonus Points”. Enter “N” on this line to redeem points
instead of giving points.
7. A coupon record number 379 must be built to provide validation for the hot dog
rolls. This is not a point coupon.

DBM1S003 CHANGE AN ITEM RECORD Page 1 of 2

Item Code 379

Description Hot Dog Rolls Link
Department Number (1-999) 100

PRICING METHOD (0-5) 3(3 = Unit Priced Coupon)

Keep Item Movement (Y/N) Y
MFR Number 37432 Price Required (Y/N) N
Coupon Value .01 Weight/Price Required (Y/N) N
Lmt/Tran & Items/Cpn 00 Coupon Sequence (0-20) 0

ITEM TYPE (0-7) 7 0=Normal Sale Item 4=Misc. Sale Item

1=Deposit Item 5=Misc. Refund Item
2=Refund Item 6=Manufac. Coupon Item
3=Deposit Return Item 7=Store Coupon Item

Coupon Family Numbers (0-999): Current Period 5 Previous Period 0

For next page, press PgDn.

If complete, press ENTER.

F1 F2 F3QUIT F4 F5 F6 F7 F8 F9 F10

Figure 45. Add a Linked Coupon to provide validation (no bonus points) Item Record -- Page
1

DBM1S004 CHANGE AN ITEM RECORD Page 2 of 2

Item Code 379

Description Hot Dog Rolls link
Linked Item Code (0-9999) 380

TAX PLANS: (Type Y=yes if Tax Plan applies, N=no).

Tax Plan A Y Tax Plan B N Tax Plan C N Tax Plan D N

USER OPTIONS: (Type Y=yes if Option applies, N=no).

User Option 1 N User Option 2 N User Option 3 N User Option 4 N
User Data 1 (0-32767) 0 Minimum Purchase Amt 0

For the following, type Y=yes, or N=no.

Food Stamp Item Y Quantity Allowed Y

Item Not in Purchase Minimum N Quantity Required N
Discountable Item Y Authorized for Sale Y
Coupon Value Multiplication Y Restricted Sale Hours N
Exception Log Item Sale N Shelf Label Print Allowed Y
Points Only Coupon N Separate Minimum per Coupon N
If complete, press ENTER.

F1 F2 F3QUIT F4 F5 F6 F7 F8 F9 F10

Figure 46. Add a Linked Coupon to provide validation (no bonus points) Item Record -- Page
2

Chapter 7. Operations 207

 8. Enter the coupon description and the department and manufacturer number of
the hot dog rolls. Enter the coupon value as .01 to validate the hot dog rolls.
Any coupon with a coupon value of .01 will only provide validation.
9. Change the family code 005 validation for the hot dog rolls.
10. A coupon record number 380 must be built to provide the discount for the
mustard.
11. Enter the coupon description and the department number of the mustard.
12. Change the pricing method to 4 to provide for the final value of the mustard.
13. Enter the manufacturer number of the mustard. Enter the coupon value of .05.
The mustard is to be sold for a final value of .05.
14. Change the family code 005.

DBM1S003 CHANGE AN ITEM RECORD Page 1 of 2

Item Code 380

Description Mustard @.05
Department Number (1-999) 100

PRICING METHOD (0-5) 4 (4 = Coupon value is net item value)

Keep Item Movement (Y/N) Y
MFR Number 75000 Price Required (Y/N) N
Coupon Value .05 Weight/Price Required (Y/N) N
Lmt/Tran & Items/Cpn 00 Coupon Sequence (0-20) 0

ITEM TYPE (0-7) 7 0=Normal Sale Item 4=Misc. Sale Item

1=Deposit Item 5=Misc. Refund Item
2=Refund Item 6=Manufac. Coupon Item
3=Deposit Return Item 7=Store Coupon Item

Coupon Family Numbers (0-999): Current Period 5 Previous P eriod 0

For next page, press PgDn.

If complete, press ENTER.

F1 F2 F3QUIT F4 F5 F6 F7 F8 F9 F10

Figure 47. Add a Linked Coupon (discount given if each coupon passes validation, no bonus
points) Item Record -- Page 1

208 Electronic Marketing PRPQ

 DBM1S004 CHANGE AN ITEM RECORD Page 2 of 2

Item Code 380

Description Mustard @.05
Linked Item Code (0-9999) 0

TAX PLANS: (Type Y=yes if Tax Plan applies, N=no).

Tax Plan A Y Tax Plan B N Tax Plan C N Tax Plan D N

USER OPTIONS: (Type Y=yes if Option applies, N=no).

User Option 1 N User Option 2 N User Option 3 N User Option 4 N
User Data 1 (0-32767) 0 Minimum Purchase Amt 0

For the following, type Y=yes, or N=no.

Food Stamp Item Y Quantity Allowed Y

Item Not in Purchase Minimum N Quantity Required N
Discountable Item Y Authorized for Sale Y
Coupon Value Multiplication Y Restricted Sale Hours N
Exception Log Item Sale N Shelf Label Print Allowed Y
Points Only Coupon N Separate Minimum per Coupon N
If complete, press ENTER.

F1 F2 F3QUIT F4 F5 F6 F7 F8 F9 F10

Figure 48. Add a Linked Coupon (discount given if each coupon passes validation, no bonus
points) Item Record -- Page 2

15. This is the last coupon in the chain. It gives the discount if each coupon
passes validation.

Linked Coupons (Multiple Items/No Points)

The Preferred Customer program is designed to use points to reward customers for
their shopping activity. Coupons that do not involve points can be written. However,
these coupons would not cause a “Card Required” message to display at the end of
the transaction if a Non-Preferred Customer gave a paper coupon designed for use
only by Preferred Customers.
COUPON #306 BUY FRANKS
BUY HOT DOG BUNS
GET MUSTARD FREE
1. Change the family code for the current period for all varieties of franks, hot dog
buns, and mustard for the promoted manufacturers to 006 for family code
validation. If this is an electronic coupon, put the coupon number in the link field
of the mustard.
2. Build a dummy coupon for coupon record 306 to provide validation for the
franks.

Chapter 7. Operations 209

 DBM1S003 CHANGE AN ITEM RECORD Page 1 of 2

Item Code 306

Description Franks Link
Department Number (1-999) 300

PRICING METHOD (0-5) 3 (3 = Unit Priced Coupon)

Keep Item Movement (Y/N) Y
MFR Number 27000 Price Required (Y/N) N
Coupon Value .01 Weight/Price Required (Y/N) N
Lmt/Tran & Items/Cpn 00 Coupon Sequence (0-20) 0

ITEM TYPE (0-7) 7 0=Normal Sale Item 4=Misc. Sale Item

1=Deposit Item 5=Misc. Refund Item
2=Refund Item 6=Manufac. Coupon Item
3=Deposit Return Item 7=Store Coupon Item

Coupon Family Numbers (0-999): Current Period 6 Previous Period 0

For next page, press PgDn.

If complete, press ENTER.

F1 F2 F3QUIT F4 F5 F6 F7 F8 F9 F10

Figure 49. Add a dummy validation Linked Coupon Item Record -- Page 1

DBM1S004 CHANGE AN ITEM RECORD Page 2 of 2

Item Code 306

Description Franks Link
Linked Item Code (0-9999) 382

TAX PLANS: (Type Y=yes if Tax Plan applies, N=no).

Tax Plan A Y Tax Plan B N Tax Plan C N Tax Plan D N

USER OPTIONS: (Type Y=yes if Option applies, N=no).

User Option 1 N User Option 2 N User Option 3 N User Option 4 N
User Data 1 (0-32767) 0 Minimum Purchase Amt 0

For the following, type Y=yes, or N=no.

Food Stamp Item Y Quantity Allowed Y

Item Not in Purchase Minimum N Quantity Required N
Discountable Item Y Authorized for Sale Y
Coupon Value Multiplication Y Restricted Sale Hours N
Exception Log Item Sale N Shelf Label Print Allowed Y
Points Only Coupon N Separate Minimum per Coupon N
If complete, press ENTER.

F1 F2 F3QUIT F4 F5 F6 F7 F8 F9 F10

Figure 50. Add a dummy validation Linked Coupon Item Record -- Page 2

3. Build a dummy coupon for coupon record number 382 to provide validation for
hot dog buns.

210 Electronic Marketing PRPQ

 DBM1S003 CHANGE AN ITEM RECORD Page 1 of 2

Item Code 382

Description Hot Dog Rolls Link
Department Number (1-999) 100

PRICING METHOD (0-5) 3(3 = Unit Priced Coupon)

Keep Item Movement (Y/N) Y
MFR Number 37432 Price Required (Y/N) N
Coupon Value .01 Weight/Price Required (Y/N) N
Lmt/Tran & Items/Cpn 00 Coupon Sequence (0-20) 0

ITEM TYPE (0-7) 7 0=Normal Sale Item 4=Misc. Sale Item

1=Deposit Item 5=Misc. Refund Item
2=Refund Item 6=Manufac. Coupon Item
3=Deposit Return Item 7=Store Coupon Item

Coupon Family Numbers (0-999): Current Period 6 Previous Period 0

For next page, press PgDn.

If complete, press ENTER.

F1 F2 F3QUIT F4 F5 F6 F7 F8 F9 F10

Figure 51. Add a dummy validation Linked Coupon Item Record -- Page 1

DBM1S004 CHANGE AN ITEM RECORD Page 2 of 2

Item Code 382

Description Hot Dog Rolls link
Linked Item Code (0-9999) 383

TAX PLANS: (Type Y=yes if Tax Plan applies, N=no).

Tax Plan A Y Tax Plan B N Tax Plan C N Tax Plan D N

USER OPTIONS: (Type Y=yes if Option applies, N=no).

User Option 1 N User Option 2 N User Option 3 N User Option 4 N
User Data 1 (0-32767) 0 Minimum Purchase Amt 0

For the following, type Y=yes, or N=no.

Food Stamp Item Y Quantity Allowed Y

Item Not in Purchase Minimum N Quantity Required N
Discountable Item Y Authorized for Sale Y
Coupon Value Multiplication Y Restricted Sale Hours N
Exception Log Item Sale N Shelf Label Print Allowed Y
Points Only Coupon N Separate Minimum per Coupon N
If complete, press ENTER.

F1 F2 F3QUIT F4 F5 F6 F7 F8 F9 F10

Figure 52. Add a dummy validation Linked Coupon Item Record -- Page 2

4. Build a coupon record number 383 to provide validation for mustard. Build this
coupon using pricing method 4 to make the mustard free.

Chapter 7. Operations 211

 DBM1S003 CHANGE AN ITEM RECORD Page 1 of 2

Item Code 383

Description Mustard free
Department Number (1-999) 100

PRICING METHOD (0-5) 4 (4 = Coupon value is net item value)

Keep Item Movement (Y/N) Y
MFR Number 75000 Price Required (Y/N) N
Coupon Value .00 Weight/Price Required (Y/N) N
Lmt/Tran & Items/Cpn 00 Coupon Sequence (0-20) 0

ITEM TYPE (0-7) 7 0=Normal Sale Item 4=Misc. Sale Item

1=Deposit Item 5=Misc. Refund Item
2=Refund Item 6=Manufac. Coupon Item
3=Deposit Return Item 7=Store Coupon Item

Coupon Family Numbers (0-999): Current Period 6 Previous Period 0

For next page, press PgDn.

If complete, press ENTER.

F1 F2 F3QUIT F4 F5 F6 F7 F8 F9 F10

Figure 53. Add a validation Linked Coupon (price method 4) Item Record -- Page 1

DBM1S004 CHANGE AN ITEM RECORD Page 2 of 2

Item Code 383

Description Mustard free
Linked Item Code (0-9999) 0

TAX PLANS: (Type Y=yes if Tax Plan applies, N=no).

Tax Plan A Y Tax Plan B N Tax Plan C N Tax Plan D N

USER OPTIONS: (Type Y=yes if Option applies, N=no).

User Option 1 N User Option 2 N User Option 3 N User Option 4 N
User Data 1 (0-32767) 0 Minimum Purchase Amt 0

For the following, type Y=yes, or N=no.

Food Stamp Item Y Quantity Allowed Y

Item Not in Purchase Minimum N Quantity Required N
Discountable Item Y Authorized for Sale Y
Coupon Value Multiplication Y Restricted Sale Hours N
Exception Log Item Sale N Shelf Label Print Allowed Y
Points Only Coupon N Separate Minimum per Coupon N
If complete, press ENTER.

F1 F2 F3QUIT F4 F5 F6 F7 F8 F9 F10

Figure 54. Add a validation Linked Coupon (price method 4) Item Record -- Page 2

5. This is the last coupon in the chain. It gives the discount if each coupon in the
chain passes validation.

Coupon Linked to Department Purchase

A coupon that requires a purchase in a specific department can be built. This
coupon can be used to reward a customer with bonus points or with a discount for
shopping in certain departments.

212 Electronic Marketing PRPQ

 COUPON #307 BUY ANY ITEM FROM MEAT DEPARTMENT
RECEIVE 75 BONUS POINTS
1. Build a store coupon record number 307. Use pricing method 3 for all point
coupons requiring validation.
2. Do not change the coupon family number or the manufacturer number because
the coupon is not restricted to any item but only to a purchase in the meat
department. Enter the department number of the meat department.

DBM1S003 CHANGE AN ITEM RECORD Page 1 of 2

Item Code 307

Description 75 Points
Department Number (1-999) 300

PRICING METHOD (0-5) 3(3 = Unit Priced Coupon)

Keep Item Movement (Y/N) Y
MFR Number 00000 Price Required (Y/N) N
Coupon Value .75 Weight/Price Required (Y/N) N
Lmt/Tran & Items/Cpn 00 Coupon Sequence (0-20) 0

ITEM TYPE (0-7) 7 0=Normal Sale Item 4=Misc. Sale Item

1=Deposit Item 5=Misc. Refund Item
2=Refund Item 6=Manufac. Coupon Item
3=Deposit Return Item 7=Store Coupon Item

Coupon Family Numbers (0-999): Current Period 0 Previous Period 0

For next page, press PgDn.

If complete, press ENTER.

F1 F2 F3QUIT F4 F5 F6 F7 F8 F9 F10

Figure 55. Add a Coupon Linked to Department Purchase Item Record -- Page 1

DBM1S004 CHANGE AN ITEM RECORD Page 2 of 2

Item Code 307

Description 75 Points
Linked Item Code (0-9999) 0

TAX PLANS: (Type Y=yes if Tax Plan applies, N=no).

Tax Plan A Y Tax Plan B N Validate Dept Y Minimum by Dept Y

USER OPTIONS: (Type Y=yes if Option applies, N=no).

User Option 1 N User Option 2 N User Option 3 N User Option 4 N
User Data 1 (0-32767) 0 Minimum Purchase Amt 1

For the following, type Y=yes, or N=no.

Food Stamp Item Y Quantity Allowed Y

Item Not in Purchase Minimum N Quantity Required N
Coupon Gives Bonus Points Y Authorized for Sale Y
Coupon Value Multiplication Y Restricted Sale Hours N
Exception Log Item Sale N Shelf Label Print Allowed Y
Points Only Coupon Y Separate Minimum per Coupon N
If complete, press ENTER.

F1 F2 F3QUIT F4 F5 F6 F7 F8 F9 F10

Figure 56. Add a Coupon Linked to Department Purchase Item Record -- Page 2

Chapter 7. Operations 213

 3. To restrict the coupon to a meat department purchase, change the minimum by
department option to “Y”. Set the minimum purchase amount to 1 ( 1 cent). The
only requirement is the purchase of an item, not to buy a specified amount.
4. This coupon awards points. Enter “Y” for “Points-Only Item.”
5. For point coupons, the line that previously displayed “Discountable Item” now
displays “Coupon Gives Bonus Points”. Enter “Y” on this line to give bonus
points.

Note: This coupon is a paper coupon. It should not be used as an electronic

coupon unless you want to place 307 in the link field of every item in the
department.

Coupon Linked to a Minimum Department Purchase

A coupon that requires a minimum purchase in a specific department can be built.
This coupon can be used to reward a customer with bonus points or with a discount
for buying specified amounts in certain departments.
COUPON #308 BUY $10 FROM MEAT DEPARTMENT
RECEIVE 25 BONUS POINTS
1. Build a store coupon record number 308. Use pricing method 3 for all point
coupons requiring validation.
2. Do not change the coupon family number or the manufacturer number. The
coupon is not restricted to a specified item but to a $10 purchase in the meat
department. Enter the department number of the meat department.

DBM1S003 CHANGE AN ITEM RECORD Page 1 of 2

Item Code 308

Description 25 Points
Department Number (1-999) 300

PRICING METHOD (0-5) 3 (3 = Unit Priced Coupon)

Keep Item Movement (Y/N) Y
MFR Number 00000 Price Required (Y/N) N
Coupon Value .25 Weight/Price Required (Y/N) N
Lmt/Tran & Items/Cpn 00 Coupon Sequence (0-20) 0

ITEM TYPE (0-7) 7 0=Normal Sale Item 4=Misc. Sale Item

1=Deposit Item 5=Misc. Refund Item
2=Refund Item 6=Manufac. Coupon Item
3=Deposit Return Item 7=Store Coupon Item

Coupon Family Numbers (0-999): Current Period 0 Previous Period 0

For next page, press PgDn.

If complete, press ENTER.

F1 F2 F3QUIT F4 F5 F6 F7 F8 F9 F10

Figure 57. Add a Coupon Linked to Minimum Department Purchase Item Record -- Page 1

214 Electronic Marketing PRPQ

 DBM1S004 CHANGE AN ITEM RECORD Page 2 of 2

Item Code 308

Description 25 Points
Linked Item Code (0-9999) 0

TAX PLANS: (Type Y=yes if Tax Plan applies, N=no).

Tax Plan A Y Tax Plan B N Validate Dept Y Minimum by Dept Y

USER OPTIONS: (Type Y=yes if Option applies, N=no).

User Option 1 N User Option 2 N User Option 3 N User Option 4 N
User Data 1 (0-32767) 0 Minimum Purchase Amt 1000

For the following, type Y=yes, or N=no.

Food Stamp Item Y Quantity Allowed Y

Item Not in Purchase Minimum N Quantity Required N
Coupon Gives Bonus Points Y Authorized for Sale Y
Coupon Value Multiplication Y Restricted Sale Hours N
Exception Log Item Sale N Shelf Label Print Allowed Y
Points Only Coupon Y Separate Minimum per Coupon N
If complete, press ENTER.

F1 F2 F3QUIT F4 F5 F6 F7 F8 F9 F10

Figure 58. Add a Coupon Linked to Minimum Department Purchase Item Record -- Page 2

3. To restrict the coupon to a meat department purchase, change the

minimum-by-department option to “Y”. Set the minimum purchase amount to
$10.00. The coupon will not validate until $10.00 in the meat department
purchases have been made.
4. This coupon awards points. Set “Points Only Coupon” to “Y” and set “Coupon
Gives Bonus Points” to “Y”.

Note: This coupon should not be used as an electronic coupon unless you want to
place 308 in the link field of every item in the department.

Coupon Linked to Minimum in Two Departments

Coupons can be linked to require minimum purchases in two different departments.
Customers can be rewarded by bonus points or by discounts for shopping in two
different departments.
COUPON #309 BUY $8.00 FROM THE MEAT DEPARTMENT
BUY $8.00 FROM PRODUCE DEPARTMENT
RECEIVE 88 POINTS
1. Build a dummy coupon record (coupon value of .01) numbered 309 to validate
the minimum purchase in the meat department.
2. Do not enter a coupon family number or a manufacturer number. The coupon is
not restricted to a specified item but only to an $8.00 purchase in the meat
department. Enter the department number for the meat department.

Chapter 7. Operations 215

 DBM1S003 CHANGE AN ITEM RECORD Page 1 of 2

Item Code 309

Description $8 Meat
Department Number (1-999) 300

PRICING METHOD (0-5) 3 (3 = Unit Priced Coupon)

Keep Item Movement (Y/N) Y
MFR Number 00000 Price Required (Y/N) N
Coupon Value .01 Weight/Price Required (Y/N) N
Lmt/Tran & Items/Cpn 00 Coupon Sequence (0-20) 0

ITEM TYPE (0-7) 7 0=Normal Sale Item 4=Misc. Sale Item

1=Deposit Item 5=Misc. Refund Item
2=Refund Item 6=Manufac. Coupon Item
3=Deposit Return Item 7=Store Coupon Item

Coupon Family Numbers (0-999): Current Period 0 Previous Period 0

For next page, press PgDn.

If complete, press ENTER.

F1 F2 F3QUIT F4 F5 F6 F7 F8 F9 F10

Figure 59. Add a dummy Coupon Linked to minimum in two departments Item Record --
Page 1

DBM1S004 CHANGE AN ITEM RECORD Page 2 of 2

Item Code 309

Description $8 Meat
Linked Item Code (0-9999) 385

TAX PLANS: (Type Y=yes if Tax Plan applies, N=no).

Tax Plan A Y Tax Plan B N Validate Dept Y Minimum by Dept Y

USER OPTIONS: (Type Y=yes if Option applies, N=no).

User Option 1 N User Option 2 N User Option 3 N User Option 4 N
User Data 1 (0-32767) 0 Minimum Purchase Amt 800

For the following, type Y=yes, or N=no.

Food Stamp Item Y Quantity Allowed Y

Item Not in Purchase Minimum N Quantity Required N
Discountable Item Y Authorized for Sale Y
Coupon Value Multiplication Y Restricted Sale Hours N
Exception Log Item Sale N Shelf Label Print Allowed Y
Points Only Coupon N Separate Minimum per Coupon N
If complete, press ENTER.

F1 F2 F3QUIT F4 F5 F6 F7 F8 F9 F10

Figure 60. Add a dummy Coupon Linked to minimum in two departments Item Record --
Page 2

3. Build a store coupon record number 385. Use pricing method 3 for all point
coupons requiring validation. This coupon record number 385 is also included in
the link field of the previous coupon.
4. Do not enter a coupon family number or manufacturer number. The coupon is
not restricted to a specified item but only to an $8.00 purchase in the produce
department. Enter the department number of the produce department.

216 Electronic Marketing PRPQ

 DBM1S003 CHANGE AN ITEM RECORD Page 1 of 2

Item Code 385

Description 88 Points
Department Number (1-999) 200

PRICING METHOD (0-5) 3 (3 = Unit Priced Coupon)

Keep Item Movement (Y/N) Y
MFR Number 00000 Price Required (Y/N) N
Coupon Value .88 Weight/Price Required (Y/N) N
Lmt/Tran & Items/Cpn 00 Coupon Sequence (0-20) 0

ITEM TYPE (0-7) 7 0=Normal Sale Item 4=Misc. Sale Item

1=Deposit Item 5=Misc. Refund Item
2=Refund Item 6=Manufac. Coupon Item
3=Deposit Return Item 7=Store Coupon Item

Coupon Family Numbers (0-999): Current Period 0 Previous Period 0

For next page, press PgDn.

If complete, press ENTER.

F1 F2 F3QUIT F4 F5 F6 F7 F8 F9 F10

Figure 61. Add a Linked Coupon, pricing method 3, point coupons require validation Item
Record -- Page 1

DBM1S004 CHANGE AN ITEM RECORD Page 2 of 2

Item Code 385

Description 88 Points
Linked Item Code (0-9999) 0

TAX PLANS: (Type Y=yes if Tax Plan applies, N=no).

Tax Plan A Y Tax Plan B N Validate Dept Y Minimum by Dept Y

USER OPTIONS: (Type Y=yes if Option applies, N=no).

User Option 1 N User Option 2 N User Option 3 N User Option 4 N
User Data 1 (0-32767) 0 Minimum Purchase Amt 800

For the following, type Y=yes, or N=no.

Food Stamp Item Y Quantity Allowed Y

Item Not in Purchase Minimum N Quantity Required N
Coupon Gives Bonus Points Y Authorized for Sale Y
Coupon Value Multiplication Y Restricted Sale Hours N
Exception Log Item Sale N Shelf Label Print Allowed Y
Points Only Coupon Y Separate Minimum per Coupon N
If complete, press ENTER.

F1 F2 F3QUIT F4 F5 F6 F7 F8 F9 F10

Figure 62. Add a Linked Coupon, pricing method 3, point coupons require validation Item
Record -- Page 2

5. If the minimum purchase requirement for both coupons is met, the customer is
awarded 88 bonus points.

Note: This is a paper [Link] should not be used as an electronic coupon unless
you want to place 309 in the link field of every item in the department.

Chapter 7. Operations 217

Coupon Linked to Minimum by Manufacturer
Customers can be rewarded by manufacturers for purchasing a minimum amount of
their products.
COUPON #310 BUY $5.00 OF A COOKIE MFR PRODUCT
RECEIVE 55 BONUS POINTS
1. Build a store coupon record number 310. Use pricing method 3 for all point
coupons requiring validation.
2. Do not change the coupon family number. The coupon is not restricted to any
item but only to a $5.00 purchase of a specific manufacturer’s cookie products.
This coupon provides validation by department and by the cookie’s
manufacturer number.

Note: This coupon should not be used as an electronic coupon unless you want to
place 310 in the link field of every cookie item in the department for this
manufacturer.

DBM1S003 CHANGE AN ITEM RECORD Page 1 of 2

Item Code 310

Description 55 Points
Department Number (1-999) 100

PRICING METHOD (0-5) 3 (3 = Unit Priced Coupon)

Keep Item Movement (Y/N) Y
MFR Number 44000 Price Required (Y/N) N
Coupon Value .55 Weight/Price Required (Y/N) N
Lmt/Tran & Items/Cpn 00 Coupon Sequence (0-20) 0

ITEM TYPE (0-7) 7 0=Normal Sale Item 4=Misc. Sale Item

1=Deposit Item 5=Misc. Refund Item
2=Refund Item 6=Manufac. Coupon Item
3=Deposit Return Item 7=Store Coupon Item

Coupon Family Numbers (0-999): Current Period 0 Previous Period 0

For next page, press PgDn.

If complete, press ENTER.

F1 F2 F3QUIT F4 F5 F6 F7 F8 F9 F10

Figure 63. Add a coupon linked to minimum by manufacturer Item Record -- Page 1

218 Electronic Marketing PRPQ

 DBM1S004 CHANGE AN ITEM RECORD Page 2 of 2

Item Code 310

Description 55 Points
Linked Item Code (0-9999) 0

TAX PLANS: (Type Y=yes if Tax Plan applies, N=no).

Tax Plan A Y Tax Plan B N Minimum by MFR Y Minimum by Dept N

USER OPTIONS: (Type Y=yes if Option applies, N=no).

User Option 1 N User Option 2 N User Option 3 N User Option 4 N
User Data 1 (0-32767) 0 Minimum Purchase Amt 500

For the following, type Y=yes, or N=no.

Food Stamp Item Y Quantity Allowed Y

Item Not in Purchase Minimum N Quantity Required N
Coupon Gives Bonus Points Y Authorized for Sale Y
Coupon Value Multiplication Y Restricted Sale Hours N
Exception Log Item Sale N Shelf Label Print Allowed Y
Points Only Coupon Y Separate Minimum per Coupon N
If complete, press ENTER.

F1 F2 F3QUIT F4 F5 F6 F7 F8 F9 F10

Figure 64. Add a coupon linked to minimum by manufacturer Item Record -- Page 2

Coupon Linked to Items per Coupons

Coupons that reflect the number of items purchased can be built to receive points
or give a discount.
COUPON #311 BUY ANY THREE 6oz GELATIN
RECEIVE THE FOURTH 6oz GELATIN FREE
RECEIVE 33 BONUS POINTS
1. Change the family code for the current period for all 6oz flavors of gelatin to 011
for family code validation. If this is an electronic coupon, put the coupon number
311 in the link field of all flavors of 6oz gelatin.
2. Build a store coupon record number 311. Use pricing method 4 with a coupon
value of .00 to create the free item coupon.
3. Enter the department and manufacturer of the gelatin. Enter the coupon value
as .00. Enter the family code as 011.

Chapter 7. Operations 219

 DBM1S003 CHANGE AN ITEM RECORD Page 1 of 2

Item Code 311

Description Free Gelatin
Department Number (1-999) 100

PRICING METHOD (0-5) 4 (4 = Coupon value is net item value)

Keep Item Movement (Y/N) Y
MFR Number 43000 Price Required (Y/N) N
Coupon Value .00 Weight/Price Required (Y/N) N
Lmt/Tran & Items/Cpn 14 Coupon Sequence (0-20) 0

ITEM TYPE (0-7) 7 0=Normal Sale Item 4=Misc. Sale Item

1=Deposit Item 5=Misc. Refund Item
2=Refund Item 6=Manufac. Coupon Item
3=Deposit Return Item 7=Store Coupon Item

Coupon Family Numbers (0-999): Current Period 011 Previous Period 0

For next page, press PgDn.

If complete, press ENTER.

F1 F2 F3QUIT F4 F5 F6 F7 F8 F9 F10

Figure 65. Add a Coupon Linked to items per coupon Item Record -- Page 1

4. Enter 14 in the ″Lmt/Tran & Items/Cpn″ field. This limit per transaction and
items per coupon defines the guidelines of how many free boxes of gelatin a
customer can receive and how many boxes must be purchased to get one free.
The 4 in the “Items per Coupon” field means that, on buying the fourth box of
gelatin a customer receives the coupon which, in this case, is a free box of
gelatin. The 1 in the items per coupon field means that only one free box of
gelatin will be given in the transaction.

DBM1S004 CHANGE AN ITEM RECORD Page 2 of 2

Item Code 311

Description Free Gelatin
Linked Item Code (0-9999) 387

TAX PLANS: (Type Y=yes if Tax Plan applies, N=no).

Tax Plan A Y Tax Plan B N Tax Plan C N Tax Plan D N

USER OPTIONS: (Type Y=yes if Option applies, N=no).

User Option 1 N User Option 2 N User Option 3 N User Option 4 N
User Data 1 (0-32767) 0 Minimum Purchase Amt 0

For the following, type Y=yes, or N=no.

Food Stamp Item Y Quantity Allowed Y

Item Not in Purchase Minimum N Quantity Required N
Discountable Item Y Authorized for Sale Y
Coupon Value Multiplication Y Restricted Sale Hours N
Exception Log Item Sale N Shelf Label Print Allowed Y
Points Only Coupon N Separate Minimum per Coupon N
If complete, press ENTER.

F1 F2 F3QUIT F4 F5 F6 F7 F8 F9 F10

Figure 66. Add a Coupon Linked to items per coupon Item Record -- Page 2

220 Electronic Marketing PRPQ

5. After the fourth gelatin is purchased, the coupon allows a discount of the retail
price of a 6oz gelatin. The next coupon to be built is 387. It is linked to the free
gelatin coupon 311. This is the point coupon for awarding 33 bonus points.

DBM1S003 CHANGE AN ITEM RECORD Page 1 of 2

Item Code 387

Description 33 Points
Department Number (1-999) 100

PRICING METHOD (0-5) 3(3 = Unit Priced Coupon)

Keep Item Movement (Y/N) Y
MFR Number 43000 Price Required (Y/N) N
Coupon Value .33 Weight/Price Required (Y/N) N
Lmt/Tran & Items/Cpn 00 Coupon Sequence (0-20) 0

ITEM TYPE (0-7) 7 0=Normal Sale Item 4=Misc. Sale Item

1=Deposit Item 5=Misc. Refund Item
2=Refund Item 6=Manufac. Coupon Item
3=Deposit Return Item 7=Store Coupon Item

Coupon Family Numbers (0-999): Current Period 011 Previous Period 0

For next page, press PgDn.

If complete, press ENTER.

F1 F2 F3QUIT F4 F5 F6 F7 F8 F9 F10

Figure 67. Add a Coupon Linked to items per coupon Item Record -- Page 1

DBM1S004 CHANGE AN ITEM RECORD Page 2 of 2

Item Code 387

Description 33 Points
Linked Item Code (0-9999) 0

TAX PLANS: (Type Y=yes if Tax Plan applies, N=no).

Tax Plan A Y Tax Plan B N Tax Plan C N Tax Plan D N

USER OPTIONS: (Type Y=yes if Option applies, N=no).

User Option 1 N User Option 2 N User Option 3 N User Option 4 N
User Data 1 (0-32767) 0 Minimum Purchase Amt 0

For the following, type Y=yes, or N=no.

Food Stamp Item Y Quantity Allowed Y

Item Not in Purchase Minimum N Quantity Required N
Coupon Gives Bonus Points Y Authorized for Sale Y
Coupon Value Multiplication Y Restricted Sale Hours N
Exception Log Item Sale N Shelf Label Print Allowed Y
Points Only Coupon Y Separate Minimum per Coupon N
If complete, press ENTER.

F1 F2 F3QUIT F4 F5 F6 F7 F8 F9 F10

Figure 68. Add a Coupon Linked to items per coupon Item Record -- Page 2

Chapter 7. Operations 221

Award Points With No Performance Required
Points can be awarded to a customer with no customer performance requirement
except presentation of a coupon. This can be a reward for a customer who has not
been a frequent shopper of a particular store.
COUPON #312 25 FREE BONUS POINTS
1. A point-only coupon must be built as a regular sale item, because store coupon
records require some type of validation. That is, the item type must be 0 to
make it a regular store item.

DBM1S003 CHANGE AN ITEM RECORD Page 1 of 2

Item Code 312

Description 25 Points
Department Number (1-999) 100

PRICING METHOD (0-5) 0

Keep Item Movement (Y/N) Y
Unit Price .25 Price Required (Y/N) N
Weight/Price Required (Y/N) N
Deal Quantity (0-99) 0

ITEM TYPE (0-7) 0 0=Normal Sale Item 4=Misc. Sale Item

1=Deposit Item 5=Misc. Refund Item
2=Refund Item 6=Manufac. Coupon Item
3=Deposit Return Item 7=Store Coupon Item

Coupon Family Numbers (0-999): Current Period 0 Previous Period 0

For next page, press PgDn.

If complete, press ENTER.

F1 F2 F3QUIT F4 F5 F6 F7 F8 F9 F10

Figure 69. Add an Award Points with no performance required Item Record -- Page 1

222 Electronic Marketing PRPQ

 DBM1S004 CHANGE AN ITEM RECORD Page 2 of 2

Item Code 312

Description 25 Points
Linked Item Code (0-9999) 0

TAX PLANS: (Type Y=yes if Tax Plan applies, N=no).

Tax Plan A Y Tax Plan B N Tax Plan C N Tax Plan D N

USER OPTIONS: (Type Y=yes if Option applies, N=no).

User Option 1 N User Option 2 N User Option 3 N User Option 4 N
User Data 1 (0-32767) 0 User Data 2 (0-32767) 0

For the following, type Y=yes, or N=no.

Food Stamp Item Y Quantity Allowed Y

Points Apply to Item N Quantity Required N
Discountable Item Y Authorized for Sale Y
Coupon Value Multiplication Y Restricted Sale Hours N
Exception Log Item Sale N Shelf Label Print Allowed Y
Points Only Item Y Item Links To Deposit N
If complete, press ENTER.

F1 F2 F3QUIT F4 F5 F6 F7 F8 F9 F10

Figure 70. Add an Award Points with no performance required Item Record -- Page 2

2. The field that previously displayed “Coupon Gives Bonus Points” in coupon
records now displays “Discountable Item” because the item type is changed to a
normal sale item.

Promotion Code Coupons

An example of a coupon validated by promotion code follows:
COUPON #313 BUY 6oz BLACK CHERRY GELATIN
RECEIVE A 25 CENT DISCOUNT
1. Change the promotion code for the 6oz black cherry gelatin to 313 for
promotion code validation. If this is an electronic coupon, put the coupon
number 313 in the link field of the 6oz black cherry gelatin.
2. Build a store coupon record number 313.

Chapter 7. Operations 223

 DBM1S003 CHANGE AN ITEM RECORD Page 1 of 2

Item Code 313

Description -25 cents
Department Number (1-999) 100

PRICING METHOD (0-5) 3 (3 = Unit Priced Coupon)

Keep Item Movement (Y/N) Y
MFR Number 00000 Price Required (Y/N) N
Coupon Value .25 Weight/Price Required (Y/N) N
Lmt/Tran & Items/Cpn 00 Coupon Sequence (0-20) 0

ITEM TYPE (0-7) 7 0=Normal Sale Item 4=Misc. Sale Item

1=Deposit Item 5=Misc. Refund Item
2=Refund Item 6=Manufac. Coupon Item
3=Deposit Return Item 7=Store Coupon Item

Coupon Family Numbers (0-999): Current Period 0 Previous Period 0

For next page, press PgDn.

If complete, press ENTER.

F1 F2 F3QUIT F4 F5 F6 F7 F8 F9 F10

Figure 71. Add a Promotion Code Discount Coupon Item Record -- Page 1

3. Change the description if needed. The department number for the black cherry
gelatin (dept 100) can be entered, but it is not needed for promotion code
validation.
4. No manufacturer number is needed in the coupon item record for promotion
code validation.
5. Enter the value of the discount in the field for coupon value (25).
6. Change the promotion code number to 313 to match the promotion code of the
6oz black cherry gelatin.
7. Ensure that the option to validate by promotion code (option 20.2) is set.

224 Electronic Marketing PRPQ

 DBM1S004 CHANGE AN ITEM RECORD Page 2 of 2

Item Code 313

Description -25 cents
Linked Item Code (0-9999) 0

TAX PLANS: (Type Y=yes if Tax Plan applies, N=no).

Tax Plan A Y Tax Plan B N Tax Plan C N Tax Plan D N

USER OPTIONS: (Type Y=yes if Option applies, N=no).

User Option 1 N User Option 2 N User Option 3 N User Option 4 N
Promo Code (0-32767) 313 Minimum Purchase Amt 0

For the following, type Y=yes, or N=no.

Food Stamp Item Y Quantity Allowed Y

Item Not in Purchase Minimum N Quantity Required N
Discountable Item Y Authorized for Sale Y
Coupon Value Multiplication Y Restricted Sale Hours N
Exception Log Item Sale N Shelf Label Print Allowed Y
Points Only Coupon N Separate Minimum per Coupon N
If complete, press ENTER.

F1 F2 F3QUIT F4 F5 F6 F7 F8 F9 F10

Figure 72. Add a Promotion Code Discount Coupon Item Record -- Page 2

Percent Off Discount Coupons

An example of a percent off discount coupon follows:
COUPON #314 BUY MILK, 1 GAL
AT 10% OFF
1. Build a store coupon record 314 for milk. Use pricing method 4, this normally
converts the coupon value to the final price. However if the price is entered as
98xxx or 99xxx the final value coupon becomes a percent off coupon. Percent
off coupons can be specified with a price of 98xxx or 99xxx where 98xxx says
to apply the discount to all matching items and 99xxx says to limit the discount
to those items that link to the coupon.
2. Enter the department and manufacturer number for the milk.
3. Enter the value of the percent discount in the field for coupon value (99100).
4. Change the family code to 014.
5. The coupon is linked to milk to provide validation. Change the family code to
014 on the milk. If this is an electronic coupon, put the coupon number 314 in
the link field for the milk.

Chapter 7. Operations 225

 DBM1S003 CHANGE AN ITEM RECORD Page 1 of 2

Item Code 314

Description Save 10% on Milk
Department Number (1-999) 500

PRICING METHOD (0-5) 4 (4 = Coupon value is net item value)

Keep Item Movement (Y/N) Y
MFR Number 11141 Price Required (Y/N) N
Coupon Value 991.00 Weight/Price Required (Y/N) N
Lmt/Tran & Items/Cpn 00 Coupon Sequence (0-20) 0

ITEM TYPE (0-7) 7 0=Normal Sale Item 4=Misc. Sale Item

1=Deposit Item 5=Misc. Refund Item
2=Refund Item 6=Manufac. Coupon Item
3=Deposit Return Item 7=Store Coupon Item

Coupon Family Numbers (0-999): Current Period 014 Previous Period 0

For next page, press PgDn.

If complete, press ENTER.

F1 F2 F3QUIT F4 F5 F6 F7 F8 F9 F10

Figure 73. Add a Percent Off Discount Coupon Item Record -- Page 1

DBM1S004 CHANGE AN ITEM RECORD Page 2 of 2

Item Code 314

Description Save 10% on Milk
Linked Item Code (0-9999) 0

TAX PLANS: (Type Y=yes if Tax Plan applies, N=no).

Tax Plan A Y Tax Plan B N Tax Plan C N Tax Plan D N

USER OPTIONS: (Type Y=yes if Option applies, N=no).

User Option 1 N User Option 2 N User Option 3 N User Option 4 N
Promo Code (0-32767) 0 Minimum Purchase Amt 0

For the following, type Y=yes, or N=no.

Food Stamp Item Y Quantity Allowed Y

Item Not in Purchase Minimum N Quantity Required N
Discountable Item N Authorized for Sale Y
Coupon Value Multiplication Y Restricted Sale Hours N
Exception Log Item Sale N Shelf Label Print Allowed Y
Points Only Coupon N Separate Minimum per Coupon N
If complete, press ENTER.

F1 F2 F3QUIT F4 F5 F6 F7 F8 F9 F10

Figure 74. Add a Percent Off Discount Coupon Item Record -- Page 2

226 Electronic Marketing PRPQ

Chapter 8. Electronic Marketing Processing
This chapter discusses home store processing as well as the processing of
customer identification cards, coupons (electronic, targeted, and redemption), and
points. It also describes how Electronic Marketing accumulates totals.

Support for Home Store Processing

Home Store Concept Supported Mainly by In-Store Processing

An enterprise that uses the home store concept can imbed home store numbers in
each customer identification number. (For more information on specifying an
imbedded home store number in a customer ID number, see “Home Store Location
in Customer Number” on page 100). The customer number should contain a home
store number if preferred customers are allowed to shop at multiple stores and have
points transferred to their home store. When preferred customers shop at a store
other than their home store, the Electronic Marketing application code creates a
transfer record that contains a record of the transaction. Host support is needed to
collect the transfer records and distribute them to a customer’s home store. Once
the transfer records are in a customer’s home store, the Electronic Marketing
application handles the processing needed to update customer records with their
out-of-store shopping activity. The option “Create and Access Customer Transfer
File” on page 86 must be set to support this transfer activity.

Home store numbers are useful only if points are accumulated for customers or
targeted coupons are used. Normal preferred customer coupons are given to all
preferred customers regardless of whether they are shopping in their home store.
The home store concept facilitates tracking and combining a customer’s points
activity and targeting coupons when the customer shops at multiple stores.

Home Store Concept Supported Mainly by Central Site Processing

If customer numbers do not contain an imbedded store number but the options
reference a nonzero area as the store number and define no home stores, any
identification number that is on file is processed as a home store customer number,
but any identification number that is not on file is processed as a non-home store
customer number. Customers who do not have an identification number on file are
not home store customers and are not automatically added to file. As no customers
are processed in this store only, all points activity is transferred out of store. The
transfer records contain a correct origin store, but the destination store must be
altered to the correct number by the central site process. Redemption of points is
allowed only for customers who have an activity record on file. Central site
processing would have to be written to assure that the needed activity records are
added in the right stores and that points updates are transferred to the right stores
to ensure that the lack of a store number in a customer’s identification number does
not cause any loss of function. This process would have to accomplish the
following:
v Determine the home store(s) for each customer
v Ensure that an activity record is present in each home store for every customer
v Route activity updates from non-home stores to the correct home store(s) to
ensure that points totals and targeted coupons are correct in each store where a
customer has an activity record.

© Copyright IBM Corp. 1991 2000 227

Support for No Home Store
If an enterprise does not define a store number field in the customer number, all
customers are considered home store customers and no points are transferred out
of store. If customers shop in multiple stores, each store keeps their activity history
without any knowledge of activity in any other stores. With this set up, each store
appears to have its own unique preferred customer program.

Support for Multiple Home Stores

Each time that a customer number is entered at a register, the customer activity file
is read to see whether the customer has a history of activity in this store. If there is
an activity record for a customer on file in this store, the customer is processed as
a home store customer regardless of their actual home store. This can be used to
allow a customer to have multiple home stores or even to allow special customers
to be “at home” in every store. The concept of multiple home stores is supported
through the options and the activity transfer process. But it requires an additional
network load to maintain duplicate activity data in multiple stores and is not
recommended. Even if an enterprise chooses to support multiple home stores in
which customers are shown their name and points history, redemption of points is
allowed only in the primary home store in which a customer enrolled. Non-home
customer records can be set in a store so that a customer is recognized by name
and all customer input data is present, but all points processing is handled as
though the customer were not on file. This provides a middle ground where
customers are recognized in multiple stores but point totals are kept only in the
home store and minimizes the network load.

Customer Identification Number Processing

This section describes how customer identification numbers are validated and how
they can be linked so that two or more numbers reference the same primary activity
record.

Validating a Customer Identification Number

Each time a customer presents a customer identification card at a checkout
transaction, a process is initiated to ensure that the identification number is valid for
use in the store.

Searching for a Customer ID in the Customer Activity File

Using a customer’s identification number, the application first searches for the
customer’s activity record in the store’s Preferred Customer Activity File.

If access to the customer activity file fails, the application bypasses the failure to
allow sales to continue. If the failure is a terminal offline condition, a base
Supermarket system cannot support preferred customer totals or electronic
coupons. However a Supermarket system with the Terminal Offline feature installed
has a subset of the Item Record File still available to the terminal in RAM and can
process electronic coupons if its records reside in RAM.

If a customer’s activity record is found in the store’s Customer Activity file, the
customer is an existing customer and is processed as a home store customer.

If a customer number is not found in the activity file, it is one of the following types:
v A new customer number (a customer has not yet enrolled)
v An invalid customer number (perhaps miskeyed)

228 Electronic Marketing PRPQ

 v A customer number for another home store.
If the customer number contains a home store number, the identification number is
validated against a range of valid store numbers. If the store number does not
validate, the customer number is rejected as an invalid number with an appropriate
operator guidance.

If the option to check to use the validation digits in customer numbers is set (see
101) these digits are checked next. If the designated positions in a customer
number do not contain the defined digit values, the customer number is rejected as
invalid number with an appropriate operator guidance. This option is used to reduce
the chance that a competitor’s customer card might be mistakenly accepted as a
valid card at your store. These validation digits are not checked for a customer
number that is found in the customer activity file.

If a customer number contains a valid store number that does not match this store,
it is accepted as an non-home preferred customer number. A Customer with such
an identification number is processed as a preferred customer, but receives only
limited recognition and awards at this time. Customers do not see their name or
activity history (and cannot receive any points-related awards), but does receive any
applicable discounts that are available to all preferred customers through electronic
coupons.

If a customer number is not found in the activity file and either no store number is
imbedded in the customer number or the imbedded store number matches this
store, this is a new customer. The operator is prompted to verify a new customer
number (to ensure that it was not entered incorrectly) and, after this operator
override, the new customer number is automatically added to the activity file and
processed. Options allow a manager’s override to be required to accept a new
customer number (see “Manager’s Override Required for New Customers” on
page 90). This might be useful once a stable enrollment base has been achieved to
assure that new customers are enrolled before they shop. Another option requires a
manager’s override for any keyed account number (see “Keyed Customer Numbers
Require a Manager’s Override” on page 88). This can help an enterprise to avoid
fraud when all preferred customers are expected to have a scannable card.

Using a Customer Number as Tender Verification Number

Options allow the preferred customer number to be used as the tender verification
account number for selected tenders (see page 122). If customers identify
themselves as preferred customers in a transaction in which they present a tender
requiring an account number, this prompt for a tender account number is bypassed
and the preferred customer number is automatically entered. Options also allow an
alternate account number to be assigned to the preferred customer and to be used
for tender verification (see page 123). This alternate account number may be a
preexisting credit account or courtesy card number. The alternate account number
is automatically substituted as the tender verification account number for the
selected tenders when a preferred customer has identified him/herself earlier in the
transaction and an alternate account number is available for the preferred customer.
These tender verification options allow the preferred customer card to be the only
card that a customer needs to present.

If an alternate account number is selected as the verification number for a tender,

this number needs to be entered into the system only once for each preferred
customer. The alternate account number is prompted for at the point of sale when it
is not present and then saved for future use. A courtesy card number would be
requested for a check tender even for a preferred customer if this number was not

Chapter 8. Electronic Marketing Processing 229

 on file and checks are selected for alternate account verification. This would happen
only once per preferred customer; the next time a preferred customer tendered a
check, the system would already have their courtesy card number saved with their
preferred customer number. The saved alternate account number can be changed
by a manual entry of a new account number using the VERIFY key during the
tender key sequence. This override of a saved account number can optionally
require an operator’s or manager’s override sequence for security (see “Override Is
Required to Change Tender Verification Number” on page 124 and “Operator’.s
Override Is Sufficient to Change Tender Number” on page 124). If both the preferred
customer number and the alternate account number are selected for use with the
same tender, the preferred customer number is used if the alternate is zero and the
alternate remains zero until an account number is manually entered. This use of
both numbers for the same tender provides a migration path from courtesy card
numbers to preferred customer numbers.

Alias/Primary Record Pair Processing

A customer’s activity record can refer to another customer’s activity record in order
to allow multiple customer identification numbers to do the following:
v Access the same primary activity record
v Contribute to and redeem from the same points total.
A customer activity record that refers to another, primary activity record is called an
alias activity record. (See “Alias Customer Activity Records for Family Members” on
page 13 .) Alias activity records are linked to primary activity records to activate this
relationship. In an alias/primary record pair, a customer’s name, identification
number, and lower half of the flag bits from an alias record override a customer’s
name, identification number, and low order bits from a primary record. This allows
the system to recognize and process individually different aliases for the same
primary activity record, within the limits of the overlaid information.

Electronic Coupon Processing

This section explains how electronic coupons are awarded, distinguished from other
types of coupons, processed, and maintained.

Awarding Electronic Coupons during Sales

Terminal Sales processes an electronic coupon through an item record that links it
to another item. If an enterprise has designated a velocity code range for preferred
customer electronic coupons (see “Coupon Velocity Code Range for Preferred
Customers” on page 97), the terminal compares an electronic coupon to this range
and processes the coupon as follows:
v If a coupon falls outside of the range, the terminal processes it according to its
type.
v If a coupon falls within the range, the terminal processes it only if a customer has
presented their preferred customer identification number. If customers have not
identified themselves yet, the terminal saves the electronic coupon for possible
processing later in the transaction. Customers receive all valid coupons when
they present their customer ID number.
After the terminal has received an electronic coupon and determined whether it is a
preferred customer or non-preferred customer coupon, it performs standard coupon
validation.

230 Electronic Marketing PRPQ

Distinguishing Electronic Coupons from Other Types
Electronic Coupons and Paper Coupons
Electronic coupons are treated similarly to paper coupons. Like paper coupons,
electronic coupons may be defined as store or manufacturer coupons, depending
on the source of the promotion money and the consequent taxability of the
coupons. However, the following distinctions apply to electronic and paper coupons:
v Electronic coupons are never doubled as an equivalent paper coupon might be.
v If an electronic coupon cannot be accepted for any reason (for example, file data
invalid, minimum purchase requirement not met, limit exceeded), an operator
guidance is not displayed. Operator guidance might confuse both the operator
and the customer because the coupon was presented and rejected automatically.
The coupon error condition is printed on the journal to provide an audit trail that
can be used if customers question why a specific electronic coupon was not
awarded to them. Since non-preferred coupons with a minimum purchase
requirement will always be delayed until total time, no B612 error message will
print for these coupons. An option is provided to bypass coupon validation.

Electronic Coupons and Preferred Customer Coupons

Any coupon that is automatically linked in from an item sale is an electronic coupon
because there is no accompanying paper in the cash drawer to account for the
coupon. Unlike preferred customer coupons, electronic coupons can be awarded to
all customers, not just preferred customers.

A preferred customer coupon can be a paper coupon (represented by a UPC within

the preferred customer range) or an electronic coupon. A preferred customer paper
coupon requires a preferred customer identification number for the item or coupon
associated with the UPC to be sold or redeemed.

Different Behavior of Non-Preferred Customer Electronic

Coupons
While electronic coupons can be set up to apply to Preferred Customers or to all
customers, non-preferred electronic coupons with a minimum purchase requirement
behave differently than similar preferred coupons. If there is a minimum purchase
requirement on a non-preferred electronic coupon, then the coupon is delayed until
total time so that the final transaction total can be compared to the minimum
purchase requirement. Available preferred coupons begin to be given as soon as a
customer number is entered. Once the customer number has been entered and a
preferred coupon that requires a minimum purchase is processed and the minimum
is met then the coupon is immediately given. If the minimum is not met then the
coupon is rejected. Any electronic coupon which is rejected at the time the
promoted item is sold is automatically re-tried at total time. If the customer number
is entered at the end of a transaction at total time then the preferred coupons will
be given then and there will be no problem with minimum purchase requirements.
Thus a preferred coupon with a minimum order size requirement may be given after
customer identification, after the promoted item, or at total time while a similar
non-preferred coupon will only appear at total time.

Implementing Cross-Promotional Electronic Coupons

Because of their positional dependence in an order, cross promotional coupons
must be carefully implemented if you wish them to immediately follow the promoted
items. If it is acceptable to present these coupons at total time, then no extra care
need be taken. To make a discount on item B conditional on the purchase of item
A, then you need to make a fake cross promotional coupon that validates against
item A and link it to a discount coupon that validates against item B.

Chapter 8. Electronic Marketing Processing 231

 If you want this coupon to be given immediately after the purchase of either
promoted item, then both item A and B need to be linked to coupon A which links to
coupon B. This will insure that the coupon is given after the last promoted item is
purchased regardless of the order in which the items are purchased.

Note: If the cross promotional coupon links to a Pricing Method 4 “net value“
coupon, then the coupon chain can be linked only from the item to be
discounted. If coupon B is a net value coupon for item B, then only item B
can be linked to coupon A.

While it is suggested that all electronic cross promotional coupons be set up using
fake coupons which are linked to all promoted items, it is only necessary to link the
coupons to any one of the promoted items in order to get the discount. In this case,
the discount will probably be given when a total is taken after all necessary
promoted items have been purchased.

It is suggested the real discount coupon be linked (perhaps indirectly) to the item
being discounted and that it be set up to validate only against the item being
discounted. For pricing method 4 “net value” coupons, it is required that the coupon
be linked only to the item being discounted to insure the correct item value is
discounted.

While you might link a coupon to item A that validates against item B to implement
a cross promotion, this may result in an incorrect coupon value for some complex
coupons such as weighted coupons or final value coupons.

Effect on Performance
In general, electronic coupons have no greater impact on system performance than
do equivalent paper coupons. The system accesses the linked-to coupon record
only for preferred customer electronic coupons, not for non-preferred customer
coupons. There is only one circumstance in which the system must access the
linked-to coupon record more than once. When a transaction that involves
promotional items is transferred to another terminal through the terminal transfer
procedure or a suspend/retrieve procedure, the system must access the coupon
record once for each promotional item.

Effect on Taxes
The package provides an additional function, to be used when you choose not to
validate electronic coupons, that prevents any store coupon or doubled coupon from
causing the taxes for a transaction to be negative. This is achieved by making store
and doubled coupons non-taxable if they would drive taxes negative. However,
there would be no need for this function if all coupons were validated as provided
by the Supermarket Application.

Electronic Coupon Maintenance

This section describes how to handle electronic coupons linked to items with
deposits and electronic coupons that apply to multiple promotional items. It also
discusses system considerations for electronic coupon processing.

Processing Electronic Coupons Linked to Items with Deposits

Electronic coupons are processed by being linked to items through item records.
There are two methods by which an electronic coupon can be linked to an item with
a deposit.

232 Electronic Marketing PRPQ

Basic Method: linkage requirement can cause problems in the case that a
preferred customer electronic coupon is linked to an item that has a deposit. If a
linked record fails, the electronic coupon chain is broken. Also, if an electronic
coupon that applies to an item with a deposit is linked from the deposit as
illustrated,
Basic Method SODA →link→ BOTTLE DEPOSIT →link→COUPON

a deposit item record must be created. A new deposit item record is required for
every new promotion of a set of items with a common deposit amount. The creation
and deletion of these deposit records add a great deal of overhead to the process
of establishing promotions. The Electronic Marketing package provides an
alternative means to handle such electronic coupons that does not require the
creation and deletion of deposit records.

Alternative Method: The alternative method allows an electronic coupon record to

be linked to an item and its associated deposit as illustrated:
Alternative SODA →link→ COUPON --link→ BOTTLE DEPOSIT

In order for the alternative method to work, the item at the beginning of the linked
chain must be marked to show that a deposit item is expected at the end of the
chain. If you perform this method without marking the first item in the chain, the
deposit is not charged unless the coupon is given. When the item sale is correctly
marked, the deposit is always charged, whether or not the coupon is given.

Items that link to deposits are marked by turning on the last reserved flag (X'10') in
the last flag field in the item record (INDICAT1A) For more information how linkage
items are marked, see “Links to Deposit” on page 344.

You can implement this deposit alternative by turning on the flag for each item in
the item file that links to a deposit item and applying the promotions without regard
to the flag. A better way is to turn on the flag when the link field is changed to insert
a coupon between an item and its deposit. The best solution may be to combine
both of these methods. This would assure that, in all cases involving items linked
through an electronic coupon to a deposit, the deposit is charged whether or not the
coupon is redeemed.

Processing Promotional Items

A single electronic coupon may apply to more than one item. It requires more than
simple file maintenance to link all of the promotional items to which an electronic
coupon might apply. It is necessary to do the following:
v Identify all of the UPCs that represent the items being promoted
v Alter the link field in the item records for each item to point to an appropriate
coupon.
The Selective Item Record Report identifies the UPCs affected through a search
based on item descriptor, manufacturer, item code range, and department and/or
price range. (See “Selective Item Record Report” on page 250.) This report can also
build maintenance batches to update the link field and perhaps the family code or
promotion code in the selected items.

These batches are subject to a potential timing problem. Preparation of the batches
must begin considerably in advance of the promotion, because the work involved in
building, testing, and transmitting the batches takes time. But, it is best to build the
batches as close as possible to the time that they will be executed. This reduces
the possibility that the batches erroneously set an item price back. These conflicting
needs can be met by doing the following steps:

Chapter 8. Electronic Marketing Processing 233

 v Preparing the batches ahead of time
v Updating the link data as soon as the batches are ready
v Linking the items to coupons that are flagged as “Not For Sale.”
These steps allow the large portion of item file changes to be made quickly, in
advance, and in manageable pieces, through immediate rather than delayed
updates. The promotions can be activated simultaneously by turning off the “Not for
Sale” flag in the new coupons. This can be accomplished by using the Selective
Item Record Report or by a maintenance batch. This approach takes advantage of
the following facts:
v It is much easier to perform maintenance on the electronic coupons than on the
items to which they apply.
v An electronic coupon that is marked as “Not for Sale” has no impact when
accessed through a link from an item sale.

Coupons marked as not for sale will process normally (as though marked for sale)
in training mode so that the promotions can be tested before being activated. In
addition, while in training mode in a coupon only transaction, the limits on like
coupons are bypassed and coupons are not doubled.

System Considerations: Host and Controller

Electronic coupon maintenance may be best handled by a combination use of the
in-store controller and the host system. An enterprise may want to handle all
electronic coupon maintenance from a central host system. But it may be difficult to
develop a system that can identify all UPCs to which an electronic coupon might
apply and create maintenance to link these UPCs to the correct coupon. To avoid
this complex host coding, an enterprise can use the in-store facilities of the
controller to build and test the appropriate maintenance batches on a controller, and
then use the host system only to distribute these batches to the stores that need
them. This procedure requires that all price maintenance be kept up-to-date on the
controller and that price changes made from the host do not overlay the link fields
set up from the controller maintenance batches.

The Electronic Marketing package provides functions that enable an enterprise to

change either the link only or the price only.
v The Alternate Delayed Data Maintenance Interface (ADDMI) is an optional
controller function that converts item record maintenance information from a
predefined format into source files and control records to be processed by the
Delayed Data Maintenance (DDM). ADDMI can be used to make link-only
changes. This isolates coupon-linking maintenance from price changes.
v ADDMI or Delayed Data Maintenance (DDM) can be used to make price-only
changes. This isolates price changes from coupon-linking maintenance.

The package provides source code changes to prevent all or selected DDM batches
from updating the link and family code fields. Based on these source code changes,
an enterprise can write source changes to prevent the coupon-linking batches from
updating prices in a store.

Targeted Coupon Processing

This section describes when to enter a customer identification number with targeted
coupons, how to validate and reuse targeted coupons, and how to define targeted
coupons in a rain check record.

234 Electronic Marketing PRPQ

Entering a Customer ID with Targeted Coupons
The order in which a customer identification number is entered in relation to
targeted coupons can affect processing of targeted coupons.

System Considerations
The system performs better when processing targeted coupons if a customer
identification number is entered after all sales. The reasons for this are as follows:
v If a customer ID number is entered before the sale of (an) item(s) linked to a
coupon targeted to the customer, the system compares the subtotals at that
point, not the total at the end of the transaction, to the conditions for accepting
the coupon. If all conditions are not met when (an) item(s) linked to a targeted
coupon are sold, the following results may occur:
– A targeted coupon may be given after a total is taken if the minimum
purchase is met by total time.
– If the system has timed out, an operator may be required to take a manual
total prior to tendering, even though the results of an automatic total are being
displayed.
v A targeted coupon may need to be processed multiple times if a customer ID
number is entered at the start of a transaction. But it needs to be processed only
once if a customer ID number is entered at the end of the transaction.
v If the customer ID number is entered at the start of a transaction, a noticeable
lag may occur between the display and print of the total in a transaction involving
targeted coupons.

Performance Impact
The order of a customer identification number and the sale of promotional items
impacts the performance of this package if the following types of coupons are used:
v Coupons that require multiple purchases
v Coupons that require a minimum transaction size
v Coupons that are targeted to specific customers.
Terminal Sales must check these limits after every matching item to determine the
validity of outstanding coupons. This potential performance impact is significant
because it occurs during item entry. The system requires fewer item record lookups
in these cases if a customer ID is entered after all sales are entered.

Validating Targeted Coupons

In general, the same validation conditions that apply to all other preferred customer
coupons (including item matching, manufacturer matching, department matching,
minimum purchase requirements, and multiple sales requirement) also apply to
targeted coupons.

In order to process targeted coupons, an enterprise must select the option to

validate preferred customer coupons (see “Validate Automatic Preferred Customer
Store Coupons” on page 88) and provide the necessary validation data in the
coupon records. This validation data includes manufacturer, promotion code, family
code, and minimum purchase requirements.

Validation for targeted coupons serves a different purpose than validation for
electronic coupons. Electronic coupons are linked to items. The system does not
access electronic coupons unless the linked-to item(s) have been purchased.
Validation is needed only to prevent a paper and an electronic coupon from being
taken on the same item or to require multiple items to be purchased before the

Chapter 8. Electronic Marketing Processing 235

 discount is awarded. Targeted coupons are linked to customer records, not item
records. Validation is critical for matching targeted coupons with required
purchases.

A targeted coupon usually takes precedence over a normal preferred customer

coupon in cases when both are available on the same item. However, if both types
of coupon are available on an item and the validation conditions for the targeted
coupon are not met, the normal preferred customer coupon can be given. In this
case, the preferred customer coupon cannot be awarded until total time. For
example, if a preferred customer buys one of an item for which a preferred
customer coupon gives $.20 off and a targeted coupon gives $.50 off for the
purchase of two, the customer receives the $.20 preferred customer discount at
total time.

Defining Reuse of Targeted Coupons

An option (see “Velocity Code Range for Reusable Targeted Coupons” on page 97)
defines the range of preferred customer coupon UPC’s that are reusable when
targeted. A Targeted coupon that is not reusable is available to selected customers
until they take advantage of it in a transaction. Once the targeted coupon is used, it
is automatically removed from the activity file and the remaining targeted coupons
are compressed toward the front of the record. If a targeted coupon is in the
reusable range, then it may be reused by the customer until action is taken from the
record. Either the limit of coupons per transaction or the quantity allowed flag in the
coupon record (see “Coupon Quantity Limit” on page 342) can be used to restrict
the number of times a targeted coupon is allowed in a transaction.

By either of these means, targeted coupons can be defined for a single usage, a
limited usage, or unlimited usage in a single transaction. This control enables you to
define the availability of a targeted coupon as follows:
v Only once in one transaction per customer
v For any number of times in one transaction per customer
v Only once per transaction for any number of transactions (perhaps with a
minimum purchase requirement)
v For any number of times per transaction for any number of transactions until the
promotion is over.

If you define a targeted coupon that does not require a matching purchase or a
minimum amount of purchases, you must limit the usage of the coupon in a
transaction because the code does not otherwise define the number of coupons to
give. If you define a targeted coupon that is not linked to a particular item but has a
minimum purchase requirement, (for example, $.50 off on $10.00 of meat
purchased), this coupon will be given for each multiple of the minimum purchase
that is satisfied up to the coupon limit defined for the transaction.

One method of allowing a customer to take advantage of a promotion two times is

to target two of the same coupon to a customer.

All targeted coupons used are logged in a special data entry string in both the
Transaction Summary Log and the Panel Diary File. This is done regardless of
whether the coupons are reusable.

Maintaining Targeted Coupons in the Customer Activity Record

When a coupon is automatically removed from a customer activity record, the
remaining available coupons are compressed toward the front of the activity record.

236 Electronic Marketing PRPQ

 The coupons at the front of the targeted coupons list are considered to be older
than those at the end of the list. If two coupons are available to the same customer
for the same item, the oldest one is used first. But, when the list of available
coupons is printed on a customer’s receipt at the end of a transaction, the newest
coupons are printed first.

Defining Targeted Coupons in the Rain Check Record

An alternative way to give selected electronic coupons to all preferred customers is
to define them as targeted coupons in the rain check record. If a selected coupon is
to be awarded to all preferred customers and applies to many items, it may be
simpler to process it as a targeted coupon in the rain check record than as an
electronic coupon linked to all promoted items. If the coupon is properly validated
against all matching items, the results are the same as if the coupon were linked to
all promoted items. For example, if you want to give all preferred customers $1.00
off on any $10.00 purchase of wine, you can link the coupon to all wine item
records, or you can target the coupon to all preferred customers by putting it in the
rain check record. In either case, the coupon must validate against sales from the
wine department. If the coupon must be linked to many item records, the rain check
alternative may be easier to implement than electronic coupon linkage. But, the rain
check targeting alternative should be used only when the coupon applies to a large
number of items that are in a single validation group, such as all items from a
manufacturer category or a department, because targeted coupons are not as
performance sensitive as electronic coupons linked to items.

In general, targeted coupons defined for all preferred customers in the rain check
record are treated like coupons linked from item records instead of like targeted
coupons. They differ from true targeted coupons in the following ways:
v Coupons targeted to specific types of customers take precedence over coupons
targeted to all customers through the rain check record.
v True targeted coupons are printed on a customer’s receipt as available for the
next visit. Targeted coupons in the rain check record are not.
v Use of true targeted coupons can be limited to a single transaction per customer.
Targeted coupons in the rain check record are available to every preferred
customer transaction regardless of prior usage.
Targeted coupons in the rain check record differ from item-linked electronic coupons
in that they must be set up to validate against matching items.

Redemption Coupon Processing

A redemption coupon has all the validation and limitation properties of a normal
coupon. The unique validation functions of the coupon processing enhancements
limit the necessary validation process to checking points coupons against only the
selected items and prior entries of the same coupon. A manufacturer coupon, a
store coupon, and an unlimited number of different points coupons can be taken on
the same item.

The redemption of points is possible only in a customer’s home store. This

restriction might be removed in the future through an option however, the restriction
is useful because it prevents customers from redeeming the same points in multiple
stores and causing their points total to become negative.

A customer may redeem points through either a checkout transaction or an in-store

enrollment procedure. Redemption of points through an in-store enrollment method

Chapter 8. Electronic Marketing Processing 237

 may be more cumbersome than through a checkout transaction, but it offers a level
of accountability not possible at point of sale.

An expected usage of redemption coupons is to provide a discount on a purchased

item in exchange for redemption of points. The system provides the necessary data
base support for redeeming points by accumulating a total of redeemed points.
Redemption of points reduces only the total of redeemed points and the net total of
points, not the total of accumulated points.

Points can be redeemed in exchange for a discount on an item by linking a

redemption coupon to a normal discount coupon. The redemption coupon should
contain the same coupon validation data as the discount coupon to which it links.
The following conditions apply:
v A customer must have purchased the item to be discounted.
v A customer must possess adequate points. Neither the redemption coupon nor
the discount coupon for the linked-to item is accepted unless there are sufficient
points to exchange for this discount. If there are insufficient points at tender time,
either the redemption coupon must be cancelled or a manager’s override is
required.
v The redemption coupon is not accepted unless all other records in the chain are
accepted.
These conditions ensure that either both the redemption coupon and the discount
coupon are accepted or neither is accepted.

If a discount coupon is linked to a redemption coupon, the points are redeemed

whether or not they are present because the discount has already been given. If a
customer’s points are negative at the end of the transaction, a manager’s override
is required to end the transaction. A transaction cannot end if the redeemed points
for the transaction are negative due to more cancels than entries.

Point Processing
The Electronic Marketing feature computes the points associated with each
preferred customer transaction and saves a cumulative point total for each preferred
customer. For an enterprise using the home store concept, the point total is
maintained only in a customer’s home store(s). Points from visits to other
participating stores can be transferred back into the home store if the appropriate
host support is provided. For an enterprise not using the home store concept, all
stores are essentially primary home stores. In this case, each store can maintain its
customers’ point totals.

Items can be marked to not contribute to points totals (see “Items Not Eligible for
Points” on page 343). Also, a points-to-cents ratio can be defined so that points
equal only a fraction of sales (see “Ratio of Points Per Cents Purchased” on
page 92).

Linkage of Points-Only Items

The capability to link one item record to another provides a powerful tool whose use
is critical to this feature. The order of linked items and the number of items in a
linked chain are useful parameters that you can adjust to meet many needs you
follow a few rules.

The first item in a linked chain that is rejected (perhaps due to failed coupon
validation or too many coupons) breaks the chain and no items past that one in the

238 Electronic Marketing PRPQ

 chain are processed. For example, if a discount coupon for a specific item is linked
to a bonus item and the discount coupon fails to validate, the bonus is not given. If
you want to give bonus points for each item purchased but discounts for only the
first three items, you must link a bonus coupon (that validates the item) to the
discount coupon.

If a preferred customer number has not been entered, the first linked item code in
the designated preferred customer range (see “Coupon Velocity Code Range for
Preferred Customers” on page 97) causes the rest of the linked chain to be saved
for possible processing later in the transaction when the customer ID is entered.
You may want to certify that all preferred customers with adequate points who
purchase a particular item exchange redemption points for a discount on that item.
You can accomplish this by the following steps:
1. Linking the promotional item to a redemption coupon (using a code in the
designated range)
2. Linking the redemption coupon to a discount coupon.
In cases such as this, the usage of an item code within the designated range for
preferred customers restricts the redemption coupon to preferred customers.

Acceptance of a redemption coupon that links to another record in a transaction in

which a customer has adequate points is deferred until either the linked chain has
been successfully ended or another redemption coupon is encountered in the chain.
If you want to print a paper coupon worth either a $.50 discount in exchange for
100 points or a $1.25 discount in exchange for 200 points, you can accomplish this
by the following steps:
1. Create a 100 point redemption coupon (using the item code you want to be
printed on the coupon).
2. Link this 100 point redemption coupon to a $.50 discount coupon.
3. Link this $.50 discount coupon to another 100 point redemption coupon.
4. Link this 100 point redemption coupon to a $.75 discount coupon.
Linkage of points items provides a great deal of power and flexibility. Any of these
coupons in the chain may or may not require the purchase of a specific item,
require a minimum purchase amount, or limit the number available per customer.
Also, different coupons in the chain may require the purchase of different items.

Any redemption coupon which links to a discount coupon should contain the same
validation data as the discount coupon.

Point Eligibility
Although the majority of preferred customers are eligible to receive points, some
options affect point eligibility. Processing flags in each preferred customer’s record
allow a user to indicate to Terminal Sales whether a customer should receive
messages, points, and other privileges. If the flag indicating that a customer should
not receive points is on, points (bonus and transaction) are not awarded.

Primary, local, and visiting customers are entitled to receive points for their
transactions in any participating store if an enterprise provides the host support
necessary to transfer any points they accumulate back to their home store.

In addition, you may use personalization options to override flags in a customer’s

record. See “Deactivate Activity Options for All Preferred Customers” on page 84

Chapter 8. Electronic Marketing Processing 239

 and “Activate Activity Options for All Preferred Customers” on page 84. If you set
these store options to not allow points, customers do not receive points from the
store.

Points Multiplication via Customer Activity Record.

Selected Preferred Customers can be individually targeted for points multiplication
through the activity file. These point increases range from 10% to 990% and apply
to all points received from sales or bonus points other than boundary bonuses. For
example, a 1 in the point multiplier field would increase the points a customer
receives in a transaction by 10%. A 10 in the point multiplier field would increase
the points a customer receives by 100%. A 99 in the point multiplier field would
increase the points a customer receives by 990%. The points multiplier that is
specified in the Rain check record applies to all customers who have no points
multiplier targeted to them. Changing the Rain check points multiplier field provides
a technique for increasing points and thus encouraging shopping during selected
times of the week.

Customer Point Adjustments at the Controller

The enrollment procedure allows a store to interactively access customer points and
change them in the following ways:
v Adjust points
v Redeem points
v Redeem rain check
v Display, change, or erase customer points.
When points information is changed at the controller, information about the change
is logged in the Preferred Customer Audit Log (see “Preferred Customer Audit Log
(EAMFBAUD)” on page 327). The Customer Audit Log optionally can be appended
to the Customer Diary file so all information on changes to customer point totals
can be stored in one file for processing by other programs and systems as needed.

Referenced Account Point Processing

The enrollment procedure allows an account to contribute all earned points to a
referenced account. The processing of referenced accounts is done periodically by
a background program which moves all points from primary accounts to referenced
accounts. This applies only to referenced accounts which are not family, since
updates to family references are immediate.

This reference processing provides a means of moving point and history information
from one account number to another when a lost card is replaced. The old (lost
card) account must be updated to reference the new (replacement card) account as
a non-family reference, and the old account is closed out by placing the 4 character
identifier (*old) anywhere in the second address line. When the background
reference processing program encounters the closed out record, it will move all
history and demographic data as well as the points to the referenced account. (See
“EAMUREFA - Preferred Customer Reference Processing” on page 293 for more
information on this program).

Support for Periodic Points Totals

While the total points earned, total points redeemed, and total transactions are
accumulated for the lifetime of each Preferred Customer, these same totals are now
also accumulated for periodic intervals. Options allow these periodic totals to be
used for points boundary processing, points redemption, customer messages, and

240 Electronic Marketing PRPQ

first time customer coupons rather than the lifetime totals. This allows a promotion
to show a customer only the points accumulated in this time period and only
redeem from these points. It also allows coupons to be targeted to all Preferred
Customers for their first transaction in the time period and allows boundary bonuses
to be given to those who exceed a points boundary during the time period.

The length of the time period for accumulating period points totals is determined by
how often these totals are reset. While these totals might be simply zeroed in all
activity records through a single input record to the Batch Maintenance Utility, a
special program is provided to close the points activity period. This background
program can be initiated manually in the store through a menu selection or through
the background program activation screen. It is suggested that this program be
started automatically by the normal store close processing. A program is provided to
manually start the close of the points activity period from the user procedures menu
and an option is provided to cause the points activity period to be automatically
closed at the proper interval based on a daily store close. It is anticipated that the
points activity period will be closed weekly, monthly, bi-monthly or quarterly while
the close of a reporting period is usually performed daily. Along with rolling over the
three periodic totals mentioned above and resetting the period start date, the close
activity period procedure also saves the previous period point totals for further
processing, optionally assigns automatic transaction discount groups to Preferred
Customers based on points earned in the period, and creates a status report that
summarizes the activity for the period.

Rather than just clear the point totals, the period close procedure will subtract the
earned points from the redeemed points if more were redeemed in the period than
earned and if period points are being used for redemption. Along with this potential
negative carryover, a maximum positive carryover amount can be defined in the
options to allow unused points to carry from one period to another if period points
are being redeemed. This option allows points to carry over from one period to
another while limiting the points buildup. Point ranges can be defined with
associated transaction discount groups to reward customers with transaction
discounts in the next period based on their volume of purchases in the prior period.
The period totals for each customer along with any points carryover amount and
prior discount group are saved in a previous activity file along with the start and end
dates for the period and the most recent purchase date and amount. Either a single
record for the most recent period or a record for each month in which a period was
closed can be kept for each customer. A period summary report is printed and is
saved in the Manager’s Message file at the end of each close of a points activity
period. The summary data varies with options, but includes the total points activity
for the period, counts of active and inactive records during the period, counts of
customers who ended the period in each defined point range, and the points status
at the start of the new activity period.

There are many ways of using the periodic point totals. Even if points are not
redeemed or shown to customers, the periodic points can be used to track
preferred customer activity over larger times than the normal reporting period.
Period points can be used for redemption rather than total points to limit the buildup
of points liability. The ability to carry a limited number of points from one period to
another allows customers a reasonable time to redeem points while still
encouraging them to redeem their points regularly in order to avoid loosing them.
Coupons and messages targeted to the first shopping trip in each period helps to
keep promotions active for all Preferred Customers as do boundary bonuses based
on purchases in the period. The automatic assignment of transaction discount

Chapter 8. Electronic Marketing Processing 241

 groups to Preferred Customers based on their purchase activity during a period
provides a totally different way to build and reward loyalty and volumes from
Preferred Customers.

Automatic Discounts via Customer Activity Record

Preferred Customers can be selected for automatic transaction discounts or tax
exemptions through definition of a discount group number in the selected activity
records. Automatic discounts or tax exemptions can be given to Preferred
Customers either as a reward for Preferred Customer activity or just as a way of
automatically recognizing that this customer is due a discount or tax exemption
independent of his Preferred Customer status. When a valid discount group number
that is defined in the terminal options is specified in the activity record for a
Preferred Customer, the Preferred Customer automatically gets the transaction
discount and/or tax exemption available to the specified discount group. This
automatic discount processing has the same effect as a keyed discount at the end
of a transaction, except that there is no upper limit imposed on the size of an
automatic discount or tax exemption and the operator need not be authorized to
give manual discounts. Options allow transaction discounts to be automatically
assigned to Preferred Customers at the close of a points activity period based on
the points earned during the activity period.

An automatic discount will appear on the customer receipt when the Preferred
Customer number is entered (if there are prior sales) and/or at each keyed total
following sales in a Preferred Customer transaction. At each automatic discount, the
total discountable sales as well as the total computed discount and/or tax
exemption is printed on the customer receipt along with the descriptor given to the
applicable discount group. If automatic coupons are due at the same time as the
discount, they are given prior to the automatic discount. Individual coupons, like
sales items, are marked as to whether they contribute to the discountable
transaction total. If a manual discount is taken for a Preferred Customer who is
selected for an automatic discount, the manual discount takes precedence and the
automatic discount is not given. If an automatic discount has already been given, it
must be manually voided (VOID,DISCOUNT) before a manual discount can be
entered.

If a discount group is assigned to the Rain check ID, then this discount is used as
the default for all Preferred Customers who are not individually selected for a
discount. Individual customers can be excluded from automatic discounts through
an option flag in their activity record. Likewise, all new customers or non-home
customers can be excluded from automatic discounts through the default activity
options specified in the Preferred Customer options file. All automatic discounts can
be deactivated through another option in this file so that discount groups can be
assigned to customers before the discounts are actually activated and so that all
automatic discounts can be easily discontinued at the end of a promotion.
Whenever a discount is given to a Preferred Customer, the customer number is
saved in the user exit field of any discount exception log entry. While this discount
function does not provide for different discounts on different items, the ability to
select the discountable items as well as the discount rate for each or all Preferred
Customers makes automatic discounts a potentially powerful method for rewarding
or inducing Preferred Customer purchases.

242 Electronic Marketing PRPQ

Provide Kiosk Support to Show Customer Their Points and Coupons
A Nosale Procedure allows any register to be placed into a Kiosk mode where the
expected entries are customer numbers and the response is the customer
messages that would normally appear in a sales transaction. These messages
include the customer identification message, the points messages, and the targeted
coupon messages. This procedure is provided to allow the status of a customer
account to be shown at a register outside of a sales transaction. While this
procedure could be used between sales transactions at a normal register, it is
intended for use at a self service Kiosk register where customers can check their
own point totals, discounts, and targeted coupons as they begin their visit to a
store.

To enter Kiosk mode, the key sequence “NOSALE, DATA ENTRY, 99 ENTER” must
be keyed at a register that is signed on and is not in a transaction. If you have
defined a customer key thru option 6.3, then the key sequence “99, CUSTOMER”
can be used to enter Kiosk mode. Once Kiosk mode is successfully entered, the
Kiosk mode message is displayed. This message can be customized and is
defaulted to “PLEASE SCAN CUSTOMER CARD”. While this message is displayed,
only four types of entries are allowed at the register:
1. A customer number can be scanned (by using a scanner) or swiped (by using
an MSR) which results in the account status being displayed and printed as at
the end of a sales transaction.
2. A customer number can be keyed with a manager’s override to show the
account status.
3. The sign-off sequence can be used to exit Kiosk mode and sign-off the register.
4. An item UPC can be scanned which results in the item descriptor and price
being displayed and/or printed at the register.

Any other entries attempted at a register which is in Kiosk mode are rejected with a
tone and a redisplay of the “PLEASE SCAN CUSTOMER CARD” message. The
entry of a new customer number or a non-home store customer number is accepted
and processed as in a sales transaction, but since there is no information on file for
these accounts, little information is shown on the display or customer receipt. Entry
of an invalid customer number is rejected with a “CHECK CUSTOMER NUMBER”
guidance which is automatically cleared after three seconds. Since all guidances in
Kiosk mode are self clearing and all keyed customer numbers require a manager’s
override, it is suggested that the terminal keyboard not be made available to
customers in a self service Kiosk. For this usage, only a scanner for input of
customer numbers and the display and printer for prompting and output of customer
information is needed. A keyboard is needed to enter and exit Kiosk mode and for
any other tasks for which this register is to be used.

While the entry of customer numbers to receive customer status is the primary
reason for Kiosk mode, this mode also provides a price verify function for customer
convenience. If a customer scans the UPC on an item at a register in Kiosk mode,
the register will display the item descriptor and price just as it would in a sales
transaction. If the same item is scanned twice in a row, then the descriptor and
price are printed along with the time/date line and the customer receipt is advanced
so that the printed information is visible. No totals are impacted by this price verify
function in Kiosk mode.

When a valid customer number is entered in Kiosk mode, the register reacts just as
when a customer number is entered at the start of a sales transaction. The user
defined customer identification message which may include the customer name is

Chapter 8. Electronic Marketing Processing 243

 displayed and the transaction header message is printed followed optionally by the
customer name and account number. The printing continues with the time/date line
followed by the user defined points message for this customer type, the optional list
of available targeted coupons, and the personalized transaction trailer message. In
essence, the printing is the same as the Preferred Customer printing in a sales
transaction except that there are no sales or tenders. Unique Kiosk mode points
messages can be defined for home, new, and visiting Preferred Customers so that
the display message and points printing can be altered from that in a sales
transaction. (See “KIOSK Points Message Offset” on page 109). The unique
customer identification display is replaced with the “PLEASE SCAN CUSTOMER
CARD” message as soon as all printing is complete.

The only journal printing in Kiosk mode is the optional customer identification
message (name and account number) followed by the time/date line. The only entry
made to the transaction log is the sign-off entry made when Kiosk mode is exited. A
single transaction number is used for a Kiosk mode session and the only totals
updated are the performance times which show the whole Kiosk mode session as
inactive time. Note that a terminal in Kiosk mode will never timeout and go into the
TERMINAL SECURED state since this mode is designed for unattended running. A
register in Kiosk mode will continue to function when offline, in standalone, or in
training mode; however, the totals shown will be limited by the ability to access a
customer’s activity data.

Totals Accumulation Processing

The Electronic Marketing PRPQ accumulates many new totals in several new files
and several old files. All of these files are documented at a detailed level in
“Appendix A. Electronic Marketing Database” on page 317. New files have been
created to contain demographic enrollment data, customer activity history, customer
transfer data, and panel diary data. New log records are added to the transaction
summary log (see panel data) and the exception log and new fields are updated in
the accounting, performance, and department totals files. Reports currently exist
only to report on the new accounting and performance data (see “Chapter 9.
Reports” on page 249).

Using Data Base for Directed Marketing

Enrollment data is created and used only by the in-store enrollment procedure. This
data provides demographic information on the preferred customers. Panel diary
data provides all available information on all preferred customer transactions. It may
also be used to collect data on non-preferred customers. This data is created by
checkout support and is never accessed by the Preferred Customer Program.
These two data files form a data base that provide an in-depth knowledge of
customers and their shopping habits. This knowledge of customers coupled with the
ability to influence customer shopping habits through electronic coupons and
rewards provide the basis for an unlimited number of directed marketing programs
that can be designed to enhance customer loyalty and improve store volumes and
profits. For example, by targeting high value electronic seafood coupons to affluent
preferred customers who frequent the store but buy little seafood, you might expect
to improve seafood volumes and profits for a relatively small marketing investment.
The size of this data base and the complexity of analyzing it make it difficult to
process within the Point of Sale system.

Updating and Transferring Totals Files

The point of sale terminal is the source of all new data for the log files, accounting
files, transfer files, and customer activity file. The terminal accesses the customer

244 Electronic Marketing PRPQ

 activity file and, if necessary, the customer transfer file. But, the only file updated
from the terminal is the transaction summary log. The checkout support program
updates all of these files based upon the data placed in the transaction log by the
terminals. From this log data, checkout support does the following:
v Updates point and coupon totals in the customer activity file for home store
customers
v Updates point and coupon totals in the activity transfer file for non-home store
customers
v Updates counts and amounts for preferred customer transactions and electronic
coupons in the accounting files
v Tracks multiple uses of the same customer number in the same day in the
exception log.

Data in the activity transfer file must be routed to the correct home stores through a
central site process. When a transfer file created in one store is moved to another
store, a background transfer processing program evaluates the data and moves the
transfer data targeted for the given store into the customer transfer file. This
transfer program selects only the data meant for the processing store. It is possible
to achieve the required data transfers by copying all transfer files to all stores. The
transfer program selects the needed data and discards the rest. In order to reduce
the networking cost of copying all files to all stores, you can send all activity transfer
data to a central site host. The host can sort it for the destination stores and send
each store only the data that it needs. The transfer program can be initiated from a
host (through Start User Program interface), or a store’s background control menu.
Options selected through personalization allow the transfer program to run
automatically once each hour to process any available data. See “Automatically
Process In-Store Transfers Each Hour” on page 86. Point and coupon activity is
transferred to customers transfer files only when they next visit their home store.
This allows customers to see the points that are transferred to their home store and
allows the points boundary processing to correctly account for points accumulated
in other stores.

Accumulating Electronic Coupons Totals

Electronic coupons may be used to automatically give any outstanding coupons to
preferred customers. An updating function is provided to allow item movement totals
to be updated for both the store coupon and the electronic coupon when a store
coupon is redeemed electronically. This produces an accurate count of both the
electronic coupons that are being redeemed and the store coupons that must be
funded. The promotional item is linked to an automatic coupon that is an alias
record for the actual store coupon. This solves the problem of the difference in
length between linked UPCs, which are only four digits, and scannable store
coupon UPCs, which are usually more than four digits. To calculate item movement
separately for the alias electronic coupon and the normal store coupon, each item
must be defined as a store coupon. The alias record must be flagged for no
movement and the normal store coupon flagged for movement.

Electronic coupons are paperless and cannot be manually counted or picked up. In
order to keep them out of the over/short position, they are put into the on-hand
tender totals rather than the net tender totals. As the accounting totals are moved
from current to previous period, the electronic coupons are automatically picked up
and are reported as such in the previous period. The cash report shows the
picked-up coupons as on hand in the office report, but they are not really in the
on-hand totals and are not carried forward into the next period’s opening balance.
The tender count procedures are altered so that paperless coupons are always

Chapter 8. Electronic Marketing Processing 245

 included in a current period tender count and the accounting record is marked so
that the cash report will be correct. Coupons which are included in a current period
tender count and are picked up through a reconcile in the current period are not
automatically picked up at the close of the period. The automatic coupon totals will
look odd in a current period cash report taken before an operator is reconciled for
the second time with automatic coupons after the first reconcile. This occurs
because some of the automatic coupons have been reconciled and others have not.
The limitation occurs because there is only one total for each type of automatic
coupon in the accounting file unlike the four totals for all other tender types. Even in
this odd case, the coupon totals will be correct once the operator is reconciled.

The coupon processing enhancements code adds additional totals accumulation

capability for electronic coupons. (See “Logging of All Coupon Data” on page 33.)
This code allows all store or manufacturer coupons to optionally be accumulated in
a sequential Coupon Tracking File. For each coupon tracked in this file, a separate
record is created that details the following information about the coupon, the item to
which the coupon applies, and the transaction:

Coupon Item Transaction

Item code Item code Terminal number
Manufacturer Manufacturer Transaction number
Family code Family code Date/time
Value Value Operator number

The totals accumulation facility applies equally to electronic coupons and to manual
coupons. As all electronic coupons require coupon item records, the same coupon
tracking records can be logged for all electronic coupons to the Exception Log
rather than to the Coupon Tracking file.

Data Space Use Adjustments

The initialization of certain Electronic Marketing variables has been moved to user
exit 7 within Electronic Marketing module EAMTSE07.J86. This allows the data
space requirements of the Electronic Marketing application to be limited or
increased depending upon how certain Electronic Marketing functions are used. The
following features have been added to Electronic Marketing by this change.
v Allow the data space requirements for coupon replay to be lowered or raised.
v Allow the data space requirements for coupon MFR substitution to be lowered or
raised.

To implement these functions follow these instructions as given in EAMTSE07.J86

and remove the !, recompile and relink.
! RAISE THE FOLLOWING VALUES IF THEY ARE TOO SMALL AND IF YOU HAVE
! SUFFICIENT TERMINAL DATA SPACE TO ACCOMMODATE MORE. (10-BYTES PER)
! THESE VALUES CAN BE LOWERED TO SAVE DATA SPACE IF THE OPTION IS
! SELECTED TO DEACTIVATE PREFERRED CUSTOMER PROCESSING.
! [Link] = 25 ! Up to 25 Delayed coupons at total time
! [Link] = 50 ! Up to 50 PC coupons at customer ID
! RAISE THE FOLLOWING VALUE IF IT IS TOO SMALL AND IF YOU HAVE
! SUFFICIENT TERMINAL DATA SPACE TO ACCOMMODATE MORE. (20-BYTES PER)
! THIS VALUE CAN BE LOWERED TO SAVE DATA SPACE IF THE OPTION IS
! SELECTED TO DEACTIVATE PREFERRED CUSTOMER PROCESSING.
! [Link] = 25 ! Up to 25 weight promotions in an order
! RAISE THE FOLLOWING VALUE IF IT IS TOO SMALL AND IF YOU HAVE
! SUFFICIENT TERMINAL DATA SPACE TO ACCOMMODATE MORE. (20-BYTES PER)
! THIS VALUE WILL ONLY BE USED IF THE OPTION IS SELECTED FOR VALIDATION
! BY PROMOTION CODES.
! [Link] = 50 ! Up to 50 promotion codes in an order

246 Electronic Marketing PRPQ

 ! RAISE THE FOLLOWING VALUE IF IT IS TOO SMALL AND IF YOU HAVE
! SUFFICIENT TERMINAL DATA SPACE TO ACCOMMODATE MORE. (6-BYTES PER)
! [Link] = 10 ! Up to 10 unlimited percent off coupons
! in an order.
! RAISE THE FOLLOWING VALUE IF IT IS TOO SMALL AND IF YOU HAVE
! SUFFICIENT TERMINAL DATA SPACE TO ACCOMMODATE MORE. (6-BYTES PER)
! THIS VALUE CAN BE LOWERED TO SAVE DATA SPACE IF CATEGORY 5 SCANNABLE
! UPC CODES ARE THE ONLY EXPECTED COUPON CODES GREATER THAN 5 DIGITS.
! [Link] = 50 ! MFR substitution for up to 50 coupons
! which contain data in the MFR area of
! the coupon UPC (??MMMMM?????)

The [Link] affects the number of coupons that can be delayed until
total time because they failed validation during the transaction for some reason
such as minimum purchase not met or cross promoted item not being sold yet. The
[Link] affects the number of coupons that can be held for replay until
the customer number is entered. The [Link] affects the number of
coupons that can be given in the order where the MFR number in the coupon item
record is substituted into the coupon item code during validation and restored later.
The MFR number may be substituted if the MFR number exists in the coupon item
record and the coupon’s item code MFR number is invalid or the EM option
“ALWAYS USE THE MANUFACTURER NUMBER FROM A COUPON RECORD” is
enabled. See the discussion of this option (on page 135) for a better explanation of
this substitution process.

Date of Last Sale Update Functions

In order to report on items based on their date of last sale, this information must be
maintained in the Item Record File. A separate background program,
EAMUDOLS.286, is provided with this package to update the Date of Last Sale in
the item record file. The Selective Item Record Report provides a way to report on
items by date of last sale (see “Selective Item Record Report” on page 250).

Promotion Code Validation

Promotion code validation is expected to be used for coupons that are managed
totally by the retailer while external coupons will continue to be validated by
manufacturer and family. The two separate validation methods will minimize
conflicts between promotions that are internal and external to the retailer. For more
discussion on promotion code validation, see “Use Promotion Codes for Coupon
Validation” on page 140.

Use of promotion codes is optional

Use of promotion codes cost over 1K in data space usage. When the promotion
code option is turned off, the terminals must go through “Loading Options” before
this space is released.

Promotion codes are values in User Exit field 1 in item records

Directions with the option definition will tell the user how to change the descriptor
“User Data 1” in EAMRDESC to say “Promotion Code” for data maintenance. This
descriptor will be automatically altered by the Electronic Marketing options report if
this report is used to activate the promotion codes option.

If promotion code support is selected and a coupon contains a promotion code,

then promotion code validation will take place regardless of other option settings or
item record flags. Thus any coupon to be validated by department or not to be
validated at all must not contain a promotion code.

Chapter 8. Electronic Marketing Processing 247

 The Selective Item Record Report will support promotion code reporting as well as
setting of promotion codes.

Validation of coupons with promotion codes

Any coupons including paper coupons, points coupons, weight coupons, and cross
promotional coupons can be validated by promotion code.

The same item can validate one coupon by promotion code and another coupon by
MFR/FAM or DEPT/FAM.

An item cancel must validate by both promotion code and MFR/FAM or DEPT/FAM.

Any coupon validated by promotion code will not be doubled.

Cross promotional coupons (fake one cent coupons for validation only) will behave
differently with promotion code validation than with any other validation in that a
unique item will be required to validate each fake coupon. Thus with promotion
code validation, you will have to buy two of each item in a cross promotional chain
before the discount will be given a second time.

Minimum purchase of coupons with promotion codes

Minimum purchase in the promotion group will replace minimum purchase
requirements by manufacturer. Minimum by department is still applicable to coupons
validated by promotion code.

Taxability and foodstampability of coupons with promotion codes

Taxability and foodstampability for all coupons validated by promotion code will
come directly from the flags in the coupon item record. The coupon will not cause
taxes to go negative. It is the retailer’s responsibility to assure that all items in the
same promotion group have the taxability and foodstampability if they are
concerned with the taxability or foodstampability of the coupon.

248 Electronic Marketing PRPQ

Chapter 9. Reports
The Electronic Marketing application can produce the following user reports:
v Selective Item Record Report
v Selective Preferred Customer Report
v Preferred Customer Audit Log Report
v Preferred Customer Exception Log Report
v Preferred Customer Options Report.

It also modifies some of the accounting reports. These reports are discussed in this
chapter in the above order.

User Reports
There are user reports available to help monitor cashiers and customers for multiple
use of the same customer card, to report on out of store transfers, to track
redemptions/adjustments, and to report on the item record file and to report on the
preferred customer, enrollment, activity, and transfer files. To access the user
reports, go the Report Menu and select 16 for User Reports:

REPORTS

Select one of the following reports

1 Automatic Report Procedure 9 Department Analysis

2 Operator/Office Cash 10 Item Movement
3 Operator Sales 11 Miscellaneous Trans
4 Store Totals Recap 12 Terminal Productivity
5 Operator Performance 13 Operator Listing
6 Over/Short 14 System Status
7 Cash Drawer Position 15 Print Filed Reports
8 Tender Listing 16 User Reports

Type your selection number, then press enter. 16

Figure 75. Report Menu

Select your choice from the User Report Menu:

User Reports

Select one of the following.

1 User Report 1
2 User Report 2
3 Selective Item Record Report
4 User Report 4
5 Preferred Customer Audit Log Report
6 Preferred Customer Exception Log Report
7 Preferred Customer Options Report
8 Selective Preferred Customer Report

Type you selection number, then press ENTER. 5

Figure 76. User Reports Menu

© Copyright IBM Corp. 1991 2000 249

Selective Item Record Report
The Selective Item Record Report is a user report that is accessed through the user
reports menu of the base Supermarket Application. It can be used for the following
purposes:
v Report on selected items in the item record or item movement files based on
user input and store options
v Report on movement of electronic coupons only
v Report on items for which electronic coupons are selected
v Find the UPCs of the items to which electronic coupons should apply
v Build an item maintenance batch for the items that need to be altered to be
linked to an electronic coupon.
Multiple search criteria, iterative searches, and multiple output formats provide for a
fully functional report on the items in the store. The report can also reset item
movement, build a DDM or ADDMI batch, build an item movement list, or delete
item records if these functions are selected through options and requested by an
authorized operator. The report is independent of all other application processing as
it acts on the following Supermarket Application files:
v Item Record File
v Item Movement File
v Item Movement List
v Exception Log File
v DDM Control File
v DDM Source File
v Store Options File.

It is dependent on the Supermarket Application only for the user report interface
and for the format of the files. The Selective Item Record Report provides an
operator interface that is consistent with the Supermarket Application and an
efficient, dependable, and user-friendly report.

For this discussion, the functions of the Selective Item Record Report are divided
into the following six categories:
v Item selection
v Item reporting
v Item alterations
v Operator interface
v Error handling
v Performance.

Item Selection
The Selective Item Record Report provides the following 16 search criteria to select
a desired set of items to report as is shown on the Selective Item Record Search
menu below:

250 Electronic Marketing PRPQ

 SELECTIVE ITEM RECORD SEARCH - STORE 0445
Wednesday, February 10, 1993
SELECT ONE OF THE FOLLOWING SEARCH CRITERIA

1 ITEMS BY DEPARTMENT RANGE 9 ITEMS BY EXCEPTION TYPE

2 ITEMS BY DEPT AND/OR MIX/MATCH 10 COUPONS BY VENDOR
3 ITEMS BY ITEM CODE RANGE 11 ITEMS USING ALIAS REFERENCE
4 ITEMS BY VENDOR AND/OR FAMILY 12 ITEMS USING LINK FIELD
5 ITEMS BY FLAG SELECTIONS 13 ITEMS USING EXIT1 OR EXIT2
6 ITEMS BY PRICE RANGE 14 ITEMS BY DATE OF LAST SALE
7 ITEMS BY DESCRIPTOR 15 ITEMS WITH INVALID DEPARTMENT
8 ITEMS BY NUMBER SOLD 16 NUMBER OF ITEMS ON FILE

TYPE YOUR SELECTION NUMBER ?

Figure 77. Selective Item Record Search

The first 14 methods allow for additional input to qualify the value or range of
values that the search should select. These searches can also be restricted to
items in a single department to limit the output. All searches except for number
eight directly search through the item record file. The search for items by the
number sold searches through the current or previous period item movement file
unless the search is for all items with no movement.

Iterative searches can be used to refine a selected list of items. You can apply the
input search criteria successively to reach a desired set of items. For example, you
might search for all items in a range of departments, then search for all items in
that list, flagged to accumulate item movement, then search through the refined list
for items with no sales in the previous item movement period. This cumulative
search would yield a list of items in the selected department range that are known
not to have sold during the previous item movement period. The flexibility provided
by multiple iterative searches allows almost any desired list of items to be isolated.
The user flags in the item record can be used to enhance this flexibility by marking
newly-added items or items that are on sale so that these criteria can be added to
the list selection process. The user exit fields can be used similarly to contain such
information as the date of last sale, a class or category number, or the aisle number
where a product is stocked to yield useful lists of items.

The date of last sale search locates all items last sold before the specified date. A
separate program (provided with this package) must be installed to capture in the
item file the ending date of the period in which an item last sold. This report only
detects a date of last sale for items that have sold after this program that captures
the dates has been successfully installed and run. The search for all coupons
assumes installation of the enhanced coupon processing user exits. If these exits
are not installed, some of the data from this search is meaningless and should be
disregarded. Sometimes there are multiple searches that result in the same
selection of items, but the type of search used determines the order and format of
the reported items. All coupon items can be isolated through search five that does
not assume the coupon processing exits and formats the output data accordingly.
The search for all items that have not sold does not check to see if the items are
flagged to accumulate movement, so an iterative search may be needed to
separate those items for which movement is not accumulated. A search for a range
of movement that includes zero requires an iterative search because the direct
search for no movement requires a range of only zero. The search for particular
flag settings provides unique help for an operator in the selection of the flag
conditions for which to be searched.

Chapter 9. Reports 251

 If more than 25,600 items match the search criteria, only the first 25,600 found will
be reported or available for successive refining searches. To overcome this
restriction, the item file can be divided into groups of less than 25600 by restricting
the original search to a single department or to a range of departments.

Online help is available in this report by pressing the F1HELP key.

Item Reporting
Item data for a selected group of items can be reported to either the display or to a
printer. In addition, the report can be printed without being displayed, or can be
displayed first and then printed. A printer is not required to run this program. An
option can be selected to bypass the prompt that allows for direct printing without
display.

Reported output is intended to be one line per item. With page headers and needed
spacing, this allows for 15 items per displayed page and 40 items per printed page.
The page headers show the following information:
v Date
v Time
v Report name
v Page number
v File size
v Code version
v Search criteria that result in this list of items.
The report can be in one of two formats and shows the following information:

Primary Report Line Alternate Report Line

v Item code v Item code
v Description v Department
v Department v Price
v Mix and match group v Current and previous period sales
v Item type v Date of last sale
v All pricing information v User exit values
v Item flags v Linked records
v Coupon families

An alternative provides two print lines per item and reports on all information in the
item record. In this format, only six items are displayed and 18 printed per page.
The two alternate formats must be selected while the report is being displayed, but
they apply to the next printing of the report. The actual report format changes
slightly based on the final search criteria. The report always shows the value of the
field being searched in the primary format.

Report output is sorted appropriately based on the search type and is not in the
order of the items on file. The final search type determines not only the format of
the report but the order of the items in the report. For example, if a search is made
for all items with current period movement and then is refined to include only items
in a range of departments, the items will be sorted by department and by item code
within a department and the base line format will be displayed. If the search order is
reversed to first report on all items in a department range and then is refined for all
items with current period movement, the report will be sorted by quantity sold and

252 Electronic Marketing PRPQ

the quantity sold will appear in place of the item flags. You can alter the order of the
reported items and the report format by using a refining search that does not alter
the list of reported items.

Printing of any report can be halted while the report is in process. However, with the
print spooler, the first lines of the report are not seen until the entire report has
been formatted and spooled. A facility is provided to purge the most recently printed
report from the print spooler so that a printing of report requested in error can be
halted. This “UnPrt” function will purge a report whether it is currently printing, but it
can only be used to purge the most recently printed item record report.

Report data can be saved to file in three different data formats, as follows:
v One format saves the actual reported lines so that the saved file can be printed
to duplicate the report.
v Another format saves the item record data for the reported items in contiguous
46-byte records. This format is like the sequential file format created or used by
the keyed file utilities.
v The final format saves only the item codes for the reported items in contiguous
6-byte records. Report data is saved in a file named [Link] in the root
directory where “x” shows the format as follows:
– “1” = Report lines
– “2” = Item records
– “3” = Items codes
– “mmdd” is the month and day of the report.

It is the user’s responsibility to delete the saved report files.

There are three possible views or formats of the item record data as printed in 132
character format. These same formats are displayed, but to see the right side of the
line, the TAB key is used. This makes for six display formats. Continuation marks
(...) are used to split the 132-character lines for printing the following in 80 character
format.
Base format:

ITEM CODE DESCRIPTION DEPT MG TYPE PM QTY PRICE APRICE ...

... FLAGS NQ WT QR PR NS RS TX FS PA ND NM SL TI PO DL UF

1200000050 COLA DIET 1 0 1 1 2.29 ...

... 008C01 N N N N N N A Y Y N N N N N N 4

Alternate format:

ITEM CODE DEPT PM QTY PRICE SALES1 SALES2 EXIT2 EXIT1 LINK...
... FAMILY QTY1 QTY2 WGT1 WGT2 DESCRIPTION

1200000050 1 1 1 2.29 75.57 96.18 417 0 0355...

... 123 33 42 - - COLA DIET

Both format:

ITEM CODE DESCRIPTION DEPT MG TYPE PM QTY PRICE APRICE ...

... FLAGS NQ WT QR PR NS RS TX FS PA ND NM SL TI PO DL UF
SALES1 SALES2 EXIT2 EXIT1 LINK...
... FAMILY QTY1 QTY2 WGT1 WGT2 DESCRIPTION

1200000050 COLA DIET 1 0 1 1 2.29 ...

Chapter 9. Reports 253

 ... 008C01 N N N N N N A Y Y N N N N N N 4
75.57 96.18 417 0 0355...
... 123 33 42 - - COLA DIET

There are six possible views or formats of the item record data shown on the
display. These same six formats are printed if the option for 132 character printed
lines is not selected.
Base format:

ITEM CODE DESCRIPTION DEPT MG TYPE PM QTY PRICE APRICE FLAGS

1200000050 COLA DIET 1 0 1 1 2.29 008C01

Base format with TAB:

ITEM CODE DESCRIPTION NQ WT QR PR NS RS TX FS PA ND NM SL TI PO DL UF

1200000050 COLA DIET N N N N N N A Y Y N N N N N N 4

Alternate format:

ITEM CODE DEPT PM QTY PRICE SALES1 SALES2 EXIT2 EXIT1 LINK FAMILY

1200000050 1 1 1 2.29 75.57 96.18 417 0 0355 123

Alternate format with TAB:

ITEM CODE SALES1 SALES2 QTY1 QTY2 WGT1 WGT2 DESCRIPTION

1200000050 75.57 96.18 33 42 - - COLA DIET

Both format:

ITEM CODE DESCRIPTION DEPT MG TYPE PM QTY PRICE APRICE FLAGS

SALES1 SALES2 EXIT2 EXIT1 LINK FAMILY

1200000050 COLA DIET 1 0 1 1 2.29 008C01

75.57 96.18 417 0 0355 123

Both format with TAB:

ITEM CODE DESCRIPTION NQ WT QR PR NS RS TX FS PA ND NM SL TI PO DL UF

SALES1 SALES2 QTY1 QTY2 WGT1 WGT2

1200000050 COLA DIET N N N N N N A Y Y N N N N N N 4

75.57 96.18 33 42 - -

On all printed reports, an additional line shows the sum of all item movement totals
(SALES) below the individual movement columns.

Item Alterations
Once a set of item records has been selected and either printed or displayed, one
or more of the following processing options can be selected. Operators can delete
selected records, reset their movement data, create an item movement list so that
future reports can be made without the search, or create a Delayed Data
Maintenance or ADDMI batch to add, replace, or delete the items. Options
determine which of these processes are made available in the store. An operator
must be authorized to perform this type of function before being allowed to proceed.

254 Electronic Marketing PRPQ

Also, operators must confirm their identity by re-entering their sign-on password
before being allowed to delete items, reset movement, or create an item record
maintenance batch.

To delete a selected list of items, an operator must be authorized to delete item

records through the data maintenance function. Once authorized operators have
made this selection and confirmed it through the entry of their password, the
records begin to print as they are deleted. This printing can be manually bypassed,
leaving only a final deletion count as evidence of the success of the operation. An
exception log entry is made for each deleted item as though the item had been
individually deleted using the data maintenance function.

To reset item movement, an operator must be authorized to reset item movement

through the Item Movement Report that is included with the Supermarket
Application. This selection is made available only if item movement data for both
the current and previous period was reported through one of the alternative report
formats. Once authorized operators have made this selection and confirmed it
through the entry of their password, the current period item movement data for the
selected items is reset. This reset is accomplished by deleting the appropriate
records from the current period item record file. If date of last sale information is
being accumulated in the item records, this date is updated for all items whose
movement data is deleted.

To build an item movement list for the reported items, an operator must be
authorized to build an item movement list through the data maintenance application.
Once authorized operators have made this selection, they are prompted for a list
number and a list description that are then used to build the item movement list.
This new item movement list is then available to provide a selection of items to the
Item Movement Report in the Supermarket Application.

In order to build an item record maintenance batch for the reported items, an
operator must be authorized to build a batch through the Delayed Data
Maintenance function. Once authorized operators have made this selection and
confirmed it through the entry of their password, then they are prompted for the
batch process (ADDMI immediate, ADDMI operator, or DDM operator), a 6-digit
batch ID (defaults to date), and the batch type (add, replace, delete, or
add/replace). Options allow the batch process to be defaulted to DDM operator,
ADDMI immediate, or to be limited to only ADDMI batches. If the batch number is
already in use, the operator is given the option of logically appending the new
records to the current batch through a new sequence number that distinguishes the
new entries in the batch.

If the batch is a replace or add/replace batch, then an authorized operator is

allowed to modify the records in the batch by entering new field values that apply to
all records in the batch. The item price, department number, current family, previous
family, mix and match group, item type, pricing method, link value, exit 1 value, exit
2 value, descriptor, or flag settings can be altered for all items in the batch. In
general, flag settings can only be altered after a search has limited the list of
records to a common setting of a single flag. If selected fields are altered for all
items in an ADDMI immediate replacement batch, then the operator is given the
choice of creating a partial record modify batch which changes only the altered
fields or a full record replacement batch with the selected fields altered. The partial
record modify batch has the advantage that it assures that only the altered fields
are changed when the batch is applied to an item record file that is different from
the file from which the batch was created.

Chapter 9. Reports 255

 After an ADDMI batch is created, the operator is given the choice to immediately
run ADDMI to process the batch. If the changes are meant only for this file, then
ADDMI would normally be executed at this time. If the changes are intended for
other stores (perhaps this one as well), then the ADDMI file [Link] must
be saved for sending to other stores before it is processed (and deleted) in this
store. If multiple ADDMI batches are created successively (probably based on
multiple searches) without ADDMI being started to process the batches, then the
batches are all appended in the single [Link] output file. These ADDMI
batches provide a convenient way to make the same set of changes to a list of item
records in multiple stores. The batches can also be used to copy records from one
store to another or to delete a common set of records from multiple stores. While
DDM batches might also be used to add, delete, or change a set of records in
multiple stores, the DDM batches are not easily portable since they require control
records to be added to a keyed file and unique source file names to be managed in
each store.

Regardless of whether ADDMI or DDM is used to apply a batch built by this report,
once the batch has been processed by ADDMI if required, the results can be
viewed using the DDM functions to look at batch errors, batch status, batch records,
and/or batch messages. If the batch is not an ADDMI immediate batch, then DDM
can even be used to edit the batch records before they are applied. Each batch
built by this report is given a message which defines the contents of the batch and
when and how the batch was built. These messages provide a convenient trail to
determine the purpose of these in-store created item record maintenance batches.
If needed, ADDMI immediate batches can even be made to exception log each item
record change as though the change were made through the data maintenance
screens.

In order to simplify the creation of item record batches which link lists of items to a
promotion coupon, a special PROMO function is provided as an alternative to the
BATCH function. Any batch that can be built using the PROMO function might also
be built using the BATCH function, but the promotion selection provides unique
validation and operator interface functions that simplify the task of putting items on
promotion or ending these promotions. When the PROMO function is selected, the
list of items to be promoted is validated to assure that:
1. None of the items in the list is already on promotion or all items in the list are
on promotion. If all items are on promotion then the PROMO function will clear
the promotion.
2. None of the items in the list link to a deposit unless all items in the list link to
the same deposit.

If either of these conditions is not met, then an appropriate guidance message is

given after which the reported list of items is displayed again so that the list can be
refined to exclude the offensive items.

In order for these validation checks to work correctly, all items which link to deposits
must be flagged as such in their item records. This validation also requires all old
promotions to be cleared before any new promotions involving any of the same
items can be created.

A major advantage of the promotion function is that it automatically handles setting

and clearing promotions on items which link to deposits in a manner which properly
maintains the deposits. Because this function always creates ADDMI immediate
batches to change the link field (and optionally the coupon family or promotion
code) through partial record modification, the operator only needs to enter the batch

256 Electronic Marketing PRPQ

 number and the promotion link value (if not clearing a promotion), and then choose
whether or not to immediately start ADDMI to apply the batch. On repetitive
creations of promotion batches within five minutes of each other, even the password
entry is bypassed to simplify the creation of multiple batches. Note that the ADDMI
immediate partial record modify batches assure that only the link (and optionally
family or promotion code) fields are altered and that the batches are of minimal size
for transmission to other stores. The immediate application of these promotion links
requires that the promotion coupons be flagged as “not for sale” until the promotion
begins. This allows the new promotions to be tested in training mode before being
activated by a single batch which turns off the “not for sale” flag in the item record
or each of the promotion coupons.

Operator Interface
The Selective Item Record Report provides a menu-driven operator interface that is
consistent with the other Supermarket Application reports and substantially
enhanced for ease of use. The function keys (such as F1HELP, F3QUIT, and
F10PRINT), PgUp and PgDn keys, and the ESC key perform as expected in
supermarket reports. Help screens are available to explain how to use any of the
reports functions. All operator input is validated and simple instructions are given on
how to correct any input errors. Feedback is given on all successful input requests
to show what the application is doing (or has done) with the input. This includes
continually updated status displays for any extended processing and guidance
messages that show the actions that can be taken to stop the processing. Escape
sequences are provided to stop any search or print request or to correct any input
request to prevent delay through unwanted processing. Defaults are provided for all
YES/NO questions so that the ENTER key can be used to answer most questions.

Error Handling
The Selective Item Record Report is designed to have a dependable interface to
the item record file so that it continues to run regardless of the contents of this file.
The search for invalid departments is a prime way for verifying the integrity of this
file because it usually identifies any irrelevant or invalid data that has been placed
in the file. Records that are found in a sequential search but that are not found
through a keyed Read because they are out of position are identified whenever they
fit the search criteria. Also, non-numeric item codes are identified with the sector
containing them so that the file can be corrected. Errors related to code or
file-access failures are displayed to an operator along with all of the diagnostic data
needed to isolate the error.

Performance
The Selective Item Record Report is designed to handle large item files in a
performance sensitive manner. The search algorithms are optimized for finding
items in the file and the sort algorithm is optimized for processing the items found.

It requires up to 500K of memory to find and sort 25,600 items, so the application
may be limited by the amount of available memory in the controller. The report uses
only the amount of memory needed based on the requests made, and all memory
is released when the report is exited.

Chapter 9. Reports 257

Selective Preferred Customer Report
The Selective Preferred Customer Report is a user report that is accessed through
the user reports menu of the base Supermarket Application. It reports on selected
customers tracked in the enrollment, activity, previous activity and customer transfer
files based on user input. The report is a useful tool with which to manage the
preferred customer data base because if provides multiple search criteria, iterative
searches, multiple output formats, and the ability to create batch updates. This
report is independent of all other preferred customer processing and does not run
against any of the base Supermarket Application files. The report logs errors to the
application event log.

For this discussion, the functions of the Selective Preferred Customer Report are
divided into the following categories:
v Customer selection
v Customer reporting
v Customer record alterations
v Operator interface
v Error handling
v Performance.

Customer Selection
The Selective Preferred Customer Report provides the following 10 search criteria
to select a desired set of items to report as is shown on the Selective Preferred
Customer Search menu below:

SELECTIVE PREFERRED CUSTOMER SEARCH - STORE 0445

Wednesday, February 10, 1993 102 K-Bytes in Activity File
SELECT ONE OF THE FOLLOWING CUSTOMER SEARCH CRITERIA

1 ACCOUNT NUMBER 9 INVALID ALIASES

2 ACTIVITY LEVEL ... 10 PREVIOUS ACTIVITY ...
3 ACCOUNT BENEFITS ...
4 DATES ...
5 ADJUSTMENTS ...
6 OPTIONS ...
7 PROFILE INFORMATION ...
8 ALTERNATE NUMBERS ...

TYPE YOUR SELECTION NUMBER ?

1 HELP 2 3 QUIT 4 5 6 7 8 BATCH 9 10

Figure 78. Selective Preferred Customer Search

All of these search methods allow for additional input to qualify the value or range
of values that the search should select. Each method involves a direct search
through the appropriate file (enrollment, activity, previous activity, or customer
transfer). Iterative searches can be used to refine a selected list of customers. This
allows the user to combine any number of the input search criteria to obtain a
desired set of customers.

If more than 25,600 customers match the search criteria, only the first 25,600 found
will be reported or available for successive refining searches.

Online help is available in this report by pressing the F1HELP key.

258 Electronic Marketing PRPQ

 Since the customer data base contains confidential data, security options are
available to deactivate any or all of the following functions:
v Erase customer records
v Print customer records
v Save customer records to file
v Batch update of customer records
v Print mailing labels.

Customer Reporting
Customer data for a selected group of items can be reported to either the display or
to a printer. You can decide whether to print the report without first displaying it or
display it and then print it. Reported output is restricted to one line per customer. If
the report is displayed, the F9 function key or the Backspace key will display
different information for the same list of customers. With page headers and needed
spacing, this allows for 15 customers per displayed page and 40 customers per
printed page. The page headers show the following information:
v Date
v Time
v Report name
v Page number
v File (name and size) searched
v Code version
v Search criteria that yielded that combination of customers.

The following different formats are used to display the customer information and the
file associated with each. Each of these formats starts with the customer account
number.
Activity File data:

NAME / TOTAL POINTS / TOTAL AUTOMATIC PREFERRED COUPON AMOUNT

/ LAST VISIT / POINTS FROM LAST ORDER / STATUS LEVEL
LAST REDEEM DATE / REDEEMED PTS / NET TOTAL / PERIOD PTS / PERIOD START DATE
/ PERIOD REDEEMED / NET PERIOD
TARGETED MSG # / TARGETED COUPONS / ALTERNATE NUMBER / OPTIONS
DISCOUNT GROUP / POINTS MULTIPLIER / FULL CUSTOMER NAME

Customer Transfer File data:

TOTAL PTS TRANSFERRED / PENDING POINTS / TOTAL TRANS TRANSFERRED

/ PENDING TRANSACTIONS / TOTAL AUTO COUPONS TRANSFERRED
/ PENDING AUTO COUPONS / LAST TRANSFER DATE

Enrollment File data:

LAST NAME / FIRST NAME / HOME PHONE / WORK PHONE

ADDRESS LINE 1 / CITY / STATE / ZIP
ADDRESS LINE 2
BIRTHDATE / ENROLLMENT DATE / LAST ADJUSTMENT / LAST REDEMPTION /
/ LAST CHANGE / LAST RAIN CHECK
# OF ADJUSTMENTS / # REDEMPTIONS / PTS ADJUSTED POSITIVE /
/ PTS ADJUSTED NEGATIVE / ADJUSTMENT FORM # / REDEMPTION FORM #
AGE / GENDER / INCOME LEVEL / FAMILY SIZE / CHILDREN’S AGES /
/ AUTHORIZATION ON FILE? / RECORD STATUS
REFERENCED ACCT / ALIAS FLAG / SOCIAL SECURITY # / DRIVERS LICENCE #

Previous Activity file data:

PERIOD START DATE / DOLP / TOTAL PERIOD POINTS / TOTAL REDEEMED /

DISCOUNT GROUP / PERIOD FLAGS / PERIOD END DATE / POINTS FROM LAST
ORDER / TOTAL # ORDERS / TOTAL POINTS CARRIED OVER ***

Chapter 9. Reports 259

 Note: If monthly data is kept for more than one period, then selected fields are
displayed for each month.

The only formats that require two lines per customer are the address and the
targeted coupon format if there are more than five targeted coupons. If this format
is selected, only six customers are displayed and 18 printed per page. Report
output is sorted appropriately based on the search type and is not in the order of
the customers on file. The final search type determines not only the format of the
report, but also the order of the customers in the report. You can alter the order of
the reported customers and the report format by using a refining search that does
not alter the list of reported customers. The printing of any report can be halted
while the report is in progress. The F2 UNPRT key is provided to purge the most
recently printed report from the print spooler. This function will purge a report
whether or not it is currently printing, but it can only be used to purge the most
recently printed customer record report.

Customer Record Alterations

Once a set of customers has been selected and either printed or displayed, one or
more of the following processing options can be selected:
v You can update a customer’s targeted messages or targeted coupons or you can
update a customer’s name in the activity record with the name from their
enrollment record.
v The customer’s discount group, point multiplier, and status level can also be
updated.
v You can create a range of new customer activity records in one step without first
performing a search.

To obtain access to these update functions, operators must confirm their identity by
re-entering their sign-on password. Once this has been done, an operator is
prompted for a batch number and, in some cases, the file to which the updates are
to be applied. If a batch file already exists, you can either append to it, or define a
new file name in which to put the updates. If the default batch file is used
([Link]), you can apply the updates immediately if you so choose. The
option to perform the updates at some later point in time by starting the background
application EAMUBATP is always available.

Report data can be saved to file in the following three different data formats:
v One format saves the actual reported lines so that the saved file can be printed
to duplicate the report.
v Another format saves the customer activity record data for the reported
customers in contiguous records that are of the length specified in the preferred
customer options. See “Activity Record Size” on page 82. This format is exactly
like the sequential file format created or used by the keyed file utilities.
v The final format saves the customer account numbers for the reported customers
in contiguous nine-byte records. Report data is saved in a file named
[Link] in the root directory, where “x” shows the format of the file as
follows:
– 4 = report lines
– 5 = activity records
– 6 = account numbers
– “mmdd” is the month and day of the report.

It is the user’s responsibility to delete the saved report files.

260 Electronic Marketing PRPQ

Operator Interface
The Selective Preferred Customer Report provides a menu-driven operator interface
that is consistent with the other Supermarket Application reports. The function keys
(F1HELP, F3QUIT, and F10PRINT), PgUp and PgDn keys, and the ESC key
perform as expected in supermarket reports. Help screens are available to explain
how to use any of the report functions. All operator input is validated and simple
instructions are given on how to correct any input errors. Feedback is given on all
successful input requests to show what the application is doing (or has done) with
the input. This includes continually updated status displays for any extended
processing and guidance messages that show the actions that can be taken to stop
the processing. Defaults are provided for all YES/NO questions so that the ENTER
key can be used to answer most questions.

Error Handling
The Selective Preferred Customer Report is modeled after the Selective Item
Record Report and is designed to continue to run regardless of the contents of the
preferred customer keyed files. Records that are found in a sequential search but
that are not found through a keyed Read because they are out of position are
identified whenever they fit the search criteria. Non-numeric customer account
numbers are identified with the sector containing them so that the file can be
corrected. Errors related to code or file-access failures are displayed to the operator
with all of the diagnostic data needed to isolate the error.

Performance
The Selective Preferred Customer Report provides the ability to do many of the
customer data base maintenance tasks that might be needed in the store, including
the following:
v Merging the contents of two enrollment files. This allows enrollment data to be
entered on multiple independent systems.
v Updating the Customer Activity File with the accounts and names from the
Customer Enrollment File. This allows an enrollment file to be built outside the
store operating system.
v Reporting on active customers who have not yet been enrolled. This allows the
progress of the enrollment process to be tracked and verified.
v Targeting a message to all active customers for whom you have no enrollment
data.
v Validating the contents of the customer data base files.
v Targeting a message to customers who have a birthday in the coming week.
v Targeting a coupon to selected preferred customers based on their total
purchases since enrollment.
v Adding a range of new account numbers to the Customer Activity File.
v Sending a mailing to those customer who have not shopped in the store in three
months.

This list provides a sample of the power of the program. This program is not
intended to target coupons based on purchase history from selected departments or
manufacturers. This level of purchase history data is provided through the panel file
data, but is not intended to be accumulated as part of the customer data base
within the store operating system.

Chapter 9. Reports 261

Preferred Customer Audit Log Report
This report is a log for the current or previous period on redemption or adjustment
of points through the preferred customer enrollment program. It is selected from the
User Report Menu.

RPP1S100 PREFERRED CUSTOMER AUDIT LOG REPORT - STORE 000

STORE NAME/ADDRESS FROM REPORT DESC 2381 06/1/91 15:43

CUSTOMER AUDIT TERM TRANS FORM #

NUMBER TYPE DATE TIME NUM NUM OPR POINTS STORE

XXXXXXXXXXX R 06/01 11:39 1 20 1 100 0

XXXXXXXXXXX R 06/01 12:33 1 38 1 050 0
XXXXXXXXXXX R 06/01 13:01 1 38 1 050 0

Figure 79. Preferred Customer Audit Log Report

Preferred Customer Exception Log Report

The Preferred Customer Exception Log Report consists of two reports:
v The Multiple Card Use Report
v The Transfer Activity Report.

To access the Multiple Card Use Report select 1 on the following screen. Then
select 1 or 2 to select a reporting period.

PREFERRED CUSTOMER EXCEPTION LOG REPORT

Select one of the following:

1 Multiple Daily Use of Preferred Customer Card

2 Inter-store Points Transfer Activity

Type your selection number, then press Enter. 1

Enter 1 to report current period or 2 to report previous period

Figure 80. Preferred Customer Exception Log Report

An example of the Multiple Card Use Report follows.

262 Electronic Marketing PRPQ

 RPP1S100 MULTIPLE CARD USE REPORT - STORE 001

STORE NAME/ADDRESS FROM REPORT DESC 2381

CUSTOMER POINTS COUPONS TRANS TERM DATE OPERATOR

NUMBER EARNED EARNED NUM NUM TIME

xxxxxxxxxxx 4.79 .25 2 1 04/29/91 10:40 1

xxxxxxxxxxx 4.78 .25 4 1 04/29/91 10:50 1
xxxxxxxxxxx 2.84 .25 6 1 04/29/91 10:59 1
xxxxxxxxxxx 2.77 .25 7 1 04/29/91 11:10 1
xxxxxxxxxxx 3.67 .85 19 1 04/30/91 10:36 1
xxxxxxxxxxx 3.08 .60 20 1 04/30/91 10:37 1
xxxxxxxxxxx 3.08 1.20 22 1 04/30/91 10:38 1
xxxxxxxxxxx 3.08 1.20 23 1 04/30/91 10:40 1
xxxxxxxxxxx 3.67 1.45 24 1 04/30/91 10:41 1
xxxxxxxxxxx 3.08 1.20 27 1 04/30/91 11:11 1
xxxxxxxxxxx 5.21 1.99 32 1 04/30/91 11:27 1
xxxxxxxxxxx 2.72 1.14 12 1 04/30/91 11:06 1

Figure 81. Multiple Card Use Report

To access the Inter-store Points Transfer Activity Report select 2 on the following
screen. Then select 1 or 2 to select a reporting period.

PREFERRED CUSTOMER EXCEPTION LOG REPORT

Select one of the following:

1 Multiple Daily Use of Preferred Customer Card

2 Inter-store Points Transfer Activity

Type your selection number, then press Enter. 2

Enter 1 to report current period or 2 to report previous period

Figure 82. Preferred Customer Exception Log Report

The following is an example of the transfer activity report.

RPP1S100 TRANSFER ACTIVITY REPORT - STORE 001

STORE NAME/ADDRESS FROM REPORT DESC 2381

TRANSFER RECORDS RECORDS ERROR

FILENAME RECEIVED TRANSFERRED DATE TIME STATUS

EAM:0350 2 2 07/02/91 13:56 OK

Figure 83. Transfer Activity Report – Example

Chapter 9. Reports 263

Preferred Customer Options Report
The Preferred Customer Options Report is a report of the current options set for
customer processing in a store that has installed the Electronic Marketing
application. For detailed descriptions of the preferred customer options, see
“Preferred Customer Options Descriptions” on page 76 to 169. This user report
allows all options values to be displayed or printed. This report will also allow any
operator who is authorized to personalize store options to change any of the
Preferred Customer options. You can also change the options file by using any
available editor. This report should be run after the options are altered to verify that
the options file [Link] is in the correct format and that all options values
are set as expected. The following describes some of these functions.

When using DREDIX to edit the option file some invalid ASCII characters, such as a
TAB character can be inadvertently inserted into the file. This will cause Electronic
Marketing to be unable to read the Electronic Marketing options file. The Electronic
Marketing options report will now look for these invalid characters, specifically any
ASCII character less than 20H and greater than 7FH and display a warning
message when one is found. A HEX editor must be used to remove them. The
following shows what the report will look like when a warning message is found:

Preferred Customer Options Report - STORE 0445 Page 1 of 17

Electronic Marketing Test Store 10/28/92 11:04

*** WARNING *** EAMFBOPT FILE CONTAINS INVALID DATA, LINE/OFFSET = 3 / 1

1.1 PROGRAM NAME = PREFERRED CUSTOMER

1.2 RAIN CHECK ID DEFINITION = 99999999999
1.3 UPC DISPLACEMENT FOR PREFERRED LINKED ITEMS = NONE
1.4- 1.8 COUPONS FOR FIRST USE OF A CUSTOMER CARD = 0 0 0 0 0

2.1 ACTIVITY FILE SIZE = 1000 RECORDS

2.2 ACTIVITY RECORD SIZE = 101 BYTES
2.3 BYTES BEFORE THE CUSTOMER NAME = 67 BYTES
2.4 CUSTOMER NAME IN ACTIVITY RECORD = FIRST AND LAST NAME
2.5 ACTIVITY OPTIONS DEFAULT = 00
2.6 DEACTIVATE ACTIVITY OPTIONS = 00
2.7 ACTIVATE ACTIVITY OPTIONS = 00
2.8 COLLECT PANEL DATA FOR ALL CUSTOMERS NO
2.9 MAXIMUM NUMBER OF COUPONS TARGETED PER CUSTOMER = 5

*** For next page, press PgDn. ***

1 2 3 QUIT 4 5 6 7 ALTER 8 9 0 PRINT

Figure 84. Options Report screen with invalid options

A warning is provided in the Electronic Marketing options report if all needed exits
are not active or if the activity file attributes do not match the options. If all needed
exits are not active, then in the section of the options report where the active exits
are reported, an extra line is displayed or printed indicating which of the needed
exits are inactive.

The following shows what this section of the report will look like if all exits are
properly enabled:

264 Electronic Marketing PRPQ

 ACTIVE CHECKOUT SUPPORT USER EXITS
1, 3, 4, 6, 11-17
ACTIVE TERMINAL USER EXITS (FROM EAMTO000)
1-3, 7, 8, 14, 18, 20, 21, 23, 24, 27, 28, 30, 31, 37, 39, 40,
42, 43, 51, 53, 54

The following shows what this section of the report will look like if one or more of
the exits is not enabled. The list under the warning line would show any user exit
not enabled. Two warnings lines could be present, one for checkout support and
one for terminal sales.
ACTIVE CHECKOUT SUPPORT USER EXITS
1, 3, 4, 6, 12-17
*** WARNING *** PREFERRED CUSTOMER USER EXITS WHICH ARE NOT ACTIVE
11

ACTIVE TERMINAL USER EXITS (FROM EAMTO000)

1-3, 7, 8, 14, 18, 20, 21, 23, 24, 27, 28, 30, 31, 37, 39, 40,
42, 43, 51, 53, 54

If the activity file (EAMFBACT) attributes, record size, key size and number of
records, do not match those in the options, then after the second activity file line
(2.2 ACTIVITY RECORD SIZE =), an extra line will be printed or displayed
indicating that a mismatch exists.

The following shows how this section of the report appears if all the activity file
attributes are correct:
2.1 ACTIVITY FILE SIZE = 1000 RECORDS
2.2 ACTIVITY RECORD SIZE = 101 BYTES
2.3 BYTES BEFORE THE CUSTOMER NAME = 67 BYTES
2.4 CUSTOMER NAME IN ACTIVITY RECORD = FIRST AND LAST NAME

The following shows how this section of the report appears if the activity file
attributes are incorrect:
2.1 ACTIVITY FILE SIZE = 1000 RECORDS
2.2 ACTIVITY RECORD SIZE = 121 BYTES
** WARNING *** PREFERRED CUSTOMER ACTIVITY FILE DOES NOT MATCH OPTIONS
2.3 BYTES BEFORE THE CUSTOMER NAME = 67 BYTES
2.4 CUSTOMER NAME IN ACTIVITY RECORD = FIRST AND LAST NAME

This report has now been enhanced to allow any Electronic Marketing option to be
edited. The following screens show an example of how the options report can be
used to correct the activity file size problem. The first screen of the options report is
shown below. The F7 ALTER function key is used to change an option.

Chapter 9. Reports 265

 Preferred Customer Options Report - STORE 0445 Page 1 of 17

Electronic Marketing Test Store 10/28/92 11:04

1.1 PROGRAM NAME = PREFERRED CUSTOMER

1.2 RAIN CHECK ID DEFINITION = 99999999999
1.3 UPC DISPLACEMENT FOR PREFERRED LINKED ITEMS = NONE
1.4- 1.8 COUPONS FOR FIRST USE OF A CUSTOMER CARD = 0 0 0 0 0

2.1 ACTIVITY FILE SIZE = 1000 RECORDS

2.2 ACTIVITY RECORD SIZE = 121 BYTES
*** WARNING *** PREFERRED CUSTOMER ACTIVITY FILE DOES NOT MATCH OPTIONS
2.3 BYTES BEFORE THE CUSTOMER NAME = 67 BYTES
2.4 CUSTOMER NAME IN ACTIVITY RECORD = FIRST AND LAST NAME
2.5 ACTIVITY OPTIONS DEFAULT = 00
2.6 DEACTIVATE ACTIVITY OPTIONS = 00
2.7 ACTIVATE ACTIVITY OPTIONS = 00
2.8 COLLECT PANEL DATA FOR ALL CUSTOMERS NO
2.9 MAXIMUM NUMBER OF COUPONS TARGETED PER CUSTOMER = 5

3.1 CREATE AND USE CUSTOMER TRANSFER FILE YES

*** For next page, press PgDn. ***

1 2 3 QUIT 4 5 6 7 ALTER 8 9 0 PRINT

Figure 85. Options Report screen one

If you want to change an option first press the F7 ALTER key. For security reasons
you will be prompted for your signon password. The options report screen with the
signon password prompt is shown below.

Preferred Customer Options Report - STORE 0445 Page 1 of 17

Electronic Marketing Test Store 10/28/92 11:04

1.1 PROGRAM NAME = PREFERRED CUSTOMER

1.2 RAIN CHECK ID DEFINITION = 99999999999
1.3 UPC DISPLACEMENT FOR PREFERRED LINKED ITEMS = NONE
1.4- 1.8 COUPONS FOR FIRST USE OF A CUSTOMER CARD = 0 0 0 0 0

2.1 ACTIVITY FILE SIZE = 1000 RECORDS

2.2 ACTIVITY RECORD SIZE = 121 BYTES
*** WARNING *** PREFERRED CUSTOMER ACTIVITY FILE DOES NOT MATCH OPTIONS
2.3 BYTES BEFORE THE CUSTOMER NAME = 67 BYTES
2.4 CUSTOMER NAME IN ACTIVITY RECORD = FIRST AND LAST NAME
2.5 ACTIVITY OPTIONS DEFAULT = 00
2.6 DEACTIVATE ACTIVITY OPTIONS = 00
2.7 ACTIVATE ACTIVITY OPTIONS = 00
2.8 COLLECT PANEL DATA FOR ALL CUSTOMERS NO
2.9 MAXIMUM NUMBER OF COUPONS TARGETED PER CUSTOMER = 5

3.1 CREATE AND USE CUSTOMER TRANSFER FILE YES

Enter your signon password to continue

1 2 3 QUIT 4 5 6 7 ALTER 8 9 0 PRINT

Figure 86. Options Report screen with prompt for password

After entering your password, a prompt box will come up asking for the option (by
number) that you want to change. The ALTER prompt box can be shifted from the
bottom of the screen to the top and back again by using the PgUp/PgDn keys.
Enter an option number. The screen on the next page shows this prompt with an
option number entered:

266 Electronic Marketing PRPQ

 Preferred Customer Options Report - STORE 0445 Page 1 of 17

Electronic Marketing Test Store 10/28/92 11:04

1.1 PROGRAM NAME = PREFERRED CUSTOMER

1.2 RAIN CHECK ID DEFINITION = 99999999999
1.3 UPC DISPLACEMENT FOR PREFERRED LINKED ITEMS = NONE
1.4- 1.8 COUPONS FOR FIRST USE OF A CUSTOMER CARD = 0 0 0 0 0

2.1 ACTIVITY FILE SIZE = 1000 RECORDS

2.2 ACTIVITY RECORD SIZE = 121 BYTES
*** WARNING *** PREFERRED CUSTOMER ACTIVITY FILE DOES NOT MATCH OPTIONS
2.3 BYTES BEFORE THE CUSTOMER NAME = 67 BYTES
2.4 CUSTOMER NAME IN ACTIVITY RECORD = FIRST AND LAST NAME
2.5 ACTIVITY OPTIONS DEFAULT = 00
2.6 DEACTIVATE ACTIVITY OPTIONS = 00
-------------------------------------------------------------------------
| ENTER THE OPTION NUMBER TO CHANGE (1.1-32.6) ? 2.2 |
| Press Enter to Exit or to Tab to the next option |
| |
| Press PgUp to move the ALTER box up |
|------------------------------| ALTER |---------------------------------|

1 2 3 QUIT 4 5 6 7 ALTER 8 9 0 PRINT

Figure 87. Options Report screen with prompt for option to change

Once you enter the option number a prompt will be given, as shown below, asking
for you to enter the new option value.

Preferred Customer Options Report - STORE 0445 Page 1 of 17

Electronic Marketing Test Store 10/28/92 11:04

1.1 PROGRAM NAME = PREFERRED CUSTOMER

1.2 RAIN CHECK ID DEFINITION = 99999999999
1.3 UPC DISPLACEMENT FOR PREFERRED LINKED ITEMS = NONE
1.4- 1.8 COUPONS FOR FIRST USE OF A CUSTOMER CARD = 0 0 0 0 0

2.1 ACTIVITY FILE SIZE = 1000 RECORDS

2.2 ACTIVITY RECORD SIZE = 121 BYTES
*** WARNING *** PREFERRED CUSTOMER ACTIVITY FILE DOES NOT MATCH OPTIONS
2.3 BYTES BEFORE THE CUSTOMER NAME = 67 BYTES
2.4 CUSTOMER NAME IN ACTIVITY RECORD = FIRST AND LAST NAME
2.5 ACTIVITY OPTIONS DEFAULT = 00
2.6 DEACTIVATE ACTIVITY OPTIONS = 00

------------------------------------------------------------------------------
| 2.2 ACTIVITY RECORD SIZE = 121 |
| ENTER NEW OPTION VALUE ? 101 |
| 31 TO 254 bytes, See documentation for record format and change activation |
| Press Enter to Exit or to Tab to the next option |
-------------------------------------| ALTER |---------------------------------

1 2 3 QUIT 4 5 6 7 ALTER 8 9 0 PRINT

Figure 88. Options Report screen with prompt new option value

Once the new option value is entered the options report screen is usually restored,
as shown below. The exception is if the option allows for multiple entries, such as
option 26.1 GUIDANCES TO BE LOWERED TO OPERATOR OVERRIDABLE. In

Chapter 9. Reports 267

 this case, once the first option is entered, the prompt remains and additional entries
can be made. Pressing the Enter key, without entering any data ends the data entry
and the screen is restored.

After an option has been changed with the ALTER function, the function key F6
SAVE is highlighted. This indicates that the changed options are in memory only
and have not yet been written to disk. This allows you to recover from any errors
you may have made by re-editing the option or quitting the report. Pressing F6
SAVE saves the changes to disk. The F6 SAVE key is then no longer highlighted.

Preferred Customer Options Report - STORE 0445 Page 1 of 17

Electronic Marketing Test Store 10/28/92 11:04

1.1 PROGRAM NAME = PREFERRED CUSTOMER

1.2 RAIN CHECK ID DEFINITION = 99999999999
1.3 UPC DISPLACEMENT FOR PREFERRED LINKED ITEMS = NONE
1.4- 1.8 COUPONS FOR FIRST USE OF A CUSTOMER CARD = 0 0 0 0 0

2.1 ACTIVITY FILE SIZE = 1000 RECORDS

2.2 ACTIVITY RECORD SIZE = 101 BYTES <A>
*** WARNING *** PREFERRED CUSTOMER ACTIVITY FILE DOES NOT MATCH OPTIONS
2.3 BYTES BEFORE THE CUSTOMER NAME = 67 BYTES
2.4 CUSTOMER NAME IN ACTIVITY RECORD = FIRST AND LAST NAME
2.5 ACTIVITY OPTIONS DEFAULT = 00
2.6 DEACTIVATE ACTIVITY OPTIONS = 00
2.7 ACTIVATE ACTIVITY OPTIONS = 00
2.8 COLLECT PANEL DATA FOR ALL CUSTOMERS NO
2.9 MAXIMUM NUMBER OF COUPONS TARGETED PER CUSTOMER = 5

3.1 CREATE AND USE CUSTOMER TRANSFER FILE YES

*** ALTERED OPTIONS ARE MARKED WITH "<A>" ***

1 2 3 QUIT 4 5 6 SAVE 7 ALTER 8 9 0 PRINT

Figure 89. Options Report screen after an option has been altered

Sample Electronic Marketing Preferred Customer Options Report

A sample is on the following page of the printed Electronic Marketing Preferred
Customer Options report, selected from the user report menu. Options can be set
differently in a store.

Preferred Customer Options Report - STORE 0445 Page 1 of 6

Electronic Marketing Test Store Date/Time

1.1 PROGRAM NAME = preferred customer

1.2 RAIN CHECK ID DEFINITION = 99999999999
1.3 UPC DISPLACEMENT FOR PREFERRED LINKED ITEMS = NONE
1.4- 1.8 COUPONS FOR FIRST USE OF A CUSTOMER CARD = 0 0 0 0 0

2.1 ACTIVITY FILE SIZE = 1000 RECORDS

2.2 ACTIVITY RECORD SIZE = 101 BYTES
2.3 BYTES BEFORE THE CUSTOMER NAME = 84 BYTES
2.4 CUSTOMER NAME IN ACTIVITY RECORD = LAST NAME ONLY
2.5 ACTIVITY OPTIONS DEFAULT = 00
2.6 DEACTIVATE ACTIVITY OPTIONS = 00
2.7 ACTIVATE ACTIVITY OPTIONS = 00
2.8 COLLECT PANEL DATA FOR ALL CUSTOMERS NO
2.9 MAXIMUM NUMBER OF COUPONS TARGETED PER CUSTOMER = 10

3.1 CREATE AND USE CUSTOMER TRANSFER FILE YES

268 Electronic Marketing PRPQ

3.2 PROCESS IN STORE TRANSFERS EACH HOUR NO
3.3 STORE COUPONS REDUCE POINTS NO
3.4 TAXES INCREASE POINTS NO
3.5 KEYED CUSTOMER NUMBERS REQUIRE A MANAGER'S OVERRIDE NO
3.6 VALIDATE AUTOMATIC COUPONS YES
3.7 USE COUPON FAMILIES IN VALIDATION OF UPC 5 COUPONS NO
3.8 MANAGER'S OVERRIDE REQUIRED FOR NEW CUSTOMERS NO
3.9 SHOW POINTS IN WHOLE DOLLAR AMOUNTS NO

4.1 PERSONALIZATION MESSAGE FORMAT = 4 (INSTEAD OF TRAILER LINE 2 )

4.2- 4.3 RATIO OF POINTS PER CENTS PURCHASED = 1 / 1
4.4 POINTS ROUNDING SELECTION = CONVENTIONAL ROUNDING
4.5 BONUS ITEM POINTS LIMIT = 999999
4.6 PREFERRED COUPONS BUFFERED IN MEMORY = 20
4.7 MAXIMUM POINTS TO CARRY INTO A NEW PERIOD = 0
4.8 AUTOMATIC CLOSE OF POINTS ACTIVITY PERIOD = NO
4.9 AUTO EXECUTION TIME FOR BATCH UPDATES = NONE
4.0 AUTO EXECUTION TIME FOR TRANSFER PROCESSING = NONE

5.1 PREFERRED CUSTOMER COUPON VELOCITY CODE RANGE = 300 TO 399

5.3 REUSABLE TARGETED COUPON VELOCITY CODE RANGE = 300 TO 350
5.5 VALID RANGE OF NON-HOME STORE NUMBERS = 1 TO 9999
6.1 AUTO EXECUTION TIME FOR REFERENCE PROCESSING = NONE
6.2 MULTIPLIER FOR COUPON MINIMUM PURCHASE AMOUNTS = NONE
6.3 KEY DEFINITION FOR CUSTOMER ENTRY KEY = 89

7.1 MAXIMUM LENGTH OF A CUSTOMER NUMBER = 11

7.2 OFFSET OF HOME STORE NUMBER WITHIN A CUSTOMER NUMBER = 2
7.3 LENGTH OF HOME STORE NUMBER WITHIN A CUSTOMER NUMBER = 4
7.4 CATEGORY TO IDENTIFY SCANNED CUSTOMER NUMBERS = 9
7.5 OFFSET OF VALIDATION DIGITS WITHIN A CUSTOMER NUMBER = 0
7.6 NUMBER OF VALIDATION DIGITS WITHIN A CUSTOMER NUMBER = 0
7.7 VALUE OF VALIDATION DIGITS WITHIN A CUSTOMER NUMBER = 0
7.8 COUNT OF HOME STORE NUMBERS SUPPORTED BY THIS STORE = 1
7.9 COUNT OF HOME STORE NUMBERS SUPPORTED ONLY BY THIS STORE = 1

8.1 HOME STORE NUMBERS SUPPORTED BY THIS STORE = 445 (0 = 445)

Preferred Customer Options Report - STORE 0445 Page 2 of 6

Electronic Marketing Test Store Date/Time

9.1 MODULO CHECK CUSTOMERS NUMBERS DURING ENROLLMENT NO

9.2 LOG ENROLLMENT ADDS/CHANGES TO A SEPARATE FILE NO
9.3 LOG ENROLLMENT REDEMPTIONS/ADJUSTMENTS NO
9.4 ALLOW ERASE OF CUSTOMER POINTS NO
9.5 FORM NUMBER REQUIRED ON REDEMPTION ENTRY NO
9.6 FORM NUMBER REQUIRED ON ADJUSTMENT ENTRY NO
9.7 FORM NUMBER REQUIRED ON RAIN CHECK ENTRY NO
9.8 EMPLOYEE NUMBER REQUIRED ON REDEMPTION ENTRY NO
9.9 EMPLOYEE NUMBER REQUIRED ON ADJUSTMENT ENTRY NO
9.0 EMPLOYEE NUMBER REQUIRED ON RAIN CHECK ENTRY NO

10.1 DEACTIVATE ENROLLMENT CHANGE FUNCTION NO

10.2 DEACTIVATE ENROLLMENT ADD FUNCTION NO
10.3 DEACTIVATE ENROLLMENT ERASE FUNCTION NO
10.4 DEACTIVATE ENROLLMENT DISPLAY FUNCTION NO
10.5 DEACTIVATE ENROLLMENT REDEMPTION FUNCTION NO
10.6 DEACTIVATE ENROLLMENT ADJUSTMENT FUNCTION NO
10.7 DEACTIVATE ENROLLMENT RAIN CHECK FUNCTION NO
10.8 USE ENROLLMENT WITHOUT AN ENROLLMENT FILE NO
10.9 ENROLLMENT ZIP FIELDS ARE NUMERIC AND PACKED YES

11.1 ONLY ALLOW 1 TERMINAL TO HAVE NEGATIVE TRANSACTIONS = NO

11.2 DEFINE WHICH TAXES TO TURN ON WITH THE TAX/NOTAX KEY = F0
11.3 KIOSK POINTS MESSAGE OFFSET = 0
11.4 MAXIMUM ITEM RECORD DESCRIPTOR LENGTH = 18
11.5 LENGTH OF ENROLLMENT STATE FIELD 2

Chapter 9. Reports 269

 11.6 LENGTH OF ENROLLMENT ZIP FIELD 5
11.7 LENGTH OF ENROLLMENT ZIP EXT FIELD 4
11.8 COUNT OF CUSTOMER DEFINED DEMOGRAPHIC FIELDS 0
11.9 LENGTH OF ENROLLMENT SOCIAL SECURITY FIELD 9

12.1 ACCUMULATE RATIO OF PLU ENTRIES TO DEPT KEY ENTRIES NO

12.2 ACCUMULATE KEYED VS SCAN TOTALS BY DEPARTMENT NO
12.3 WEIGHT ITEMS DON'T REQUIRE WEIGHT KEY YES
12.4 DISPLAY BACKUP INDICATOR AT REGISTERS NO
12.5 ALLOW TAX EXEMPTION WITHOUT A DISCOUNT KEY NO
12.6 CASH CHECKS USING A SALES TRANSACTION NO
12.7 REMIND OPERATOR TO TAKE THE CUSTOMER'S MONEY NO
12.8 INTERPRET RESTRICTED TIME PERIODS AS UNRESTRICTED TIMES NO
12.9 SUPPORT FOR MULTIPLE CASH DRAWERS NO
12.0 SHOW TIME IN 12 HOUR FORMAT NO

13.1 CHECK THE SUM OF ALL VOIDS AT EACH VOID ENTRY NO

13.2 HIGHLIGHT THE PRINTING OF AUTOMATIC COUPONS YES
13.3 HIGHLIGHT THE PRINTING ALL EXCEPTIONAL ENTRIES YES
13.4 PRINT AVAILABLE TARGETED COUPONS ON THE CUSTOMER RECEIPT YES
13.5 REMIND THE CHECKER TO ASK FOR A CUSTOMER CARD NO
13.6 USE PERIOD POINTS FOR BOUNDARY OPTIONS NO
13.7 ONLY POINTS IN THIS PERIOD ARE AVAILABLE FOR REDEMPTION NO
13.8 NEW CUSTOMER MESSAGE STARTS EACH NEW ACTIVITY PERIOD NO
13.9 NEW CUSTOMER COUPONS START EACH NEW ACTIVITY PERIOD NO
13.0 KEEP MONTHLY PREVIOUS POINTS ACTIVITY FOR CUSTOMERS NO
Preferred Customer Options Report - STORE 0445 Page 3 of 6

Electronic Marketing Test Store Date/Time

14.1 TENDERS USING PREFERRED CUSTOMER NUMBER AS ACCOUNT NUMBER = NONE

14.2 TENDERS USING ALTERNATE CUSTOMER NUMBER AS ACCOUNT NUMBER = NONE
14.3 OVERRIDE IS REQUIRED TO CHANGE TENDER VERIFICATION NUMBER NO
14.4 OPERATOR'S OVERRIDE IS SUFFICIENT TO CHANGE TENDER NUMBER NO

15.1 POINT BOUNDARY OPTIONS NOT DEFINED

16.1 KEEP OLD PERIOD AUDIT LOG DATA YES

16.2 APPEND AUDIT DATA TO EAMPANEL AT CLOSE NO
16.3 KEEP AUTO STORE COUPONS IN DEPT TOTALS EXIT FIELD NO
16.4 KEEP MULTIPLIED COUPONS IN DEPT TOTALS EXIT FIELD NO
16.5 KEEP AUTO VENDOR COUPONS IN DEPT TOTALS EXIT FIELD NO
16.6 EXCLUDE AUTO COUPONS FROM REPORTED COUPON COUNTS NO
16.7 ADD PERIOD SUMMARY INFORMATION TO PANEL FILE NO
16.8 DEPOSIT AUTO VENDOR COUPONS IN MISC. ACCOUNT NO
16.9 DEPOSIT AUTO STORE COUPONS IN MISC. ACCOUNT NO
16.0 DEPOSIT MULTIPLIED COUPONS IN MISC. ACCOUNT NO

17.1 POINT RANGES FOR PERIOD CLOSE REPORT NOT DEFINED

18.1 AUTOMATIC DISCOUNTS FOR ASSOCIATED POINTS RANGES NOT DEFINED

19.1 EXCLUDE NON-POINTS ITEMS FROM MINIMUM PURCHASE LIMITS NO

19.2 ADD CUSTOMER NUMBER TO COUPON TRACKING FILE RECORDS NO
19.3 ALWAYS USE THE MANUFACTURER NUMBER FROM A COUPON RECORD YES
19.4 STAGE ACTIVITY FILE AT EACH CLOSE OF REPORTING PERIOD NO
19.5 TREAT ALL NON-PREFERRED CUSTOMERS AS RAIN CHECK CUSTOMERS NO
19.6 REMOVE DOUBLED COUPONS FROM STORE COUPONS BY DEPARTMENT NO
19.7 OVERRIDE NEEDED FOR KEYED PREFERRED CUSTOMER COUPONS NO
19.8 ACCEPT ELECTRONIC AND PAPER VENDOR COUPONS ON SAME ITEM NO
19.9 ACCEPT ELECTRONIC AND PAPER STORE COUPONS ON SAME ITEM NO
19.0 DOUBLED COUPONS AVAILABLE ONLY TO PREFERRED CUSTOMERS NO

20.1 SAVE DATE OF LAST SALE FOR ITEMS AT CLOSE OF MOVEMENT NO

20.2 USE PROMOTION CODES FOR COUPON VALIDATION NO
20.3 SHOW ONLY PAPER COUPONS IN CASH DRAWER REPORTS NO
20.4 BYPASS JOURNAL PRINTING OF AUTOMATIC COUPON REJECTIONS NO
20.5 BYPASS RECEIPT PRINTING OF TARGETED COUPON NUMBERS NO

270 Electronic Marketing PRPQ

20.6 MATCH COUPONS AGAINST CROSS PROMOTIONAL GROUP NO
20.7 AUTOMATIC TARE FROM WEIGHT ITEM RECORDS YES
20.8 BYPASS FIXED TARGETED MESSAGE IF PROMOTION TEXT PROVIDED NO
20.9 VALIDATE EXPIRATION DATE WITH MSR ENTRY OF CUSTOMER ID NO
20.0 DEACTIVATE UNIQUE ELECTRONIC MARKETING EXIT CODE NO

21.1 USE COMPRESSED PRINT IN THE SELECTIVE CUSTOMER REPORT NO

21.2 USE 132 CHARACTER LINES IN THE SELECTIVE CUSTOMER REPORT NO
21.3-21.4 ADDRESS LABEL FORMAT 1 = 5 LINES, 40 CHARACTERS
21.5-21.6 ADDRESS LABEL FORMAT 2 = 6 LINES, 35 CHARACTERS
21.7-21.8 ADDRESS LABEL FORMAT 3 = NOT DEFINED

22.1 DEACTIVATE SELECTIVE CUSTOMER REPORT ERASE FUNCTION NO

22.2 DEACTIVATE SELECTIVE CUSTOMER REPORT PRINT FUNCTION NO
22.3 DEACTIVATE SELECTIVE CUSTOMER REPORT SAVE FUNCTION NO
22.4 DEACTIVATE SELECTIVE CUSTOMER REPORT BATCH FUNCTION NO
22.5 DEACTIVATE SELECTIVE CUSTOMER REPORT LABEL FUNCTION NO
Preferred Customer Options Report - STORE 0445 Page 4 of 6

Electronic Marketing Test Store Date/Time

22.6 NO PRINT OF SELECTIVE CUSTOMER REPORT BEFORE DISPLAY NO

22.7 DEACTIVATE VERIFY OF TARGETED COUPONS WHEN CREATING A BATCH NO
22.8 DEACTIVATE PROMPT FOR RESTORE BATCH WHEN CREATING A BATCH NO
22.9 DEACTIVATE PROMPT FOR FILE COPY WHEN CREATING A BATCH NO
23.1-23.0 RESERVED FOR FUTURE USE

24.1 ALL COUPONS REQUIRE AT LEAST DEPARTMENT LEVEL VALIDATION NO

24.2 VALIDATE ALL DEPARTMENT KEYED COUPONS BY DEPARTMENT NO
24.3 SEQUENCE NUMBER AND VELOCITY CODE IN STORE COUPON UPC'S NO
24.4 STORE COUPONS LOGGED IN THE COUPON TRACKING FILE NO
24.5 VENDOR COUPONS LOGGED IN THE COUPON TRACKING FILE YES
24.6 DOUBLED COUPONS LOGGED IN THE COUPON TRACKING FILE NO
24.7 COUPON TRACKING FILE ENTRIES IN COMPRESSED FORMAT NO

25.1 MANUFACTURER NUMBER TO IDENTIFY UPC 5 STORE COUPONS = NONE

25.2 RANGE OF COUPON UPCS TO LOG IN THE COUPON TRACKING FILE = ALL
25.4 RANGE OF DEPARTMENTS TO VALIDATE BY SUBTOTAL GROUP = NONE
26.1 GUIDANCES TO BE LOWERED TO OPERATOR OVERRIDABLE = 199

27.1 DOUBLED COUPON VALUE LIMIT PER COUPON = 9999

27.2 NO DOUBLING OF COUPONS OVER THE VALUE LIMIT NO
27.3 VALUE LIMIT APPLIES TO THE SUM OF THE COUPON AND DOUBLE NO
27.4 MINIMUM TRANSACTION SIZE FOR COUPON DOUBLING = 0
27.5 DOUBLED COUPON COUNT LIMIT PER ORDER = 999
27.6 PURCHASE AMOUNT FOR THE COUPON DOUBLING COUNT LIMIT = 0
27.7 LIMIT OF IDENTICAL COUPONS TO BE DOUBLED IN AN ORDER = 999
27.8 MANUAL COUPON DOUBLING ALLOWED NO , LOOKUP KEY CODE = NONE

28.1 DAYS OF WEEK ON WHICH COUPON DOUBLING IS NOT ACTIVE = NONE

29.1-29.0 RESERVED FOR FUTURE USE
30 END OF FILE MARKER = *END*

SELECTIVE ITEM RECORD REPORT OPTIONS

31.1 ALLOW SAVING OF REPORT DATA TO FILE YES

31.2 ALLOW PRINTING OF THE REPORT WITH NO DISPLAY NO
31.3 ALLOW RESETTING OF ITEM MOVEMENT NO
31.4 ALLOW CREATION OF MAINTENANCE BATCHES NO
31.5 ALLOW DELETION OF ITEM RECORDS NO
31.6 ALLOW CREATION OF ITEM MOVEMENT LISTS NO
31.7 EXIT FIELD 1 CONTAINS PACKED DECIMAL DATA NO
31.8 EXIT FIELD 2 CONTAINS PACKED DECIMAL DATA NO
31.9 REPORT EXIT 1 AND EXIT 2 AS A SINGLE FIELD NO
31.0 USE A 1 PAGE MENU FOR ALL 16 SEARCH SELECTIONS YES

32.1 PRINTED REPORTS ARE IN COMPRESSED MODE NO

Chapter 9. Reports 271

 32.2 PRINTED REPORTS USE 132 CHARACTER LINE FORMATS NO
32.3 AUTOMATICALLY UPDATE ITEM FAMILY WITH THE LOW 3 LINK DIGITS NO
32.4 ALL BATCHES ARE CREATED AS DDM OPERATOR CONTROLLED BATCHES NO
32.5 ALL BATCHES ARE CREATED AS ADDMI BATCHES NO
32.6 ALL BATCHES ARE CREATED AS ADDMI IMMEDIATE UPDATES NO
32.7 AUTOMATICALLY UPDATE PROMOTION CODES TO EQUAL THE LINK NO
Preferred Customer Options Report - STORE 0445 Page 5 of 6

Electronic Marketing Test Store Date/Time

*** PREFERRED CUSTOMER MESSAGE TEXT ***

*** FOR THE FIRST 10 MESSAGES ***

0 Points message for home store Preferred Customers

DISPLAY = GOOD CUSTOMER @nnnnnnnnnnnnnnnnnnnnnn
PRINT 1 = THIS ORDER ADDED @ccc OF COUPONS AND ,1
PRINT 2 = @ttttt VALUE POINTS TO BRING YOUR NEW ,1
PRINT 3 = TOTAL TO @cggg SAVED AND @ppppp POINTS,3

1 Points message for non-home store Preferred Customers

DISPLAY = WELCOME TO OUR STORE @nnnnnnnnnnnnnnnnnn
PRINT 1 = LOOK FOR @ttttt POINTS TO BE ,1
PRINT 2 = TRANSFERRED TO YOUR HOME STORE ,1

2 Points message for new Preferred Customers

DISPLAY = WELCOME NEW MEMBER @aaaaaaaaaaaa
PRINT 1 = PRESENT YOUR CARD WITH EVERY ORDER
PRINT 2 = AND RECEIVE PROMOTIONAL DISCOUNTS
PRINT 3 = **** YOU SAVED @cnz ON THIS ORDER ****

3 Points message for non-Preferred Customers

DISPLAY = VALUED CUSTOMER
PRINT 1 = ASK THE MANAGER HOW OUR NEW FREQUENT ,1
PRINT 2 = BUYER PROGRAM CAN SAVE YOU MONEY ,1
PRINT 3 = YOU COULD HAVE SAVED @cnzz TODAY ,3

4 Personalization message for Preferred Customers

DISPLAY = WE RECOGNIZE CUSTOMER LOYALTY
PRINT 1 = WE APPRECIATE YOUR LOYAL PATRONAGE ,1
PRINT 2 = @nnnnnnnnnnnnnnnnnnnnnnnnnnn ,6

5 Points message for transferred Preferred Customer points

DISPLAY = * TRANSFERRED IN @txxxx POINTS
PRINT 1 = @txxxx POINTS FROM @qx TRANSACTIONS ,1
PRINT 2 = THROUGH @dxxxxxx TRANSFERRED IN ,2

6 Points message for Preferred Customer Rain check

DISPLAY = PLEASE SCAN CUSTOMER CARD
PRINT 1 = TO RECEIVE THE @ttttt POINTS FOR THIS ,1
PRINT 2 = ORDER, YOU MUST PRESENT THIS RECEIPT ,1
PRINT 3 = TO THE MANAGER WITH YOUR ID CARD ,1

7 Preferred Customer bonus points message

PRINT 1 = @tbbbb BONUS POINTS ARE ADDED TO ,1
PRINT 2 = @tiiii POINTS FOR ITEMS PURCHASED ,1

8 Preferred Customer redeemed points message

PRINT 1 = @trrrr POINTS REDEEMED IN THIS ORDER ,1
PRINT 2 = FOR A TOTAL OF @rrrrr POINTS REDEEMED ,1

9 Preferred Customer available targeted coupons message

PRINT 1 = THE FOLLOWING COUPONS ARE STILL ,1
PRINT 2 = AVAILABLE TO YOU UNTIL NEXT MONTH ,2
Preferred Customer Options Report - STORE 0445 Page 6 of 6

Electronic Marketing Test Store Date/Time

272 Electronic Marketing PRPQ

 *** PANEL FILTER OPTIONS ***

REAL TIME FILTER FILE EAMFBFLT

00:ZZ:2:3:4:5:6:7:8:9:10:11:12:13:KK KEY 8 OFF

ACTIVE CHECKOUT SUPPORT USER EXITS

1, 3, 4, 6, 11-17

ACTIVE TERMINAL USER EXITS (FROM EAMTO000)

1-3, 7, 8, 14, 18, 20, 21, 23, 24, 27, 28, 30, 31, 37, 39, 40,
42, 43, 51, 53, 54

Accounting Reports
The electronic coupon data and preferred customer sales data that is added to the
accounting totals (see “Accumulating Electronic Coupons Totals” on page 245) is
used by the altered accounting reports to help account for the paperless electronic
coupons and to show the volume of preferred customer activity by operator/terminal
and for the entire store. Lines are added to the operator/terminal and summary
cash reports, the store recap report, and the operator performance report to show
the following values:
v Counts and amounts of preferred customer purchases and coupons
v Percentage of sales accounted for by preferred customers
v Average purchase for a preferred customer compared to a nonparticipating
customer.
Lines are added to the operator/terminal, office, and summary cash reports to
separate accountability for the paperless coupons from accountability for the
counted store and manufacturer coupons.

Chapter 9. Reports 273

274 Electronic Marketing PRPQ
Part 3. Utilities and Programming
Chapter 10. Utilities -- Installation and Operational . . . . . . . . . . 277
Installation Utilities . . . . . . . . . . . . . . . . . . . . . . . 277
DESCADDE - Auto Install of Electronic Marketing Descriptors . . . . . . 277
DESCADDR - Auto Install of New Report Descriptors . . . . . . . . . 278
DESCADDS - Auto Install of New Sales Descriptors. . . . . . . . . . 278
FIXFILES - Keyed File Record Reformatting . . . . . . . . . . . . 279
FIXR1OPT - Convert Options Files to New Format . . . . . . . . . . 280
LOGNAMES - Install Preferred Customer Logical Names . . . . . . . . 281
Operational Utilities . . . . . . . . . . . . . . . . . . . . . . . 282
EAMUBATP - Batch Maintenance for Keyed files . . . . . . . . . . . 282
Functions and Limitations . . . . . . . . . . . . . . . . . . 283
Batch Interface Definition. . . . . . . . . . . . . . . . . . . 283
Batch Maintenance File (EAMBATCH) . . . . . . . . . . . . . . 284
Record Format - Batch Header Record . . . . . . . . . . . . . 284
Record Format - Data Record . . . . . . . . . . . . . . . . . 285
Record Format - Targeted Coupon Data Record . . . . . . . . . . 287
Examples of Targeted Coupon Record Usage within EAMBATCH: . . . 288
Record Format - Message Record . . . . . . . . . . . . . . . 289
Batch Report (EAMBREPT) . . . . . . . . . . . . . . . . . . 289
Record Format - Report Header Record . . . . . . . . . . . . . 289
Record Format - Report Data Record . . . . . . . . . . . . . . 290
Batch Status (EAMBSTAT) . . . . . . . . . . . . . . . . . . 290
Record Format . . . . . . . . . . . . . . . . . . . . . . 290
Exception Log Updates . . . . . . . . . . . . . . . . . . . 291
Delayed Data Maintenance Error Log Updates . . . . . . . . . . . 291
System Error Log Updates . . . . . . . . . . . . . . . . . . 292
Sample EAMBATCH Data . . . . . . . . . . . . . . . . . . 292
EAMUREFA - Preferred Customer Reference Processing . . . . . . . . 293
EAMUROLP - Roll Customer Period Totals Procedure . . . . . . . . . 294
EAMUPM3L - Manual Close of Points Activity Period . . . . . . . . . 294
EAMUPM4L - Maintain Targeted Coupon Messages . . . . . . . . . . 295
EAMUXFER - Process Customer Data from Other Stores. . . . . . . . 295
EAMUFILT - Filters Transaction Summary Log Data . . . . . . . . . . 295
EAMUPKUP - Automatic Pickup of Paperless Coupons . . . . . . . . 296
EAMUDOLS - Date of Last Sale Update Function . . . . . . . . . . 296
Item Record Update . . . . . . . . . . . . . . . . . . . . 296
Item Movement Staging . . . . . . . . . . . . . . . . . . . 297
Input Options (Parameters) . . . . . . . . . . . . . . . . . . 297

Chapter 11. Electronic Marketing Unique User Exits . . . . . . . . . 299

Electronic Marketing Unique User Exits . . . . . . . . . . . . . . . 299
Electronic Marketing Terminal User Exits . . . . . . . . . . . . . . . 300
Exit TSEMEC01 - Called After The Read Of A Customer Activity Record 300
Exit TSEMEC02 - Called After The Read Of A Customer Transfer Record 301
Exit TSEMEC03 - Called After The Read Of A Coupon Message Record 301
Exit TSEMEC04 - Called After The Input Of A Customer Number in
Response to a Prompt (Input from MSR) . . . . . . . . . . . . . 302
Exit TSEMEC05 - Called After Validation Of A Customer Number . . . . . 302
Exit TSEMEC06 - Called After Computing A Coupon Value Based On The
Value Of Matching Items . . . . . . . . . . . . . . . . . . . 303
Exit TSEMEC07 - Called Before Assuring The Minimum Purchase For A
Coupon Is Met. . . . . . . . . . . . . . . . . . . . . . . 303
Exit TSEMEC08 - Called After Computing The Points Value Of An Order 304

© Copyright IBM Corp. 1991 2000 275

 Exit TSEMEC09 - Called After Saving A Coupon For Total Time . . . . . 304
Exit TSEMEC10 - Called At Checking For Crossing A Points Boundary 305
Exit TSEMEC11 - Called Before Giving Automatic Coupons At The Entry Of
A Customer Number . . . . . . . . . . . . . . . . . . . . 305
Exit TSEMEC12 - Called Before Giving Automatic Coupons At Total Time 306
Electronic Marketing Controller User Exits . . . . . . . . . . . . . . 307
Exit CSEMEC01 - Called After the Read of a Customer Activity Record 307
Exit CSEMEC02 - Called After the Read of a Customer Transfer Record 308
Exit CSEMEC03 - Called Before the Write of a Customer Activity Record 309
Exit CSEMEC04 - Called Before the Write of a Customer Transfer Record 310
Exit CSEMEC05 - Called Before the Write of an Activity Transfer Record 310
Exit CSEMEC06 - Called After The Update Of Accounting Totals . . . . . 311
Exit CSEMEC07 - Called Before The Write Of A Preferred Customer Audit
Log Record . . . . . . . . . . . . . . . . . . . . . . . . 312
Exit CSEMEC08 - Called Before the Write of a Panel Diary Record . . . . 312
Exit CSEMEC09 - Called Before The Write Of A Coupon Tracking Record 313

276 Electronic Marketing PRPQ

Chapter 10. Utilities -- Installation and Operational
This chapter documents the Electronic Marketing utility programs. This includes
programs used to support the installation and operation of the Electronic Marketing
application.

Installation Utilities
The following utility programs are documented in the Installation Utilities section:
v DESCADDE - Auto Install of Electronic Marketing Descriptors
v DESCADDR - Auto Install of New Report Descriptors
v DESCADDS - Auto Install of New Sales Descriptors
v FIXFILES - Keyed File Record Reformatting
v FIXR1OPT - Convert Options Files to New Format
v LOGNAMES - Install Preferred Customer Logical Names.

DESCADDE - Auto Install of Electronic Marketing Descriptors

This utility program can be used to update or add descriptors to the Electronic
Marketing descriptor file, [Link]. By using this utility to install or change
a descriptor, a great deal of error-prone manual entry can be avoided in the process
of installing this package.

This utility program is run only on the master controller and will update the set of
descriptors added or altered for Preferred Customer processing. If you do not like
the default descriptors, change them after running these programs, unless you want
to change one or more of the default descriptors contained in [Link].

It is not necessary to run this program during the installation of Electronic

Marketing. It is sufficient that [Link] is copied to your system.

This program is supplied as a load module, DESCADDE.286. This module is

executed in command mode while in or when pointing to the disk and directory onto
which you have chosen to place this code. The program can be run from the A disk
since there is no real reason for the code to reside on a controller.

In response to the DESCADDE command, the program will proceed to add the new
report descriptors and will print each new descriptor that is added, updated or
rejected. The program will reject any descriptor whose length is over 40 characters
and any descriptor numbered over 5000. The program will complete with a printed
status message that shows whether all new descriptors were processed
successfully.

The report descriptors to be added by the DESCADDE program reside in a module

named [Link]. The program looks for the needed input data file first on
C:ADX_IPGM, and if it is not found, then it looks in the root directory of the A drive.
If you do not like the default descriptors, you can change them with an editor before
running the program.

The following shows an example input file for this program:

824,"FILE TRANSLATION PROCESS COMPLETED SUCCE"
825,"SSFULLY "
826,"FILE TRANSLATION PROCESS COMPLETED WITH"
827,"ERRORS "
828,"EAMUROLP MUST BE RUN AS A BACKGROUND PR"
829,"OGRAM. "

© Copyright IBM Corp. 1991 2000 277

 The following shows what the output from this program would look like:
"ADD DESCRIPTORS TO EAMEDESC "
DESCRIPTOR 824 ADDED AS FILE TRANSLATION PROCESS COMPLETED SUCCE
DESCRIPTOR 825 ADDED AS SSFULLY
DESCRIPTOR 826 ADDED AS FILE TRANSLATION PROCESS COMPLETED WITH
DESCRIPTOR 827 ADDED AS ERRORS
DESCRIPTOR 828 ADDED AS EAMUROLP MUST BE RUN AS A BACKGROUND PR
DESCRIPTOR 829 ADDED AS OGRAM.
"ALL INPUT SUCCESSFULLY PROCESSED "

DESCADDR - Auto Install of New Report Descriptors

This utility program adds all of the report descriptors needed for the Electronic
Marketing application. Use of this utility program to install the report descriptors
removes the necessity for a great deal of manual entry.

This utility program is run only on the master controller. It attempts to update the
master copy of the report descriptor file [Link]. The program overwrites
the set of descriptors added or altered for preferred customer processing with the
default descriptors. If you do not want the new default descriptors, change them
after running this utility program.

This utility program is supplied as a load module DESCADDR.286. This module is

executed in Command mode while in or pointing to the disk because there is no
reason for the code to reside on a controller.

It is executed by typing DESCADDR on the command line, then pressing Enter.

In response to the DESCADDR command, the utility program adds the report
descriptors and prints each report descriptor that is added or updated. The utility
program completes with a printed status message that shows whether all report
descriptors were processed successfully.

The report descriptors to be added by this utility program reside in a module named
[Link]. The module is supplied with the Electronic Marketing application
and contains all of the report descriptors that are needed by the Electronic
Marketing application.

This utility program searches for the input file [Link] first on
C:ADX_IPGM, and if it does not locate the file there, in the root directory of the A
drive.

The data in the input file defines the report descriptors and their target locations
with a separate line in the form:
4342,"Coupon Gives Bonus Points"

for each report descriptor to be added.

DESCADDS - Auto Install of New Sales Descriptors

This utility program adds all of the Terminal Sales Descriptors needed by the
Electronic Marketing application. Use of this utility program to install the sales
descriptors removes the necessity for a great deal of manual entry.

The utility program is run only on the master controller. It updates the master copy
of the Terminal Sales Descriptor file [Link].

278 Electronic Marketing PRPQ

 This utility program overwrites the original set of descriptors with an altered set for
preferred customer processing. If you do not want to use the new default
descriptors, change them after running this utility program.

The utility program is supplied as a load module DESCADDS.286. The module is

executed in Command mode while in the directory or when pointing to the disk and
directory onto which you have chosen to place DESCADDS.286.

The utility program can be run from the A: disk by typing DESCADDS from the
command line and then pressing Enter.

In response to the DESCADDS command, the utility program adds sales

descriptors and prints each sales descriptor that is added or updated. The utility
program completes with a printed status message that shows whether all sales
descriptors were processed successfully.

The sales descriptors to be added by this utility program reside in a module named
[Link]. The utility program searches for the input file [Link]
first on C:\ADX_IPGM, and if it does not locate the file there, it searches the root
directory of the A: drive. The data in the input file defines the sales descriptors and
their target locations with a separate line in the form:
"935,"CHECK CUSTOMER NUMBER "

for each sales descriptor to be added.

FIXFILES - Keyed File Record Reformatting

This utility program alters the size of the records in a keyed file as it copies them
from a saved copy to a new copy.

The requirements for running the utility are:

v The saved and new files must reside on ADX_IDT1 before you run the utility.
v A logical name must exist for the new file.
v The saved and new copies must have the same file name, but the file extension
can be different.
Run this utility if the saved and new copies of a keyed file use different record or
key lengths.

The FIXFILES.286 load module is executed from the command line by typing the
name FIXFILES and pressing Enter. You must be either in the directory where
FIXFILES resides or point to that directory.

It is not necessary to copy the utility to the C: drive. It can be run from the A: drive.

The utility prompts for the name of the saved file and the disk drive where this file is
found in the ADX_IDT1 directory.

If the Preferred Customer Activity File is to be altered, a prompt is displayed for the
lengths of the customer name field and the saved file. After the input is provided,
the utility shows how it will change the records and prompts for an OK to continue.
After the OK, the utility processes all records in the saved file by reformatting them
and writing them to the new file. The saved file is not altered. The records in the
new file are replaced.

Chapter 10. Utilities -- Installation and Operational 279

 This procedure can be run multiple times for the same files. During execution, the
number of records found, reformatted, and written to the new file is displayed.

In the process of reformatting keyed records, all data in the records that is possible
to save is preserved. The following table presents the ways that data in the records
is preserved under various conditions.

IF the. . . THEN the old. . .

Record key is enlarged Record key is right justified and padded with
packed zeros
Record key is reduced Record key is truncated from the left
Record size is enlarged Record is padded on the right with zeros
Record size is reduced Record is truncated from the right

In the Preferred Customer Activity File, the customer name is located in a defined
position at the end of the record. (See 323.) If the start of the customer name is
moved further back into the record, additional packed zeros are inserted prior to the
name field.

The utility program handles any keyed file, but it is specifically intended to handle
changes in the Preferred Customer Activity File. For this file, you define the new
record length, (see “Activity Record Size” on page 82) the new size and contents of
the customer name field (see “Format of Customer Name in Activity Record” on
page 83), and the need for any additional fields. The following steps can be
performed to make these changes to the activity file:
1. Sign off all registers. (The store must be closed.)
2. Stop checkout support from the background screen.
3. Rename [Link] to [Link] on \ADX_IDT1.
4. Verify that the file options in [Link] are set correctly.
5. Start checkout support to create a new, empty activity file.
6. Run FIXFILES to reformat and move the old records to the new file.
7. Test the system to ensure that it runs correctly against the new file.
8. Erase the file [Link] when you are sure the new file is correct.

FIXR1OPT - Convert Options Files to New Format

This utility program converts the two options files used by Electronic Marketing
application, 1991 release into the one larger options file used by Electronic
Marketing application.

A user who is converting from the earlier release to the current release can use this
utility program to migrate his old options to the new format and thereby avoid
having to re-enter the options.

The two files [Link] and [Link] provide input to the utility
program. A logical name must exist for both of these files. The data from these files
is merged into a local file named [Link]. This file can be used to replace
[Link]. It is suggested that the options report be used to record all
options values before this conversion and used again after the conversion to verify
the new options settings.

This utility program is supplied as a load module FIXR1OPT.286. This module is

executed in command mode. The program can be run from the A disk since there is
no real reason for the code to reside on a controller. In response to the FIXR1OPT
command, the program will proceed to create the new options file

280 Electronic Marketing PRPQ

 C:\ADX_IPGM\[Link]. Any errors encountered during the processing will
be displayed. If the processing completes without errors, then the new file can be
renamed to [Link] and have its distribution type changed to
COMPOUND PER UPDATE by the file utilities. Only after this last step can the new
options report be used to verify the contents of the file and to set the newly
available options.

LOGNAMES - Install Preferred Customer Logical Names

This utility program adds all of the logical names needed for the Electronic
Marketing PRPQ to the user logical names file. By using this utility program to
install these user logical names, a great deal of manual entry can be avoided in the
process of installing this package.

This utility program should be run on the master controller. It will then attempt to
update the user logical file names for both the master and the Alternate (DD)
controllers. If it is run on other than the master, it will attempt to update the user
logical file names for both the master and for the controller on which it is running.
The program will not normally add or change a logical name that already exists on
the user logical names file, so it can be run multiple times with no negative impacts.
If the parameter ″REPLACE″ is specified after the LOGNAMES command, then
mismatching logical names that are already present will be replaced with the new
logical name.

The utility program is supplied as a load module LOGNAMES.286. The module is

executed in Command mode while in the directory or when pointing to the disk and
directory onto which you have chosen to place LOGNAMES.286. The utility
program can be run from the A disk by typing LOGNAMES from the command line
and then pressing Enter. In response to the LOGNAMES command, the utility
program adds logical names and prints each logical name that is added or is
already present. It will also print any previously defined logical names which do not
match the new input names and will show if the old name was replaced by the new
name. The utility program completes with a printed status message that shows
whether all logical names were processed successfully.

The logical names to be added by this utility program reside in a module named
[Link] supplied with the Electronic Marketing application. It contains all
of the logical names that are needed by the Electronic Marketing application. The
utility program searches for the input file [Link] first on C:\ADX_IPGM,
and if it does not locate the file there, it searches the root directory of the A: drive.

The following shows an example input file for this program.

! This is a comment line
"EAMFBOPT","ADX_IPGM:[Link]:"
"EAM: ,"
"ADXLXACN::C:\ADX_IDT4\EAMX"
"EAMPANEX","ADXLXACN::C:\ADX_IDT4\[Link]"
"EAMPANEL","ADXLXACN::C:\ADX_IDT4\[Link]"
"EAMFBAUD","ADXLXACN::C:\ADX_IDT4\[Link]"
"EAMFBAUO","ADXLXACN::C:\ADX_IDT4\[Link]"

The following shows an example output file when these logical names already exist.
Note that one logical name is new and is added, one differs from the data file and
what is on the system, and the others are identical. Also, note that the program tells
you to run LOGNAMES with the replace option if you want to actually update the
one option that is different.

Chapter 10. Utilities -- Installation and Operational 281

 THIS CONTROLLER IS CC AND THE MASTER CONTROLLER IS CC
ADD LOGICAL NAMES TO ADXLXAAN::ADX_SPGM:[Link]
EAMFBOPT ADDED AS ADX_IPGM:[Link]
EAM: ALREADY PRESENT, LEFT AS IS
OLD NAME: ADXLXACN::C:\ADX_IDT4\EAMX
NEW NAME: ADXLXACN::D:\ADX_IDT4\EAMX
EAMPANEX ALREADY PRESENT, LEFT AS IS
EAMPANEL ALREADY PRESENT, LEFT AS IS
EAMFBAUD ALREADY PRESENT, LEFT AS IS
EAMFBAUO ALREADY PRESENT, LEFT AS IS
*** SPECIFY “LOGNAMES REPLACE” TO REPLACE MISMATCHING NAMES ***

The following shows an example output file when LOGNAMES is run again except
this time with the REPLACE option.
THIS CONTROLLER IS CC AND THE MASTER CONTROLLER IS CC
ADD LOGICAL NAMES TO ADXLXAAN::ADX_SPGM:[Link] WITH REPLACEMENT
EAMFBOPT ALREADY PRESENT, LEFT AS IS
EAM: ALREADY PRESENT, REPLACED WITH NEW NAME
OLD NAME: ADXLXACN::C:\ADX_IDT4\EAMX
NEW NAME: ADXLXACN::D:\ADX_IDT4\EAMX
EAMPANEX ALREADY PRESENT, LEFT AS IS
EAMPANEL ALREADY PRESENT, LEFT AS IS
EAMFBAUD ALREADY PRESENT, LEFT AS IS
EAMFBAUO ALREADY PRESENT, LEFT AS IS

Operational Utilities
The following utility programs are documented in the Operational Utilities section:
v EAMUBATP - Batch Maintenance for Keyed files
v EAMUREFA - Preferred Customer Reference Processing
v EAMUROLP - Roll Customer Period Totals Procedure
v EAMUPM3L - Manual Close of Points Activity Period
v EAMUPM4L - Maintain Targeted Coupon Messages
v EAMUXFER - Process Customer Data from Other Stores
v EAMUFILT - Filters Transaction Summary Log Data
v EAMUPKUP - Automatic Pickup of Paperless Coupons
v EAMUDOLS - Date of Last Sale Information for Item Movement.

EAMUBATP - Batch Maintenance for Keyed files

BATCH is a background utility program that applies maintenance updates provided
in a predefined file ([Link]) to any keyed files specified in the input data.
BATCH formatted keyed file maintenance data sent to the store controller in file
EAMBATCH is started by sending a START USER PROGRAM command for
EAMUBATP.286 from the host.

The BATCH maintenance program EAMUBATP can optionally be started

automatically once a day after a designated time.

Use of BATCH for keyed file maintenance provides six primary benefits:
v Changes for many keyed file records can be transmitted in one sequential file to
reduce transmission time and host processing.
v Multiple batches of changes for multiple keyed files can be transmitted in one file
to the store controller.
v Selected fields in a keyed file can be modified, leaving other keyed record data
unchanged.
v Groups of similar records in a keyed file can be changed or reported as a group
with one input record.

282 Electronic Marketing PRPQ

v The number of records in a keyed file can be reported with a single request.
v Targeted coupons can be added, deleted, or reported to/from the Customer
Activity file regardless of their location in the record.

Functions and Limitations

All keyed file data provided to this process must be a subset of the keyed file data
as it exists in the store controller file. There is no translation of data fields. BATCH
processes all input data in the order in which it appears in the input file. All
maintenance is applied immediately, so there is not a concept of delayed
maintenance. The execution status of all BATCH jobs is recorded in a special status
file ([Link]) as well as in the Exception Log, and all errors are recorded in
the Delayed Data Maintenance Error Log and possibly in the System Error Log. The
batch status file is intended for host processing and the Delayed Data Maintenance
Error log and Exception log can be reported in the store. A unique logical name is
used to access the Delayed Maintenance Error Log so that these errors can be
logged to a different file for host retrieval.

For a given batch, you can make the following selections:

v Select whether a full record is to be treated as a replacement or as an addition.
v Select whether an add is allowed to replace or whether a replace is allowed to
add. This provides for the “Add if not present” and “Replace only if present”
functions as well as the “Add or replace” function.
v Select whether an error should be logged for a replace record that does an add
or an add record that does a replace.
v Select whether to add the record with partial data and all other fields to X'00'
when a partial replace is requested for a specific record and the record is not on
file.

All BATCH report requests cause output report data to be appended to the batch
report file ([Link]). A report header record is followed by the reported
keyed file records packed sequentially.

There is no limit on the number of records that can be altered or reported with a
single BATCH request.

Batch Interface Definition

The BATCH program is named EAMUBATP.286 and resides on ADX_IPGM. It can
be started from the background application screen or by a START USER
PROGRAM command from the host. The BATCH input file is named
[Link] and resides on ADX_IDT1. It is loaded from the host using the
name /BATCH. The records in the input file are created by the host and are
processed solely by BATCH.

The format of this data is defined below except for the format of the keyed file
record data, which is defined where the keyed file is defined. For information on the
format of the keyed input and output files provided by the Electronic Marketing
application, see “Appendix A. Electronic Marketing Database” on page 317. The
BATCH report file is named [Link] and resides on ADX_IDT4 where it
can be dumped to the host using the name /BREPT. The batch status file is named
[Link] and resides on ADX_IDT4 where it can be dumped to the host
using the name /BSTAT.

BATCH immediately renames [Link] to [Link] when it starts

processing to allow the input file to be reloaded immediately after BATCH is started.
BATCH should be configured to start at every IPL so that it can recover after a

Chapter 10. Utilities -- Installation and Operational 283

 power failure. In this case, it will reprocess [Link]. If invalid input data is
found, the invalid input file is saved in [Link]. Only the most recent input
file with invalid data is saved.

Note: Logical names must be defined for all of the files in order for them to be
correctly accessed in a LAN environment.

BATCH logs selected errors to the Delayed Maintenance Error File. The format of
this file is defined in the Supermarket Programmers Guide BATCH creates the
following error codes:
07 Record to be added already exists; update discarded.
09 Record to be added already exists; record replaced.
24 Record to be replaced not found; record added.
25 Record to be deleted not found.
35 Record to be reported not found.
90 Master did not match local sequential record, update discarded:
v Local copy of EAMFBACT does not match the master file.
v EAMFBACT contains badly randomized data.
v Concurrent targeted update by another process (EAMCSMLL).
91 Read of EM options failed, options defaulted for maximum coupons.
92 Record did not have free space to add targeted coupon(s).
93 File open error; batch discarded.
95 Invalid BATCH; input file discarded.
96 Invalid BATCH; batch discarded.
97 Invalid BATCH; record discarded.
99 Record to be modified not found, update discarded.

Batch Maintenance File (EAMBATCH)

Filename: EAMBATCH I/O Session: 1
Organization: Sequential File Copies: 2
Record Length: Variable Distribution class: Mirrored

The batch maintenance file contains the commands and associated data required
for updating or reporting a keyed file. This file contains batch header records, data
records and message records. All data records and message records are
associated with the prior batch header record. The file must begin with a batch
header record. The records contain no internal field delimiters. The records are
delimited by a CR/LF X'0D0A'.

Record Format - Batch Header Record

Field Name Type Length Description
RECORD TYPE ASCII 1 “H” for header record (X'48')
FILENAME ASCII 8 Eight character logical file name to process
STORE UPD 2 Store number intended to receive updates
A value if zero allows any store apply the updates
BATCH UPD 3 Batch number to associate errors and status

284 Electronic Marketing PRPQ

Field Name Type Length Description
FLAGS INT 1 Flag byte
bit 0 X'80' If delete not found, log as error.
bit 1 X'40' Full length records are treated as
replaces rather than adds.
bit 2 X'20' Replace can do an add.
bit 3 X'10' Add can do a replace.
bit 4 X'08' Pad and Add on partial replace when
record is not on file.
bit 5 X'04' If replace does add, log as error.
bit 6 X'02' If add does replace, log as error.
bit 7 X'01' Multiple deletes allowed per record.

Batch header records denote the beginning of a group of maintenance changes that
are to be applied to the same keyed file. The header record provides the keyed file
name and other identification data for a batch of maintenance. All header records
contain 15 bytes of fixed data as well as the two byte record delimiter.

The flags in the header record define how to handle record adds or replaces when
the record is or is not present. These flags also allow for a record add with only
partial record data supplied and for deletes of multiple file records with only a single
input data record.

Record Format - Data Record

Field Name Type Length Description
RECORD TYPE ASCII 1 “D” for data record (X'44')
OPTIONS INT 1 Option flags for Update
bit 0 X'80' X'FE' in key data = do not care
bit 1 X'40' Key data is doubled to give range
bit 3 X'20' Flags to test off provided
bit 2 X'10' Flags to test on provided
bit 4 X'08' Report record(s)
bit 5 X'04' Report and Delete record(s)
bit 6 X'02' Flags to turn off provided
bit 7 X'01' Flags to turn on provided
KEY-OFFSET UPD 1.5 Offset of “key” within record(s) (0 - 508)
KEY-LENGTH UPD 1.5 Length of “key” data within input (0 - 508)
KEY-DATA See v255 Data to be used to find record(s) to update
note.
UPD-OFFSET UPD 1.5 Offset of Update field in record(s) (0 - 508)
UPD-LENGTH UPD 1.5 Length of Update data in input (0 - 508)
UPD-DATA See v255 Data to be updated into record(s)
note.
Note: The type of data is user-defined.

Data records contain the information required to update, add, delete, or report a
single record or a group of records in a keyed file. If the key field in the input data
overlaps the entire key field of the file record, (KEY-OFFSET = 1, KEY-LENGTH >=
KEY LENGTH defined for the file) only a single keyed record is processed. If the
data key does not include the record key, any record on file that matches the key
data at the proper offset will be updated. If the key data contains a range, the key
data is split into halves (low limit followed by high limit) and all records that have

Chapter 10. Utilities -- Installation and Operational 285

 data within or equal to the limits at the key offset are processed. If no record
exactly matches the input data key (whether or not it includes the record key), none
of the keyed records will be processed as a result of this input record. A “Do not
Care” character can be used in a simple key (not flags and not range) to cause the
key to match when not all data in the key matches. The key data is in the same
format as the file data being referenced as a key.

An update will not be allowed to alter the key to a record, but the update field can
contain the key at your discretion. Any update field that contains the complete
record data (with or without the key) is considered a full record add or replace
based upon the options for the batch. Any update field that does not contain
complete record data is considered a partial record update that requires the record
to be on file. The update data must be exactly in the format that is needed in the
updated record.

Flag fields to be used to test or modify records can be provided in either the
KEY-DATA or UPD-DATA fields. Flags to turn on or off or to test for on or off can
only be in the range of one to four bytes each. If both on and off flags are provided
(up to eight bytes), they must be of equal length. If both on and off flags are
provided, the off flags must precede the on flags. On an update, the requested flags
are turned off first and then the request flags are turned on. On the test for a key
match, the flags specified to be off must all be off and the flags specified to be on
must all be on in order for the key to match. If the options specify that test flags are
provided but the input flags are all zero, all records will match. Flags in the key are
mutually exclusive with a key range or with “Don’t Care” characters in the key.

The KEY-OFFSET / KEY-LENGTH fields can be considered a single three-byte

packed field to simplify processing. In this case, the offset is the first three digits in
the field while the length is the following 3 digits. The UPD-OFFSET /
UPD-LENGTH fields can be considered a single three-byte packed field in the same
way.

The offset fields KEY-OFFSET and UPD-OFFSET are unit-indexed so that the first
byte of a record is considered offset one. All offsets and lengths must be less than
or equal to the full keyed record length to be valid. If the KEY-DATA is not the
length specified by the KEY-LENGTH or if the UPD-DATA is not the length specified
by the UPD-LENGTH, the input record will be discarded and an error will be logged.
All fields defined in this record must be present except for the data fields, that can
be defined with a length of zero. The minimum record length is eight bytes and the
maximum record length is 1023 bytes. A KEY-OFFSET and KEY-LENGTH of zero
means to report or modify all records in the keyed file. A request to delete or report
a record must have UPD-OFFSET = UPD-LENGTH = 0. A request to modify a
record or set of records must have a nonzero value for UPD-OFFSET and
UPD-LENGTH unless the Pad and Add flag is on. If a valid record key is provided
with a Pad and Add request and no update data is given, an empty (all X'00')
record is added for the given record key if the record is not already on file.

If a key field, data field, or record ends prematurely, the next record is read and
appended. This allows a X'0D0A' to be imbedded in a data record. If the appended
data does not create a valid record, it will be treated as a new record after the
original record is discarded as invalid data.

286 Electronic Marketing PRPQ

 Record Format - Targeted Coupon Data Record
Table 2. Targeted Coupon Data Record
Field Name Type Length Description
RECORD TYPE ASCII 1 T for targeted coupon record (X'54')
OPTIONS INT 1 Option flags for Update
bit 0 X'80' X'FE' in key data = don’t care
bit 1 X'40' Key data is doubled to give range
bit 3 X'20' Flags to test off provided
bit 2 X'10' Flags to test on provided
bit 4 X'08' Report record(s) containing coupon
bit 5 X'04' Delete coupon if present
bit 6 X'02' Add coupon if not present
bit 7 X'01' Replace coupon if present
KEY-OFFSET UPD 1.5 Offset of “key” within record(s) (0 - 508)
KEY-LENGTH UPD 1.5 Length of “key” data within input (0 - 508)
KEY-DATA See v255 Data to be used to find record(s) to update
note.
UPD-OFFSET UPD 1.5 Offset of Update field in record(s) (0 - 508)
UPD-LENGTH UPD 1.5 Length of Update data in input (0 - 508)
UPD-DATA See v255 Data to be updated into record(s)
note.
Note: The type of data is user-defined.

The targeted coupons in the Customer Activity File form a list, so the BATCH
program provides special processing to allow targeted coupons to be added to or
deleted from the list. This list processing also allows reporting or alteration of
records which contain selected coupons anywhere in the list. Special list processing
occurs only with data records which begin with a record type of “T”. These special
data records are valid only when the file name in the BATCH header record is
EAMFBACT and either the key offset or the update offset has a value of 34.
Records which update (add, delete, or replace) targeted coupons are valid only if
the update offset has a value of 34 and the update data has a length which is a
multiple of 2. Records which report or alter records based on the targeted coupon
contents are valid only if the key offset is 34 and the key data has a length which is
a multiple of 2. The offset of 34 allows all targeted coupons in the record to be
referenced through the offset of the first targeted coupon. The update length as a
multiple of 2 recognizes the fact that each targeted coupon requires two bytes.

Targeted coupon records are a special form of data record that allows list
processing for finding records with selected targeted coupons and for performing
partial record updates on targeted coupons. This list processing applies to the key
and/or update field whenever the key and/or update offset is 34. Other than the
unique list processing, the only other differences between targeted coupon data
records and normal data records are defined by the options flags in the data record.
When the update offset is 34, the flag that normally defines a record deletion now
defines the deletion of targeted coupons and therefore allows update data to define
the coupon(s) to be deleted. Also on targeted coupon updates, a single flag defines
whether a targeted coupon is added to a list if it is already present in the list. If both
the key and update point to targeted coupons, then an option flag allows for the
replacement of one targeted coupon with another. Without any of these option flags,
a targeted coupon update is processed as an add to the list of coupons. Key flags
are not allowed with a key offset of 34. The “don’t care” character is also invalid in

Chapter 10. Utilities -- Installation and Operational 287

 any targeted coupon record where a key offset of 34 denotes list processing on the
key field. When the key offset is other than 34, the record key processing is
performed just the same as with standard data records. When the update offset is
other than 34, the record update processing is performed just the same as with
standard data records.

All list processing for targeted coupons requires the BATCH process to read the
Preferred Customer options and use the Customer Activity record length, the offset
of the Customer name, and the maximum number of targeted coupon to determine
the location of all targeted coupons within an activity record. List processing for the
key field in a targeted coupon record involves finding and potentially altering or
deleting all targeted coupons which match the single key coupon, any of multiple
key coupons, or the range of key coupons. List processing for the update field in a
targeted coupon record involves deleting the updated coupon wherever it is found,
replacing the found coupons with the new coupons, or adding the new coupon to an
unused position, perhaps only if the coupon is not already present. An empty
position in the coupon list is represented by X'0000' so this value is used to look for
an empty slot for an add and to replace a coupon value on a delete. An add is
always placed in the first empty slot in the record and an error is logged whenever
an add to an activity record is not processed due to a lack of free space in the
coupon list. After any targeted coupon replace or delete, the empty coupon slots in
the activity record are moved to the end of the targeted coupon area so that the
most recent adds should always be at the end of the coupon list. You can assure
that all targeted coupons are at the front of the lists by processing a request to
replace all targeted coupons of 0 with a value of 0.

The key or update data for a targeted update can contain many targeted coupon
numbers up to the maximum number of targeted coupons allowed per customer. If
the list of coupons to be replaced is longer than an associated list of replacement
coupons, then the last replacement coupon is used multiple times. This allows a list
of coupons to be replaced by a single coupon. An error is given if the list of
replacement coupons is longer than the list of coupons to be replaced.

Examples of Targeted Coupon Record Usage within EAMBATCH:

1) Add targeted coupon 321 to customer 91234567890:
2) Add targeted coupon 321 to customer 91234567890 if not already present
3) Add targeted coupons 321 and 333 to customer 91234567890 if not present

Type Opt Off/Len Data (Key) Off/Len Data (Update)

1) X'54 00 001 009 000000091234567890 034 002 0321'
2) X'54 02 001 009 000000091234567890 034 002 0321'
3) X'54 02 001 009 000000091234567890 034 004 03210333'

4) Delete targeted coupon 321 from customer 91234567890:

5) Delete targeted coupons 321 and 333 from customer 91234567890:
6) Delete targeted coupon 321 from all customers:

Type Opt Off/Len Data (Key) Off/Len Data (Update)

4) X'54 04 001 009 000000091234567890 034 002 0321'
5) X'54 04 001 009 000000091234567890 034 004 03210333'
6) X'54 04 034 002 0321 000 000'

7) Delete targeted coupons from 300 to 400 from all customers:

8) Delete targeted coupons 333 from all customer who have 321:
9) Replace all occurrences of targeted coupon 321 with 333:
10) Replace all targeted coupons between 320 and 330 with coupon 321:

Type Opt Off/Len Data (Key) Off/Len Data (Update)

7) X'54 44 034 004 03000400 000 000'

288 Electronic Marketing PRPQ

 8) X'54 04 034 002 0321 034 002 0333'
9) X'54 01 034 002 0321 034 002 0333'
10) X'54 41 034 004 03200330 034 002 0321'

11) Compress all targeted coupons to the front of the record:

12) Report all customers with targeted coupon 321:
13) Report all customers with targeted coupons 321 or 333:
14) Report all customers with any targeted coupons between 300 and 400:

Type Opt Off/Len Data (Key) Off/Len Data (Update)

11) X'54 01 034 002 0000 034 002 0000'
12) X'54 08 034 002 0321 000 000'
13) X'54 08 034 004 03210333 000 000'
14) X'54 48 034 004 03000400 000 000'

15) Add targeted coupon 321 to all customers who have targeted coupons
between 320 and 330 and don’t already have 321:
16) Set status level to 3 for all customers who have targeted coupon 333 :
17) Add targeted coupon 321 to all customers with more than 9999 points:
18) Delete targeted coupon 321 from all customers who are not eligible
for preferred coupons.

Type Opt Off/Len Data (Key) Off/Len Data (Update)

15) X'54 42 034 004 03200330 034 002 0321'
16) X'54 00 034 002 0333 029 001 03'
17) X'54 40 010 008 00010000 99999999 034 002 0321'
18) X'54 14 031 001 04 034 002 0321'

Record Format - Message Record

Field Name Type Length Description
RECORD TYPE ASC 1 “M” for message record (X'4D')
TEXT ASC v? ASCII message text (up to 30,000 characters)

Batch message records allow text data to accompany a set of data records. It is
assumed that batch message records will contain a description of function or
contents of the associated data records. Batch processing just ignores message
records.

Batch Report (EAMBREPT)

Filename: EAMBREPT I/O Session: 7
Organization: Sequential File Copies: 2
Record Length: Variable Distribution class: Mirrored

The batch report file contains report header records and records from the keyed file
being reported. Each input data record requesting a report generates a header
record. The records contain no internal field delimiters. The records are delimited by
a CR/LF X'0D0A'.

Record Format - Report Header Record

Field Name Type Length Description
RECORD TYPE ASCII 1 “R” for Report header record (X'52')
FILENAME ASCII 8 Eight character logical file name reported
STORE UPD 2 Store number generating report
BATCH UPD 3 Batch number of input header record

Chapter 10. Utilities -- Installation and Operational 289

Field Name Type Length Description
DATETIME UPD 5 Date and Time (YYMMDDhhmm) report processed
REC-SEARCH UPD 3 Count of records searched for key match
REC-FOUND UPD 3 Count of records found with key match
REC-LENGTH UPD 2 Length of reported records (without delimiters)
KEY-OFFSET UPD 1.5 Offset of “key” within record(s) (0 - 508)
KEY-LENGTH UPD 1.5 Length of “key” data within input (0 - 508)
KEY-DATA See v255 Data used to find reported records
note.
Note: The type of data is user-defined.

Report header records denote the beginning of a group of keyed file records
reported due to a single report request. The header record provides the keyed file
name, record length, and report selection criteria. All header records contain at least
30 bytes of data as well as the two byte record delimiter.

Record Format - Report Data Record

Report data records contain the keyed file record data exactly as it exists on the file
in the PC. The records are delimited by a CR/LF X'0D0A'. The records are reported
in the order that they are found on file.

Batch Status (EAMBSTAT)

Filename: EAMBSTAT I/O Session: 2
Organization: Sequential File Copies: 2
Record Length: 26 Distribution class: Mirrored

The batch status file contains a single status record for each input header record
that is processed. The records contain no internal field delimiters. The records are
delimited by a CR/LF X'0D0A'.

Record Format
Field Name Type Len Description
RECORD TYPE ASCII 1 “S” for status record (X'53')
DATETIME UPD 5 Date and Time (YYMMDDhhmm) processed
ERROR-CODE ASCII 2 Worst error code encountered
FILENAME ASCII 8 Eight-character logical file name processed
STORE UPD 2 Store number processing data
BATCH UPD 3 Batch number of input header record
ERROR-COUNT UPD 2 Count of records with errors
RECORD-COUNT UPD 3 Count of records processed (errors or success) Larger of input
records or updated records

Batch status records contain 26 bytes of data followed by a two-byte Cr/Lf delimiter.
If the error count is nonzero, this means that errors were encountered during
processing. The possible error codes sorted by severity are as follows:
95 Invalid BATCH; input file discarded.
93 File open error; batch discarded.

290 Electronic Marketing PRPQ

96 Invalid BATCH; batch discarded.
97 Invalid BATCH; record discarded.
90 Master did not match local sequential record, update discarded.
99 Record to be modified not found, update discarded.
91 Read of EM options failed, options defaulted for maximum coupons.
92 Record did not have free space to add targeted coupon(s).
07 Record to be added already exists; update discarded.
09 Record to be added already exists; record replaced.
24 Record to be replaced not found; record added.
25 Record to be deleted not found.
35 Record to be reported not found.

Exception Log Updates

For each status record, a type 43 record is written to the exception log to show the
execution of a batch. The last byte of the four-byte batch number contains the
packed error code. These data errors as the last byte (Seq ID) of the 4-byte batch
number.

Delayed Data Maintenance Error Log Updates

For each error encountered, a record is written to the Delayed Data Maintenance
Error Log to show the error. The error codes as shown in the batch are given and
the operator is shown as “888888888” in order to distinguish the BATCH created
records. All records with a “97” error (invalid data record discarded) will contain an
additional error indicator as the last byte (Seq ID) of the four-byte batch number.
These data error indications define the nature of the data error as follows:
0 INVALID RECORD TYPE
1 KEY OFFSET OR LENGTH FIELD IS NOT NUMERIC
2 UPDATE OFFSET OR LENGTH FIELD IS NOT NUMERIC
3 INPUT DATA DOES NOT MATCH INPUT LENGTHS
4 UPDATE IS TARGETED TOTALLY WITHIN RECORD KEY
5 “DON’T CARE” IS NOT ALLOWED WITH KEY RANGE
6 KEY FLAGS ARE NOT ALLOWED WITH KEY RANGE OR “DON’T CARE”
7 UPDATE FLAGS ARE NOT ALLOWED ON REPORT OR DELETE
8 DOUBLE KEY DATA CANNOT BE SPLIT IN HALF
9 INPUT KEY EXTENDS PAST THE END OF THE RECORD
10 DOUBLE UPDATE DATA CANNOT BE SPLIT IN HALF
11 UPDATE DATA EXTENDS PAST THE END OF THE RECORD
12 NO UPDATE DATA ALLOWED ON REPORT OR DELETE
13 UPDATE DATA REQUIRED IF NOT REPORT OR DELETE OR PAD AND
ADD
14 KEY LENGTH SPECIFIED WITH NO KEY OFFSET
15 KEY OFFSET SPECIFIED WITH NO KEY LENGTH
16 DELETE OF MULTIPLE RECORDS NOT ALLOWED BY HEADER FLAGS
17 RECORD TYPE “T” REQUIRES TARGET FILE “EAMFBACT”
18 RECORD TYPE “T” REQUIRES A KEY OR UPDATE OFFSET OF 34

Chapter 10. Utilities -- Installation and Operational 291

 19 UPDATE LENGTH MUST BE A MULTIPLE OF 2 FOR TARGETED
COUPONS
20 KEY LENGTH MUST BE A MULTIPLE OF 2 FOR TARGETED COUPONS
21 “DON’T CARE” IS NOT ALLOWED WITH A TARGETED COUPON KEY
22 KEY FLAGS ARE NOT ALLOWED WITH A TARGETED COUPON KEY
23 CANNOT REPORT WHILE ALTERING TARGETED COUPONS
24 REPLACE REQUIRES MATCHING TARGETED KEYS AND UPDATES
25 TARGETED ADD, DELETE, OR REPLACE ARE MUTUALLY EXCLUSIVE

System Error Log Updates

Severe or unexpected errors are logged in the System Error Log. For more
information, see “System Error Log Usage” on page 355. The ten bytes of user data
in these log entries are defined as follows:
Bytes 1,2
Last two bytes of record key for most recently processed record (as defined
by file format)
Bytes 3,4
Session number of failing file access (ASCII)
01 Input Data File (EAMBATCH)
02 Output Status File (EAMBSTAT)
03 Keyed file - sector mode for search
04 Keyed file - keyed mode for update
05 DDM Error Log (EAMDMERB)
06 Exception Log (EAMEXCPT)
07 Report File (EAMBREPT)
08 Options file (EAMFBOPT)
09 Saved Input File Containing Errors (EAMBERRD)
10 Work File for Report Output from Search (EAMBAWRK)
11 Printer for unrecoverable errors
Bytes 5,6
Error code from operating system (ASCII)
Bytes 7-10
Error value from operating system (packed)

Sample EAMBATCH Data

Header and data record to report all records in keyed file EAMFBACT.
Key Upd
Type File Name Store Batch Flag Type Opt O/L O/L
x“48 45414D4642414354 0000 010203 00 0D0A 44 08 000000 000000 0D0A”
ASCII H E A M F B A C T CRLF D CRLF

Header and data record to update the name in an activity record in

file EAMFBACT or to add the record if it is not present.

Type File Name Store Batch Flag

x“48 45414D4642414354 0000 020304 08 0D0A”
ASCII H E A M F B A C T CRLF

Key

292 Electronic Marketing PRPQ

 Type Opt O/L KEY DATA
x“44 00 001009 000000090445000472
ASCII D
UPD
O/L UPDATE DATA
068017 57616C646F20532E2057696C6465722020 0D0A”
W a l d o S . W i l d e r CRLF

Header and data record to locate all alias accounts in the activity
file EAMFBACT and present them with message 11.

Type File Name Store Batch Flag

x“48 45414D4642414354 0000 030405 00 0D0A”
ASCII H E A M F B A C T CRLF

Key Key UPD Update

Type Opt O/L Data O/L Data
x“44 10 031001 20 030001 11 0D0A”
ASCII D CRLF

Header and data record to turn on the trading stamp flag in all item
records in which it is not already on.

Type File Name Store Batch Flag

x“48 45414D4954454D52 0000 050607 00 0D0A”
ASCII H E A M I T E M R CRLF

Key Key UPD Update

Type Opt O/L Data O/L Data
x“44 21 008001 04 008001 04 0D0A”
ASCII D CRLF

EAMUREFA - Preferred Customer Reference Processing

This background utility processes enrollment and activity file records for those
customers that have both a referenced account number entered AND the
alias/family field set to “N” in their enrollment record.

For these customers, this utility program will transfer the activity points from the
primary account to the referenced account by redeeming the points from the
primary account and adding them to the points earned by the referenced account.

If the referenced account is a home store record, but does not already exist, then
an activity record will be created. If the referenced account is a non-home store
record, then a transfer record will be created and added to the EAM:ssss file.

This utility program can also be used to close out an old account number and
create the new (or update the existing) enrollment and activity records. To close out
an old account, for example, if customer has lost their card, just put “*old” anywhere
in the second address line, enter the new account number in the reference account
field and ensure that the alias/ family field is set to “N”.

When EAMUREFA is run, all the history (as well as the points) from the first
account is moved over to the referenced account. Once the account has been
closed, the ″*old″ can still be seen as well as the special character ″v″.

In order to run EAMUREFA, the enrollment file must exist and the option to use
EAMUREFA, ″AUTOMATIC EXECUTION TIME FOR REFERENCE PROCESSING″
must be turned on. For more information on this option, see “Automatic Execution
Time for Batch Updates” on page 95. Anytime points are redeemed from an
account, an audit record is created and written to EAMFBAUD.

Chapter 10. Utilities -- Installation and Operational 293

 This option provides an alternative and/or a backup to the “Start User Program”
interface from the host to assure that reference processing occurs at least once a
day. The option on when to start the program is provided so that the reference
processing can be scheduled when the store is not busy.

EAMUREFA will only transfer newly earned points or newly closed accounts so,
multiple executions cause no problem.

EAMUROLP - Roll Customer Period Totals Procedure

This background utility program rolls the periodic points totals in the customer
activity file into a new period. The points earned, points redeemed, and transaction
count for the activity period are reset for a new period along with the period start
date.

If a non-zero carry-over limit is specified, then up to that amount of non-redeemed

points can be carried into the new period. Automatic discounts can be set based on
points accumulated in the prior period.

This program is designed to be executed automatically during a close by checkout

support or manually by the user procedure, EAMUPM3L.

Activity fields impacted:

v [Link] - points earned in period
v [Link] - points redeemed in period
v [Link] - transactions in period
v [Link]$ - period start date
v [Link] - discount group for next period.

This program updates only the current and previous period Customer activity files
and the manager’s message file. After completion a status message is written to
manager’s message file.

To install this program EAMUROLP.286 must be copied to ADX_IPGM and the

system file utilities need to be used to assure that the file distribution type on each
module is compound per update.

This is a background program which you may wish to configure on the background
application screen if you want the ability to manually start these programs in the
store.

EAMUROLP will cause no harm if run multiple times in the same day, but it will
close the points activity period prematurely if run on the wrong day.

If you intend to have the close of the Preferred Customer points activity period
automatically started during the store close, then use system configuration to define
a new background program as follows:
Define Program Name ADX_IPGM:EAMUROLP.286
with Initial Message RESTART CLOSE OF ACTIVITY PERIOD
with Parameter List RESTART
and IPL Start = YES (for PLD recovery reasons)

EAMUPM3L - Manual Close of Points Activity Period

This user procedure is used to call EAMUROLP to manually close the points activity
period. When executed it asks the operator if they want to close the points period. If
the operator answers yes it prompts for the operators password. If the operator

294 Electronic Marketing PRPQ

 correctly enters the password then EAMUROLP is called. If EAMUROLP is
successfully started a success message is displayed. If there has been an error, an
error message is displayed. To install the procedure simply copy EAMUPM3L.286 to
ADX_IPGM. Even if the option is selected to automatically close the Preferred
Customer points activity on period intervals, it is still a good idea to install this
program (with very restricted operator authorization for its use) so that it will be
available as a manual backup should it be needed.

EAMUPM4L - Maintain Targeted Coupon Messages

This user procedure maintains the targeted coupon messages and allows text
messages to be provided for targeted coupons so the terms of a promotion can be
printed on the receipt tape of those customers to whom the coupon is targeted.

The text messages for targeted coupons are kept in a separate keyed file. The
coupon itself need not be on the item file when the promotional message is created,
but it must be on the item file before the promotional message will be shown to a
customer. If the coupon is on the item file, then the coupon attributes are shown
along with the coupon message.

This utility allows you to add, change, delete, or report all coupon messages. The
coupon messages are accessed through the same 4-digit number used to link the
coupon to an item or to a customer. This number is also printed on the customer
receipt.

The delete function just blanks out all message text. All blank text is equivalent to
no message.

EAMUXFER - Process Customer Data from Other Stores

This background utility program processes customer data that has been transferred
into the store from other stores. This program is usually started from the host after
the transfer files have been sent. Its purpose is to move data from activity transfer
files to the pending transfer file. The activity transfer files are named EAM:ssss
where the range of ssss values may be passed to this program as input
parameters. The program also always uses ssss in the range of 0 to 9. See
“Preferred Customer Transfer File (EAMFBXFR)” on page 325 and “Preferred
Customer Activity Transfer File (EAMXssss)” on page 326 for the file layout of these
files.

Data is not moved from the found activity files to the pending transfer file unless the
Home store is supported in this store and the data did not originate in this store or it
was created because of a file error. Data is only moved to the pending transfer file
for accounts that are present in the customer activity file. The customer activity file
is flagged to show the presence of pending transfer data.

This program is usually started from the host after the transfer files have been sent.
This program will run harmlessly if started accidentally. It will usually find no files to
transfer and if it did it will just process them normally.

EAMUFILT - Filters Transaction Summary Log Data

This utility program creates additional copies of the Panel file by filtering the
transaction summary log data at a store close. This program is started by a
Electronic Marketing automatically when a reporting period is closed. The presence
of any [Link] files (where x is a number from one to nine) defines the
need for background filtering and creation of the associated [Link] output

Chapter 10. Utilities -- Installation and Operational 295

 file. If these files are present then EAMUFILT will be automatically executed at the
close. NOTE: Electronic Marketing can perform this same filtering in real time as
the TLOG is processed. The presence of [Link] defines the need for this
real time filtering of the data. The data will be filtered as it is put into
[Link] by checkout support processing. EAMUFILT supports up to nine
input filter files and nine associated output panel files, while real time filtering only
supports one. (See “Panel Filter File (EAMFBFLT)” on page 336 for the file layout
and additional documentation.)

EAMUPKUP - Automatic Pickup of Paperless Coupons

This background utility program provides the automatic pickup of paperless coupons
in the previous period. These coupons might be automatic (linked) store or
manufacturer coupons or doubled coupons. The pickup will occur automatically at
the close of an accounting period so all totals are impacted in the previous period.
Coupons will be picked up from the on-hand fields if the on-hand coupon data just
matches the automatic coupon data as it should if no tender counts were done in
current period. This processing looks like a tender transfer. If tender counts were
done in current period, then the coupons are picked up through a process that
looks like a normal pickup processing.
Pickup Processing: Transfer Processing:
Add AUTO to Op/Tm pickup amt Add AUTO to Op/Tm pickup amt
Sub AUTO from Op/Tm net amt Zero Auto in Op/Tm Onhand amt
Add AUTO to Office pickup amt Add AUTO to Office pickup amt
Add AUTO to Office net amt Add AUTO to Office net amt
Add AUTO to Office AUTO amt Add AUTO to Office AUTO amt

This program updates only the Previous Period Accounting File. It is started by
Electronic Marketing automatically when a reporting period is closed. This program
will run harmlessly if started accidentally as it will find all paperless coupons in the
previous period already picked up.

EAMUDOLS - Date of Last Sale Update Function

In order to report on items based on their date of last sale, this information must be
maintained in the Item Record File. A separate background program,
EAMUDOLS.286, is provided to update the Date of Last Sale in the item record file.
The Selective Item Record Report provides a way to report on items by date of last
sale (see “Selective Item Record Report” on page 250).

Item Record Update

This program searches the item movement file and updates a Date of Last Sale in
the item records for those items sold during the period. The date is taken from the
item movement file and is either the date that the item movement period started
(current period) or the date when it ended (previous period). This date is placed into
user exit field two in the appropriate item records as an integer with the value
(month * 100) + day of month. This user exit field is not updated if the item is a
coupon because the coupon processing function uses this same exit field for unique
coupon data. This program is intended to be run after a close of the item movement
file and would normally process the previous period item movement file. The
installation instructions show how to activate this program automatically through
user exits when the proper store closing procedure is run. Updating the date of last
sale at the end of a reporting period adds to the amount of store close processing,
but this technique prevents any performance degradation during normal sales
periods.

296 Electronic Marketing PRPQ

 Item Movement Staging
Options provided to this program through input data define the name of the item
movement file to be searched and the type of processing desired. As this program
is already searching through the item movement file, it provides an option to stage
this item movement data into a sequential file in order to compress the data for host
retrieval. For more information, see “Staged Item Movement File (EAMIMOV1)” on
page 351. Options provide the name for this output file and some formatting
information, and the program then copies the item movement records from the
keyed input file to a sequential output file. The records in this output file exactly
match those in the input file, so the staging process performed looks exactly like
that which might be done by the keyed file utilities with four major exceptions:
v The restart field is dropped from the output data to cut the output record size to
only the useful 18 bytes.
v The output integers for count, amount, and weight are optionally converted to
binary (bytes 1234 through 4321).
v If an output file already exists when this program is activated, the new output
data will be appended to the old output data.
v The store record is always placed at the top of any new data to distinguish which
day the data came from.
This program compresses the item movement data and also provides a good
solution for handling multiple periods of item movement data in case the host is
unable to retrieve this data for several periods. There is also an option to delete the
input item movement file once this program has completed its processing of the file.
This option can be used to save disk space and would normally only be used after
the program has successfully staged the data to sequential format. If the old period
item movement file is deleted through this option, the Selective Item Record report
will be unable to search for items based on the old period item movement. This
item movement staging function can be implemented independently of the Date of
Last Sale Updating or any of the other functions in the Electronic Marketing
application in the same way that the Selective Item Record Report can be
implemented independently of the Coupon Processing Functions.

Input Options (Parameters)

This background program requires two input parameters and allows for three. The
first parameter is an input item movement file name of the form EAMIMxxx that is
defaulted to “EAMIMOVO” if the parameter is not validly provided. The second input
parameter specifies three conditions:
v Whether exit field two in the item records is to be updated with the Date of Last
Sale for all item codes in the input movement file
v Whether the input item movement file is to be deleted
v Whether staged movement data will contain integer or binary data.
This parameter ranges from “zero” to “seven” where odd numbers select item
record date updates, numbers zero, one, four, and five select to delete the input
movement file, and numbers less than four select binary staged output data.
Table 3. Date of Last Sale Input Options and Parameters
Parameter 2 Date of Last Sale Update Delete Input Staged Format
0 NO YES BINARY
1 YES YES BINARY
2 NO NO BINARY
3 YES NO BINARY

Chapter 10. Utilities -- Installation and Operational 297

Table 3. Date of Last Sale Input Options and Parameters (continued)
Parameter 2 Date of Last Sale Update Delete Input Staged Format
4 NO YES INTEGER
5 YES YES INTEGER
6 NO NO INTEGER
7 YES NO INTEGER

The third parameter is an output item movement file name of the form EAMIMxxx.
This parameter is optional. If this parameter is validly provided, it gives the file
name to contain the sequential output records staged from the input file. If
parameter two is “zero” and parameter three is not validly provided, then parameter
three is defaulted to “EAMIMOV1”. If parameter two is a value other than “zero” and
parameter three is not validly provided, no staging of item movement data is
performed. The input parameters to this program must be separated by a comma or
a blank (for example, “EAMIMOVO,1,EAMIMOV1”). If no parameters are provided,
they are defaulted to “EAMIMOVO,3”.

If output file staging is selected, then logical names should be defined for the output
file and for the work file so that they are in the same directory. For example,
Define: To Be:
EAMIMWRK ADXLXACN::C:\ADX_IDT4\[Link]
EAMIMOV1 ADXLXACN::C:\ADX_IDT4\[Link]

The program should work with both logical names or with neither but does not work
with only one. Both are suggested for LAN.

If updating of the date of last sale is selected, for each record in the item movement
file, the associated item record is updated with the date of the store close. This date
is placed into user exit field two in the format required by the Selective Item Record
Report (Month * 100 + Day). The exit field is not updated if the item is a coupon
record because exit field two has a different meaning for store coupons.

298 Electronic Marketing PRPQ

Chapter 11. Electronic Marketing Unique User Exits
Electronic Marketing Unique User Exits
Because the Electronic Marketing code in the Terminal Sales program
EAMTS11L.286 and in the Checkout Support program EAMCSMLL.286 is
implemented through supermarket user exits, these same user exits can be used to
alter the processing of the Electronic Marketing code. To install the Electronic
Marketing code in the terminal and controller checkout programs, modules of the
name EAMTSExx.J86 or EAMCSExx.J86 are included in the supermarket exits
EAMTSUxx.J86 and EAMCSUxx.J86. By adding code before one of these include
statements one can alter the input conditions seen by the Electronic Marketing
code. By adding code after one of these include statements, one can redo or
reverse parts or all of the just completed Electronic Marketing processing. Thus
each segment of terminal or controller checkout code (represented by a module of
named EAMTSExx.J86 or EAMCSExx.J86) has a user exit before and after the
segment because the processing is implemented through the supermarket user
exits.

All new I/O added by Electronic Marketing to the terminal input and output devices
(keyboard, scanner, printer, display) uses the same user exits to allow change of
this I/O as does the supermarket application. Thus all new keyed or scanned input
for Electronic Marketing goes through exit 14 (TSUPEC14). All new print lines
created by Electronic Marketing go through the appropriate printer exits
(TSUPEC20 for receipt, TSUPEC21 for journal, and TSUPEC22 for document
insert). All new displays created by Electronic Marketing goes through exit 23
(TSUPEC23). Use of these standard supermarket exits by the Electronic Marketing
functions allows user alteration of these inputs and outputs at the register just as
though they were created by the supermarket application.

Despite the many opportunities to alter Electronic Marketing functions through the
standard supermarket user exits, there are still several points the processing flow of
Electronic Marketing functions where unique new file I/O is performed or large new
processing paths are executed. In order to allow these new functions to be user
altered without the maintenance problems associated with source code changes,
several new exits unique to Electronic Marketing have been added to terminal and
controller checkout.

New include files named EAMEMTxx.J86 for terminal checkout and

EAMEMCxx.J86 for controller checkout are included in the compiles of
[Link] and [Link] respectively via the modules
EAMTSESU.J86 and EAMCSESU.J86. Each of these exit points is called from a
critical point in the Electronic Marketing code. A single Electronic Marketing option
can be used to deactivate all of these exit points. To add code to the Electronic
Marketing processing path through these exits, one need only add the needed code
to one or more of the exit modules EAMEMxxx.J86, then re-compile and relink the
terminal or controller exit modules (EAMTSUPC and/or EAMCSUPC) just as is
done for all other Supermarket user exit code.

To truly understand the conditions at the entry to each of the following exits and the
conditions that will cause the exit to be invoked, one should study the Electronic
Marketing source code which surrounds the call to each exit. While variables are
suggested for reference or update in each exit, there are many more variables
defined in EAMTSEVA.J86 and EAMCSEVA.J86 that may be referenced or altered

© Copyright IBM Corp. 1991 2000 299

 as needed. Many of the supermarket variables also have meaning for and impact
on the Electronic Marketing processing as altered through these exits.

Electronic Marketing Terminal User Exits

The next section describes the Terminal User Exits provided by the Electronic
Marketing application.

Exit TSEMEC01 - Called After The Read Of A Customer Activity Record

Input Parameters: None.
Return Parameter: None.

Global Variables for Reference Only:

[Link]
[Link]
[Link]
[Link]
[Link]$
[Link]

Suggested Global Variables for Update:

[Link]
[Link]
[Link]
[Link]$
[Link]$
[Link]$
[Link]
[Link]
[Link]
[Link]
[Link]$
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]$
[Link]$
[Link]$
[Link]
[Link]
[Link]
[Link]$
[Link]
[Link]$

Comments: THE VARIABLES [Link],

[Link],AND [Link] DEFINE
WHETHER THE READ WAS SUCCESSFUL, AND IF NOT,
WHETHER THIS IS A HOME STORE CUSTOMER. IF THE
READ WAS SUCCESSFUL, THEN THIS IS A HOME STORE
CUSTOMER. THE CODE IN USERCARD.J86 IS EXECUTED
JUST PRIOR TO THIS EXIT.

Function Definition:
FUNCTION TSEMEC01 PUBLIC ! AFTER THE READ OF A CUSTOMER ACTIVITY RECORD
! insert user exit code here
END FUNCTION

300 Electronic Marketing PRPQ

Exit TSEMEC02 - Called After The Read Of A Customer Transfer
Record
Input Parameters: None.
Return Parameter: None.

Global Variables for Reference Only:

[Link]
[Link]
[Link]
[Link]
[Link]$

Suggested Global Variables for Update:

[Link]
[Link]$
[Link]$
[Link]$
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]

Comments: THE CODE IN USERXFRD.J86 IS EXECUTED JUST

PRIOR TO THIS EXIT

Function Definition:
FUNCTION TSEMEC02 PUBLIC ! AFTER THE READ OF A CUSTOMER TRANSFER RECORD
! insert user exit code here
END FUNCTION

Exit TSEMEC03 - Called After The Read Of A Coupon Message Record

Input Parameters: None.
Return Parameter: None.

Global Variables for Reference Only:

[Link]
C$ (RECORD KEY)
B$ (FULL RECORD)
TS.TEMP5I2 (COUNT OF COUPONS)
I% (CURRENT COUPONS)
[Link]$(I%) (FIXED PRINT DATA)
[Link].TMSG1
[Link]

Suggested Global Variables for Update:

A$ (RECORD DATA)

Comments: THE PRINTING OF COUPON MESSAGES OCCURS

ONLY AT EOT FOR AVAILABLE TARGETED COUPONS

Function Definition:
FUNCTION TSEMEC03 PUBLIC ! AFTER THE READ OF A COUPON MESSAGE RECORD
! insert user exit code here
END FUNCTION

Chapter 11. Electronic Marketing Unique User Exits 301

Exit TSEMEC04 - Called After The Input Of A Customer Number in
Response to a Prompt (Input from MSR)
Input Parameters: None.
Return Parameter: None.

Global Variables for Reference Only:

[Link]
[Link]
[Link]$

Suggested Global Variables for Update:

[Link] (0 OR ERROR)
[Link] (0, 73, OR 80)
[Link]$(2) (ACCOUNT NUMBER)
[Link]$(4) (EXPIRATION DATE)

Comments: CUSTOMER NUMBER INPUT MADE WITHOUT A

PROMPT IS ACCESSIBLE IN SUPERMARKET EXIT 14.
VALID ENTRY PROCESSED IF MOTORKEY IS 80.

Function Definition:
FUNCTION TSEMEC04 PUBLIC ! AFTER RESPONSE TO CUSTOMER NUMBER PROMPT
! insert user exit code here
END FUNCTION

Exit TSEMEC05 - Called After Validation Of A Customer Number

Input Parameters: None.
Return Parameter: None.

Global Variables for Reference Only:

[Link]
[Link]
[Link]
[Link]$
[Link]$
[Link]
[Link]

Suggested Global Variables for Update:

[Link]
[Link]
[Link](9) (-1 = ERROR)
[Link]
[Link]$

Comments: IF THE CUSTOMER NUMBER IS REJECTED,

THEN THE GUIDANCE WILL BE IN [Link]
IF MOTORKEY IS 0, OTHERWISE THE GUIDANCE HAS
BEEN SAVED THROUGH TSCSEC03 FOR A POSSIBLE OVERRIDE

Function Definition:
FUNCTION TSEMEC05 PUBLIC ! AFTER VALIDATION OF A CUSTOMER NUMBER
! insert user exit code here
END FUNCTION

302 Electronic Marketing PRPQ

Exit TSEMEC06 - Called After Computing A Coupon Value Based On
The Value Of Matching Items
Input Parameters: None.
Return Parameter: None.

Global Variables for Reference Only:

[Link](2)
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link](1)
[Link].INDICAT1

Suggested Global Variables for Update:

[Link] (VALUE OF DISCOUNT)
TS.TEMP2I4 (AMOUNT BEING DISCOUNTED
[Link]
[Link]

Comments: THIS EXIT APPLIES ONLY TO COUPONS USING

PRICING METHOD 4.

Function Definition:
FUNCTION TSEMEC06 PUBLIC ! AFTER COMPUTING A P.M. 4 COUPON VALUE
! insert user exit code here
END FUNCTION

Exit TSEMEC07 - Called Before Assuring The Minimum Purchase For A

Coupon Is Met
Input Parameters: None.
Return Parameter: None.

Global Variables for Reference Only:

[Link](2)
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]

Suggested Global Variables for Update:

[Link] (REQUIRED PURCHASE)
TS.TEMP1I4 (AMOUNT TOWARDS MINIMUM)
[Link]$

Comments: THIS EXIT APPLIES ONLY TO COUPONS WITH A

MINIMUM PURCHASE REQUIREMENT IN AN ORDER
THAT INCLUDES SALES.

Function Definition:
FUNCTION TSEMEC07 PUBLIC ! BEFORE CHECKING A COUPON MINIMUM PURCHASE
! insert user exit code here
END FUNCTION

Chapter 11. Electronic Marketing Unique User Exits 303

Exit TSEMEC08 - Called After Computing The Points Value Of An Order
Input Parameters: None.
Return Parameter: None.

Global Variables for Reference Only:

[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link](0,0)
[Link](7)
[Link](8)
[Link](0,0,0)
[Link]
[Link]

Suggested Global Variables for Update:

[Link]

Comments: THIS EXIT MAY BE ENTERED MULTIPLE TIMES IN

AN ORDER TO ASSURE ADEQUATE POINTS FOR
REDEMPTION.

Function Definition:
FUNCTION TSEMEC08 PUBLIC ! AFTER COMPUTING THE POINTS VALUE OF AN ORDER
! insert user exit code here
END FUNCTION

Exit TSEMEC09 - Called After Saving A Coupon For Total Time

Input Parameters: None.
Return Parameter: None.

Global Variables for Reference Only:

[Link]
[Link](2)
[Link](1)
[Link]
[Link]
[Link]
[Link](1)
[Link]
I% (SAVE OFFSET AT SALE)

Suggested Global Variables for Update: NONE

Comments: USE THIS EXIT TO SAVE ADDITIONAL DATA IN

USER DEFINED VARIABLES.

Function Definition:
FUNCTION TSEMEC09 PUBLIC ! AFTER SAVING A COUPON FOR TOTAL TIME
! insert user exit code here
END FUNCTION

304 Electronic Marketing PRPQ

Exit TSEMEC10 - Called At Checking For Crossing A Points Boundary
Input Parameters: None.
Return Parameter: None.

Global Variables for Reference Only:

[Link]
[Link]
[Link]
[Link]
X% (NEW POINTS TOTAL)
[Link]
[Link]
[Link]

Suggested Global Variables for Update:

I% (BOUNDARY CROSSED INDICATION)
[Link]
[Link]
[Link]

Comments: THIS EXIT GETS CONTROL ONLY AFTER THE

FINAL TENDER IS MADE FOR AN ORDER.

Function Definition:
FUNCTION TSEMEC10 PUBLIC ! AT CHECKING FOR CROSSING A POINTS BOUNDARY
! insert user exit code here
END FUNCTION

Exit TSEMEC11 - Called Before Giving Automatic Coupons At The

Entry Of A Customer Number
Input Parameters: None.
Return Parameter: None.

Global Variables for Reference Only:

[Link]
[Link]
[Link]
[Link]$
[Link]$
[Link]$
[Link]
[Link]
[Link]
[Link]
[Link]
[Link](1)
[Link]

Suggested Global Variables for Update:

[Link]
[Link](2)
[Link](1)

Comments: THIS EXIT GETS CONTROL ONLY WHEN COUPONS

ARE AVAILABLE AFTER ENTRY OF A VALID CUSTOMER
NUMBER.

Function Definition:
FUNCTION TSEMEC11 PUBLIC ! BEFORE AUTOMATIC COUPONS AT CUSTOMER ENTRY
! insert user exit code here
END FUNCTION

Chapter 11. Electronic Marketing Unique User Exits 305

Exit TSEMEC12 - Called Before Giving Automatic Coupons At Total
Time
Input Parameters: None.
Return Parameter: None.

Global Variables for Reference Only:

[Link]
[Link]
[Link]
[Link]$
[Link]$
[Link]$
[Link]
[Link]
[Link]
[Link]

Suggested Global Variables for Update:

I% (COUNT TO REPLAY)
[Link](2)
[Link](1)

Comments: THIS EXIT GETS CONTROL ONLY WHEN COUPONS

ARE POTENTIALLY AVAILABLE AT TOTAL TIME.

Function Definition:
FUNCTION TSEMEC12 PUBLIC ! BEFORE AUTOMATIC COUPONS AT TOTAL TIME
! insert user exit code here
END FUNCTION

306 Electronic Marketing PRPQ

Electronic Marketing Controller User Exits
The next section describes the Controller User Exits provided by the Electronic
Marketing application.

Exit CSEMEC01 - Called After the Read of a Customer Activity Record

Input Parameters: None.
Return Parameter: None.

Global Variables for Reference Only:

[Link]
[Link]$
[Link]$
[Link]
[Link]
[Link]
[Link]$
[Link]$
[Link]$
[Link]
[Link]

Global Variables for Reference Only:

[Link]
[Link]
[Link]
[Link]$
[Link]$
[Link]$
[Link]
[Link]
[Link]
[Link]
[Link]$
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]$
[Link]$
[Link]$
[Link]
[Link]
[Link]
[Link]$
[Link]
[Link]$
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]$
[Link]
[Link](1)

Comments: THE VARIABLES [Link],

[Link], AND [Link]
DEFINE WHETHER THE READ WAS SUCCESSFUL,

Chapter 11. Electronic Marketing Unique User Exits 307

 AND IF NOT, WHETHER THIS IS A HOME STORE CUSTOMER.
IF THE READ WAS SUCCESSFUL, THEN THIS IS A HOME
STORE CUSTOMER.
THE CODE IN USERCARD.J86 IS EXECUTED JUST
PRIOR TO THIS EXIT.

Function Definition:
FUNCTION CSEMEC01 PUBLIC ! AFTER THE READ OF A CUSTOMER ACTIVITY RECORD
! insert user exit code here
END FUNCTION

Exit CSEMEC02 - Called After the Read of a Customer Transfer Record

Input Parameters: None.
Return Parameter: None.

Global Variables for Reference Only:

[Link]
[Link]$
[Link]$
[Link]
[Link]
[Link]
[Link]$
[Link]$
[Link]$
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]$
[Link]
[Link](1)

Suggested Global Variables for Reference Only:

[Link]
[Link]$
[Link]$
[Link]$
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]

Comments: THE CODE IN USERXFRD.J86 IS EXECUTED JUST

PRIOR TO THIS EXIT

Function Definition:
FUNCTION CSEMEC02 PUBLIC ! AFTER THE READ OF A CUSTOMER TRANSFER RECORD
! insert user exit code here
END FUNCTION

308 Electronic Marketing PRPQ

Exit CSEMEC03 - Called Before the Write of a Customer Activity
Record
Input Parameters: None.
Return Parameter: None.

Global Variables for Reference Only:

[Link]
[Link]$
[Link]$
[Link]
[Link]
[Link]
[Link]$
[Link]$
[Link]$
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]$
[Link]
[Link](1)
[Link]
[Link]

Suggested Global Variables for Reference Only:

[Link]
[Link]$
[Link]$
[Link]$
[Link]
[Link]
[Link]
[Link]
[Link]$
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]$
[Link]$
[Link]$
[Link]
[Link]
[Link]
[Link]$
[Link]
[Link]$

Comments: THE CODE IN USERCAUP.J86 IS EXECUTED JUST

AFTER THIS EXIT

Function Definition:
FUNCTION CSEMEC03 PUBLIC ! BEFORE THE WRITE OF A CUSTOMER ACTIVITY RECORD
! insert user exit code here
END FUNCTION

Chapter 11. Electronic Marketing Unique User Exits 309

Exit CSEMEC04 - Called Before the Write of a Customer Transfer
Record
Input Parameters: None.
Return Parameter: None.

Global Variables for Reference Only:

[Link]
[Link]$
[Link]$
[Link]
[Link]
[Link]
[Link]$
[Link]$
[Link]$
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]$
[Link]
[Link](1)

Suggested Global Variables for Update Only:

[Link]
[Link]$
[Link]$
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]

Comments: THE CODE IN USERXFUP.J86 IS EXECUTED JUST

AFTER THIS EXIT

Function Definition:
FUNCTION CSEMEC04 PUBLIC ! BEFORE THE WRITE OF A CUSTOMER TRANSFER RECORD
! insert user exit code here
END FUNCTION

Exit CSEMEC05 - Called Before the Write of an Activity Transfer

Record
Input Parameters: None.
Return Parameter: None.

Global Variables for Reference Only:

[Link]
[Link]$
[Link]$
[Link]
[Link]
[Link]
[Link]$
[Link]$

310 Electronic Marketing PRPQ

 [Link]$
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]$
[Link]
[Link](1)
[Link]

Suggested Global Variables for Update:

X$

Comments: X$ CONTAINS THE RECORD TO BE WRITTEN JUST

AFTER THIS EXIT

Function Definition:
FUNCTION CSEMEC05 PUBLIC ! BEFORE THE WRITE OF AN ACTIVITY TRANSFER RECORD
! insert user exit code here
END FUNCTION

Exit CSEMEC06 - Called After The Update Of Accounting Totals

Input Parameters: None.
Return Parameter: None.

Global Variables for Reference Only

[Link]
[Link]$
[Link]$
[Link]
[Link]
[Link]
[Link]$
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]$
[Link]
[Link](1)

Global Variables for Update:

[Link]$
[Link]$

Comments: [Link]$ AND [Link]$ HAVE BEEN

UPDATED WITH E.M. UNIQUE DATA. BASE CODE WRITES
RECORDS.

Function Definition:
FUNCTION CSEMEC06 PUBLIC ! AFTER THE UPDATE OF ACCOUNTING TOTALS
! insert user exit code here
END FUNCTION

Chapter 11. Electronic Marketing Unique User Exits 311

Exit CSEMEC07 - Called Before The Write Of A Preferred Customer
Audit Log Record
Input Parameters: None.
Return Parameter: None.

Global Variables for Reference Only:

[Link]
[Link]$
[Link]$
[Link]
[Link]
[Link]
[Link]$
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]$
[Link]
[Link](1)

Suggested Global Variables for Update:

[Link]$

Comments: THE CODE IN USERRAUP.J86 IS EXECUTED JUST

AFTER THIS EXIT TO WRITE [Link]$ TO FILE

Function Definition:
FUNCTION CSEMEC07 PUBLIC ! BEFORE THE WRITE OF AN AUDIT LOG RECORD
! insert user exit code here
END FUNCTION

Exit CSEMEC08 - Called Before the Write of a Panel Diary Record

Input Parameters: None.
Return Parameter: None.

Global Variables for Reference Only:

[Link]
[Link]$
[Link]$
[Link]
[Link]
[Link]
[Link]$

Suggested Global Variables for Update:

[Link]$

Comments: [Link]$ IS WRITTEN TO FILE JUST

AFTER THIS EXIT.

Function Definition:
FUNCTION CSEMEC08 PUBLIC ! BEFORE THE WRITE OF A PANEL DIARY RECORD
! insert user exit code here
END FUNCTION

312 Electronic Marketing PRPQ

Exit CSEMEC09 - Called Before The Write Of A Coupon Tracking
Record
Input Parameters: None.
Return Parameter: None.

Global Variables for Reference Only:

[Link]
[Link]$
[Link]$
[Link]
[Link]
[Link]
[Link]
WORK4I2 (CONTAINS SESSION NUMBER)

Suggested Global Variables for Update:

WORK$

Comments: WORK$ IS WRITTEN TO FILE JUST

AFTER THIS EXIT.

Function Definition:
FUNCTION CSEMEC09 PUBLIC ! BEFORE THE WRITE OF A COUPON TRACKING RECORD
! insert user exit code here
END FUNCTION

Chapter 11. Electronic Marketing Unique User Exits 313

314 Electronic Marketing PRPQ
Part 4. Appendixes

© Copyright IBM Corp. 1991 2000 315

316 Electronic Marketing PRPQ
Appendix A. Electronic Marketing Database
File and Options Support. . . . . . . . . . . . . . . . . . . . . 318
Preferred Customer Enrollment File (EAMFBCUS) . . . . . . . . . . . 320
Preferred Customer Activity File (EAMFBACT) . . . . . . . . . . . . . 322
Preferred Customer Previous Activity File (EAMFBAPP) . . . . . . . . . 324
Electronic Marketing Report Descriptors File (EAMEDESC) . . . . . . . . 325
Preferred Customer Transfer File (EAMFBXFR) . . . . . . . . . . . . 325
Preferred Customer Activity Transfer File (EAMXssss) . . . . . . . . . . 326
Preferred Customer Audit Log (EAMFBAUD) . . . . . . . . . . . . . 327
Redemption Adjustment Record Format . . . . . . . . . . . . . . 327
Rain check Record Format . . . . . . . . . . . . . . . . . . 327
Preferred Customer Enrollment Change Log (EAMFBCHG) . . . . . . . 328
Preferred Customer Messages File (EAMFBMSG) . . . . . . . . . . . 330
Panel Diary File (EAMPANEX). . . . . . . . . . . . . . . . . . . 330
Period Header String . . . . . . . . . . . . . . . . . . . . . 331
Marker for Preferred Customer Transactions . . . . . . . . . . . . 331
Marker for Items to which Preferred Customer Coupons Might Apply. . . . 331
Marker for Coupon Tracking Transactions . . . . . . . . . . . . . 332
Automatic Coupon Transaction Data String . . . . . . . . . . . . . 332
Customer Identification String . . . . . . . . . . . . . . . . . . 332
Preferred Customer Transaction Data String . . . . . . . . . . . . 333
New Tender Verification Account Number String . . . . . . . . . . . 333
Alias Electronic Coupon Item Code String . . . . . . . . . . . . . 333
Coupon Tracking String . . . . . . . . . . . . . . . . . . . . 334
Bonus/Redemption Points String . . . . . . . . . . . . . . . . . 334
Redemption/Adjustment String. . . . . . . . . . . . . . . . . . 335
Period Summary String . . . . . . . . . . . . . . . . . . . . 335
Panel Filter File (EAMFBFLT) . . . . . . . . . . . . . . . . . . . 336
Targeted Coupon Messages File (EAMFBTCM) . . . . . . . . . . . . 340
Item Record File Usage (EAMITEMR) . . . . . . . . . . . . . . . . 341
Linked Coupons . . . . . . . . . . . . . . . . . . . . . . . 341
Linked Alias Coupons . . . . . . . . . . . . . . . . . . . . 342
Coupon Quantity Limit. . . . . . . . . . . . . . . . . . . . 342
Coupon Weight Limit . . . . . . . . . . . . . . . . . . . . 342
Weight Items . . . . . . . . . . . . . . . . . . . . . . . 343
Items Not Eligible for Points. . . . . . . . . . . . . . . . . . 343
Points-Only Items . . . . . . . . . . . . . . . . . . . . . 343
Bonus Coupons . . . . . . . . . . . . . . . . . . . . . . 344
Redemption Coupons . . . . . . . . . . . . . . . . . . . . 344
Links to Deposit . . . . . . . . . . . . . . . . . . . . . . 344
Coupons that Require Separate Minimum Purchase Amounts . . . . . 344
Pricing Method 4 “Net Value” and “Percent Off” Coupons . . . . . . . 344
Summary of Item Record Changes for Coupons . . . . . . . . . . 346
Allow Coupon Validation by Department with Minimum Purchase by
Transaction . . . . . . . . . . . . . . . . . . . . . . . . 346
Allow Minimum Purchase by Department with No Coupon Validation. . . . 347
Allow Minimum Purchase by Department with Validation by MFR . . . . . 347
Staged Item Movement File (EAMIMOV1) . . . . . . . . . . . . . . 351
Record Format – Store Record . . . . . . . . . . . . . . . . . 351
Record Format – Movement Record . . . . . . . . . . . . . . . 352
Accounting File Usage (EAMACCTC) . . . . . . . . . . . . . . . . 352
Performance File Usage (EAMPERFC) . . . . . . . . . . . . . . . 353
Department Totals File Usage (EAMDEPTC) . . . . . . . . . . . . . 353
Exception Log Usage (EAMEXCPT) . . . . . . . . . . . . . . . . 354

© Copyright IBM Corp. 1991 2000 317

 User Log of Data Entry = X'19' (Customer number seen multiple times) 354
Addition to 02 and 03 Log Entries . . . . . . . . . . . . . . . . 354
User Log = X'99' (Transfer activity file processed) . . . . . . . . . . 354
System Error Log Usage . . . . . . . . . . . . . . . . . . . . . 355
Preferred Customer Coupon Tracking File (EAMCOUPC) . . . . . . . . . 356
Sample Coupon Record . . . . . . . . . . . . . . . . . . . . . 358
Packed Format (only demonstrable in Hex) . . . . . . . . . . . . . . 358
Exception Log Format (only demonstrable in Hex) . . . . . . . . . . . 358

The Electronic Marketing application supports a number of input and output files.
The files documented in this appendix show an offset in decimal when the
offset is shown.

File and Options Support

The file structure was designed for maximum flexibility and optimal performance
and disk utilization. There are three primary input files and two optional input files:
v Options file, providing customizing input
v Messages file, providing all preferred customer text
v Item Record File, providing the electronic coupon
v Optional filter files
v Optional targeted coupon message interface.
The options and messages files are designed to be set up by a data processing
professional at a test site and then propagated to stores, instead of being altered in
stores. The item record interface to electronic coupons is critical for establishing
consistency with the Supermarket Application. This consistency leads to full
functional compatibility. Maintenance of electronic coupons is enhanced by the
many tools available to maintain the Item Record File. For more information, see
“Item Record File Usage (EAMITEMR)” on page 341.

The many output files, necessary to maintain compatibility, performance, and

flexibility, are as follows:
v Three preexisting files, used by the Electronic Marketing application for the same
purposes as they served for the Supermarket Application:
– Accounting file
– Operator performance file
– Exception log file.
v Five sequential output files, that are optional, are designed to provide a method
to manage potentially large amounts of output data simply and efficiently. They
are as follows:
– Enrollment Change File
– Audit log
– Coupon tracking files
– Activity Transfer File, streamlined to enhance network performance and
minimize host processing costs
– Panel Diary File, designed to capture a full history of customer data and
present this massive amount of data as simply as possible.
v These new keyed files, designed as separate files to separate data by its usage,
as follows:
– Preferred Customer Enrollment File, that is not required in the store and is
never accessed during the checkout transaction. The enrollment file gives an

318 Electronic Marketing PRPQ

 enterprise maximum flexibility to decide what customer information to obtain
and where to enter and maintain this information.
– Preferred Customer Activity File, that is accessed by the checkout process for
each preferred customer transaction and is optimized for performance and
integrity.
– Previous period activity files, is optional.
– Targeted coupon messages file, is optional.
– Preferred Customer Transfer File, that is also optional because it is accessed
only if an enterprise supports multiple stores (see “Count Home Store
Numbers Supported by This Store” on page 102) and needs to transfer activity
data from one store to another when customers shop in non-home stores. It is
effectively an optional, low-usage extension of the customer activity file.

Each of the new preferred customer output files is created and maintained
completely by the application code to minimize the installation and maintenance
support required. Duplicate copies of each of the files are kept to maintain backup
integrity. All but the current period activity file are effectively optional. But the
sequential files are always created, whether or not they will be used. Each of these
files is opened only when needed, but may be held open for multiple accesses for
performance reasons. Each register releases the new keyed files at sign-off.
Checkout support closes both of the transfer files and the activity file on each hour
at the close of the period. This processing allows an enterprise to access these files
for maintenance purposes when they are not needed for processing preferred
customers. The panel file is closed only at the end of the accounting period and
cannot be accessed for the period in process. If an enterprise selects to accumulate
data in the panel file (see “Collect Panel Data for All Customers” on page 85), it is
responsible for discarding data from the old period panel file periodically. This
prevents the old period file from filling all available disk space.

An enterprise must create and maintain each of the new input files. The package
provides default files are provided for the options, filter, and messages files. If the
option file is present but contains invalid data, valid defaults are substituted. The
contents of the messages and options files are read in the following ways:
Table 4. Reading the Contents of Messages and Options Files
File Where Read When Read
Message file Into Extended Terminal Each time the terminal reloads the base
Memory terminal options
Options file Into Extended Terminal When the base options are read At each
Memory operator sign-on
Options file By controller checkout Only when it reads the base options at
support program initialization

File error processing for all preferred customer files accesses is consistent with the
Supermarket Application. All critical file access failures are logged and recovery is
attempted whenever it is possible. Failed preferred customer accesses are
bypassed, particularly at the terminal, so that sales can continue even if these files
are unavailable. The preferred customer processing does not stop a terminal from
running in stand-alone, but the loss of preferred customer totals and electronic
coupons for stand-alone transactions make this an undesirable method of primary
backup. The Preferred Customer Activity File is designed to be compatible with the
terminal offline feature. Offline electronic coupons and offline totals accumulation

Appendix A. Electronic Marketing Database 319

 should be available even though some of the activity file processing (such as
preferred customer message processing) is lost when the activity file is
inaccessible.

Preferred Customer Enrollment File (EAMFBCUS)

The customer enrollment file contains a single record for each preferred customer
for their home store. This record contains the demographic data entered for a
customer at enrollment. The enrollment program also tracks adjustments and
redemptions in this file. Two copies of the file are maintained for backup. The file is
accessed and updated only by the enrollment program. It is optional, depending on
whether the in-store enrollment program is used and whether this file is accessed
by the program.
Filename: EAMFBCUS I/O Session: 1
Organization: Keyed File Copies: 2
Record Length: 254 Distribution class: Mirrored
Table 5. Preferred Customer Enrollment File
Field Name Type Length Offset Description
CUSTNUM PD 9 0 Customer ID number left-padded with zeroes to length 18,
then packed
RSTAT ASCII 1 9 Record status “1”—“7” = last enrollment function to update
this record
LNAME ASCII 17 10 Customer last name
FNAME ASCII 13 27 Customer first name
ALINE1 ASCII 25 40 Apt., PO Box, RT number, etc.
ALINE2 ASCII 25 65 Street address
CITY ASCII 20 90 City name
STATE ASCII 2 110 State abbreviation
ZIP PD 3 112 Zip code
ZIPEXT PD 2 115 Zip code extension
HPHONA PD 2 117 Home phone area code
HPHONE PD 4 119 Home phone number
BPHONA PD 2 123 Business phone area code
BPHONE PD 4 125 Business phone number
DRIVER ASCII 20 129 Driver’s license number
HSTORE PD 3 149 Home store number
CUSTDEMO PD 3 152 Customer Demographic Field
RESERVED PD 1 155 Reserved
SSNBREXT PD 2 156 Social Security number (extension)
SSNBR PD 5 158 Social Security number
GENDER ASCII 1 163 Gender (M or F)
INCOME ASCII 1 164 Family annual income level indicator
BDATE PD 3 165 Birth date (YYMMDD)
EDATE PD 3 168 Enrollment date (YYMMDD)
FSIZE PD 1 171 Family size

320 Electronic Marketing PRPQ

Table 5. Preferred Customer Enrollment File (continued)
Field Name Type Length Offset Description
CHAGE1 PD 1 72 Child 1 age
CHAGE2 PD 1 73 Child 2 age
CHAGE3 PD 1 74 Child 3 age
CHAGE4 PD 1 75 Child 4 age
CHAGE5 PD 1 76 Child 5 age
CHAGE6 PD 1 77 Child 6 age
CHAGE7 PD 1 78 Child 7 age
TNBRA PD 2 179 Number of adjustments
TNBRR PD 2 181 Number of redemptions
TPADJP PD 4 183 Total points adjusted plus
TPADJN PD 4 187 Total points adjusted minus
LADNBR PD 3 191 Last adjustment form number
LRDNBR PD 3 194 Last redemption form number
LADATE PD 3 197 Last adjustment date (YYMMDD)
LRDATE PD 3 200 Last redemption date YYMMDD
CDATE PD 3 203 Last change date for record YYMMDD
LRCDATE ASCII 3 206 Last rain check date YYMMDD
CUSAUT ASCII 1 209 Customer authorization (Y=Yes, N=No)
ALIAS ASCII 1 210 Referenced = Alias (Y=Yes, N=No)
REFCUS PD 9 211 Referenced account to get all points
LASTRC PD 3 220 Last rain check amount
STATEEXT ASCII 1 223 STATE (extension)
ZIPASC ASCII 5 224 ZIP (Alphanumeric)
ZIPEXTASC ASCII 4 229 ZIPEXT (Alphanumeric)
DRIVEREXT ASCII 5 233 DRIVER (extension)
USERDATA ASCII 16 238 Reserved for User Data

The records in the file intentionally have unused space in case you want to use the
file to save additional demographic data. With two records per sector, only about
3200 records fit in a 1MB (MB = 1 048 576 bytes) file at an 80% packing factor.

Appendix A. Electronic Marketing Database 321

 Preferred Customer Activity File (EAMFBACT)
The Preferred Customer Activity File contains a single record for each preferred
customer for their home store. This file accumulates buying activity information for
each customer and provides input for customer transaction processing. The records
contain the information needed at the terminal during a transaction. A copy of this
file is maintained on all controllers. Updates to the file are made through checkout
support or controller maintenance functions. A copy of the file can optionally be
saved at store closing as EAMFBACX for additional backup or to checkpoint activity
data for a host dump.
Filename: EAMFBACT I/O Session: 55
Organization: Keyed File Copies: 1 per controller
| Record Length: 31—508 bytes
| Distribution class: Compound
Table 6. Preferred Customer Activity File
Field Name Type Length Offset Description
CUSTNUM PD 9 0 Customer identification number (up to 18 digits)
TOTAL POINTS PD 4 9 Total points accumulated (0—999,999.99) Gross totals
including adjustments
TOTAL TRANS PD 2 13 Total number of transactions (0—9999)
REDEEMED PTS PD 4 15 Redeemed points
AUTO COUPONS PD 3 19 Automatic store coupon amount
LAST DATE PD 3 22 Date of last purchase (YYMMDD)
LAST POINTS PD 3 25 Number of points from last transaction
STATUS LEVEL PD 1 28 Customer status level (0—99)
MESSAGE PD 1 29 Message number (7—49) to be shown at next visit
OPTIONS PD 1 30 Flags defining optional processing
X'80' Do not give preferred discounts
X'40' No updates of non-home record, only input
X'20' Use alternate number as alias ID
X'10' Transfer data available to be printed
X'08' Do not give enrolled customer points
X'04' Do not give auto coupons
X'02' Do not collect panel data
X'01' Do not personalize trailer message
DISCOUNT PD 1 31 Discount group number for customer
MULTIPLIER PD 1 32 Point multiplier (0-99) in tenths 1 = 10% increase, 10 =
100% increase
TARGET COUPS PD 10 33 Targeted coupon deal numbers (0—9999)
ALT CUSTNUM PD 9 43 Alternate customer number (up to 18 digits)
PERIOD PD 2 52 Period starting date (MMDD)
PERIOD POINTS PD 4 54 Points in this period (0-99999999)
PERIOD TRANS PD 2 58 Transaction is this period (0-9999)
PERIOD REDEEM PD 4 60 Points redeemed in this period
LAST REDEEM PD 3 64 Date of last redemption (YYMMDD)
SALES TOTAL PD 4 67 Gross+ less Gross- for all transactions
USER DATA PD v183 71 User fields (extra targeted coupons)

322 Electronic Marketing PRPQ

 Table 6. Preferred Customer Activity File (continued)
Field Name Type Length Offset Description
LAST TNUM ASCII 1 ?? Transaction number of last update
CUSTOMER ASCII 30 ?? Customer name to be printed (optional field)

This is a fixed-length record with the length defined by the activity record size
option, described on page 82. The customer name field can range from zero to 30
bytes but must be the same length in all records. Your selection of the length of this
field applies to all records. If all fields prior to SALES TOTAL (offset 67) are defined
as above and a 17-character name field is defined, the record is 84 bytes in length.
At this length, six records fit into each sector, allowing about 9600 records in a 1MB
file at an 80% packing factor. With a full 30-character name and the SALES TOTAL
field, five records fit into each sector, allowing about 8000 records in a 1MB file at
an 80% packing factor. If all data is defined as above, including 26 bytes of user
data, four records fit into each sector, allowing about 6400 records in a 1MB file at
an 80% packing factor. These records should be defined as 254, 169, 127, 101, 84,
or 72 bytes or perhaps smaller, because it is not advantageous to leave empty
space in a sector.

The personalization options “Activity Record Size” on page 82 and “Bytes Before
the Customer Name in Activity Record” on page 82 define the length of this record
and the number of bytes that precede the descriptor in the record. These options
can determine the size of the record. The record can be as small as 31 bytes if
both the record length and the descriptor offset options are set to 31. The fields that
are truncated are not used. If you have space limitations and do not need period
totals or an alternate account number, you should set the record size to 63 and the
descriptor offset to 43 to allow for a 20-character descriptor and fit eight records in
each sector. This would reduce the total file size by 37% in excess of that needed
for this size descriptor with all data fields. Likewise, you might set the record size to
101 and the descriptor offset to 91 to allow ten bytes of user space along with a
| 20-character descriptor with five records per sector.

| Note: Options allow part or all of the USER DATA field to be used for additional
| targeted coupons. With a 508 byte record and a 30 character customer
| name descriptor, 407 bytes of user data are available to hold up to 203
| additional targeted coupons. Adding to the five coupons stored at offset 33,
| this allows a total of 208 targeted coupons. With a 508 byte record and NO
| customer name descriptor, 437 bytes of user data are available to hold up to
| 218 additional targeted coupons. Adding to the five coupons stored at offset
| 33, this allows a total of 223 targeted coupons. This is the maximum number
| of targeted coupons supported by the Electronic Marketing application.

| The “LAST TNUM” field contains the low byte of the transaction number of the last
transaction used to update this record. This is used to distinguish two transactions
for the same customer and same amount in the same day so that totals are
properly updated instead of being discarded as duplicates. This field exists only if
the activity record is long enough to contain user data and if some of the user data
is not reserved for targeted coupons. When this field is present, it always occupies
the last byte of the user data area.

Appendix A. Electronic Marketing Database 323

Preferred Customer Previous Activity File (EAMFBAPP)
Filename: EAMFBAPP I/O Session: 63
Organization: Keyed File Copies: 1 per controller
Record Length: 36 Distribution class: Mirrored

The previous customer activity file is a keyed file which contains a single record for
each preferred customer who is in the customer activity file when a points activity
period is closed. This file and its contents are created by the period close procedure
that is used to reset points totals periodically. If the period close procedure is not
used, then this file does not exist. Each time that the activity period is closed, the
prior period information for each customer is saved in this file. Neither the file nor
any of its records are ever deleted, but rather, the active records are overlayed at
each successive close. The file can optionally contain up to 12 monthly records for
each customer by keeping all records for the most recent year and overlaying only
records with the same period starting month. Two copies of the file are maintained
for backup.
Table 7. Customer Previous Activity File Record Format
Field Name Type Length Offset Description
CUSTNUM PD 9 0 Customer identification number (up to 18 digits)
START DATE PD 2 9 Date of start of period (MMDD)
END DATE PD 2 11 Date of end of period (MMDD)
LAST DATE PD 3 13 Date of last purchase (YYMMDD)
LAST POINTS PD 3 16 Number of points from last transaction
PERIOD POINTS PD 4 19 Total points accumulated during period (Gross total
including adjustments)
PERIOD TRANS PD 2 23 Total number of transactions in period
REDEEMED PTS PD 4 25 Total points redeemed during period
CARRYOVER PTS PD 4 29 Points carried into the new period
DISCOUNT PD 1 33 Discount group number for prior period
FLAGS ASCII 1 34 Flags defining totals X'01' Carry over amount is negative
RESERVED PD 1 35 Reserved for future use

324 Electronic Marketing PRPQ

Electronic Marketing Report Descriptors File (EAMEDESC)
Filename: EAMEDESC I/O Session: 61,6
Organization: Random File Copies: 1 per controller
Record Length: 49 Distribution class: Compound

The Electronic Marketing report descriptors file is a random file which contains the
descriptor text needed for the Preferred Customer reports. These descriptors can
be up to 40 characters in length with a maximum value defined for each descriptor
in the file. The file is a random file so that any descriptor can be accessed
individually. The record length of 49 bytes accommodates a 40-byte descriptor with
delimiters and a 2 digit length. The format of this file is an exact match for the
terminal sales descriptors file [Link] that comes with the supermarket
application. Since it is in the same format, you can use the personalization
procedure to alter the contents of this file if you wish. You need to save
[Link] as [Link], copy [Link] to [Link]
and then select to personalize sales descriptors. Because of the file switch, you will
see the Electronic Marketing report descriptors. Once the personalization is
complete, you must restore [Link] to [Link] and then restore
[Link] to [Link].
Table 8. Electronic Marketing Report Descriptors File Record Format
Field Name Type Length Offset Description
DESCRIPTOR ASCII v40 0 Descriptor up to 40 characters in quotes
MAXLENGTH ASCII v2 v44 Maximum length (1-40), 2 digits in quotes

Preferred Customer Transfer File (EAMFBXFR)

The Preferred Customer Transfer File contains a single record for each preferred
customer who has transferred points from another store. All updates to the file are
made through checkout support or controller maintenance functions because the
register never updates the file.
Filename: EAMFBXFR I/O Session: 54
Organization: Keyed File Copies: 1 per controller
Record Length: 36 bytes Distribution class: Compound :edl
Table 9. Customer Transfer File
Field Name Type Length Offset Description
ACCOUNT PD 9 0 Customer account number
PENDING POINTS PD 4 9 Points in transfer (0—999,999.99)
PENDING TRANS PD 2 13 Transactions in transfer
PENDING COUPON PD 3 15 Automatic coupons in transfer (.00—9999.99)
LAST DATE PD 3 18 Date of last transferred purchase (YYMMDD)
LAST POINTS PD 3 21 Number of points from last transferred trans.
TOTAL POINTS PD 4 24 Total points transferred
TOTAL TRANS PD 2 28 Total transactions transferred
TOTAL COUPON PD 3 30 Total automatic coupons transferred
RESERVED PD 3 33 Reserved for future use

Appendix A. Electronic Marketing Database 325

 Fourteen of these records fit in a sector, and about
22,000 records fit in a 1MB file. These records can
be deleted to minimize the required file size, but the
maximum file size would contain as many records
as the Preferred Customer Activity File.

Preferred Customer Activity Transfer File (EAMXssss)

The Preferred Customer Activity Transfer File is used to move preferred customer
information from one store to another. Each record contains the information needed
to transfer a preferred customer transaction. There is one outbound file per store
but there can be many inbound files. The files are named EAMXssss, where ssss is
the originating store number for any outbound file. The application maintains two
copies of the outbound file. The distribution attributes of the inbound files are
determined by the mechanism used to move them into the store. It is suggested
that these files also be mirrored for backup.

Inbound files can have numbers in the range of 0000 to 0009 or in the range of
valid store numbers defined in the options (see “Valid Range of Non-Home Store
Numbers” on page 98). A record in an inbound file is processed in a given store
only if the record did not originate in that store and the destination store number is
supported there.
Filename: EAMXssss I/O Session: 11
Organization: Sequential File Copies: 1 out, many in
Record Length: 32 bytes Distribution class: Mirrored
Table 10. Customer Activity Transfer File
Field Name Type Length Offset Description
HOME STORE PD 2 0 Destination store number
USED STORE PD 2 2 Originating store number
ACCOUNT PD 9 4 Customer account number
POINTS PD 3 13 Points for this transaction
COUPONS PD 2 16 Coupon amount for this transaction
DATETIME PD 5 18 Date and time of transaction (YYMMDDHHmm)
TERMINAL PD 2 23 Terminal where transaction took place
TRANSACTION PD 2 25 Transaction number for this transaction
REDEEMED PD 4 27 Points redeemed in transaction
OPTIONS PD 1 31 Options flags
X'04' Redemption points are negative
X'02' Transaction points are negative
X'01' Immediate activity update

All data in the record is packed decimal numerics and all fields are fixed-length with
no separating delimiters. Each record contains 32 bytes of data and there are no
record delimiters. Each record requires exactly 32 bytes of file space.

326 Electronic Marketing PRPQ

Preferred Customer Audit Log (EAMFBAUD)
The Preferred Customer Audit Log is used to log points redemption and points
adjustment events for security auditing purposes. Two copies of the log are
maintained. An old period copy of the audit file is maintained that consists of all the
audit data appended since the last time that this old period file was dumped and
purged. Current period audit data is appended to the old period file at the close of
every reporting period. The current period file cannot be retrieved by the host
because it must always be available for updates. The accumulation of old period
audit log data is optional; the old period Audit Log need not exist.

There is an option that causes the current period audit log data to be reformatted
and appended to the panel file EAMPANEL at the close of a reporting period. See
“Append Audit Data to Panel File” on page 130.
Filename: EAMFBAUD I/O Session: 9
Organization: Sequential File Copies: Current, Old
Record Length: 36 bytes Distribution class: Mirrored

Redemption Adjustment Record Format

Table 11. Customer Audit Log
Field Name Type Length Offset Description
ACCOUNT PD 9 0 Customer account number
TRANTYPE PD 1 9 “R” = redemption, “A” = adjustment
DATETIME PD 5 10 Date and time of transaction (YYMMDDHHmm)
TERMINAL PD 2 15 Terminal where transaction took place
TRANSACTION PD 2 17 Transaction number for this transaction
OPERATOR PD 5 19 Operator/Employee who performed transaction
POINTSP PD 4 24 Points adjusted/redeemed plus
POINTSM PD 4 28 Points adjusted/redeemed minus
SERIALNUM PD 3 32 Form serial number
RESERVED PD 1 35 Reserved

In the file data structure, this record is surrounded by quotes and followed by a
carriage return/line feed (X'0D0A') to yield a net usage of 40 bytes per record.

Rain check Record Format

Table 12. Customer Audit Log
Field Name Type Length Offset Description
ACCOUNT PD 9 0 Customer account number
TRANTYPE PD 1 9 “X” = rain check
DATETIME PD 5 10 Date and time of original transaction
TERMINAL PD 2 15 Terminal where rain check transaction took place
TRANSACTION PD 2 17 Transaction number for rain check transaction
OPERATOR PD 5 19 Operator/employee who performed rain check transaction
POINTSP PD 4 24 Points adjusted/redeemed plus

Appendix A. Electronic Marketing Database 327

Table 12. Customer Audit Log (continued)
Field Name Type Length Offset Description
UNUSED PD 4 28 Unused
STORENUM PD 2 32 Store where rain check transaction took place
RESERVED PD 2 34 Reserved

In the file data structure, this record is surrounded by quotes and followed by a
carriage return/line feed to yield a net usage of 40 bytes per record.

A rain check transaction performed from the controller enrollment procedure logs
both an adjustment record and a rain check record. The adjustment record
describes the situation at the time of the rain check adjustment. The rain check
record describes the situation at the time the sales transaction is adjusted.

Preferred Customer Enrollment Change Log (EAMFBCHG)

The Preferred Customer Enrollment Change Log is used to log changes to the
enrollment file. This file is optional and is intended to aid the maintenance of a host
copy of the enrollment data. Two copies of the log are maintained for backup.

These 256 byte records contain the 254 bytes of enrollment data from a Preferred
Customer Enrollment File record followed by a carriage return/line feed (X'0D0A').
The 254 bytes of enrollment data is formatted exactly as defined in the Preferred
Customer Enrollment file (see “Preferred Customer Enrollment File (EAMFBCUS)”
on page 320). The carriage return/line feed delimits each record. Records are
written to this file when the in-store enrollment procedure is used to alter enrollment
data. The file can contain multiple records for a customer if that customer’s data
was altered multiple times. In this case, the last record in the file represents the
most recent data for the customer. The records are written as the changes occur.
The RSTAT field in each record shows the last enrollment function to act on this
record. An RSTAT value of three indicates that the record has been deleted.
Filename: EAMFBCHG I/O Session: 2
Organization: Sequential File Copies: 2
Record Length: 256 bytes Distribution class: Mirrored
Table 13. Preferred Customer Enrollment Change Log
Decimal
Field Name Type Length Offset Description
CUSTNUM PD 9 0 Customer ID number left-padded with zeroes to length 18,
then packed
RSTAT ASCII 1 9 Record status “1”—“7” = last enrollment function to update
this record. For example, record status “3” = record has
been deleted.
LNAME ASCII 17 10 Customer last name
FNAME ASCII 13 27 Customer first name
ALINE1 ASCII 25 40 Apt., PO Box, RT number, etc.
ALINE2 ASCII 25 65 Street address
CITY ASCII 20 90 City name
STATE ASCII 2 110 State abbreviation
ZIP PD 3 112 Zip code

328 Electronic Marketing PRPQ

Table 13. Preferred Customer Enrollment Change Log (continued)
Decimal
Field Name Type Length Offset Description
ZIPEXT PD 2 115 Zip code extension
HPHONA PD 2 117 Home phone area code
HPHONE PD 4 119 Home phone number
BPHONA PD 2 123 Business phone area code
BPHONE PD 4 125 Business phone number
DRIVER ASCII 20 129 Driver’s license number
HSTORE PD 3 149 Home store number
CUSTDEMO PD 3 152 Customer Demographic Field
RESERVED PD 1 155 Reserved
SSNBREXT PD 2 156 Social Security number (extension)
SSNBR PD 5 158 Social Security number
GENDER ASCII 1 163 Gender (M or F)
INCOME ASCII 1 164 Family annual income level indicator
BDATE PD 3 165 Birth date (YYMMDD)
EDATE PD 3 168 Enrollment date (YYMMDD)
FSIZE PD 1 171 Family size
CHAGE1 PD 1 72 Child 1 age
CHAGE2 PD 1 73 Child 2 age
CHAGE3 PD 1 74 Child 3 age
CHAGE4 PD 1 75 Child 4 age
CHAGE5 PD 1 76 Child 5 age
CHAGE6 PD 1 77 Child 6 age
CHAGE7 PD 1 78 Child 7 age
TNBRA PD 2 179 Number of adjustments
TNBRR PD 2 181 Number of redemptions
TPADJP PD 4 183 Total points adjusted plus
TPADJN PD 4 187 Total points adjusted minus
LADNBR PD 3 191 Last adjustment form number
LRDNBR PD 3 194 Last redemption form number
LADATE PD 3 197 Last adjustment date (YYMMDD)
LRDATE PD 3 200 Last redemption date YYMMDD
CDATE PD 3 203 Last change date for record YYMMDD
LRCDATE ASCII 3 206 Last rain check date YYMMDD
CUSAUT ASCII 1 209 Customer authorization (Y=Yes, N=No)
ALIAS ASCII 1 210 Referenced = Alias (Y=Yes, N=No)
REFCUS PD 9 211 Referenced account to get all points
LASTRC PD 3 220 Last rain check amount
STATEEXT ASCII 1 223 STATE (extension)
ZIPASC ASCII 5 224 ZIP (Alphanumeric)

Appendix A. Electronic Marketing Database 329

Table 13. Preferred Customer Enrollment Change Log (continued)
Decimal
Field Name Type Length Offset Description
ZIPEXTASC ASCII 4 229 ZIPEXT (Alphanumeric)
DRIVEREXT ASCII 5 233 DRIVER (extension)
USERDATA ASCII 16 238 Reserved for User Data

Preferred Customer Messages File (EAMFBMSG)

The description and table for the Preferred Customer Messages File is in Chapter 6.
Personalization of Preferred Customer Options and Messages on page 169.

Panel Diary File (EAMPANEX)

Filename: EAMPANEX, EAMPANEL
I/O Session: 24
Organization: Sequential File Copies: Current, Old
Record Length: Variable Distribution class: Mirrored

The Panel Diary File contains all of the transaction summary log information for
selected preferred customers. It may optionally contain sales information on all
customers, whether or not they presented a preferred customer ID. The data in the
file consists of the host format of string types zero to 11 from the transaction
summary log. The content of these strings as well as the data types for host format
are defined in the IBM 4680 Supermarket Application: Programming Guide Two
copies of the file are maintained by the application.

An old period copy of the panel file is maintained that consists of appended panel
data since the last time this old period file was dumped and purged. Current period
panel data is appended to the old period file at the close of every reporting period.
This old period file can be retrieved by the host in EBCDIC by requesting the file
name $PANEL through ADCS. The current period file cannot be retrieved by the
host because it must always be available for updates.

The file size can become very large, but the data in this file is compressible. You
can use the system file compression facilities to compress the panel file before it is
transmitted across phone lines. This substantially reduces transmission time. The
data can be decompressed at the host.

The panel file grows at a rate of about 3MB per $100,000.00 of contained sales
data. For example, a store that produces $500,000.00 of business a week and
keeps panel data for customers accounting for 80% of that volume should expect to
accumulate 12MB of panel data a week. This panel data can be compressed using
the operating system file utilities to achieve a compression ratio of four to one. For
example, a 12MB panel file can be compressed into a 3MB file for transmission.

An optional panel filtering function (see “Panel Filter File (EAMFBFLT)” on

page 336) reduces the size of the Panel Diary file by deleting all information for
selected items, manufacturers, or departments. It can also create multiple copies of
the old period panel file containing different subsets of the panel data. These
functions are selected by the presence and contents of panel filter files. Up to nine
additional old period panel files (EAMPANL1 through EAMPANL9) can be added

330 Electronic Marketing PRPQ

 through the filter function. It is suggested that the filtering function be used to
reduce the contents of all Panel files because the size of the customer purchase
history data can be large.

The contents of string types zero to 11 of the Transaction Summary Log are defined
in the IBM 4680 Supermarket Application: Programming Guide The fields defined in
these strings and are delimited by ASCII characters as follows:
Items to be Delimited ASCII Character
Fields “:” (colon)
Strings “,” (comma)
Records ASCII carriage return/line feed

The fields in the Transaction Summary Log definitions. are packed decimal. They
are represented in the panel file as ASCII numerics except for the flag fields. The
flag fields are represented by the ASCII characters 0—F that define the
hexadecimal value of the fields. These data definitions are consistent with the new
data format of the Transaction Summary Log as provided through the application
translation routines. String type 11 contains the new data unique to the preferred
customer function. The panel file can be directly printed in the store through the
command PRINT EAMPANEL, to view the file contents, or the file can be dumped
to the host in EBCDIC and directed to a printer.

A period header is added to the panel data to delimit the start of a new reporting
period. This header string contains the date and time of the start of the period and
the store number. The Period Header string appears in all Panel files, but the date
and time information may not be consistent. The foreground panel file (EAMPANEL)
contains the date and time that the new file is created for the new accounting
period. All background panel files contain the date and time from the first sales
transaction in the period.

Period Header String

Table 14. Period Header String
Field Name Type Length Description
STRING TYPE ASCII 2 Period Header string type of “81”
DATE/TIME ASCII 10 Date and time as YYMMDDHHmm
STORE NUMBER ASCII 4 Store number printed on customer receipt

Marker for Preferred Customer Transactions

If a preferred customer ID is recognized in a sales transaction, the transaction is
marked in the Panel Diary File through the X'00400000' flag in field INDICAT1 in
the transaction header string. This flag has this meaning only when the TRANTYPE
field in this string type 00 has a value of zero to designate a checkout transaction.

Marker for Items to which Preferred Customer Coupons Might Apply

If items to which a preferred customer coupon might apply are marked on a
customer’s receipt, they are marked in the Panel Diary File through the X'0001' flag
in field INDICAT2 in an item string type 1.

Appendix A. Electronic Marketing Database 331

Marker for Coupon Tracking Transactions
If a coupon which requires capture in the coupon tracking file was recognized in a
sales transaction, then the transaction is marked in the Panel Data through the
X'00000010' flag in field INDICAT1 in the transaction header string.

Automatic Coupon Transaction Data String

A new data entry string is defined to show the count and amount of automatic
(linked to) store or manufacturer coupons in a transaction. This string can be in a
non-preferred customer transaction as well as a preferred customer transaction
because automatic coupons can be set up to apply to all customers.

This information is critical to the function that automatically picks up paperless

coupons.
Table 15. Automatic Coupon Transaction Data String
Field Name Type Length Description
STRING TYPE ASCII 2 Data entry string type of “11”
IDENTIFIER ASCII 2 Two characters of “< <” to define string
MFRCPN AMT ASCII v5 Amount of automatic manufacturer coupons
STRCPN AMT ASCII v5 Amount of automatic store coupons
MFRCPN CNT ASCII v5 Count of automatic manufacturer coupons
STRCPN CNT ASCII v5 Count of automatic store coupons
UNUSED ASCII 1 Reserved, value of “0”

Customer Identification String

Two new data entry strings are created by the preferred customer code and appear
in each panel file record for preferred customers. The first occurs at any entry of a
customer number and is called a customer identification string. More than one of
these strings can appear in a transaction if multiple customer numbers are entered
(see “How to Enter Multiple Customer ID Numbers per Transaction” on page 179).
or if the same number is entered multiple times. The second data entry string is
created for a preferred customer at the end of the transaction. This string always
appears immediately preceding the string for the final tender in a preferred
customer transaction.
Table 16. Customer Identification String
Field Name Type Length Description
STRING TYPE ASCII 2 Data entry string type of “11”
IDENTIFIER ASCII 1 A character of “?” to define string
ACCOUNT ASCII v18 Entered customer account number
NOSALE DATA ASCII v4 Data keyed with NOSALE key (default = “0”) Expiration
date (YYMM) if MSR entry of customer number
STORE NUMBER ASCII v4 Store number printed on customer receipt
UNUSED ASCII 1 Reserved, value of “0”
UNUSED ASCII 1 Reserved, value of “0”

332 Electronic Marketing PRPQ

Preferred Customer Transaction Data String
Table 17. Customer Transaction Data String
Field Name Type Length Description
STRING TYPE ASCII 2 Data entry string type of “11”
IDENTIFIER ASCII 2 Two characters of “> >” to define string
ACCOUNT ASCII v18 Final customer account number
POINTS ASCII v9 Points earned for transaction (including bonus)
COUPON AMT ASCII v5 Automatic preferred coupon total amount
COUPON CNT ASCII v2 Automatic preferred coupon total count
MESSAGE ASCII v2 Number of messages given from activity file
XFERR CNT ASCII v2 Count of transferred transactions
XFERR AMT ASCII v9 Amount of transferred transactions
BONUS PTS ASCII v9 Bonus points given in transaction
REDEEMED PTS ASCII v9 Points redeemed during transaction

New Tender Verification Account Number String

A new data entry string is defined to show a new tender verification account number
from a manual override of the account number from the Preferred Customer Activity
File. This string applies only to preferred customer transactions. The new alternate
account number replaces the old one in the Preferred Customer Activity File. This
string usually follows the tender string for the new account number used.
Table 18. New Tender Verification Account Number String
Field Name Type Length Description
STRING TYPE ASCII 2 Data entry string type of “11”
IDENTIFIER ASCII 2 Two characters of “;;” to define string
ACCOUNT ASCII v18 New Tender Verification account number
UNUSED ASCII 1 Reserved, value of “0”
UNUSED ASCII 1 Reserved, value of “0”
UNUSED ASCII 1 Reserved, value of “0”
UNUSED ASCII 1 Reserved, value of “0”

Alias Electronic Coupon Item Code String

A new data entry string is defined to show the primary item code when an electronic
coupon uses an alias item record to access a UPC that is too big to fit in the item
record link field. This item code is needed so that item movement can be
accumulated against both item codes that represent the coupon. The simple data
entry sting is recognized because it immediately precedes an item string for an
electronic coupon.
Table 19. Alias Electronic Coupon Item Code String
Field Name Type Length Description
STRING TYPE ASCII 2 Data entry string type of “11”
ITEMCODE ASCII 4 Linked-to item code for alias electronic coupon
UNUSED ASCII 1 Reserved, value of “0”

Appendix A. Electronic Marketing Database 333

Table 19. Alias Electronic Coupon Item Code String (continued)
Field Name Type Length Description
UNUSED ASCII 1 Reserved, value of “0”
UNUSED ASCII 1 Reserved, value of “0”
UNUSED ASCII 1 Reserved, value of “0”
UNUSED ASCII 1 Reserved, value of “0”

Coupon Tracking String

If the coupon processing enhancements are used to log coupons to the Coupon
Tracking Log (see “Coupon Tracking Options” on page 34), a data entry string is
generated to show the need for this logging and to provide extra data to log. This
string type immediately follows the coupon string to which it applies.
Table 20. Coupon Tracking String
Field Name Type Length Description
STRING TYPE ASCII 2 Data entry string type of “11”
UNUSED ASCII 2 NULL string
IDENTIFIER ASCII 2 Two characters of “= =” to define string
LOGFLAGS ASCII v2 Flags to be logged in EAMCOUPC record
CAMPAIGN ASCII v? Campaign number if keyed in
MFRNUM ASCII v5 Manufacturer number from item record
PROMO CODE ASCII v5 Promotion code used to validate the coupon

Bonus/Redemption Points String

A new data entry string is defined to show the information associated with items or
coupons that give bonus points or require the redemption of preferred customer
points. A bonus points string can appear in a regular customer transaction, but it
does not have any meaning except for a preferred customer transaction. This string
replaces the item entry string that normally accompanies an item or coupon.

Note: The INDICAT1, INDICAT2 and INDICAT3 fields in this string all contain the
DECIMAL representation of these flag fields. These same fields in the TLOG
would be represented by hexadecimal values. For example, a value of hex
2000 for INDICAT1 would be represented here as decimal 8192.
Table 21. Bonus Redemption Points String
Field Name Type Length Description
STRING TYPE ASCII 2 Data entry string type of “11”
IDENTIFIER ASCII 2 Two characters of “< >” to define string
ITEMCODE ASCII v12 Item code for bonus item/coupon
VALUE ASCII v5 Points associated with item/coupon
UNUSED ASCII 1 Reserved, value of “0”
FAMILIES ASCII v6 Family codes for item/coupon
INDICAT1 ASCII v5 Decimal value of INDICAT1 in TLOG string type 01
INDICAT2 ASCII v5 Decimal value of INDICAT2 in TLOG string type 01

334 Electronic Marketing PRPQ

Table 21. Bonus Redemption Points String (continued)
Field Name Type Length Description
INDICAT3 ASCII v2 Decimal value of INDICAT3 in TLOG string type 01
Digit 1 0 = Bonus item
6 = Manufacturer coupon
7 = Store coupon
Digit 2 8 = Redemption of points
9 = Bonus points

UNUSED ASCII 1 Reserved, value of “0”

UNUSED ASCII 1 Reserved, value of “0”

Redemption/Adjustment String
The data from the Preferred Customer Audit Log optionally can be appended to the
end of the foreground panel file EAMPANEL at the end of a reporting period. This
data is reformatted to match all other panel file data, but the content is the same as
the Preferred Customer Audit Log with the one exception that redemptions from the
registers are omitted. You can move this audit data into the old period panel file
instead of, or in addition to, moving it to the old period audit log file. This would
combine all information about preferred customer points history in the same file. If a
redemption occurs at the terminal, this information already has appeared in the
Panel file through a Bonus/Redemption points string and is not needed from the
Audit log. The redemption/adjustment strings in the panel file are the only indication
of redemptions or adjustments performed through the enrollment procedure.
Table 22. Redemption/Adjustment String
Field Name Type Length Description
STRING TYPE ASCII 2 Redemption/Adjustment string type of “82”
ACCOUNT ASCII v18 Customer account number
TRANTYPE ASCII 1 “R”= redemption, “A”= adjustment, “X”= rain check
DATETIME ASCII 10 Date and time of transaction (YYMMDDHHmm)
TERMINAL ASCII v3 “0”
TRANSACTION ASCII v4 “0”
OPERATOR ASCII v9 Operator/employee who performed transaction
POINTSP ASCII v8 Points adjusted/redeemed plus
POINTSM ASCII v8 Points adjusted/redeemed minus
SERIALNUM ASCII v6 Form serial number or store number for rain check
RESERVED ASCII 1 Reserved

Period Summary String

A period summary string optionally can be appended to the end of the foreground
panel file EAMPANEL at the end of a reporting period. This string contains the
Electronic Marketing totals reported in the Summary Cash Report. These totals
represent a summary for the accounting period. They are not necessarily a
summary for the Panel file data because filtering may have reduced the Panel file

Appendix A. Electronic Marketing Database 335

 to a subset of the accounting data. This summary record is provided to allow
validation of any process that summarizes the information in the panel file.
Table 23. Period Summary String
Field Name Type Length Description
STRING TYPE ASCII 2 Period Summary string type of “83”
TOTLCNT ASCII v9 Number of sales transactions
TOTLAMT ASCII v9 Total sales amount
PCUSCNT ASCII v9 Number of preferred customer transactions
PCUSAMT ASCII v9 Total amount sold to preferred customers
PCCPCNTS ASCII v9 Preferred customer coupon count
PCCPAMT ASCII v9 Preferred customer coupon amount
ITEMPTS ASCII v9 Points given for item sales during period
BONSPTS ASCII v9 Bonus points given during period
REDMPTS ASCII v9 Points redeemed during period
AMFRCPN ASCII v9 Automatic (paperless) manufacturer coupon amount
ASTRCPN ASCII v9 Automatic (paperless) store coupon amount

The net sales for preferred customers is the sum of the gross plus and gross minus
amounts in all transaction header records that are marked for preferred customers.
The transaction count should match the number of these records. The same totals
for all sales transaction header strings should give the total sales amount and
transaction count if data is kept for regular customers. The preferred coupon count
and amount reflect the sum of all coupon records with UPC codes within the
preferred customer coupon range. The point totals reflect the sum of the points from
all preferred customer transaction data strings (see 333). The automatic coupon
totals reflect the sum of paperless coupons from all automatic coupon transaction
data strings (see 332). If there are no paper preferred coupons, and automatic
coupons are given only to preferred customers, the automatic coupon totals should
match the preferred customer coupon total.

Panel Filter File (EAMFBFLT)

Filename: EAMFBFLT,EAMFBFLx
I/O Session: 29
Organization: Sequential File Copies: 0 to 10
Record Length: Variable Distribution class: Compound

The Panel Diary File is a reformatted subset of the Transaction Summary Log data
that normally contains all data from sales transactions for all preferred customers or
for all customers. This data includes a nearly complete record of each transaction
and is frequently more extensive than necessary. A panel filtering function is
provided to allow some of the excess information to be culled from the file. The
panel filter is intended to provide the following three functions:
v The ability to reduce the size of the panel file and increase manageability by
deleting selected data that is not needed
v The ability to delete from the panel data all information for selected items,
manufacturers, or departments
v The ability to create multiple copies of the panel data that contain different
subsets of the panel information.

336 Electronic Marketing PRPQ

The panel file contains about 3 million bytes for each 100,000.00 dollars of sales
data. If you decide to process this data initially at a department level rather than at
an item level, you can remove all item codes to reduce the size of this data by
about 20%. You can achieve large savings by removing other information such as
coupon family codes, taxes, and tenders if this information is not needed for
preferred customer purchase history analysis. Reducing the contents and the size
of the panel file reduces the cost of transmitting, storing, and analyzing its
information.

The panel data may be valuable to entities outside the enterprise, such as
manufacturers. But, you might not want to provide all information on sales and
customers to outside entities. By filtering the data, you can provide a manufacturer
detailed information on who is buying his products without showing the prices at
which the products were purchased. Likewise you may want to sell information on
what types of customers are buying what types of products, excluding all data on
sales from a specialty department or on house brands. By allowing the panel data
to be reduced in the store to selected classes of items, the filter function reduces
the effort and cost of selling subsets of purchase history data.

The panel filtering function provides for the creation in the store of multiple
variations on the panel data. For example, you may create one subset of the panel
data for promotion planning and analysis, create another set of this data to sell to a
marketing research company, and create a third subset to give to suppliers in
exchange for additional participation in promotions. The filtering function can
provide access to some of these functions at an earlier date and at a lower cost.

User-created panel filter files activate this filter function and provide the selection of
information that is to be filtered out of the panel data.

There are ten possible panel diary filter files ([Link] and [Link]
through [Link]) that activate and define filtering for the ten possible
output panel files ([Link] and [Link] through
[Link]). You must create, initialize, and place each of these filter files, as
needed, on ADX_IDT1 as a compound file.

The presence of [Link] defines the need for filtering of the data at the
moment that it is put into [Link] by checkout support processing.

The presence of any [Link] files (where x is a number from one to nine)
defines the need for background filtering and creation of the associated
[Link] output file. This background filtering is accomplished by an
independent background task that runs against the previous period Transaction
Summary Log file after a store close. As background filtering runs against a single
previous period Transaction Summary Log file, the selection of this filtering (through
the creation of a filter file) requires that all previous period transaction information
be in a single Transaction Summary Log file.

There can be up to ten independent filtering processes, one real time and nine
background tasks at store closing, based upon the presence of filter files and of
available background tasks to process the filter files. The selection of any of these
filtering processes and, by extension, of the associated filtered output data is made
independently by the presence of a filter file.

In order to understand the output of the filtering process, you must first understand
the Transaction Summary Log data that is the input to the filter and the Panel Diary
data as it appears without filtering. The Transaction Summary Log contains records

Appendix A. Electronic Marketing Database 337

 that represent transactions such as strings (fields) that represent item sales or
tenders, and substrings that represent individual data elements such as item codes
or prices. (For more information, see Appendix A in the IBM 4680 Supermarket
Application: Programming Guide ).

The data types in the Transaction Summary Log file are delimited as follows:
Records Delimited by carriage return/line feed (X'0D0A')
Strings Bounded by quotes
Delimited by commas X'222C22' = “,”)
Substrings Delimited by colons (X'3A' = :).

The Panel Diary file contains the host format of strings types zero through 11 from
the Transaction Summary Log. The delimiters in the panel file are all the same as in
the Transaction Summary Log, but the packed numeric data is converted to ASCII
numeric data and the flag data is converted to the ASCII representation of the HEX
value of the data. The filtering function deletes selected substrings by nulling out
the data and leaving the delimiters. Selected strings or records are filtered out by
nulling out the string or record and any associated delimiters. The nature of this
filtering process should allow any program that processes the panel data to run
successfully whether or not the panel data has data removed through filtering. The
filtering process only removes data from the associated Panel file. It does not add
data to the file, or merge or summarize data in the file.

Filter input data consists of ASCII strings that are images of the panel data strings.
For example, a filter input string of:
“01:itemcode:price:dept:XXfamily:flag1:flag2:flag3”

represents the item entry string type 01 and indicates to delete the coupon family
code field. Each filter string is a separate record in the filter file and must be
delimited from other records by a carriage return/line feed. Each filter record relates
to a single input string type and is used only to process that string type. If the first
two characters of a filter record are not the numeric value for a string type of 00
through 11, the record is ignored as a comment record. If no filter record applies to
a given input string, the input string is formatted for the panel file without filtering.

There can be multiple active filter records for each string type. Multiple filter records
for the same string type exist only when a key field is used to distinguish a
particular range of data to which a filter record applies. The order of the filter
records is important because only the first filter record that applies to a given input
string is used to filter that string. Up to 125 different active filter records can be
used to define the needed filtering requirements. Upper and lower case is
equivalent in all filter records.

The only characters in a filter record, other than the string type, that are actually
processed are the following key strings: “:”, “:XX”, “:ZZ”, “KK:”, and “KEY”. All other
filter record input is for documentation only. The characters that are processed have
the following meaning:
Colons Denote field delimiters in a filter string just as in an actual data
string.
:XX Denotes fields to be filtered. These fields are nulled and the
delimiting colons remain. If all fields given in the filter record for a
given string type are marked to be discarded, the entire string is
discarded. The number of fields given in a filter record need not

338 Electronic Marketing PRPQ

 match the number of fields in the actual data string. Up to 16 fields
beyond the string type can be defined in any filter record.
:ZZ Denotes strings whose presence implies that the entire transaction
is to be filtered out of the panel data. If the filter record that applies
to a given input string contains no “:XX” or “:ZZ”, the string is
processed without filtering.
For example, a filter record of
“01:itemcode:price:dept:XXfamily:XXflag:flag2:flag3” is the same as
a filter record of “[Link]XX:XX” in that it indicates to delete the fourth
and fifth substrings after the string type from an item entry string.
A filter record of “07:XX” is the same as a filter record of
“07:XXtaxa:XXtaxb:XXtaxc:XXtaxd:
XXsalesa:XXsalesb:XXsalesc:XXsalesd” in that it indicates to delete
all type seven tax strings.
A filter record of “05:type:tender:fee:account:status” is a comment
that indicates to not filter a tender string and that may be omitted
without changing the effect.
A filter record of “10:ZZoverride:reason” indicates to delete any
transaction containing a manager’s override string.
KK: Denotes a key field to be used to determine whether the filter
record applies to a given input string. Only one key field can be
designated in a filter record, and it is valid only if valid key data is
given.
Key Data is designated by the keyword “KEY” followed by key data and
it is valid only if a key field is designated through “KK:”. Key data
can have the following forms:
KEY = nn KEY = nn—nnn where nn is numeric data
KEY NE nn KEY NE nn—nnn
KEY = xxH KEY = xxH—xxxH where xx is hex data
KEY NE xxH KEY NE xxH—xxxH or {:;<=>?} = {ACDEF}
KEY = nn ON KEY = xxH ON all designated flags on
KEY = nn OFF KEY = xxH OFF all designated flags off
KEY = xxP KEY NE xxP where xx is the packed
contents of a single byte

Note: Blanks in the key data are optional, but either a blank or an “–” should
separate the two data fields when a range is provided. The “=” is also
optional. The key data is matched against the packed input data from the
TLOG rather than the ASCII data in the panel file. This leads to the packed
designation shown as “xxP” above to distinguish a sub-field value of X'FF'
from a numerically equivalent sub-field value of X'0255'.

The value of any packed numeric data in the TLOG is taken as the value of the
unpacked digits. A department number field in the TLOG may contain a value of
X'0123', this would be isolated by a key value of 123 or of 7BH rather than 123H.
As the key field designator must end with a colon, an additional field might be
needed in the filter input when a record is deleted based on the contents of the last
field in the record. In this case, the filter record ends with “:XXlastKK:XXdummy”
instead of “:XXlastKK”. If a type one item string is discarded based on input key
criteria, any associated item extension is also discarded.

Sample usages of the key field in a filter record are as follows:

Appendix A. Electronic Marketing Database 339

 01:XX:XX:XX:XX:XX:XX:XXKK:XX KEY = 10 - 59
Drop deposits, deposit returns, refunds, and miscellaneous transaction item
01:XXitemcodeKK:XX:XX:XX:XX:XX:XX KEY=1234500000—1234599999
Drop items from manufacturer 12345

01:XX:XX:XXdeptKK:XX:XX:XX:XX KEY 123

Drop items from department 123

11:XXKK:XX KEY = ??P

Drop redundant customer number data entry strings

Comments can follow valid filter input in a filter record if an exclamation point
separates the comments from the data. For this reason, exclamation points are not
allowed in the filter data. A default filter file, shipped as [Link], reduces
the panel data by deleting fields that normally would not be needed for purchase
history analysis. This default file contains the following active records:
00:term:trans:time:type:strings:checker:0:total+:total−:XX
Drop performance timings from header

01:XX:XX:XX:XX:XX:XX:XXKK:XX KEY = 10—39

01:XX:XX:XX:XX:XX:XX:XXKK:XX KEY = 90—99
Drop deposits, deposit returns, refunds, and deposit cancels

01:itemcode:price:dept:XX:XX:flag2:flag3
Drop family codes and item record flags
02:XX:XX:XX:XX:XX:qty/wgt:flags
Drop item record pricing information

07:XX ! Drop tax

08:XX ! Drop tax refund
09:XX ! Drop change given
10:XX ! Drop manager’s overrides
11:XX:XXKK:XX KEY = ==P ! Drop coupon tracking data
11:XXKK:XX KEY = ??P ! Drop redundant customer number data

Targeted Coupon Messages File (EAMFBTCM)

Filename: EAMFBTCM I/O Session: 56
Organization: Keyed File Copies: 1 per controller
Record Length: 127 bytes Distribution class: Compound

The targeted coupon messages file is an optional keyed file which contains a record
for each targeted coupon for which the user wishes to provide message text. This
message text is optionally printed on the receipt tape of the customers who are
eligible for the targeted coupon along with information from the coupon item record.
Up to three print lines, each with 38 characters of free formatted text, can be
supplied for each targeted coupon to describe the promotion to the eligible
customers. All blank print lines will not be printed on the customer receipt. A record
with all blank text is the same as no record on file.

This file and its contents are created by the user procedure that is used to maintain
targeted coupon messages. The size of the file is determined by the UPC range
defined for targeted coupons. The message maintenance procedure provides the
ability to add, change, delete or report on all coupon messages. The only other
code which uses this file is the terminal code that prints the text on the receipt tape
of customers to whom the coupons are targeted. A copy of this optional input file is
kept on each controller so that each terminal can read the messages from its local
controller.

340 Electronic Marketing PRPQ

Table 24. Targeted Coupon Message File Record Format
Field Name Type Length Offset Description
COUPON NUM PD 2 0 Coupon number (linkage to coupon)
COUPON MSG ASCII 114 2 Coupon message text (3 38-char. lines)
RESERVED ASCII 11 116 Reserved

Item Record File Usage (EAMITEMR)

Filename: EAMITEMR I/O Session: 4
Organization: Keyed File Copies: 1 per controller
Record Length: 46 bytes Distribution class: Mirrored

The Item Record File is a Supermarket Application file. It is fully documented in

Appendix A of the IBM 4680 Supermarket Application: Programming Guide The
preferred customer processing makes special use of several fields in the item
record. These special uses of the item record for preferred customer processing are
described below.

Linked Coupons
The Item Record File provides the data base for electronic coupons. All of the tools
available to support item record maintenance are also available to support
electronic coupons.

In order for coupons (discounts) to be given automatically to preferred customers,

item records for these coupons must be created. These records must be created
with item codes in the range defined in the preferred customer options (see
“Coupon Velocity Code Range for Preferred Customers” on page 97) and they must
be defined as coupons. Electronic coupons can be defined as store or manufacturer
coupons, depending on the source of the promotional funds and consequent
taxability of the coupon. The items to which the discounts apply must be linked to
the electronic coupon records.

This linkage between the promotional items and the electronic coupons is
processed only for preferred customers. In order to give the coupon to all
customers, you can link an item to a coupon outside the range of item codes for
preferred customers. The actual UPC used as the key to the linked coupon record
can be displaced from the coupon range by an option that appends digits to the
linked UPC code (see “UPC Displacement for Preferred Customer Linked Items” on
page 79). This allows the four-digit UPCs to be used for velocity-coded items such
as produce. But the displaced items cannot be linked to another item.

If you want a customer to receive only one coupon regardless of the number of
items he/she buys, you can set the flag in the coupon item record to prohibit the
entry of quantity (see 348).

If coupon validation is selected, the item records for the automatic coupons must
contain all of the additional data available for coupons through the Coupon
Processing Enhancements. This includes such data as the manufacturer number of
the item(s) for the coupon, the number of items needed for the coupon, the number
of coupons available per customer, and the minimum purchase amount required to
receive the coupon.

Appendix A. Electronic Marketing Database 341

 Linked Alias Coupons
Electronic coupons may be used to automatically give preferred customers the
benefit of any outstanding store coupons. You can link a promotional item to a
coupon record that is an alias record for a normal store coupon record. This solves
the problem of the difference in length between linked UPCs, that are only four
digits, and scannable store coupons, that often use longer UPC numbers. The
promotional item is linked to an item code in the coupon velocity code range for
preferred customers. This record in turn contains as an alias item code the full item
code used by the store coupon. To obtain item movement separately on the alias
electronic coupon and on the normal store coupon, the alias record must be flagged
for no movement and the normal store coupon must be flagged for movement. The
descriptor in the alias record is used for automatic redemption of the coupon and
the descriptor in the store coupon record is used when the coupon is redeemed
through normal entry of the store coupon UPC.

Coupon Quantity Limit

When a preferred customer shows identification at the end of a transaction, all
applicable coupons are automatically processed. If the customer has purchased
more than one of an item to which a coupon applies, you can limit him/her to only
one of these coupons per transaction by setting the “Quantity Not Allowed” flag in
the coupon item record (see 348). With this flag set, only one of each coupon is
presented at customer identification regardless of how many items were purchased.
If a promotional item is entered after customer identification and is entered with a
quantity, this same processing of the “Quantity Not Allowed” flag will result in only
one coupon for the several items.

If multiple, like, promotional items are entered singly after customer identification, a
customer receives one coupon per entry because the quantity is one in each case.
In order to limit the customer, in all cases, to a certain number of like coupons per
transaction, the Lmt/Tran flag can be used to define a limit per transaction for each
electronic coupon. For more information, see “Limit of Like Coupons in a
Transaction” on page 24. This limit is strictly enforced regardless of when or how
the promotional items and customer number are entered.

Coupon Weight Limit

Coupons can be defined which reduce the price per pound on promotional weight
items. These weight required coupons can be used on random weight items (UPC
category 2) as well as on items that are weighed at the point of sale. The value in
the coupon item record is the discount per pound. These weight required coupons
can be paper coupons, non-preferred or preferred electronic coupons, or even
targeted coupons. If a weighted coupon applies to multiple weight items, then it is
not apparent whether the discount should be applied to the total weight or the
largest package. If the “Quantity not Allowed” flag is set in the item record for a
weight required coupon, then the discount is applied only to the largest package
sold at the time the customer is identified as a preferred customer. If this flag is not
set, then the discount will be applied to the sum of the weights for all of the
matching promotional weight items.

As with non-weight coupons, the Coupon Processing Enhancements can be used to

limit the number of like, weight-required coupons to be accepted in a transaction. If
this function is used to limit a weight coupon to one per customer, the “Quantity Not
Allowed” flag must be set in the coupon to assure that the coupon is applied to the
largest package when a customer shows identification at the end of the transaction.
If a customer shows identification at the start of the transaction and this limit is set,
the size of the discount depends upon the order in which the promotional weight
items are entered.

342 Electronic Marketing PRPQ

Note: Promotional weight items may also be linked to non-weight coupons to
achieve a fixed discount that is independent of the weight of the item.

Weight Items
The Supermarket Application accumulates weight, dollar value, and package count
movement for most weight items, but does not accumulate weight movement for
weight items sold with only a keyed price or sold using a category two (random
weight) UPC code. Because the preferred customer program needs to compute the
weight for such sales to apply a weight coupon, this function is used to update the
weight movement when possible. The package weight for a random weight item
containing a nonzero price per pound in the item record is computed as the UPC
price divided by the price per pound. This package weight is used to calculate the
discount for a weight-required coupon and also to update item movement totals.
The item records for all category two item codes must contain the correct price per
pound or no price at all.

Items Not Eligible for Points

Points are normally accumulated based on the value of all sales. But the awarding
of points for certain items may be unwanted or even illegal. The trading stamp flag
in the item record is used to define those items for which points may (or may not)
be accumulated. If an item is marked as eligible for trading stamps, it is eligible for
points. If it is marked as not eligible for trading stamps, it is not eligible for points.
This flag pertains to all items except for coupons. You can define whether coupons
reduce points through personalization options (see “Store Coupons Reduce Points”
on page 87). A trading stamp program may be used with the preferred customer
program, but this would normally be prohibited by setting the trading stamp rate to
zero.

Points-Only Items
Bit 5 in IR.INDICAT1A (Reserved flag X'20') distinguishes points-only items. These
items (or coupons) have no monetary value, but contribute to or reduce preferred
customer points. The number of points associated with the item is in the price field.
A normal item with this flag on provides bonus points to a customer. A coupon item
with this flag on can either provide bonus points or require the redemption of points.
The number of points that apply to a coupon are restricted to five digits because the
price field for a coupon is restricted to five digits. The difference between a
points-only item and a points-only coupon is that the coupon requires validation and
requires the prior purchase of a matching item.

New accounting totals for the amount of redeemed and bonus points are
accumulated by operator and/or terminal. Item movement totals for points-only
items can be maintained at the discretion of the user. Sales of points-only items can
be logged in the exception file. The sale of a points-only item may affect item
movement totals but does not influence any other transaction totals, including
department totals and net sales accounting totals. Point coupons are not tracked in
the coupon tracking file. The displays and prints for a points-only item are uniquely
formatted and marked so that they can be distinguished from normal sales.

Points-only items apply only to preferred customers. It is suggested, but not

required, that these items use item codes within the unique preferred customer
range (300 to 399), particularly when points-only items are linked to other items. But
preferred customer item codes may not be appropriate when used for items such as
scannable paper coupons. If a points-only item is accepted for a customer who has
not been identified as a preferred customer, the operator is prompted at the entry of
the first tender to either enter the customer’s ID number or void the points item.

Appendix A. Electronic Marketing Database 343

 Bonus Coupons
A points-only coupon is selected as a bonus points coupon through a second item
record flag that is interpreted uniquely for points-only coupons. A bonus item
provides points without coupon validation. A bonus coupon requires validation
against the sale of an item. When either a bonus item or a bonus coupon is sold or
tendered, a customer is awarded positive bonus points. Promotional items can be
linked, through preferred customer item codes, to bonus items. This provides bonus
points to preferred customers who purchase the items. Bonus item vouchers can be
printed (perhaps by using scannable UPC codes) and used as nonspecific awards
to compensate a preferred customer for grievances or to promote shopping on
selected days of the week. Bonus coupons that require the purchase of specific
items can be distributed to all preferred customers or to selected preferred
customers, or can be electronically targeted to selected preferred customers. If a
transaction ends with a negative amount of bonus points from cancels, the bonus
points are not processed.

Redemption Coupons
The discount flag (INDICAT1, bit 1, reserved flag X'20', of the item record file) for a
points-only coupon defines whether the coupon provides bonus points or requires
the redemption of points. This flag is interpreted uniquely only for a points-only
coupon. In this case, a flag setting of zero denotes positive (bonus) points while a
flag setting of one denotes negative (redeemed) points. After this flag is uniquely
interpreted for a points only coupon, it is set to one to prevent the coupon from
contributing to discountable totals.

Links to Deposit
Bit four in IR.INDICAT1A (Reserved flag x “10”) is used to distinguish items that are
linked both to a deposit and to electronic coupons. In this case, the coupon or
coupons are linked to the item and the deposit for that item is linked to the last
coupon in the chain. If this flag is turned on in the first item in the chain, the deposit
on the item is always charged, regardless of whether the coupon chain is broken
through a failed validation. This flag is generally used only for marking items that
link to deposits, but it can be used to mark any item that links first to a coupon and
then to a non-coupon to assure that the link between the item and the non-coupon
is preserved whether or not the coupon is accepted. This flag has a different
meaning in any item record that is defined as a coupon.

Coupons that Require Separate Minimum Purchase Amounts

Bit 4 in IR.INDICAT1A (Reserved flag X'10') is used to distinguish coupons which
require separate sales to satisfy the minimum purchase requirement for each usage
of the coupon in a transaction. This flag has meaning only for coupons that have a
minimum purchase requirement. If this flag is set in a coupon with a $10.00
minimum purchase amount, then a customer must have $20.00 of purchases to
redeem two of the same coupons in an order. Note that the same purchases can be
used to satisfy the minimum purchase requirements for any two different coupons
regardless of this flag. Coupons are considered different if they reference separate
item records.

Pricing Method 4 “Net Value” and “Percent Off” Coupons

While many coupons created for electronic marketing use pricing method 3 to allow
for entry of an associated manufacturer number, pricing method 4 can also be used
to associate a manufacturer number with a coupon and to define “net value” or
“percent off” coupons. For a net value coupon, the price in the coupon record is the
reduced or net value of the item after the coupon is applied. A pricing method 4
coupon with a price of .49 says to discount the matching items down to .49 rather
than to reduce the matching item’s value by .49. A coupon with a net value of .49
will give .51 off on a 1.00 item and .45 off on a .94 item. These net value coupons

344 Electronic Marketing PRPQ

are particularly useful for discounting a large set of items down to a common value
when all of the items retail for about the same value. A pricing method 4 coupon
with a price in the coupon record of 99xxx or 98xxx denotes a “percent off” coupon
which is to discount the matching items by xx.x%. Thus a coupon for 10% off is
specified using pricing method 4 and a price of 98100 or 99100. A coupon for 1/3
off would be defined with a price of 98333 or 99333. Pricing method 4 coupons are
never doubled.

“Percent off” coupons can be specified with a price of 98xxx or 99xxx where 98xxx
says to apply the discount to all matching items and 99xxx says to limit the discount
to those items that link to the coupon. For coupons which are linked to items, the
user must decide whether the coupon should apply to only the linked items or to
any items which match through coupon validation. If a coupon is set to apply to
matching items through a 98xxx percent and the coupon does not validate at any
level, then the discount is applied to the total order. Paper or targeted “percent off”
coupons can use either 98xxx or 99xxx as long as validation information is supplied
to isolate the matching items. A paper coupon using 99xxx which bypasses
validation will prompt for a value to discount while an equivalent targeted coupon
will be ignored. “Percent off” coupons can be created to apply to the transaction
total, the total for a department or a department subtotal group, all items from a
manufacturer, or any set of items defined by a department and family, manufacturer
and family, promotion code, or coupon linkage. Note that there is no way to require
a separate minimum purchase for each item discounted by a “percent off” coupon.

The unique aspect of all pricing method 4 coupons is that they need the value of
the matching item(s) in order to determine the value of the discount. This is very
simple when the coupon is linked to the item and is available immediately after the
sale. In this case, the coupon discounts the value of the item which linked to it. This
is why pricing method 4 coupons should be linked only to matching items. The only
two exceptions to this rule are for weighted coupons linked to non-weighted items
and for “percent off” coupons specified with a price of 98xxx. These two types of
coupons will find the value of the matching item(s) while all others will use the value
of the linked item. These exceptions allow weighted net value and “percent off”
coupons to be more easily used in cross item promotions such as “chicken legs for
.19 a pound with the purchase of brand X barbecue sauce” or “10% off all dairy
items with the purchase of a turkey”. When linked pricing method 4 coupons are
delayed because of a minimum purchase requirement, a cross promotional
requirement, or because they are available only to preferred customers and the
customer ID is entered at the end of the order, then only the total value and count
of matching items is saved. If the discount is for a limited number of items, then
based upon the level of coupon validation, the discount is applied either to the
average item value or the largest matching item value. This leads to limitations on
pricing method 4 coupons when only a limited number (more than one) are
available in an order and the discounted items vary in value.

Paper or targeted pricing method 4 coupons must use coupon validation to find the
value of the matching items. Since the only values found are the largest and the
total, net value coupons should usually be limited to only one item if the item values
vary. Paper or targeted “percent off” coupons can be limited to the single largest
item or can be applied to all items. Since “percent off” coupons are expected to be
used on items with different values, the system will assume that a coupon for
multiple items should discount the matching total rather than a multiple of the
largest matching value. In some cases this requires that limits on the amount of
items to be discounted are manually enforced. Thus a targeted coupon for 20% off

Appendix A. Electronic Marketing Database 345

 on beef can either apply to the largest package or to all packages purchased in the
order. Limiting such a coupon to five packages or to 20 pounds must be done
manually.

Summary of Item Record Changes for Coupons

The following information is added to the item record file for coupon item records.
As this information will be used only for coupon item records, the fields used to
contain the data can be used for normal purposes in all other item records.
Manufacturer number for validation (5 digits)
Minimum purchase amount (-1 to 327.67)
Sequence number (0 to 20)
Number allowed per transaction (0 to 9) (0 = 1) for STR coupons
(0 = 99) for MFR coupons
(9 = 99) for STR coupons
Items required for coupon (0 to 9) (0 = 1)

Flags: Redemption item excluded from minimum purchase amount (1 bit)

Minimum purchase amount applies only to manufacturer (1 bit)
Minimum purchase amount applies only to department (1 bit)
Coupon is validated only against like coupons by quantity (1 bit)
Compute coupon value to yield given net item value (1 bit)
Validate coupon by department if no manufacturer present (1 bit)

This data is distributed across the following fields:

High half of price field (MFR number)

Multi-pricing group number (sequence)
Sale quantity (trans limit times 10 + items per coupon)
User field 2 (minimum purchase amount)
Trading stamp flag (item excluded from purchase minimum)
Tax C flag (minimum purchase by manufacturer) -or-
(validate by dept if no manufacturer)
Tax D flag (minimum purchase by department)
Reserved flag 2 (X'20') (validate like coupons by quantity)
Pricing method (pricing method 4 implies net value given)

Coupons are always unit-priced to accommodate this use of the pricing fields. In
order to maintain this data, the pricing method for coupons is set to three or four
even though the pricing method is not used. This is not true if the manufacturer
number is not supported in the item file. Support of the sequence number is
optional, and the defaults are one coupon per transaction, one item per coupon,
and no minimum purchase amount. If the trading stamps allowed flag is on, the
item value is excluded from the minimum purchase amount. Coupons are always
treated as though trading stamps apply. If no minimum purchase amount is
specified, then the Tax C and Tax D flags are used as normal tax indications. If a
minimum purchase amount is present, then the Tax D flag is used to require the
minimum purchase amount to be satisfied from the designated department and the
Tax C flag is used either to require the minimum purchase from the designated
manufacturer or to force department level validation, depending upon whether a
manufacturer number is provided in the item record. If a minimum purchase amount
is present, then the coupon is not taxable under tax plan C or tax plan D. If the
coupon must be taxable under tax plan C or D, then no minimum purchase amount
can be specified. If validation by department is needed and there is no minimum
purchase amount, then a minimum purchase amount of 1 (cent) can be specified to
enable the validation flag.

Allow Coupon Validation by Department with Minimum Purchase by

Transaction
To enable this feature the Minimum by MFR flag of coupon record should be set to
yes and the MFR field of the coupon record set to 00000. This will force department

346 Electronic Marketing PRPQ

 not MFR validation. The minimum purchase field should have the desired minimum
purchase amount entered in it. Finally the Minimum by Dept flag should be set to
no.

Allow Minimum Purchase by Department with No Coupon Validation

To enable this feature the Minimum by MFR flag of coupon record should be set to
no and the MFR field of the coupon record set to 00000. This will force neither
department nor MFR validation. The minimum purchase field should have the
desired minimum purchase amount entered in it. Finally the Minimum by Dept flag
should be set to Yes to indicate that the minimum applies only to the coupon’s
department.

Allow Minimum Purchase by Department with Validation by MFR

To enable this feature the Minimum by MFR flag of coupon record should be set to
no and the MFR field of the coupon record set to the valid manufacturer. This will
force validation by manufacturer. The minimum purchase field should have the
desired minimum purchase amount entered in it. Finally the Minimum by Dept flag
should be set to Yes to indicate that the minimum applies only to the coupon’s
department.

The table on the following page defines the relationship between the coupon record
inputs and the coupon validation and minimum purchase requirements.

INPUTS RESULTS
Minimum Non-zero MFR in Tax C Min by Tax D Coupon Minimum
Purchase > 0 ** Record MFR or Validate Minimum by Validation Purchase
Dept Dept Required
No No N/A N/A None *** None
No No N/A N/A None *** None
No Yes N/A N/A By MFR None
Yes No No No None *** For Order
Yes No No Yes None *** For Dept
Yes No Yes No By Dept For Order
Yes No Yes Yes By Dept For Dept
Yes Yes No No By MFR For Order
Yes Yes No Yes By MFR For Dept
Yes Yes Yes No By MFR For MFR
Yes Yes Yes Yes By MFR For MFR
Note: ** A minimum purchase amount of .01 is adequate to meet this requirement. *** Validation will be by
department if the option “ALL COUPONS REQUIRE AT LEAST DEPARTMENT LEVEL VALIDATION” is
selected.

Only a single character sequence number can exist in a coupon UPC and the range
of sequence numbers in the item record is zero through 20. The following table
must be used to determine the meanings of item record sequence numbers outside
of the zero through 9 range.
Item Record Valid UPC Manager can override
Sequence number Sequence number Sequence number mismatch

0 Any n/a
1 1 (or 0) NO

Appendix A. Electronic Marketing Database 347

 2 1 (or 0) NO
3 1 (or 0) NO
4 1 (or 0) NO
5 1 (or 0) NO
6 1 (or 0) NO
7 1 (or 0) NO
8 1 (or 0) NO
9 9 (or 0) NO
10 0 NO
11 1 (or 0) YES
12 1 (or 0) YES
13 1 (or 0) YES
14 1 (or 0) YES
15 1 (or 0) YES
16 1 (or 0) YES
17 1 (or 0) YES
18 1 (or 0) YES
19 9 (or 0) YES
20 0 YES

Field Name Type Length Offset Description

ITEMCODE PD 6 0 Item code – right justified with leading zeroes
INDICAT0 INT 1 6
Bit 7–:hex.80:ehex. =
Quantity not allowed
Bit 6–X'40' =
Weight or price required; item is sold by weight
Bit 5–X'20' =
Quantity required
Bit 4–X'10' =
Price required
Bit 3–X'08' =
Item sale is exception logged
Bit 2–X'04' =
Item is not authorized for sale
Bit 1–X'02' =
Item not authorized for sale during restricted
hours
Bit 0–X'01' =
No item movement kept

348 Electronic Marketing PRPQ

Field Name Type Length Offset Description
INDICAT1 INT 1 7
Bit 7–X'80' =
Tax plan A applies to item
Bit 6–X'40' =
Tax plan B applies to item
Bit 5–X'20' =
For Electronic Marketing coupon item records:
minimum purchase by manufacturer; for all
other item records: Tax plan C applies to item
Bit 4–X'10' =
For Electronic Marketing coupon item records:
minimum purchase by department. For all
other item records: Tax plan D applies to item
Bit 3–X'08' =
Food stamp item
Bit 2–X'04' =
For Electronic Marketing coupon item records:
item excluded from purchase minimum; for all
other item records: points apply to item
Bit 1–X'02' =
For Electronic Marketing points items:
redemption Item; for all other item records:
non-discountable item
Bit 0–X'01' =
Coupon value multiplication not allowed on this
item

INDICAT1A INT 1 8
Bit 7–X'80' =
No shelf label printed in store
Bit 6–X'40' =
Reserved
Bit 5–X'20' =
For Electronic Marketing: point item. For all
other item records: reserved
Bit 4–X'10' =
For Electronic Marketing coupon item records:
separate minimum per coupon. For all other
item records: links to deposit
Bit 3–X'08' =
User flag 1
Bit 2–X'04' =
User flag 2
Bit 1–X'02' =
User flag 3
Bit 0–X'01' =
User flag 4

Appendix A. Electronic Marketing Database 349

Field Name Type Length Offset Description
INDICAT2 PD 1 9 X'TP' where T is type and P is pricing method
T=0 Normal item sale
T=1 Deposit
T=2 Refund
T=3 Deposit return
T=4 Misc. trans. receipt (sale)
T=5 Misc. trans. payout (refund)
T=6 Manufacturer coupon
T=7 Store coupon
T=8 Reserved
T=9 Reserved
P=0 Unit or split package pricing
P=1 Base + 1 pricing
P=2 Group threshold pricing
P=3 Reduced deal pricing
P=4 Increased deal pricing
P=5 Pricing data is in another record. The item code
for this record is in the six bytes starting at
SALEQUAN.
P>5 Reserved
NOTE: For Electronic Marketing, a pricing method of
four (4) in a coupon item record implies that the value
of the coupon will be calculated to yield a net price of
the value in the price field.
DEPARTME PD 2 10 Department number (value 1—999)
FAMILYNU PD 1.5 12 Coupon family number. A coupon with an equal Family
(CURRENT) number can be applied to this item. (Value 0—999) or
Miscellaneous account number from which the item
amount is added if this is a miscellaneous item. (Value
0—999, where 0 implies no update.)
FAMILYNU PD 1.5 13.5 Coupon family number. A coupon with an equal Family
(PREVIOUS) number can be applied to this item. (Value 0—999) or
Miscellaneous account number from which the item
amount is subtracted if this is a miscellaneous item. (Value
0—999, where 0 implies no update.)
MPGROUP PD 1 15 Multipricing group number / Mix-and-match number when a
combination of items comprise a deal. (Value 0—99, where
0 = mix only with self.) NOTE: For Electronic Marketing
coupon item records, this field contains the coupon
sequence number.
SALEQUAN PD 1 16 Count or weight of items in the deal. (Whole units only, no
fractional weights.) (Value 0—99, where 0 is equivalent to
1.) NOTE: For Electronic Marketing coupon item
records, this field contains both the maximum number
of this coupon per transaction (x) and the number of
matching items required to validate this coupon (y)
according to the equation (x*10) + y.

350 Electronic Marketing PRPQ

Field Name Type Length Offset Description
SALEPRIC PD 5 17 Pricing method 0 or 1: format 00pppppppp Where:
pppppppp
= unit price if SALEQUAN = 0 or 1
= deal price if SALEQUAN > 1
Pricing method 2: format pppppsssss Where:
v ppppp = package deal price
v sssss = single unit price
Pricing method 3 or 4: format uuuuurrrrr Where:
v uuuuu = unit price
v rrrrr = reduced price
NOTE: For Electronic Marketing Coupon Item Records,
format mmmmmvvvvv where:
v mmmmm = manufacturer’s number for validation
v vvvvv = value of coupon
LINKEDTO PD 2 22 Item code to be sold with the sale of this item. (Value
0—9999, 0 = no linked item.)
ITEMNAME CHR 18 24 Item descriptor to be printed on receipt (no commas
allowed).
USEREXIT1 INT 2 42 User field for use with exits. NOTE: Optionally used by
promotion code
USEREXIT2 INT 2 44 User field for use with exits.
Note: For Electronic Marketing Coupon Item Records:
minimum purchase amount for coupon to be accepted. For
non-coupon optionally used by date of last sale.

Staged Item Movement File (EAMIMOV1)

Filename: EAMIMOV1 I/O Session: 4
Organization: Keyed File Copies: 1
Record Length: 18 Distribution class: Mirrored

The Staged Item Movement File is an optional output file that contains contents of
the keyed item movement file in a compressed sequential format. The store record
always precedes all data records for the same period and thereby delimits the
periods when multiple keyed files are staged into the same sequential file. The
records contain no internal field delimiters and there are no delimiters between the
records.

Record Format – Store Record

Table 25. Staged Item Movement File – Store Record
Field Name Type Length Description
ITEMCODE UPD 6 X'999999999999' for a store record
DATETIME UPD 5 Date and Time when period closed (YYMMDDHHmm)
RESERVED ASCII 7 Unused

Appendix A. Electronic Marketing Database 351

Record Format – Movement Record
Table 26. Staged Item Movement File - Movement Record
Field Name Type Length Description
ITEMCODE UPD 6 Item number
NUMITEMS BIN 4 Count of the number of items sold
AMTSALE BIN 4 Sum of the sale amount for the items sold
WEIGHT BIN 4 Total weight of the items sold

An option determines whether the four-byte fields are in a binary format or in a PC

integer format. The only difference in these formats is in the order of the bytes. In
binary, the most significant byte comes first but in a PC integer format, the most
significant byte comes last.

Accounting File Usage (EAMACCTC)

The accounting file is a Supermarket Application file. This file is fully documented in
Appendix A of the IBM 4680 Supermarket Application: Programming Guide The
preferred customer processing accumulates new totals in the 72 bytes of space
reserved at the end of every record. The automatic coupon fields are the only ones
updated in the store office record.
Filename: EAMACCTC I/O Session: 12
Organization: Keyed File Copies: Current, Previous
Record Length: 508 bytes Distribution class: Mirrored
Table 27. Accounting File Usage
Field Name Type Length Offset Description
See Programming 0—10
Guide.
INDICAT0 INT 1 11 Bit 5—X'04' indicates a successful automatic pickup of
paperless coupons. Bit 6—X'02' indicates automatic
coupons have been counted in the current period.
See Programming 2—331
Guide.
AMTTAXSA INT 4 332 Amount of standalone taxes
RESERVED ASCII 36 336 Reserved
ITEMPTS INT 4 372 Points given for enrolled customer sales
BONUSPTS INT 4 376 Bonus points given to enrolled customers
REDEEMPTS INT 4 380 Points redeemed by enrolled customer
AUMFRAMT INT 4 384 Electronic MFR coupon amount
AUSTRAMT INT 4 388 Electronic STR coupon amount
DBCPNAMT INT 4 392 Double coupon amount
PFCUSAMT INT 4 396 Enrolled customer transaction amount
PFCUSCNT INT 2 400 Enrolled customer transaction count
PFCPNCNT INT 2 402 Enrolled customer auto coupon count
PFCPNAMT INT 4 404 Enrolled customer auto coupon amount
USERINTS INT 60 408 Fifteen four-byte integers for exit use

352 Electronic Marketing PRPQ

Table 27. Accounting File Usage (continued)
Field Name Type Length Offset Description
USEREXIT ASCII 40 468 User field for use with exits

Performance File Usage (EAMPERFC)

The Operator Performance File is a Supermarket Application file. This file is fully
documented in Appendix A of the IBM 4680 Supermarket Application: Programming
Guide The preferred customer processing accumulates new totals in the 32 bytes of
space reserved at the end of every operator record.
Filename: EAMPERFC I/O Session: 33
Organization: Keyed File Copies: Current, Previous
Record Length: 508 bytes Distribution class: Mirrored
Table 28. Performance File Usage
Field Name Type Length Offset Description
See Programming 0—411
Guide.
AMTTAXSA INT 4 412 Amount of standalone taxes
RESERVED ASCII 8 416 Reserved
ITEMPTS INT 4 424 Points given for participating customer sales
BONUSPTS INT 4 428 Bonus points given to enrolled customers
REDEEMPTS INT 4 432 Points redeemed by enrolled customer
PFCUSAMT INT 4 436 Preferred customer transaction amount
PFCPNCNT INT 2 442 Preferred customer auto coupon count
PFCPNAMT INT 4 444 Preferred customer auto coupon amount
USERINTS INT 40 448 Ten four-byte integers for use with exits
USEREXIT ASCII 20 488 User field for use with exits

Department Totals File Usage (EAMDEPTC)

The Department Totals File is a Supermarket Application file. This file is fully
documented in Appendix A of the IBM 4680 Supermarket Application: Programming
Guide The preferred customer processing can optionally use the five user exits
fields for coupon totals. See the option “KEEP AUTOMATIC COUPON TOTALS IN
DEPARTMENT FILE EXIT FIELDS” for a fuller explanation of this use of these
fields.
Filename: EAMDEPTC I/O Session: 50
Organization: Direct File Copies: Current, Previous
Record Length: 512 bytes Distribution class: Mirrored
Table 29. Department File Usage
Field Name Type Length Offset Description
See Programming 0—71
Guide.
USEREXIT INT 20 72 Five four-byte fields for use with exits

Appendix A. Electronic Marketing Database 353

Exception Log Usage (EAMEXCPT)
The Exception Log File is a sequential log file that contains entries describing
exceptional user actions that impact totals or security. This file is created and
maintained by the Supermarket Application. Only new “19” and “99” records are
added by the Electronic Marketing enhancements.
Filename: EAMEXCPT I/O Session: 21
Organization: Sequential File Copies: Current, Old
Record Length: Variable Distribution class: Mirrored

User Log of Data Entry = X'19' (Customer number seen multiple times)
Table 30. Exception Log entry = X'19'
Field Name Type Length Offset Description
TERMINAL PD 2 0 Terminal number
TRANSNUM PD 2 2 Transaction number
DATETIME PD 5 4 Date and time of transaction (YYMMDDHHmm)
CODE PD 1 9 Type of exception log entry (value = X'19')
OPERATOR PD v5 10 Operator number
CUSTOMER PD 9 10+v5 Customer account number
POINTS ASCII v9 Points for this transaction
COUPONS ASCII v5 Value of automatic coupons for this transaction

This entry is logged for the second and any subsequent use of the same customer
number at the same store during the same day. It is also logged for all uses of the
rain check ID as defined in the preferred customer options (see “Rain check ID
Definition” on page 78). This entry is intended to help in the detection of fraudulent
use of customer cards.

Addition to 02 and 03 Log Entries

Discounts or tender exceptions which are exception logged for Preferred Customers
will include the Preferred Customer number in the user exit portion of the 02 or 03
type exception log entries.

User Log = X'99' (Transfer activity file processed)

Table 31. Exception Log entry = X'99'
Field Name Type Length Offset Description
TERMINAL PD 2 0 Terminal number
TRANSNUM PD 2 2 Transaction number
DATETIME PD 5 4 Date and time of transaction (YYMMDDHHmm)
CODE PD 1 9 Type of exception log entry (value = X'19')
OPERATOR PD 0 10 Operator number = “ ”. Null field.
FILE NAME ASCII 8 10 Input file name
RECORDS ASCII v5 18 Number of valid records in the input file

354 Electronic Marketing PRPQ

Table 31. Exception Log entry = X'99' (continued)
Field Name Type Length Offset Description
UPDATES ASCII v5 Number of records transferred
STATUS ASCII 3 “ERR” if errors logged, otherwise “OK”

This entry is logged each time that an input transfer file is processed.

System Error Log Usage

The System Error Log is a file maintained by the operating system and accessed by
the applications through the ADXERROR function. The data placed in the log by the
applications is viewed through the operating system Error Log Scan procedure. This
data is accessed from the main menu through the key sequence 6, ENTER, 1,
ENTER, 6, ENTER, ENTER. The preferred customer package is consistent with the
Supermarket Application in the format of the entries that it places in the log. The
only data unique to these applications is the session number usage, described as
follows:
Table 32. Preferred Customer Session Number Usage
Session
Number File name Module Where Used
1 Customer Enrollment File EAMFBCUS * EN
2 Customer Enrollment Change EAMFBCHG * EN
File
6 Report Descriptors File EAMEDESC * RP
8 Options/Messages files EAMFBOPT * CS * TS
EAMFBMSG
9 Redemption/Adjustment Audit EAMFBAUD * CS
File
11 Activity Transfer File EAMXssss * CS
20 Sales Descriptors EAMSDESC * TS
23 Coupon Tracking Log EAMCOUPC * CS
24 Panel Diary File EAMPANEX * CS
29 Panel Filter file EAMFBFLT * CS
36 Old period totals files EAMPANEL * CS * CS * CS
EAMFBAUO
EAMCOUPO
54 Customer Transfer File EAMFBXFR * CS, * TS
55 Customer Activity File EAMFBACT * CS
56 Targeted Coupon Messages EAMFBTCM * TS
File
63 Customer Previous Activity EAMFBAPP * CS
File
64 Report Descriptor File EAMRDESC * CS

Notes:
1. The abbreviations used in the Where Used column above stand for the
following:

Appendix A. Electronic Marketing Database 355

 v EN = Enrollment Program
v RP = Reports
v CS = Checkout Support Program
v TS = Terminal Sales Program
Table 33. Selective Item Record Report Session Numbers
Session Number Description
4 ITEM RECORD FILE (KEYED)
5 ITEM RECORD FILE (SEQUENTIAL)
6 ITEM MOVEMENT FILE (SEQUENTIAL)
8 STORE OPTIONS FILE
16 ITEM MOVEMENT LIST FILE
21 EXCEPTION LOG FILE
42 CURRENT PERIOD ITEM MOVEMENT FILE (KEYED)
43 OLD PERIOD ITEM MOVEMENT FILE (KEYED)
56 DELAYED DATA MAINTENANCE CONTROL FILE
57 DELAYED DATA MAINTENANCE SOURCE FILE
64 PRINTER OUTPUT

Table 34. Date of Last Sale and Item Movement Staging Session Numbers
Session Number Description
01 INPUT ITEM MOVEMENT FILE (SEQUENTIAL)
02 WORK FILE
03 INPUT ITEM MOVEMENT FILE (KEYED)
04 OUTPUT ITEM MOVEMENT FILE
05 ITEM RECORD FILE

Preferred Customer Coupon Tracking File (EAMCOUPC)

The Preferred Customer Coupon Tracking File is mirrored for data security. There is
a current period and an old period copy of this file. The old period file contains the
data from the most recently closed reporting period and the current period file
contains data for the period in process. The records in this file contain information
about coupons that have been accepted. The file can contain manufacturer
coupons and/or store coupons based on user-specified options. (See “Vendor
Coupons Logged in the Coupon Tracking File” on page 152 and “Store Coupons
Logged in the Coupon Tracking File” on page 152, respectively.) User-definable
options also determine whether doubled coupons are to be collected with store
coupons (see “Doubled Coupons Logged in the Coupon Tracking File” on page 153)
and define the range of coupon UPCs to be tracked in this file (see “Range of
Coupon UPCs to Log in the Coupon Tracking File” on page 154). Only coupons with
a real monetary value will be tracked in this file. Therefore, point coupons and fake
1 cent cross promotional coupons will not be tracked.

For additional information on the contents of this file, see “Logging of All Coupon
Data” on page 33.
Filename: EAMCOUPC I/O Session: 23

356 Electronic Marketing PRPQ

 Organization: Sequential File Copies: Current, Old
Record Length: Variable Distribution class: Mirrored
Table 35. Coupon Tracking File
Field Name Type Length Description
TERMINAL ASCII v3 Terminal number where coupon was taken
TRANSACTION ASCII v4 Transaction number in which coupon was taken
DATE/TIME ASCII 10 Date and time of transaction YYMMDDHHMM
RECORD TYPE ASCII 2 Record type of “99” (for exception log)
OPERATOR ASCII v9 Operator number accepting the coupon
COUPON MFR ASCII v5 Manufacturer number of coupon
COUPON UPC ASCII v12 Item Code of coupon
COUPON FAM ASCII v3 Family number of coupon
COUP VALUE ASCII v6 Value of coupon
ITEM UPC ASCII v12 Item Code of matching item
ITEM FAMILY ASCII v3 Family number of matching item
ITEM PRICE ASCII v8 Price of matching item
CAMPAIGN ASCII v6 Campaign number from coupon (see note)
ENTRY FLAGS ASCII v3 Decimal representation of one-byte integer
containing coupon entry type flags
X'80' Coupon was linked to
X'40' Coupon key pressed with item code
X'20' Keyed Campaign Number (see note)
X'10' Keyed coupon value required
X'08' Keyed coupon value
X'04' Keyed coupon item code (0 = scanned)
X'02' Coupon created by doubling
X'01' Store coupon (0 = MFR coupon)
VALID FLAGS ASCII v5 Decimal representation of two-byte integer
containing coupon validation flags
X'8000' Coupon required multiple items
X'4000' Keyed value limit check
X'2000' Coupon value exceeds item value
X'1000' Quantity not satisfied for coupon
X'0800' Too many coupons relative to sales
X'0400' Too many like coupons for transaction
X'0200' Coupon has expired
X'0100' Minimum purchase not satisfied
X'0080' Coupon good for free item
X'0040' Operator’s override required
X'0020' Manager’s override required
X'0010' No validation performed (No MFR number)
X'0008' Only family super group is valid
X'0004' Only manufacturer is valid
X'0002' Only department is valid
X'0001' No match found
Note: Only keyed campaign numbers can be captured at this point since the ability to capture this number via
scanning has not been demonstrated and may require additional code modifications. An option allows the
customer number to be placed in this field in place of the coupon campaign number.

In the ASCII format defined above, the fields are delimited by the standard PC
delimiters of “,” (X'222C22'). This ASCII format is readable. It allows the file to be

Appendix A. Electronic Marketing Database 357

 directly printed or typed. Also, the file can be printed after being dumped to the host
employing the standard ASCII to EBCDIC translation available through the
operating system.

The ASCII format creates a large volume of data. An optional PACKED format can
also be selected. The PACKED format contains the same data in the same order,
but the data is packed so that two numeric characters fit into every byte and the
field delimiter is a single colon (X'3A'). This format does not offer the ease of
interpretation provided by the ASCII format, but it uses only about half the space of
the ASCII format and substantially reduces the time required to transmit this data.

A record similar in format to that defined here can be logged in the exception log
file if the coupon type is not selected for collection in the coupon tracking file and
the item record associated with the coupon is flagged to “log all sales”. The first five
fields above are formatted in the exception log exactly as is done for all other
exception log records. The remaining portion of the record is an exact match to the
ASCII format.

Sample Coupon Record

ASCII FORMAT (shown first in ASCII then in Hex)

“1”,23”,“8804110945”,“99”,“1”,“99000”,“59900006625”,“66”,“25”

“9900012763”,“66”,“123”,“0”,“4”,“32768”CRLF

X'2231222C223233222C2238383034313130393435222C223939222C2231222C'
X'223939303030222C223539393030303036363235222C223636222C223235222C'
X'2239393030303132373633222C223636222C22313233222C2230222C2234222C'
X'223332373638220D0A'

Packed Format (only demonstrable in Hex)

X'22013A233A88041109453A993A013A0990003A0599000066253A663A253A
99000127633A663A01233A003A043A032768220D0A'

Exception Log Format (only demonstrable in Hex)

X'220001222C220023222C228804110945222C2299222C2201222C'
X'223939303030222C223539393030303036363235222C223636222C223235222C'
X'2239393030303132373633222C223636222C22313233222C2230222C2234222C'
X'223332373638220D0A'

You can anticipate about 100 bytes per coupon in ASCII format or 50 bytes per
coupon in packed format. These figures can be multiplied by the number of
expected coupons in the file to calculate the expected space requirements for the
file. If space is needed to allow for a week between host dumping (and deletion) of
the coupon data and 50,000 coupons are expected to be logged in a week, either
2.5MB or 5MB of space must be reserved for coupon tracking depending upon the
data format chosen.

358 Electronic Marketing PRPQ

Appendix B. Supermarket Application Base Coupon
Processing
Supermarket Application Base Support . . . . . . . . . . . . . . . 359
Format of Industry Coupon Code . . . . . . . . . . . . . . . . . 359
Coupon Validation . . . . . . . . . . . . . . . . . . . . . . 359
Coupons. . . . . . . . . . . . . . . . . . . . . . . . . . 359

This appendix summarizes the support for coupons provided in the Supermarket
Application.

Supermarket Application Base Support

Format of Industry Coupon Code

5 MMMMM FFFVV Where:

MMMMM = Manufacturer identification number

FFF = Family code (Determined by manufacturer)
VV = Table value for price lookup
(for example, 10 = $.10, 67 = $1.25, 26 = $1.50/2)

Coupon Validation
v Validation using manufacturer number / department number and family code
(FC):
– For a coupon item record with a manufacturer number in the UPC, validate by
manufacturer number and family code.
– For a coupon item record without a manufacturer number in the UPC,
(00000), validate by department number and family code.
v A family code of 000 in the coupon item record or a UPC five code causes family
code validation to be disregarded (000 = any FC OK).
v An item record with a family code of 991 validates with any family code of the
same manufacturer.
v There is space for two family codes in all item records. Either family code
validates a coupon.
v A coupon value cannot exceed the total value of sales for a coupon family or for
a manufacturer. (An override is possible.)
v Manufacturer and store coupon validation must be performed separately; for
example, a manufacturer coupon and store coupon can be validated against the
same item (tender + discount).
v An item can be used only to validate one coupon of the same type (manufacturer
or store coupon).

Coupons
There are two types of coupons:
v Manufacturer
v Store.

A manufacturer coupon is a form of tender for the item to which the coupon applies.

© Copyright IBM Corp. 1991 2000 359

 A store coupon is a form of discount on the coupon’s item.

Coupons are entered in the following ways:

v Pressing appropriate manufacturer or store coupon keys (with department keys)
v Setting up appropriate records in the Item Record File (flags) – PLUs
v Scanning manufacturer coupons with UPC five formats.

Personalization options affect coupon in the following ways:

v Taxability
v Multiplier values (for example, 2X and other values).

Coupon limits are as follows:

v Key entry limits by department
v Negative entry limits (counts and amounts)
v Exception logging options.

360 Electronic Marketing PRPQ

Appendix C. Electronic Marketing Code Glossary
Supermarket Modules modified for Electronic Marketing: . . . . . . . . . 361
Electronic Marketing Load Modules:. . . . . . . . . . . . . . . . . 361
Required Data Files: . . . . . . . . . . . . . . . . . . . . . . 362
Terminal Sales and Checkout Support EXIT Code: . . . . . . . . . . . 362
Report EXIT Code: . . . . . . . . . . . . . . . . . . . . . . . 362
Electronic Marketing File Summary: . . . . . . . . . . . . . . . . . 363
Electronic Marketing Application Summary: . . . . . . . . . . . . . . 363
Electronic Marketing Customer File Usage Summary: . . . . . . . . . . 364

Supermarket Modules modified for Electronic Marketing:

[Link] Altered Terminal Sales User Exit module
EAMTSUxx.J86 Altered Terminal Sales User Exit include files
[Link] Altered Terminal Sales link list
EAMTS11L.286 Terminal Checkout with Electronic Marketing exits installed
[Link] Altered Checkout Support User Exit module
EAMCSUxx.J86 Altered Checkout Support User Exit include files
[Link] Altered Checkout Support link list
EAMCSMLL.286 Checkout Support with Electronic Marketing exits installed
[Link] Altered Report's User Exit module
EAMRPU01.J86 Altered Report's User Exit include file
[Link] Altered Cash Report link list
EAMRPCRL.286 Cash Report with Electronic Marketing exits installed
[Link] Altered Performance Report link list
EAMRPPFL.286 Performance Report with Electronic Marketing exits installed
[Link] Altered Recap Report link list
EAMRPSTL.286 Recap Report with Electronic Marketing exits installed
[Link] Altered Electronic Marketing Accounting Object code
EAMACTCL.286 Altered Tender Count Load module
EAMACARL.286 Altered Automatic Reconciliation Load module
[Link] Altered Electronic Marketing Item Record Maintenance Object code
EAMDB55L.286 Altered Item Record Maintenance Program
EAMDMCBL.286 Altered Delayed Data Maintenance Load module
EAMDMDEL.286 Altered Delayed Data Maintenance Load module
EAMDMMLx.J86 3 include files for source changes to Delayed Data
Maintenance
[Link] Altered Delayed Data Maintenance Object code
EAMDMMLl.286 Altered Delayed Data Maintenance Load module
EAMUPM2L.286 In-store enrollment Procedure (as user procedure)
EAMUPM3L.286 User procedure to manually close a points activity period
EAMUPM4L.286 User procedure to maintain targeted coupon messages
EAMRPU3L.286 Selective Item Record Report
EAMRPU5L.286 Preferred Customer Audit Log Report
EAMRPU6L.286 Preferred Customer Exception Log Report
EAMRPU7L.286 Preferred Customer Options Report
EAMRPU8L.286 Selective Customer Report

Electronic Marketing Load Modules:

EAMUDOLS.286 Background program for Date of Last Sale updates
EAMENROL.286 In-store enrollment Procedure
EAMUPM2L.286 In-store enrollment Procedure (as user procedure)
EAMUPM3L.286 User procedure to manually close a points activity period
EAMUPM4L.286 User procedure to maintain targeted coupon messages
EAMRPU3L.286 Selective Item Record Report
EAMRPU5L.286 Preferred Customer Audit Log Report
EAMRPU6L.286 Preferred Customer Exception Log Report
EAMRPU7L.286 Preferred Customer Options Report

© Copyright IBM Corp. 1991 2000 361

 EAMRPU8L.286 Selective Customer Report
EAMBATZF.286 Installation program for the BATCH program
EAMUBATP.286 Background program for BATCH maintenance of keyed files
EAMUPKUP.286 Background program for auto pickups of paperless coupons
EAMUROLP.286 Background program to close points activity period
EAMUREFA.286 Background program for Reference point transfers
EAMUXFER.286 Background program for processing transferred points
FIXFILES.286 Utility program for enlarging keyed records
FIXR1OPT.286 Utility program for reformatting the options files
LOGNAMES.286 Utility program for installing user logical names
DESCADDR.286 Utility program for installing report descriptors
DESCADDS.286 Utility program for installing sales descriptors
DESCADDE.286 Utility program for installing Electronic Marketing
descriptors

Required Data Files:

[Link] 8 primary MAGIC screen files for the enrollment program
[Link] 8 alternate MAGIC screen files for the enrollment program
[Link] Display manager screen file for the enrollment program
[Link] 3 MAGIC Message files for the enrollment program
[Link] Default Electronic Marketing Messages File
[Link] Default Electronic Marketing Options File
[Link] Input data for installing user logical names
[Link] Input data for installing report descriptors
[Link] Input data for installing Electronic Marketing report
descriptors
[Link] Electronic Marketing descriptors

Terminal Sales and Checkout Support EXIT Code:

[Link] Altered Terminal Sales link list
[Link] 3 Electronic Marketing object modules for Terminal Checkout
(Medium Memory Model)
[Link] 3 Electronic Marketing object modules for Terminal Checkout
(Big Memory Model)
EAMTSExx.J86 25 include files for Terminal Checkout exits
EAMTSCxx.J86 15 include files for Terminal Checkout exits
[Link] Altered Controller Checkout link list
[Link] 2 Electronic Marketing object modules for Controller Checkout
EAMCSExx.J86 13 include files for Controller Checkout exits
EAMCSCxx.J86 8 include files for Controller Checkout exits
USERxxxx.J86 6 include files for common Electronic Marketing code
EAMTS11L.286 Terminal Checkout with Electronic Marketing exits installed
EAMCSMLL.286 Checkout Support with Electronic Marketing exits installed

Report EXIT Code:

[Link] 3 Altered link lists for the accounting reports
EAMRPExx.J86 2 common report exits for the accounting reports
EAMCRE01.J86 EAMRPU01 exit code for the cash report
EAMPFE01.J86 EAMRPU01 exit code for the recap and performance reports
EAMRPCRL.286 Cash Report with Electronic Marketing exits installed
EAMRPPFL.286 Performance Report with Electronic Marketing exits installed
EAMRPSTL.286 Recap Report with Electronic Marketing Exits installed

362 Electronic Marketing PRPQ

Electronic Marketing File Summary:
Logical Primary
Dependency Name Description Usage Format Distribute

EAMT:000 Terminal Options Input Sequen Compound

EAMSOPTS Store Options Input Sequen Compound
EAMOPERA Operator Authorization Input Keyed Compound
EAMIMOVx Item Movement File Input Keyed Compound
EAMITEMR Item Record File In/Out Keyed Compound
Supermarket EAMACCTx Accounting File Output Keyed Mirrored
Application EAMPERFx Performance File Output Keyed Mirrored
files EAMMTRNx Misc. Transactions Output Keyed Mirrored
EAMTERMS Terminal Status Output Keyed Mirrored
EAMOSTAT Operator Status Output Keyed Mirrored
EAMDMCTL Data Maint. Control Output Keyed Mirrored
EAMILIST Item Movement List Output Keyed Mirrored
EAMTRANx Transaction Log In/Out Sequen Mirrored
EAMEXCPx Exception Log Output Sequen Mirrored
EAMD:xxx Data Maint. Source Output Sequen Mirrored
EAMDMERR Data Maint. Error Output Sequen Mirrored

Required EAMFBACT Activity File In/Out Keyed Compound

Electronic EAMFBOPT Options File Input Sequen Compound
Marketing EAMFBMSG Messages File Input Sequen Compound
files EAMEDESC Descriptors File Input Random Compound

EAMFBCUS Enrollment File Output Keyed Mirrored

EAMFBAPP Previous Activity Output Keyed Mirrored
EAMFBACX Activity Checkpoint Output Keyed Compound
EAMFBTCM Targeted Coupon Message Input Keyed Compound
Optional EAMFBXFR Customer Transfer File Input Keyed Compound
Electronic EAMFBFLx Panel Filter File Input Sequen Compound
Marketing EAM:ssss Activity Transfer File In/Out Sequen Mirrored
files EAMFBAUx Audit Log Output Sequen Mirrored
EAMFBCHG Enrollment Change Log Output Sequen Mirrored
EAMPANEx Panel Diary Log Output Sequen Mirrored
EAMCOUPx Coupon Tracking Log Output Sequen Mirrored
EAMxxxxx Saved Report File Output Sequen Mirrored

EAMBATCH Batch Maintenance Input Input Sequen Mirrored

EAMBREPT Batch Report File Output Sequen Mirrored
EAMBSTAT Batch Status File Output Sequen Mirrored
EAMDMERR Batch Error Log Output Sequen Mirrored

Electronic Marketing Application Summary:

Load
Name Description Change Usage Optional

EAMTS11L Terminal Checkout Exits Terminal No

EAMCSMLL Controller Checkout Exits Background No

EAMRPCRL Cash Report Exits Foreground No

EAMRPPFL Performance Report Exits Foreground No
EAMRPSTL Store Recap Report Exits Foreground No

EAMDMMLL Delayed Data Maintenance Source Background Yes

EAMACTCL Tender Count Link Foreground Yes
EAMACARL Automatic Reconciliation Link Foreground Yes
EAMDB55L Item Record Maintenance Link Foreground Yes
EAMDMCBL Delayed Data Maintenance Link Foreground Yes
EAMDMDEL Delayed Data Maintenance Link Foreground Yes

EAMENROL Customer Enrollment New Foreground Yes

Appendix C. Electronic Marketing Code Glossary 363

 EAMUPM3L Close Points Activity Period New Foreground Yes
EAMUPM4L Coupon Message Maintenance New Foreground Yes
EAMRPU3L Selective Item Record Report New Foreground Yes
EAMRPU5L Audit Log Report New Foreground Yes
EAMRPU6L Exception Log Report New Foreground Yes
EAMRPU7L Options Report New Foreground No
EAMRPU8L Selective Customer Report New Foreground Yes

EAMUPKUP Pickup Paperless Coupons New Background No

EAMUXFER Process Transferred Points New Background Yes
EAMUDOLS Add Date of Last Sale to I.R. New Background Yes
EAMUFILT Filter Panel File New Background Yes
EAMUROLP Close Points Activity Period New Background Yes
EAMUREFA Transfer referenced points New Background Yes
EAMUBATP BATCH Keyed File Maintenance New Background Yes

EAMBATZF Install BATCH Error Messages New Command Yes

FIXFILES Enlarge Keyed File Records New Command Yes
FIXR1OPT Migrate options files New Command Yes
LOGNAMES Install User Logical Names New Command Yes
DESCADDS Install Sales Descriptors New Command Yes
DESCADDR Install Report Descriptors New Command Yes
DESCADDE Install E. M. Descriptors New Command Yes

Electronic Marketing Customer File Usage Summary:

Program File Mode File Activity

TERMINAL INPUT EAMFBMSG Signon

CHECKOUT EAMFBOPT Signon
EAMITEMR Item sale
EAMFBACT Customer identification
EAMFBXFR EOT in PC order
EAMFBTCM EOT coupon printing

OUTPUT EAMTRANx End of Transaction

CHECKOUT INPUT EAMFBOPT Initialization

SUPPORT EAMTRANx Primary input
EAMFBACT PC transaction
EAMFBFLT Panel Record needed
EAMACCTP Period Summary needed
EAMPANEX Close of period
EAMFBAUD Close of period
EAMCOUPC Close of period

OUTPUT EAMFBACT Update PC totals

EAMACCTC Update PC totals
EAMPERFC Update PC totals
EAMEXCPT Update PC totals
EAM:ssss Points transfer needed
EAMFBXFR Points transfer done
EAMFBAUD In-lane redemption
EAMPANEX Panel Record needed
EAMCOUPC Coupon Tracking needed
EAMPANEL Close of period
EAMFBAUO Close of period
EAMCOUPO Close of period
EAMFBACX Close of period

CUSTOMER INPUT EAMFBOPT Initialization

ENROLLMENT EAMFBACT Enter Customer ID
EAMFBCUS Enter Customer ID

OUTPUT EAMFBAUD Adjustment/Redemption

EAMFBACT Update name/points
EAMFBCUS Update data/points

364 Electronic Marketing PRPQ

 EAMFBCHG Update EAMFBCUS

ACCOUNTING INPUT EAMFBOPT Initialization

REPORTS EAMACCTx Cash Report
EAMPERFx Perf/Recap Report
Program File Mode File Activity

SELECTIVE INPUT EAMITEMR Report Items

ITEM RECORD EAMIMOVx Report Movement
REPORT EAMOPERA Check Auth.
EAMSOPTS Valid Depts

OUTPUT EAMIMOVx Reset Movement

EAMDMCTL Batch Update
EAMD:xxx Batch Update
EAMILIST Build I.M. List
EAMxxxxx Save Report File
EAMITEMR Delete Records
EAMEXCPT Delete Records

AUDIT LOG INPUT EAMFBOPT Initialization

REPORT EAMFBAUx Report

EXCEPTION INPUT EAMFBOPT Initialization

REPORT EAMEXCPx Report

OPTIONS INPUT EAMFBOPT Report Options

REPORT EAMEDESC Report Descriptors
EAMFBMSG Report Messages
EAMFBFLx Report Filters
EAMSOPTS Report Exits
EAMT:000 Report Exits

SELECTIVE INPUT EAMFBOPT Initialization

CUSTOMER EAMENCUS Report Customers
REPORT EAMFBACT Report Activity
EAMFBXFR Report Transfers
EAMOPERA Get Password
EAMFBAPP Report Period Totals

OUTPUT EAMxxxxx Save Report File

EAMBATCH Batch Update

EAMUPKUP INPUT EAMFBOPT Initialization

(Auto CPN EAMACCTP Automatic Coupons
Pickup )
OUTPUT EAMACCTP Automatic Pickup
EAMACCxL
EAMTERMS
EAMOSTAT
EAMMTRNP Auto Misc. Trans
EAMMTRxL

EAMUXFER INPUT EAMFBOPT Initialization

(Transfer EAM:SSSS Primary Input
Processing) EAMFBACT Test for Home

OUTPUT EAMFBACT Transfer Pending

EAMFBXFR Transfer Pending
EAMEXCPT Log processing
EAM:ERRD Save Error Input

Program File Mode File Activity

EAMUDOLS INPUT EAMIMOVO Primary Input

(Date of

Appendix C. Electronic Marketing Code Glossary 365

 Last Sale) OUTPUT EAMITEMR Update Items
EAMIMOV1 Stage Movement

EAMUFILT INPUT EAMFBOPT Initialization

(Panel EAMTRANx Primary Input
Filter ) EAMFBFLx Filter Definition
EAMFBACT Panel Allowed

OUTPUT EAMPANLx Primary Output

EAMUBATP INPUT EAMBATCH Primary Input

(Batch
File OUTPUT EAM????? Primary Output
Maint.) EAMBSTAT Output Status
EAMBREPT Output Report
EAMEXCPT Output Errors
EAMDMERR Output Errors
EAMBERRD Output Errors

EAMUPM4L INPUT EAMFBOPT Initialization

(Coupon EAMFBTCM Report Coupon Status
Message EAMITEMR Report Coupon Status
Maint. )
OUTPUT EAMFBTCM Update Coupon Message

EAMUROLP INPUT EAMFBOPT Initialization

EAMFBACT Primary Input

OUTPUT EAMFBAPP Roll to Old

EAMFBACT Clear Current
EAMMMESG Report Status

366 Electronic Marketing PRPQ

Glossary
A M
Alias customer activity record. A record for a Manufacturer Coupon. A coupon which represents a
customer in the Preferred Customer Activity File that tender against the item sold.
contains an indication marking it as an alias record and
pointing to a primary activity record that contains
accumulated point information and processing
N
instructions for a customer and their family members.
Net value coupon. A coupon whose value represents
Alias records allow multiple customer identifications to
the final price of the discounted item rather than the
access the same primary activity record and contribute
discount price. Coupons that are created using pricing
to and redeem from the same points total.
method 3 are net value coupons.
Automatic coupon. A manufacturer or store coupon
Non-home store concept. An enterprise operating
that automatically provides a discount when a customer
plan that does not designate home stores for
buys a promoted item but that has no paper counterpart
customers. All customers are considered home
for a customer to present (at the point of sale).
customers and can receive points and recognition in all
of the enterprise’s stores in which they shop.
B
Non-participating customers. A customer who is not
Bonus Point Coupon. A coupon whose value enrolled in the Preferred Customer Program.
represents the number of points to be added to a
preferred customer’s points total. Bonus point coupons Non-preferred customer coupon. A coupon with a
are a subset of points coupons. UPC outside of the range defined for preferred
customers that is given to all customers, including
preferred and non-preferred (unenrolled) customers.
E
Normal sales coupon. A coupon whose value
Electronic coupon. A manufacturer or store coupon represents the amount to be subtracted from the
that automatically provides a discount when a customer transaction balance due. Normal sales coupons apply to
buys a promoted item but that has no paper counterpart all preferred customers.
for a customer to present (at the point of sale). See
automatic coupon.
P
Enrollment. A procedure by which an enterprise
assigns unique identification numbers to customers who Paper coupon. A manufacturer or store coupon
choose to participate in the Preferred Customer printed on paper that a customer can redeem for a
program and electronically captures certain discount on a product. Paper coupons may be given to
demographic information that describes each customer. all customers or designated for preferred customers
only.

H Personalization. Used in some stores as

customization. The Electronic Marketing application
Home Store Concept. An enterprise operating plan provides default preferred customer options, and
that designates a home store for each preferred messages that can be personalized to achieve desired
customer. A home store is the store where a customer processing.
enrolls, usually shops, receives recognition, and gains
and receives points. Points. The accumulation of transaction points is a
method provided by Electronic Marketing to reward local
customers. Points reflect a customer’s history of
L purchase activity and are related to the tender value of
items purchased (but, may differ from this value as they
Local home store customer. A customer who is are affected by taxes, coupons, bonus points, and other
shopping in a store that is in their local area and that is factors). points may be redeemed in exchange for
defined to support giving local home store recognition something of value, such as a special discount on a
customers and benefits. The points accumulated for a product.
local home store customer are transferred to the
primary home store, where they can be redeemed.

© Copyright IBM Corp. 1991 2000 367

Preferred customer coupon. A coupon with a UPC customers’ activity records. Targeted coupons allow
within the range defined for preferred customers that is promotions to be targeted to a selected subset of
given to preferred customers only. preferred customers.

Preferred customer identification number. A unique

number assigned during enrollment to each customer V
who chooses to participant in the Preferred Customer
program. A (preferred) customer identification number is Validation. A process initiated each time a preferred
the only identification a customer customer presents a preferred customer identification
card at a checkout. A transaction that checks the
Primary customer activity record. A record for a number to ensure that it is (valid for use) (allowed to be
customer in the Preferred Customer Activity Record that used) in that store. Also a process initiated when a
contains accumulated point information and instruction coupon is used to ensure that all the conditions required
for processing a customer’s transactions needs to be for receiving the coupon, such as purchase of (linked to)
considered enrolled. (matching) item and minimum purchase requirement,
are met.
Primary home store customer. A customer who is
shopping in their primary home store in which they Visiting Preferred Customer. A customer who is
enrolled. enrolled in the Preferred Customer program but who is
shopping in a store that is not in their local area and is
not the store in which he/she enrolled.
R
Rain check customer. A customer who uses a store
rain check identification number when he/she does not
have their preferred customer identification card. Rain
check customers can receive some benefits and
accumulate points for a transaction.

Rain check identification number. A predefined store

identification number available to be used for preferred
customers when they do not have their preferred
customer identification card. A rain check identification
enables customers to receive some benefits and
accumulate points for a transaction.

Record. A collection of related items of data, treated

as a unit. For example, the Preferred Customer
Enrollment File contains a single record for each
preferred customer with the demographic data entered
during enrollment. A complete set of such records may
form a file.

Redemption coupon. A coupon whose value

represents the number of points to be subtracted from a
preferred customer’s point total by the redemption of
points in exchange for something of value, such as a
special discount. Redemption coupons are a subset of
points coupons.

S
Store Coupon. A coupon that represents a discount
on the coupon item but, is accounted for as tender.

T
Targeted coupon. A coupon that is designated for
selected preferred customers and that is linked to them
through the placement of the coupon item code in the

368 Electronic Marketing PRPQ

Index
A coupons (continued)
industry coupon code xxiii, 359
accounting file usage file - EAMACCTC xxiii, 352
limit transaction/limit xxiii, 28, 199
accounting reports xxiii, 273
linked to department purchase xxiii, 212
activate additional messages xxiii, 173
linked to items per coupon xxiii, 219
activate terminal and controller exits xxiii, 65
linked to minimum by manufacturer xxiii, 218
activity file - EAMFBACT xxiii, 322
linked to minimum department purchase xxiii, 214
activity record types 13
linked to two departments xxiii, 215
alias xxiii, 13
logging off data xxiii, 33
family members xxiii, 13
normal sales xxiii, 10
primary customer xxiii, 13
personalization of processing xxiii, 35
activity transfer file - EAMXssss xxiii, 326
processing, electronic xxiii, 230
adjusting a customer record xxiii, 193
processing, redemption xxiii, 237
alias customer activity record xxiii, 13
processing, targeted xxiii, 234
audit log file - EAMFBAUD xxiii, 327
sample xxiii, 197
auto install of Electronic Marketing descriptors xxiii,
scanning, store xxiii, 21
277
tracking file xxiii, 356
auto install of new report descriptors xxiii, 278
UPC 7, 8, and 9 digit support xxiii, 27
auto install of new sales descriptors xxiii, 278
validation xxiii, 23, 26
automatic discounts via customer activity record xxiii,
242 CSEMEC01 After the Read of a Customer Activity
auxiliary functions 14 Record xxiii, 307
default xxiii, 14 CSEMEC02 After the Read of a Customer Transfer
optional xxiii, 17 Record xxiii, 308
award, redeeming CSEMEC03 Before the Write of a Customer Activity
no performance required xxiii, 222 Record xxiii, 309
redeeming xxiii, 191 CSEMEC04 Before the Write of a Customer Transfer
Record xxiii, 310
CSEMEC05 Before the Write of an Activity Transfer
B Record xxiii, 310
background application configure xxiii, 53 CSEMEC06 After The Update Of Accounting
background programs install xxiii, 44 Totals xxiii, 311
base Supermarket Application coupon processing xxiii,
CSEMEC07 Before The Write Of Preferred Customer
359
Audit Log Record xxiii, 312
batch maintenance for keyed files
maintenance file EAMBATCH xxiii, 284 CSEMEC08 Before the Write of a Panel Diary
maintenance for keyed files xxiii, 282 Record xxiii, 312
report xxiii, 289 CSEMEC09 Before The Write Of A Coupon Tracking
status EAMBSTAT xxiii, 290 Record xxiii, 313
batch program, install 61 customer
executing xxiii, 62
activity records (see activity records) xxiii
bonus coupons xxiii, 10
enrollment xxiii, 7
identification xxiii, 7, 8, 177, 228
C item record data xxiii, 19
code, promotion, validation xxiii, 26, 247 key, customer number, configure xxiii, 55
configuration and installation xxiii, 37 messages xxiii, 8, 172
configure multiple customer IDs xxiii, 179
background application xxiii, 53 multiplication limits xxiii, 30
key sequences for auxiliary functions xxiii, 54 rain check xxiii, 8
logical names for batch program xxiii, 61 receipt
optional customer number key xxiii, 55 preferred customer xxiii, 180
controller exits 307 regular customer xxiii, 180
activate xxiii, 65 recognition xxiii, 8
coupons record alterations xxiii, 260
base Supermarket Application processing xxiii, 359 reporting xxiii, 259
bonus xxiii, 197, 223 rewards xxiii, 8
electronic xxiii, 10 roll period totals xxiii, 294
final value xxiii, 201, 202, 205, 209, 225 selection xxiii, 258

© Copyright IBM Corp. 1991 2000 369

D Electronic Marketing (continued)
overview xxiii, 5
data entry line xxiii, 173
processing xxiii, 227
data files, required xxiii, 362
unique user exits xxiii, 299
data space use adjustments xxiii, 246
electronic marketing coupons 10
database, electronic marketing xxiii, 13
processing xxiii, 230
date of last sale update functions xxiii, 45, 247, 296
DDM error log xxiii, 291 end of options indicator xxiii, 162
deactivate preferred customer processing xxiii, 77 enrolled customer receipt xxiii, 180
default, preferred customer options xxiii, 76 enrollment and identification xxiii, 7
default auxiliary functions xxiii, 14 enrollment file - EAMFBCUS 320
delayed data maintenance error log xxiii, 291 enrollment change file - EAMFBCHG xxiii, 328
department totals file usage file xxiii, 353 entering rain check xxiii, 195
DESCADDE auto install of Electronic Marketing enterprises
descriptors xxiii, 277 home store concept xxiii, 12
DESCADDR auto install of new report descriptors xxiii, non-home store concept xxiii, 13
278 entry line, data xxiii, 173
DESCADDS auto install of new sales descriptors xxiii, erasing a record xxiii, 187
278 error
descriptor file, report xxiii, 325 handling xxiii, 257, 261
descriptors log updates DDM xxiii, 291
electronic marketing report, personalize xxiii, 68 system log updates xxiii, 292
report, personalize xxiii, 66 system log usage xxiii, 355
terminal sales, personalize xxiii, 65 error log usage, system xxiii, 355
diary, panel file xxiii, 330 exception log updates xxiii, 291
discounts, automatic via customer activity record xxiii exception log usage file xxiii, 354
displaying a record xxiii, 189 exit code xxiii, 38, 40, 42, 148, 299
exits
E activate xxiii, 65
controller xxiii, 65, 307
EAMACCTC - accounting file usage file xxiii, 352
terminal xxiii, 65, 300
EAMBATCH batch maintenance file xxiii, 284
EAMBSTAT batch status xxiii, 290
EAMCOUPC - coupon tracking file xxiii, 356
EAMDEPTC - department total file usage file xxiii, 353
F
EAMEDESC - report descriptor file xxiii, 325 family members xxiii, 13
EAMEXCPT - exception log usage file xxiii, 354 file
EAMFBACT - activity file xxiii, 322 batch maintenance or keyed xxiii, 282
EAMFBAPP - previous activity file xxiii, 324 change message xxiii, 173
EAMFBAUD - audit log file xxiii, 327 default preferred customer messages xxiii, 174
EAMFBCHG - enrollment change log file xxiii option support xxiii, 318
EAMFBCUS - enrollment file xxiii, 320 preferred customer messages xxiii, 169
EAMFBFLT - panel filter file xxiii, 336 preferred customer options xxiii, 75
EAMFBMSG - messages file xxiii, 330 support xxiii, 318
EAMFBTCM - targeted coupon messages file xxiii, 340 filter file - EAMFBFLT xxiii, 336
EAMFBXFR - transfer file xxiii, 325 final value coupons xxiii, 201, 225
EAMIMOV1 - staged item movement file xxiii, 351 FIXFILES - keyed file record reformatting xxiii, 279
EAMITEMR - item record usage file xxiii, 341 FIXR1OPT - convert option files to new format xxiii,
EAMPANEX - panel diary file xxiii, 330 280
EAMPERFC - performance file usage file xxiii, 353 foodstamps, accept only xxiii, 15
EAMUBATP batch maintenance for keyed files xxiii,
functions, auxiliary 14
282
default xxiii, 14
EAMUPM3L manual close of points activity
optional xxiii, 17
period xxiii, 294
EAMUROLP roll customer period totals procedure xxiii,
181, 294
EAMXssss - activity transfer file xxiii, 326 H
electronic coupons xxiii, 11 hardware supported xxiii, 6
Electronic Marketing home store 11
concepts xxiii, 7 enterprises that use xxiii, 12
database xxiii, 13, 318 multiple, processing support xxiii, 228
descriptors, personalize xxiii, 68 processing support xxiii, 227

370 Electronic Marketing PRPQ

I linked coupons (continued)
minimum in two departments xxiii, 215
I/O session number xxiii, 355
multiple items/no points xxiii, 209
ID, customer xxiii, 7, 8
multiple items plus points xxiii, 205
identification, customer 7, 8
load modules xxiii, 361
definition option xxiii, 78
log
entering xxiii, 177
audit file xxiii, 327
establishing xxiii, 178
enrollment change file xxiii, 328
multiple customers xxiii, 179
exception usage file xxiii, 354
number processing xxiii, 228
system error xxiii, 355
preferred customers xxiii, 179
logging off coupon data xxiii, 33
targeted coupons xxiii, 178
logical names, add xxiii, 52, 61
industry coupon code xxiii, 181, 359
LOGNAMES install preferred customer logical
install
names xxiii, 281
background panel filters as needed 62
batch keyed file maintenance program 61
in-store enrollment program 60 M
installation and configuration 37 messages 8, 173
add messages used by batch program xxiii, 62 activate additional xxiii, 173
add user logical names xxiii, 52 add, used by the batch program xxiii, 62
background programs xxiii, 44 change file xxiii, 173
batch program xxiii, 61 coupon file - EAMFBTCM xxiii, 340
configure background application xxiii, 53 customer identification xxiii, 172
configure key sequences for aux functions xxiii, 54 default preferred customer file xxiii, 174
configure logical names for batch program xxiii, 61 file - EAMFBMSG xxiii, 330
configure optional customer number key xxiii, 55 maintain targeted coupon xxiii, 295
notes xxiii, 37 preferred customer xxiii, 169
optional date of last sale update function xxiii, 45 where shown xxiii, 172
optional source code changes xxiii, 47 multiple customer IDs xxiii, 179
optional user procedures xxiii, 45 multiple home store support xxiii, 228
re-link data maintenance, tender count, automatic multiplication limits xxiii, 30
reconciliation xxiii, 43
report exit code xxiii, 42
terminal and controller checkout exit code xxiii, 40 N
user reports xxiii, 44 negative balance due xxiii, 15
interface, operator xxiii, 32 net value coupons xxiii, 10
item non-home store 13
alterations xxiii, 254 enterprises that use xxiii, 13
points-only xxiii, 9 non-preferred coupons xxiii, 10
record data xxiii, 28 normal sales coupons xxiii, 10
record report options xxiii, 163
record usage file xxiii, 341
reporting xxiii, 252 O
selection xxiii, 250 operator interface xxiii, 32, 257, 261
staged item movement file xxiii, 351 operator name xxiii, 15
optional auxiliary functions xxiii, 17
options file, personalization 75
K accept electronic and paper vendor coupons on
key sequences, configure xxiii, 54 same item xxiii, 138
KIOSK support xxiii, 243 Accept Electronic/Paper Store Coupons on Same
Item xxiii, 139
accumulate keyed versus scan totals by
L department xxiii, 112
limit transaction/limit coupons xxiii, 199 accumulate ratio of PLU entries to DEPT key
line, data entry xxiii, 173 entries xxiii, 112
link list, terminal checkout support xxiii, 38 activate activity options for all preferred
linked coupons customers xxiii, 84
department purchase xxiii, 212 activity file size xxiii, 81
discount/redeem points xxiii, 202 activity options default xxiii, 83
items per coupon xxiii, 219 activity record size xxiii, 82
minimum by manufacturer xxiii, 218 add customer number to coupon tracking file
minimum department purchase xxiii, 214 records xxiii, 135

Index 371
options file, personalization 75 (continued) options file, personalization 75 (continued)
add period summary string to panel file xxiii, 131 count home store numbers supported by this
Address Label Size Definitions for Selective store xxiii, 102
Customer Report xxiii, 149 count home store numbers supported only by this
all store xxiii, 102
Automatically Update Promotion Codes to Equal count of boundary levels defined for special
Link Value xxiii, 169 processing xxiii, 125
Batches Are Created as ADDMI Batches xxiii, count of customer defined demographic fields xxiii,
168 111
Batches Are Created as ADDMI Immediate Coupon Tracking File Entries in Compressed
Updates xxiii, 168 Format xxiii, 153
Batches Are Created as DDM Operator Controlled coupon velocity code range for preferred
Batches xxiii, 168 customers xxiii, 97
All Coupons Require at Least Department Level coupons targeted for the first use of a customer
Validation xxiii, 150 card xxiii, 81
allow create and access customer transfer file xxiii, 86
Creation of Item Movement Lists xxiii, 165 Days of Week on Which Coupon Doubling is Not
Creation of Maintenance Batches xxiii, 164 Active xxiii, 162
Deletion of Item Records xxiii, 165 deactivate activity options for all preferred
Printing of the Report with No Display xxiii, 164 customers xxiii, 84
Resetting of Item Movement xxiii, 164 deactivate preferred customer processing xxiii, 77
Save date of last sale at close of item Deactivate Unique Electronic Marketing Exit
movement xxiii, 140 Code xxiii, 148
Saving of Report Data to File xxiii, 163 default xxiii, 76
allow erase of customer points xxiii, 104 define taxes to turn on with the TAX/NOTAX
allow tax exemption without a discount key xxiii, key xxiii, 108
114 deposit automatic coupons into misc accounts xxiii,
always use the manufacturer number from coupon 132
record xxiii, 135 descriptions xxiii, 76
append audit data to panel file xxiii, 130 display backup indicator at registers xxiii, 113
automatic close of the points activity period xxiii, 94 Double Coupons Available only Preferred
automatic discounts for associated points Customers xxiii, 139
ranges xxiii, 134 Doubled Coupon Count Limit Per Order xxiii, 160
automatic execution time for batch updates xxiii, 95 Doubled Coupon Value Limit Per Coupon xxiii, 158
automatic execution time for reference Doubled Coupons Logged in the Coupon Tracking
processing xxiii, 98 File xxiii, 153
automatic execution time for transfer employee number required on redemption,
processing xxiii, 96 adjustment, and/or rain check xxiii, 106
Automatic Tare from Weight Item Records xxiii, 144 end of options indicator xxiii, 162
automatically process in-store transfers each enrollment zip fields Are numeric and packed xxiii,
hour xxiii, 86 107
Automatically Update Item Family with Low 3 Link entering a rain check xxiii, 195
Digits xxiii, 167 exclude automatic coupons from reported coupon
bonus item points limit xxiii, 93 counts xxiii, 131
bonus points awarded at boundary crossing xxiii, exclude non-points items from minimum purchase
126 limits xxiii, 134
boundary repeats at each multiple of boundary Exit Field 1 Contains Packed Decimal Data xxiii,
points xxiii, 126 165
Bypass Fixed Targeted Message if Promotion Text Exit Field 2 Contains Packed Decimal Data xxiii,
Provided xxiii, 146 166
Bypass Journal Printing Automatic Coupon form number required on redemption, adjustment,
Rejections xxiii, 143 and/or rain check xxiii, 105
Bypass Receipt Printing of Targeted Coupon format of customer name in activity record xxiii, 83
Numbers xxiii, 143 highlight printing of all exceptional entries xxiii, 118
bytes before the customer name in activity highlight printing of automatic coupons xxiii, 118
record xxiii, 82 home store location in customer number xxiii, 100
cash checks using a sales transaction xxiii, 114 home store numbers supported by this store xxiii,
category number to uniquely identify customer 103
numbers xxiii, 101 interpret restricted time periods as unrestricted
check sum of all voids at each void entry xxiii, 117 times xxiii, 115
collect panel data for all customers xxiii, 85 item record report xxiii, 163

372 Electronic Marketing PRPQ

options file, personalization 75 (continued) options file, personalization 75 (continued)
keep automatic coupon totals in Dept file exit points total that defines boundary xxiii, 125
fields xxiii, 130 preferred coupons buffered in memory xxiii, 93
keep monthly previous points activity for print available targeted coupons on customer
customer xxiii, 122 receipt xxiii, 119
keep old period audit log data xxiii, 129 Printed Reports are in Compressed Mode xxiii, 167
key definition for customer entry key xxiii, 99 Printed Reports Use 132 Character Line
keyed customer numbers require a manager’s Formats xxiii, 167
override xxiii, 88 program name xxiii, 76
KIOSK points message offset xxiii, 109 Purchase Amount for the Coupon Doubling Count
length of enrollment Social Security field xxiii, 112 Limit xxiii, 160
length of enrollment state field xxiii, 110 rain check ID definition xxiii, 78
length of enrollment ZIP field xxiii, 110 Range of coupon UPCs to log in coupon tracking
length of enrollment ZIPEXT field xxiii, 111 file xxiii, 154
level increment awarded at boundary crossing xxiii, Range of Departments to Validate by Subtotal
126 Group xxiii, 154
Limit on Number of Identical Coupons to be Doubled ratio of points per cents purchased xxiii, 92
in an Order xxiii, 161 remind checker to ask for customer card xxiii, 119
List of Guidances Lowered to Allow Operator remind operator to take customer’s money xxiii, 115
Override xxiii, 156 remove doubled coupons from store coupons by
log enrollment alteration to separate sequential dept xxiii, 137
file xxiii, 104 Report Exit 1 and Exit 2 as a Single Field xxiii, 166
manager’s override required for new run enrollment procedure without enrollment
customers xxiii, 90 file xxiii, 107
Manual Coupon Doubling Allowed, Lookup Key Code Save Date Last Sale for Items at Close Item
Defined xxiii, 161 Movement xxiii, 140
Manufacturer Number to Identify UPC 5 Store selectively deactivate each enrollment function xxiii,
Coupons xxiii, 154 106
Match Coupons Against Cross Promotional Selectively Deactivate Selective Customer Report
Group xxiii, 144 Functions xxiii, 150
maximum item record descriptor length xxiii, 109 Sequence Number and Velocity Code in Store
maximum number of coupons targeted per Coupon UPCs xxiii, 152
customer xxiii, 85 Show Only Paper Coupons in Cash Drawer
maximum points to carry from one period to Reports xxiii, 142
another xxiii, 94 show points in whole dollar amounts xxiii, 90
message presented at boundary crossing xxiii, 127 show time in 12-hour format xxiii, 117
Minimum Transaction Size for Coupon stage activity file at each close of period xxiii, 136
Doubling xxiii, 159 Store Coupons Logged in the Coupon Tracking
modulo check customer numbers during File xxiii, 152
enrollment xxiii, 103 store coupons reduce points xxiii, 87
multiplier for coupon minimum purchase support for multiple cash drawers xxiii, 116
amounts xxiii, 99 taxes increase points xxiii, 87
new customer coupons start each new activity tenders using alternate customer # as account
period xxiii, 121 # xxiii, 123
new customer message starts each new activity tenders using preferred customer # as account
period xxiii, 121 # xxiii, 122
No Doubling of Coupons Over the Value Limit xxiii, treat all non-preferred customers as rain check xxiii,
158 136
only allow one terminal to have negative UPC displacement for preferred customer linked
transactions xxiii, 108 items xxiii, 79
only points this period are available for Use 132 Character Lines in Selective Customer
redemption xxiii, 120 Report xxiii, 148
operator’s override sufficient to change tender Use a One Page Menu for All 16 Search
# xxiii, 124 Selections xxiii, 166
override needed for keyed preferred customer Use Compressed Print in the Selective Customer
coupons xxiii, 138 Report xxiii, 148
override required to change tender verification use coupon families in validation of UPC 5
# xxiii, 124 coupons xxiii, 89
personalization message format xxiii, 91 use period points for boundary options xxiii, 120
point ranges for period close report xxiii, 133 Use Promotion Codes for Coupon Validation xxiii,
points rounding selection xxiii, 92 140

Index 373
options file, personalization 75 (continued) preferred customer (continued)
valid range of non-home store numbers xxiii, 98 transfer file - EAMFBXFR xxiii, 325
Validate All Department Keyed Coupons by previous activity file EAMFBAPP xxiii, 324
Department xxiii, 151 program name xxiii, 76
validate automatic preferred customer store promotion code validation xxiii, 26, 247
coupons xxiii, 88
Validate Expiration Date with MSR Entry Customer
ID xxiii, 147 R
validation digits in customer number xxiii, 101 rain check customers 8
Value Limit Applies to Sum of Coupon and entering xxiii, 195
Double xxiii, 159 ID definition xxiii, 78
velocity code range for reusable targeted recognition, customer xxiii, 8
coupons xxiii, 97 record, changing 185
Vendor Coupons Logged in the Coupon Tracking adjusting xxiii, 193
File xxiii, 152 alterations, customer xxiii, 260
weight items do not require weight key xxiii, 113 erasing xxiii, 187
override for negative balance xxiii, 16 record type, activity 13
alias customer xxiii
family members xxiii, 13
P primary customer xxiii, 13
panel diary file EAMPANEX xxiii, 330 redeeming and award xxiii
paper coupons xxiii, 10 redemption coupon processing xxiii, 237
perform configuration changes 52 redemption coupons xxiii, 10
performance considerations xxiii, 35, 257 regular customer receipt xxiii, 180
performance file usage file EAMPERFC xxiii, 353 report 68
periodic points totals xxiii, 240 accounting xxiii, 273
personalization (See also options, personalization) descriptor file EAMEDESC xxiii, 325
report descriptors xxiii, 66 descriptors, electronic marketing, personalize xxiii
report descriptors, electronic marketing xxiii, 68 descriptors, personalize xxiii, 66
terminal sales descriptors xxiii, 65 exit code, install xxiii, 42
personalization of coupon processing xxiii, 35 item record options xxiii, 163
points preferred customer audit log xxiii, 262
activity period manual close xxiii, 294 preferred customer exception log xxiii, 262
award with no performance required xxiii, 222 preferred customer options xxiii, 264
bonus coupons xxiii, 197, 223 selective item record xxiii, 250
periodic totals support xxiii, 240 selective preferred customer xxiii, 258
points-only xxiii, 9 user xxiii, 44, 249
processing xxiii, 238 required data files xxiii, 362
transaction xxiii, 9 rewards, customer xxiii, 8
points coupons xxiii, 10
points-only xxiii, 9
preferred customer S
activity file - EAMFBACT xxiii, 322 sales coupons, normal xxiii, 10
activity transfer file - EAMXssss xxiii, 326 sales descriptors, personalize terminal xxiii, 65
audit log file - EAMFBAUD xxiii, 327 scanning coupons xxiii, 21
audit log report xxiii, 262 selective
coupons xxiii, 10 item record report xxiii, 250
deactivate processing xxiii, 77 preferred customer report xxiii, 258
default messages file xxiii, 174 session number, I/O xxiii, 355
enrollment change file - EAMFBCHG xxiii, 328 source code changes xxiii, 47
enrollment file - EAMFBCUS xxiii, 320 staged item movement file xxiii, 351
enrollment screen xxiii, 183 store
exception log report xxiii, 262 coupon scanning xxiii, 21
I/O session number xxiii, 355 coupon validation xxiii, 23
identification xxiii, 179 home xxiii, 11
messages file xxiii, 169 non-home xxiii, 13
messages file - EAMFBMSG xxiii, 330 string
options default xxiii, 76 alias electronic coupon item code xxiii, 333
options descriptions xxiii, 76 automatic coupon transaction data xxiii, 332
options file xxiii, 75 bonus/redemption points xxiii, 334
options report xxiii, 264 coupon tracking xxiii, 334
previous activity file - EAMFBAPP xxiii, 324 customer identification xxiii, 332

374 Electronic Marketing PRPQ

string (continued) user exits
customer transaction data xxiii, 333 CSEMEC01 After the Read of Customer Activity
new tender verification account number xxiii, 333 Record xxiii, 307
period header xxiii, 331 CSEMEC02 After the Read of Customer Transfer
period summary xxiii, 335 Record xxiii, 308
redemption/adjustment xxiii, 335 CSEMEC03 Before the Write of Customer Activity
subtotals, printed xxiii, 15 Record xxiii, 309
supported hardware xxiii, 6 CSEMEC04 Before the Write of Customer Transfer
system error log updates xxiii, 292 Record xxiii, 310
system error log usage xxiii, 355 CSEMEC05 Before the Write of Activity Transfer
system performance xxiii, 35 Record xxiii, 310
CSEMEC06 After The Update Of Accounting
Totals xxiii, 311
T CSEMEC07 Before The Write Of Preferred Customer
targeted coupons xxiii, 11, 178, 295 Audit Log Record xxiii, 312
messages file xxiii, 340 CSEMEC08 Before the Write of a Panel Diary
processing xxiii, 234 Record xxiii, 312
taxability xxiii, 16 CSEMEC09 Before The Write Of A Coupon Tracking
terminal Record xxiii, 313
exits, activate xxiii, 65 TSEMEC01 After The Read Of A Customer Activity
sales descriptors, personalize xxiii, 65 Record xxiii, 299, 300
TSEMEC02 After Read Of Customer Transfer
terminal checkout and support link list xxiii, 38
Record xxiii, 301
terminal exits
TSEMEC03 After The Read Of A Coupon Message
TSEMEC01 After The Read Of A Customer Activity
Record xxiii, 301
Record xxiii, 300
TSEMEC04 After Input Of Customer Number In
TSEMEC02 After Read Of Customer Transfer
Response To a Prompt (Input from MSR) xxiii,
Record xxiii, 301
302
TSEMEC03 After The Read Of A Coupon Message
TSEMEC05 After Validation Of A Customer
Record xxiii, 301
Number xxiii, 302
TSEMEC04 After Input Of Customer Number In
TSEMEC06 After Computing Coupon Value Based
Response To a Prompt (Input from MSR) xxiii,
On Value Of Matching Items xxiii, 303
302
TSEMEC07 Before Assuring Minimum Purchase For
TSEMEC05 After Validation Of A Customer
Coupon Is Met xxiii, 303
Number xxiii, 302
TSEMEC08 After Computing The Points Value Of An
TSEMEC06 After Computing Coupon Value Based
Order xxiii, 304
On Value Of Matching Items xxiii, 303
TSEMEC09 After Saving A Coupon For Total
TSEMEC07 Before Assuring Minimum Purchase For
Time xxiii, 304
Coupon Is Met xxiii, 303
TSEMEC10 At Checking For Crossing A Points
TSEMEC08 After Computing The Points Value Of An
Boundary xxiii, 305
Order xxiii, 304
TSEMEC11 Before Giving Automatic Coupons At The
TSEMEC09 After Saving A Coupon For Total
Entry Of A Customer Number xxiii, 305
Time xxiii, 304
TSEMEC12 Before Giving Automatic Coupons At
TSEMEC10 At Checking For Crossing A Points
Total Time xxiii, 306
Boundary xxiii, 305
TSUPEC14 terminal user exit xxiii, 299
TSEMEC11 Before Giving Automatic Coupons At The
Entry Of A Customer Number xxiii, 305 user reports xxiii, 249
TSEMEC12 Before Giving Automatic Coupons At utilities
Total Time xxiii, 306 DESCADDE auto install of Electronic Marketing
totals accumulation processing xxiii, 244 descriptors xxiii, 277
totals usage file, department xxiii, 353 DESCADDR auto install of new report
tracking file, coupon xxiii, 356 descriptors xxiii, 278
transaction DESCADDS auto install of new sales
points xxiii, 9 descriptors xxiii, 278
transfer file EAMFBXFR xxiii, 325 FIX1ROPT convert option files to new format xxiii,
TSUPEC14 user exit xxiii, 299 280
FIXFILES keyed file record reformatting xxiii, 279
LOGNAMES install preferred customer logical
U names xxiii, 281
UPC, 7, 8, and 9 digit coupons xxiii, 27
usage file, item record xxiii, 341

Index 375
V
validating store coupons xxiii, 23, 26
validation, promotion code xxiii, 26, 247

W
weight, display 15
category 2 sales xxiii, 15

376 Electronic Marketing PRPQ

Readers’ Comments — We’d Like to Hear from You
4680 Supermarket
Electronic Marketing Support PRPQ: User’s Guide

Publication No. SC30-3547-01

Overall, how satisfied are you with the information in this book?

Very Satisfied Satisfied Neutral Dissatisfied Very Dissatisfied

Overall satisfaction h h h h h

How satisfied are you that the information in this book is:

Very Satisfied Satisfied Neutral Dissatisfied Very Dissatisfied

Accurate h h h h h
Complete h h h h h
Easy to find h h h h h
Easy to understand h h h h h
Well organized h h h h h
Applicable to your tasks h h h h h

Please tell us how we can improve this book:

Thank you for your responses. May we contact you? h Yes h No

When you send comments to IBM, you grant IBM a nonexclusive right to use or distribute your comments in any
way it believes appropriate without incurring any obligation to you.

Name Address

Company or Organization

Phone No.
 ___________________________________________________________________________________________________
Readers’ Comments — We’d Like to Hear from You Cut or Fold
SC30-3547-01 IBM Along Line

_ _ _ _ _ _ _Fold
_ _ _ and
_ _ _Tape
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _Please
_ _ _ _ do
_ _ not
_ _ _staple
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _Fold
_ _ _and
_ _ Tape
______

PLACE
POSTAGE
STAMP
HERE

IBM Corporation
Design & Information Development
Dept. CJMA/Bldg. 645
P.O. Box 12195
Research Triangle Park, NC
27709-9990

________________________________________________________________________________________
Fold and Tape Please do not staple Fold and Tape

Cut or Fold
SC30-3547-01 Along Line