======================================================= IBM Retail Application Release 1.3 Refresh 5 README ======================================================= TABLE OF CONTENTS: 1.0 Dual Currency support 2.0 Change to spawning from OPOS.EXE and IPOS.EXE 3.0 Language file modifications for RA V1.03.05 ------------------------------------------------------ 1.0 Dual Currency support Overview -------- RA V1.03.05 includes new support for two currencies at the same time. This support will be useful for the new Euro currency which will be introduced in 1999 as well as any stores that border on two countries and would like to accept currency from both countries. The new dual currency support is not simply an enhancement of the RA foreign currency support that has always existed within RA. The RA Dual Currency support involves the following new functionality: Dual Currency Configuration --------------------------- There is a new menu option on the IPOS POS PERSONALIZATION MENU for the dual currency configuration program. The dual currency configuration is stored in the file DUALCURR.CFG. A dual currency configuration will define the Primary Currency for the store and the Alternate Currency for the store. The primary currency is still used for all statistical reporting. The alternate currency will be reported separate from the primary currency on tender related reports. There are 3 possible modes for dual currency: 1. OFF - Dual currency is not used. The application functions, screens, and reports do not change. 2. FOREIGN ONLY - Dual currency is only used for foreign currency conversions from foreign to alternate currency and from alternate to primary currency. The application functions, screens, and reports do not change. 3. ON - Dual currency is used. The application functions. screens, and reports will change to support dual currency functions. The dual currency configuration includes the following personalization options for both the primary and alternate currency: - currency description - currency prefix 3 characters that will display/print before the amount to differentiate the two currencies from each other - currency symbol 1 character symbol that will display/print before the amount to differentiate the two currencies from each other. If the currency symbol is defined, then the symbol is used in place of the prefix. If the symbol is not available then the 3 character prefix is used, - ISO currency id This is the ISO standard code for the currency. This field is not used directly by RA. It is logged to the tlog for use at the home office. - Exchange rate This is the exchange rate in relationship to the other currency. For example, if you enter an exchange rate on the primary currency personalization screen then you are stating the exchange rate of the primary to the alternate. If you enter an exchange rate on the alternate currency personalization screen then you are stating the exchange rate of the alternate to the primary. Only one exchange rate is used. If an exchange rate is specified for both currencies, then the alternate currency exchange rate is always used for currency conversions regardless of whether the conversion is from primary to alternate or alternate to primary. The decimal point must be manually entered in the exchange rate field. The dual currency configuration includes the following personalization options for the alternate currency only: - The ability to define, by tender type, whether the alternate currency is acceptable as a tender payment, tender refund, both, or neither. In addition, the alternate currency cash tender can be configured to be a valid option for change due back to the customer in a sale transaction. The primary currency does not have these configuration options. The primary currency is always assumed to be valid for payment, refund and cash or store credit change. The menus for selecting the valid tender types for the alternate currency for payments and refunds will show all 16 tender types. However, if a tender type is selected as valid for alternate currency and this tender type has not been configured for the primary currency via the RA tender keyboard configuration, then the tender type will still not be available for the alternate currency because there is no tender key defined for the tender type. There is an additional dual currency configuration option for SWAP UTILITY WILL CONVERT PLU PRICES. This configuration option is explained in more detail below in the section describing the dual currency swap utility program. Foreign Currency changes for Dual Currency ------------------------------------------ There are no changes to RA foreign currency support when Dual Currency is set to OFF in the Dual Currency Configuration. If Dual Currency is set to FOREIGN or ON, then the foreign currency configuration table will change on the foreign currency configuration screen. A new field will be added for each currency to indicate which of the dual currencies (primary or alternate) that the foreign currency exchange rate is specified. This setting will be used by RA to convert from the foreign currency to the primary currency for POS transactions and reporting. For example, if you have a foreign currency "C" which has exchange rate that is specified to the alternate currency "B", then RA will automatically perform a two step conversion to convert the foreign currency "C" into the primary currency "A". First, currency "C" will be converted to currency "B" based on the exchange rate in the foreign currency configuration for "C". Then, currency "B" will be converted to currency "A" based on the exchange rate in the dual currency configuration file. The process is reversed when a conversion is performed from the primary currency to the foreign currency. This new currency indicator on the Foreign Currency Configuration screen is stored in the dual currency configuration file DUALCURR.CFG. This design was chosen to avoid the need for an upgrade conversion program for the foreign currency configuration file CURRENCY.TBL. Denomination Table changes for Dual Currency -------------------------------------------- There are no changes to RA denomination table support when Dual Currency is set to OFF or FOREIGN in the Dual Currency Configuration. If Dual Currency is set to ON, then a menu is presented to the user to select the currency (primary or alternate) before the denomination table is displayed. There are no changes to the denomination table file. The denomination table information for the alternate currency is maintained in the new file DENOM2.TBL. Register POS checkout changes for Dual Currency ----------------------------------------------- There are no changes to the RA POS checkout screens or functions when Dual Currency is set to OFF or FOREIGN. When Dual Currency is set to on, the following POS checkout functions change: 1. Cashier item entry screen and tender screen layout The screens will display the primary and alternate currency amounts for the following: - TOTAL, AMT TENDERED, AMT DUE, CHANGE (touch POS displays the the AMT TENDERED in primary currency only) - LAYAWAY DEPOSIT amount - LAYAWAY BALANCE DUE on the layaway status report screen 2. Customer 2x20 The customer 2x20 will display the primary and alternate currency amounts for the following: - TOTAL, DUE TO/FROM CUST, and CHANGE 3. Receipt/Journal The receipt and journal will print the primary and alternate currency amounts for the following: - SUBTOTAL, TOTAL, TOTAL PAYMENT, and CHANGE (the currency that is used for CHANGE in the transaction is indicated on the receipt and journal with "**") - BALANCE DUE and NEW BALANCE for layaway transactions - Layaway payment schedule amount for layaway transactions In addition, the exchange rate between the primary and the alternate currency is always printed on the receipt for every transaction. 4. Menu for dual currency (primary or alternate) selection There is a new menu for dual currency selection when a tender type is selected that is valid for the alternate currency. The following prompts are affected: - Payment tender type If the alternate currency is valid as a payment tender for the tender type selected then the dual currency selection menu will appear after the tender key is pressed (if the tender type is a credit card, then the dual currency selection menu will not appear until after the credit card is swiped). The menu selection will prompt for the selection of the primary or alternate currency. To minimize cashier key strokes, the tender type key may be pressed a second time to quickly select the primary currency from the menu. - Refund tender type If the alternate currency is valid as a refund tender for the tender type selected then the dual currency selection menu will appear after the tender key is pressed (if the tender type is a credit card, then the dual currency selection menu will not appear until after the credit card is swiped). The menu selection will prompt for the selection of the primary or alternate currency. To minimize cashier key strokes, the tender type key may be pressed a second time to quickly select the primary currency from the menu. - Cash change to the customer If the alternate currency is valid for cash change then the dual currency selection menu will appear at the end of the transaction. This menu will provide the cashier with the ability to specify which currency is being given to the customer as cash change in the transaction. To minimize cashier key strokes, the CASH key may be pressed to quickly select the primary currency from the menu. - Store Credit change to the customer If the alternate currency is valid for store credit refunds, then the dual currency selection menu will appear at the end of the transaction. This menu will provide the cashier with the ability to specify which currency is being given to the customer as a store credit in the transaction. - Layaway Deposit Amount entry The dual currency menu for layaway deposit will prompt the cashier for the currency type that is to be used for the entry of the deposit amount. The purpose of this menu is to allow the cashier to be able to enter the amount of the layaway payment in either currency. This menu does not affect the dual currency selection menus which may appear during the selection of tenders. It is only used to interpret the currency type of the layaway deposit amount entry. - Return of Store Gift Certificate or Store Credit Certificate The dual currency menu will prompt the cashier for the currency type of the certificate that is being returned by the customer. This menu does not affect the dual currency selection menus which may appear during the selection of tenders for the refund. - On Account Payment Transaction The dual currency menu for On Account Payment will prompt the cashier for the currency type that is to be used for the entry of the payment amount. The purpose of this menu is to allow the cashier to be able to enter the amount of the on account payment in either currency. This menu does not affect the dual currency selection menus which may appear during the selection of tenders. It is only used to interpret the currency type of the on account payment amount entry. - Payin Transaction The dual currency selection menu will be used if the alternate currency is valid for cash (tender, refund, or change) - Pickup Transaction The dual currency selection menu will be used if the alternate currency is valid for the tender type chosen (tender, refund, or change if cash tender type is chosen). - Payout Transaction The dual currency selection menu will be used if the alternate currency is valid for cash (tender, refund, or change). - Cash a Check Transaction The dual currency selection menu will always be used to prompt for the currency type of the check to be cashed. The dual currency selection menu will be used again if the alternate currency is valid for cash (refund or change) to select the currency type of the cash to be given to the customer. This prompting is required to support a check cashing transaction where the check to be cashed is a different currency than the cash to be provided. For example, this prompting is required to support the cashing of a check where the check is in the alternate currency, but the cash for the check is to be given in the primary currency. 5. Credit/Check user exit processing There is a global variable called G->currencyType which can be used by the user exits during a credit/check authorization. This variable will have the value PRIMARY_CURRENCY or ALTERNATE_CURRENCY. The 2 values are #defines within DUALCURR.H and these values are automatically available to the user exits. This global variable will contain the currency type of the most recent tender used in a multi-tender transaction. This information can be used when necessary in a credit/check authorization process. 6. POS reports The tender section of the REGISTER REPORT, CASHIER REPORT, and STORE REPORT will include totals for the alternate currency tenders (assuming the alternate currency was used at the POS). 7. End of Day procedures - cash count If a cash count is performed, then the cash count will prompt for additional amounts including: - starting bank for the alternate currency if cash is valid for the alternate currency - alternate currency cash amounts if cash is valid for the alternate currency - alternate currency tender amounts other than cash for all tenders that are valid for the alternate currency The cash count report will include count detail and over/short information for the alternate currency as well as the primary currency. Back Office changes for Dual Currency ------------------------------------- There are no changes to the RA back office screens or functions when Dual Currency is set to OFF or FOREIGN. When Dual Currency is set to on, the following back office functions change: 1. Screen Inquiries The screen inquiry functions for REGISTER TENDER TOTALS and CASHIER TENDER TOTALS will include additional screens for the display of the alternate currency tender totals. 2. POS reports The tender section of the REGISTER REPORT and CASHIER REPORT will include totals for the alternate currency tenders (assuming the alternate currency was used at the POS). 3. End of Day procedures - cash count If a cash count is performed via the OPOS back office, then the cash count will prompt for additional amounts including: - starting bank for the alternate currency if cash is valid for the alternate currency - alternate currency cash amounts if cash is valid for the alternate currency - alternate currency tender amounts other than cash for all tenders that are valid for the alternate currency The cash count report will include count detail and over/short information for the alternate currency as well as the primary currency. 4. OPOSCURR.EXE This is a new back office utility which will prompt for the changing of the exchange rate between the primary and the alternate currency. It is provided so that a store manager can have the ability to change the dual currency exchange rate, but yet not have the ability to change any other dual currency configuration options. This program must be added to the OPOS menu system by the RA customer or business partner by using the CHGFILE/MAKEMENU utility. Night Operator changes for Dual Currency ---------------------------------------- There are no changes to the RA Night Operator reports when Dual Currency is set to OFF or FOREIGN. When Dual Currency is set to on, the following Night Operator reports change: 1. Register Report/Clear The tender section of the register report will include totals for the alternate currency tenders (assuming the alternate currency was used at the POS). 2. Cashier Report/Clear The tender section of the cashier report will include totals for the alternate currency tenders (assuming the alternate currency was used at the POS). TLOG file (SAxxxxx.NEW) changes for Dual Currency ------------------------------------------------- There are no changes to the SAxxxxx.NEW file when Dual Currency is set to OFF or FOREIGN. Please refer to the file RATLOG.TXT on disk 1 of the base install package for details on changes to the TLOG for dual currency support. The most recent version of this document can also be found in the documents section of the RA support web page at: \\www.raleigh.ibm.com\rds\ Tender/Sales file (SUxxxxx.NEW) changes for Dual Currency --------------------------------------------------------- There are no changes to the SUxxxxx.NEW file when Dual Currency is set to OFF or FOREIGN. When Dual Currency is set to on, two records are created in the SUxxxxx.NEW for each register close. The first record does not change. The second record will contain tender amount information for the alternate currency. The second record will have the same record layout as the first record as documented in Appendix G of the RA Planing and Installation Guide with two differences: 1. The amount/sign fields in location 015 - 190 will contain amounts for the alternate currency. 2. The data in location 191 - 735 will contain filler of all zeros. This area is reserved for future RA modifications. If dual currency is set to ON, the second record will always exist in the SUxxxxx.NEW file regardless of whether or not the alternate currency was used at the POS. Swap Utility Program for Dual Currency (SWAPCURR.EXE) ----------------------------------------------------- The swap utility program will be used primarily to support the conversion of the Euro from alternate currency to primary currency. The program can be run from the DOS command line or from a batch file in the \POS directory. Screen output from the program can be redirected to a file if desired by using the redirection available in DOS. The swap utility will convert all amount fields in the RA database from primary currency to alternate currency and it will then swap the primary currency and the alternate currency in the dual currency configuration file. Note that if the dual currency configuration option for SWAP UTILITY WILL CONVERT PLU PRICES is set to OFF, then the following amount fields will NOT be converted by the swap utility: PLU prices (including sale prices and incentive amounts) STYLE prices Promotional Event pricing Global pricing Changes to the above amount fields can be downloaded to the store in advance with records in the PLU.CHG file. When the swap utility runs, all files that are changed are backed up prior to the change in a directory called \POS\PRESWAP. In the event of an error during the swap process, all files from the PRESWAP directory are restored into the \POS directory automatically. The files in the PRESWAP directory are not deleted by the swap utility because they may need to be restored if a problem is later found with the conversions made by the swap utility. The files in the PRESWAP directory must be deleted by the RA customer after the swap is determined to be a success. 2.0 Change to spawning from OPOS.EXE and IPOS.EXE When the back office is executed, the initial program that is started is OPOS.EXE. As menu options are selected, OPOS.EXE will call other executable modules to perform various operations. This calling of other executable modules is known as "spawning". There is a significant amount of DOS memory overhead when a spawn occurs, and there can be insufficient memory available on a small number of RA configurations to support the amount of spawning that is performed by RA for certain menu options. To address this potential problem, OPOS.EXE and IPOS.EXE will now save some DOS memory to disk and then free that memory before they spawn to another program. This will allow for additional memory to be used by the spawned program. The DOS memory that is saved to disk is saved in a temporary file with the name RTSHxxxx.TMP where xxxx is a number starting with 0000 and incremented automatically to avoid conflict if multiple spawns occur on the same network. These temporary files will be deleted automatically as control is passed from the spawned program back to OPOS.EXE or IPOS.EXE. This process is completely transparent to the end user, but it was documented in this readme so that technical readers can be aware of the change. 3.0 Language file modifications for RA V1.03.05 Language files modified from V1.03.04 to V1.03.05 ------------------------------------------------- IPOSCURR.STR - new language prompt file IPOS02.M01 - added a menu option for DUAL CURRENCY CONFIGURATION Please refer to section 3.0 from the Refresh 4 README below for details on language file changes for previous refreshes of RA. ======================================================= IBM Retail Application Release 1.3 Refresh 4 README ======================================================= TABLE OF CONTENTS: 1.0 Documentation APARS included in this Refresh 1.1 IR37120 - DOCUMENT REVISION TO PLANNING AND INSTALLATION GUIDE THE DEAL RECORD NUMBER STARTING AND ENDING IN POSITION 162. 2.0 APARS that affect Retail Application documentation: 2.1 IR36983 - The capability of deleting items off a store created purchase order. 2.2 IR37594 - Documentation to revise the sales non taxable line for non- taxable/non merchandise needs to removed due to balancing issues. 3.0 Language file modifications for RA refreshes 4.0 Enhancements included in this Refresh 4.1 RS232 support for the IBM SureMark 4610 POS thermal printer 4.2 RS232 support for a barcode scanners 4.3 Support for 4695 integrated touch hardware 4.4 Double byte character set support ------------------------------------------------------ 1.0 Documentation APARS included in this Refresh 1.1 IR37120 - On page F-3 of the Planning and Installation Guild lists the DEAL RECORD NUMBER starting and ending in position 162. The actual position should be 153, before color, size and width. Each position for color, size and width should be increased by 1. 2.0 APARS that affect Retail Application documentation: 2.1 IR36983 - The capability of deleting items off a store created purchase order. FILE NAME: DE.CHG File DESCRIPTION: Home office transmission file for Inventory Management FILE TYPE: ASCII Record Type 01 - Header Record - Transaction The field for "Transaction type" in this record includes a new possible value of: 01 - Line item deletion on store created purchase order Record Type 02 - Detail Record Item - Transaction The field for "Transaction type" in this record includes a new possible value of: 01 - Line item deletion on store created purchase order. FILE NAME: SAXXXXX.NEW DESCRIPTION: DAILY TRANSACTION FILE ("TLOG") FILE TYPE: ASCII SEQUENTIAL STRING TYPE 96 - DATA ENTRY NOTIFICATION STRING The field for "Notification Type" in this string includes a new possible value of: 05 - PURCHASE ORDER DOCUMENT ITEM(S) DELETED If the Notfication Type is 5, then this Type 96 string will be followed by one or more Type 94 strings which will provide the specific items that were deleted from the Purchase Order document. STRING TYPE 94 - DATA ENTRY TRANSACTION DETAIL ITEM STRING The field for "New Transaction flag" in this string includes a new possible value of: 2 - host initiated item delete from a purchase order document 2.2 IR37594 - Documentation to revise the sales non taxable line for non- taxable/non merchandise needs to removed due to balancing On page 10-31 in the Guide to Operation the following revision is added. NON TAXABLE SALES The net amount of all items for which tax was not applied. This item is calculated as follows: Amt of non-taxable items on sales transaction + Amt of non-taxable items sold on exchange transactions + Amt of non-taxable items on a final layaway transaction + Amt of non-taxable items layaway partial pickup transactions - Amt of non-taxable items return transactions - Amt of non-taxable items returned on exchange transactions | Removed the non merchandise non taxable amount. 3.0 Language file modifications for RA refreshes Overview -------- The RA support team will start including the names of all string and menu files that are modified with each refresh. This list should make it easier to build RA update packages for specific customers. The modified language files must be be included with the update package to the customer or the RA application may not function properly. In typical RA installs there are 4 subdirectories for language files: String files: *.STR, *.220, *.PTR, MAKEFILE.ASC, CHGFILE.DAT \POS\STR ---> contains default (english) string files \POS\Lxxx where xxx is the country code that is used at the installation ---> contains country specific string files Menu files: *.M* \POS\MENU ---> contains default (english) menu files \POS\Mxxx where xxx is the country code that is used at the installation ---> contains country specific menu files The language files in the following lists should be updated in both the default (STR and MENU) subdirectories as well as the country specific (Lxxx and Mxxx) subdirectories. For additional detail on specific changes to each language file, please refer to the NLS.CHG file which is included with each refresh. Language files modified from V1.03.03 to V1.03.04 ------------------------------------------------- REGCFG.STR OPOS12.STR AUTOZ.STR Language files modified from V1.03.02 to V1.03.03 ------------------------------------------------- IPOS09.STR OPOS06.STR Language files modified from V1.03.01 to V1.03.02 ------------------------------------------------- None! Language files modified from V1.03.00 to V1.03.01 ------------------------------------------------- OPOSGP.STR OPOSGP.M01 OPOSGP.M02 OPOSGP.M03 UNMARK.M01 OPOS.M04 OPOS14.M03 SOD.STR EOD.STR UTIL.STR IPOS09.STR OPOS12.STR OPOS17.STR REGISTER.STR REGISTER.220 ZSTLSAL.STR ZSTLPRD.STR ZPLUPRD.STR DE.STR All Time and Attendance feature string and menu files! Language files modified from V1.02.04 to V1.03.00 ------------------------------------------------- MAKEFILE.ASC CHGFILE.DAT IPOSTCH.STR IPOSTCH.M01 IPOS02.M02 MENU.STR REGISTER.STR REGISTER.220 OPOS17.STR IPOS09.STR REGCFG.STR DE.STR DEFUNC.STR DE.M07 Language files modified from V1.02.03 to V1.02.04 ------------------------------------------------- OPOS06.STR OPOS14.STR Language files modified from V1.02.02 to V1.02.03 ------------------------------------------------- REGISTER.PTR OPOS05.STR OPOS06.STR OPOS14.STR OPOS17.STR DPTCLS.STR DE.STR ZREG.STR ZCASHIER.STR Language files modified from V1.02.01 to V1.02.02 ------------------------------------------------- REGISTER.STR REGISTER.220 Language files modified from V1.02.00 to V1.02.01 ------------------------------------------------- IPOSP07.STR REGISTER.STR REGISTER.PTR ZCASHIER.STR ZPROD.STR ZREG.STR ZSPSN.STR ZSPSNDPT.STR ZSUSPEND.STR ZZIPCODE.STR TM07.STR 4.0 Enhancements included in this Refresh 4.1 RS232 support for the IBM SureMark 4610 POS thermal printer The SureMark POS printer is now fully supported in POS register checkout via RS232 attached to COM1 or COM2 of a PC or POS register. This support includes changes to the REGISTER PERSONALIZATION screen in IPOS to allow the selection of the RS232 port as OFF, COM1, or COM2 for the SureMark printer (default is OFF). Port configuration is done automatically within the REGISTER.EXE program so there are no changes required to the AUTOEXEC.BAT to configure the port. All functions that are supported by RA on the SureMark in RS485 (POSSDOS) mode are now also supported in RS232 mode including document handling, franking, micr reading, check face printing and flipping. In addition, a cash drawer attached directly to the SureMark is also supported (the cash drawer is only supported in SureMarks that are RS232 attached). To support a cash drawer attached to the SureMark printer, you must personalize the RA IPOS PCCD PRINTER CASH-DRAWER PERSONALIZATION with: CODE 1: x ---> pulse width on time x 2 milliseconds CODE 2: y ---> pulse width off time x 2 milliseconds CODE 3: 0 CODE 4: 0 From IBM internal testing, an acceptable setting for these parameters appears to be: x = 50 y = 0 However, cash drawer pulse generation settings may vary for different cash drawers. Please refer to the SureMark user's guide and to the documentation provided with your cash drawer for additional details. Failure to set the cash drawer options properly could result in an early failure (burn out) of the cash drawer hardware. The SureMark printer is NOT supported by the Night Operator feature. This means that it is not possible to configure Night Operator to print 40 column reports to the SureMark printer. 4.2 RS232 support for a barcode scanners Barcode scanners are now supported in POS register checkout via RS232 attached to COM1 or COM2 of a PC or POS register. This support includes changes to the REGISTER PERSONALIZATION screen in IPOS to allow the selection of the RS232 port as OFF, COM1, or COM2 for the scanner (default is OFF). The DOS MODE.COM utility must be used in the AUTOEXEC.BAT to properly configure the port used by the scanner. This is due to the fact that different scanners may require different RS232 configurations. The scanner should be programmed to include an key scancode after the data to allow the item to be accepted into the transaction without requiring the key to be pressed on the keyboard. 4.3 Support for 4695 integrated touch hardware The 4695 integrated touch hardware is now supported with RA POS checkout in touch mode. 4.4 Double byte character set support Double byte character set support has been added to the RA Base and Night Operator feature. Although only Japanese DBCS has been tested with this new functionality, the following country codes and codepages should function properly: country country code code pages ------- ------------ ---------- Japan 81 932 or 942 China 86 1381 Taiwan 886 950 North Korea 850 949 South Korea 82 949 ======================================================= IBM Retail Application Release 1.3 Refresh 3 README ======================================================= TABLE OF CONTENTS: 1.0 Documentation APARS included in this Refresh 1.1 IR36288 - DOCUMENT REVISION TO ADD A SALES NON-TAXABLE LINE FOR NON-TAXABLE/NON-MERCHANDISE 2.0 APARS that affect Retail Application documentation: 2.1 IR36561 - ADD SUPPORT FOR DISPLAYING, PRINTING AND LOGGING THE ALTERNATE PLU NUMBER IN POS CHECKOUT. 2.2 IR36856 - ADD SUPPORT FOR DISPLAYING OF PLU LIST ON CHANGE PLU AND DELETE PLU OPERATIONS IN OPOS. ------------------------------------------------------ 1.0 Documentation APARS Included in this Refresh 1.1 IR36288 - On page 10-31 in the Guide to Operation the following revision is added. NON TAXABLE SALES The net amount of all items for which tax was not applied. This item is calculated as follows: Amt of non-taxable items on sales transaction + Amt of non-taxable items sold on exchange transactions + Amt of non-taxable items on a final layaway transaction + Amt of non-taxable items layaway partial pickup transactions - Amt of non-taxable items return transactions - Amt of non-taxable items returned on exchange transactions | Amt of non-taxable items sold non merchandise transactions + 2.0 APARS that affect Retail Application documentation: 2.1 IR36561 - ADD SUPPORT FOR DISPLAYING, PRINTING AND LOGGING THE ALTERNATE PLU NUMBER IN POS CHECKOUT. A personalization option has been added in IPOS to turn on a new function of the REGISTER program that allows for the display, print, and log of the alternate PLU number instead of the primary PLU number if the alternate PLU number is used to enter an item. Item entry using the alternate PLU number will result in the alternate PLU number being displayed on the item list on the screen, printed on all receipts, and logged to the TLOG in the SKU/CLASS field of the S01 string. In addition, if the alternate PLU number is logged to the TLOG, the SKU/CLASS INDICATOR field of the S01 string will contain a new value of 2 to indicate that the entry in the SKU/CLASS field is an alternate PLU number. Values for SKU/CLASS INDICATOR field: 0 = SKU 1 = CLASS 2 = ALTERNATE SKU <----- NEW! Restrictions: The RA color, size, and width functions cannot be used together with this new alternate PLU function. If the new alternate PLU function is not used, then the color, size, and width functions remain unchanged from previous refreshes of RA. Also, if the new alternate PLU function is used, the LENGTH ALTERNATE KEY value in PRICE MANAGEMENT PERSONALIZATION in IPOS must be greater than 3. 2.2 IR36856 - ADD SUPPORT FOR DISPLAYING OF PLU LIST ON CHANGE PLU AND DELETE PLU OPERATIONS IN OPOS. A complete PLU listing can now be displayed on the screen during PLU Maintenance operation in OPOS. This list is displayed by pressing on the CHANGE PLU or DELETE PLU screens in OPOS. ======================================================= IBM Retail Application Release 1.3 Refresh 2 README ======================================================= TABLE OF CONTENTS: 1.0 Documentation APARS included in this Refresh 1.1 IR34980 - DOCUMENTATION REGARDING WHAT NEEDS TO BE ACTIVATED BEFORE RETRIEVING A SUSPENDED TRANSACTION TO BE UPDATED. 2.0 APARS that affect Retail Application documentation: 2.1 IR34190 - SUREONE POS PRINTER SOMETIMES PRINTS GARBAGE AT THE END OF THE STORE CLOSING REPORTS. IMPORTANT: Changes to the AUTOEXEC.BAT on a SureOne are --------- required for this refresh! 2.2 IR35930 - IF A SUREONE DOS SERVER EXPERIENCES A POS PRINTER PROBLEM, THE SERVER STOPS SERVICING THE NETWORK UNTIL THE PRINTER PROBLEM IS CORRECTED. IMPORTANT: Changes to the AUTOEXEC.BAT on a SureOne are --------- required for this refresh! 3.0 Other Notes 3.1 Updated version of FMICRU.FMT ------------------------------------------------------ 1.0 Documentation APARS Included in this Refresh 1.1 IR34980 - On page 4-56 in the Guide to Operation the following revision is added. NOTE: Retrieving a suspended transaction requires the following functions be active: Preferred Customer, Layaway, Return, Tax Override and Employee Purchase. 2.0 APARS that affect Retail Application documentation: 2.1 IR34190 - SUREONE POS PRINTER SOMETIMES PRINTS GARBAGE AT THE END OF THE STORE CLOSING REPORTS. 2.2 IR35930 - IF A SUREONE DOS SERVER EXPERIENCES A POS PRINTER PROBLEM, THE SERVER STOPS SERVICING THE NETWORK UNTIL THE PRINTER PROBLEM IS CORRECTED. IMPORTANT: The APARS that address the SureOne POS printer problems require the MODE command in the AUTOEXEC.BAT of the SureOne to be changed. Previously, MODE was used to setup the printer (COM3) and the 2x20 display (COM4) as follows: C:\DOS\MODE COM3:96,N,8,1,P C:\DOS\MODE LPT1=COM3 C:\DOS\MODE COM4:96,N,8,2 With this refresh, the MODE command MUST be changed in the AUTOEXEC.BAT as follows: C:\DOS\MODE COM3:96,N,8,1 C:\DOS\MODE COM4:96,N,8,2 Note that we are no longer using the P (retry) parameter on the MODE command for COM3. Also, note that we do not redirect the printer output from LPT1 to COM3. In this refresh level, the print lines are sent directly to the printer (COM3). There is no change to the MODE command for the 2x20 (COM4). 3.0 Other Notes 3.1 Updated version of FMICRU.FMT The check micr parsing table FMICRU.FMT has been updated with additional micr formats to support additional checks. Please contact IBM support if you have any other micr formats that should be added to the table or if you discover that a specific micr format is being interpreted incorrectly by the table. ======================================================= IBM Retail Application Release 1.3 Refresh 1 README ======================================================= TABLE OF CONTENTS: 1.0 Documentation APARS included in this Refresh 1.1 IR33578 - Layout of IFXXXXX.NEW File is non-specific. 1.2 IR33501 - Package key documentation needs to be updated in the Planning and Installation Guide. 2.0 Enhancements included in this Refresh 2.1 Electronic Journal Search and Print current and archived EJ files 2.2 Store (All registers) Statistics and Tender Reporting 2.3 Global Pricing Maintenance in OPOS 2.4 Touch Enablement of SOD (Start of Day) and EOD (End of Day) 2.5 New User Exits for Touch POS 2.6 Support for add or change in PLU.CHG for PLUs, Styles, Depts, Classes 2.7 Time and Attendance Enhancements 2.8 Fractional Quantity Sales Support 2.9 Layaway Initialization Fee Taxability 2.10 Customer Name Address Block Suppression on Credit Card Transactions 2.11 PC Printer support on the register in non-PCCD mode 3.0 Other Notes 3.1 NT DOS 4694 Client setup instructions 3.2 Comments concerning Offline Mode 3.3 Problems with the SureOne POS keyboard 3.4 New printer station for Receipt and Electronic Journal ------------------------------------------------------ 1.0 Documentation APARS Included in this Refresh 1.1 IR33578 - Layout of IFXXXXX.NEW File is non-specific. Changes made to Appendix D page 1 of the Release 3 Planning and Install Guide add additional information below Action Codes. FILE NAME: IFxxxxx.NEW DESCRIPTION: DAILY TRANSACTION FILE FILE TYPE: ASCII SEQUENTIAL DESCRIPTION BYTES LOCATION STORE NUMBER 5 001 - 005 ACTION CODE 2 006 - 007 EMPLOYEE NUMBER 9 008 - 016 LAST NAME 18 017 - 034 FIRST NAME 12 035 - 046 ADDRESS 1 30 047 - 076 ADDRESS 2 30 077 - 106 CITY 16 107 - 122 STATE 20 123 - 142 ZIP CODE 10 143 - 152 HOME PHONE 12 153 - 164 EMERGENCY PHONE 12 165 - 176 EMERGENCY CONTACT 24 177 - 200 US CITIZEN 1 201 - 201 (YN) ID TYPE 1 30 202 - 231 ID TYPE 2 30 232 - 261 SOCIAL SECURITY NUMBER 9 262 - 270 WORK STATUS 1 271 - 271 NORMAL WORK HOURS 3 272 - 274 99V9 SALARY TYPE 1 275 - 275 WBMH SALARY RATE 7 276 - 282 9(5)V99 SEX 1 283 - 283 MF MARITAL STATUS 1 284 - 284 BIRTH DATE 6 285 - 290 MMDDYY DEPENDENTS 2 291 - 292 START DATE 6 293 - 298 MMDDYY JOB CLASS 5 299 - 303 TERMINATION DATE 6 304 - 309 MMDDYY ACTION CODE: 1 - NEW EMPLOYEE RECORD 2 - CHANGED EMPLOYEE RECORD 3 - TERMINATION RECORD SALARY TYPE: | 1 - (W)eekly | 2 - (B)i-weekly | 3 - (M)onthly | 4 - (H)ourly 1.2 IR33501 - Package key documentation needs to be updated in the Planning and Installation Guide. The Planning and Installation Guide, page 2-20 needs to be changed for the Package Key. The Guide indicates that the individual item prices will not print; only the package price total will print, however, the individual package prices will print on the receipt. 2.0 Enhancements included in this Refresh 2.1 Electronic Journal Search and Print current and archived EJ files Overview -------- The Electronic Journal is a digitized copy of the hardcopy receipt tape, and provides the store manager with a means of easily storing, retrieving, searching, and reviewing sales transactions. Each register has its own electronic journal, and a new electronic journal is created whenever the Start Of Day date for the register changes. Superseded electronic journals are archived for a limited period of time on the harddisk. The archival period is set by the value entered in the NUMBER OF DAYS TO SAVE DETAIL option found in the SYSTEM PERSONALIZATION menu in IPOS. An archived electronic journal is retrieved by entering the Start Of Day date (not necessarily the actual calendar date) in effect when the electronic journal was created. Operating the Electronic Journal -------------------------------- The Electronic Journal is accessed through OPOS, and the Startup Screen appears as shown below. ELECTRONIC JOURNAL +--------------------------------------+ | | | ENTER REGISTER NUMBER | | (PRESS FOR ALL): ___ | | | | | | ENTER DATE TO SEARCH | | (PRESS FOR TODAY): | | | +--------------------------------------+ The user either enters nothing on the first line to select all journals matching the date, or enters a single register number. Pressing on the Enter Date To Search line defaults to the date of the last Start Of Day. Following the Startup Screen the Navigation Screen is displayed, as shown below. The navigation controls are in the box on left, and the journal itself is displayed on the right. ELECTRONIC JOURNAL +-------------------------+ REGISTER #001 02-18-97 ALL | 1. PAGE UP | +----------------------------------------+ | 2. PAGE DOWN | | Crescent Wrench 15.00 | | 3. LINE UP | | 000000000005 | | 4. LINE DOWN | | Ladder 95.00 | | | | 000000000006 | | 5. TOP OF FILE | | Screwdriver Set 55.00 | | 6. END OF FILE | | 000000000005 | | 7. MARK | | | | | | TOTAL 165.00 | | 8. FIND TRANS NUMBER | | AMOUNT TENDERED | | 9. FIND SALESPERSON | | Cash 165.00 | | 10. FIND CASHIER | | | | 11. FIND OTHER | | | | | | TOTAL PAYMENT 165.00 | | 12. REPEAT LAST FIND | | RETAIL APPLICATION/DOS | | 13. NEXT REGISTER | | IS THE SOLUTION | | 14. SEARCH CURRENT/ALL | | FOR SPECIALTY STORES AROUND THE WORLD | | | | #773 02-18-97 04:12P JANE | | SELECT OPTION: __ | | | +-------------------------+ +----------------------------------------+ PRESS TO EXIT CURRENT LINE: 2 Most of the navigation controls are self-explanatory. Page Up and Page Down move up or down one screen. Line Up and Line Down moves the display one row in either direction. Top Of File and End OF File moves to the beginning or end of the journal. Mark places a "start marked text" pointer on the top journal row currently displayed and places an "end marked text" pointer on the third-from-the-last row of the display. Text between the start and end rows, inclusive, are marked with highlighting. As the user navigates down in the file the "end marked text" pointer will move down as well, staying on the third-from-the- last row displayed . In this way the user can mark more text than can appear on screen at one time. After Mark is selected, the user may note that the word "MARK" changes to "UNMARK/PRINT...." By selecting UNMARK/ PRINT..., a menu is displayed which gives the choice of either unmarking or printing the highlighted text. Find Trans Number allows the user to enter a sales transaction number to find. Find Salesperson and Find Cashier are similarly used. Find Other allows the user to enter a string of characters to find in the journal. If the user selected ALL registers on the startup screen, there is the option of either limiting a search to the journal currently displayed or searching across all journals. When ALL is chosen, Next Register and Search Current/All will be displayed on the navigation screen as shown above. These entries are not displayed if a single register is entered on the startup screen. Next Register forces the next journal to display. Journals are sequenced in ascending numeric order. Following the last journal in the list, the first journal is displayed to begin the loop again. Search Current/All toggles the searches to either limit to the journal currently displayed or to span across all journals. An indicator in the upper right of the screen shows whether the search is in CURRENT or ALL. When Search Current is active, the search will begin at whatever journal line is shown at the top of the display. The search will continue to the end of the journal and then loop back to the beginning of the journal. A message PASSED END OF FILE is shown when the search wraps to the beginning of the journal. When Search All is active, the search will begin at whatever journal line is shown at the top of the display. The search will continue to the end of the journal and then begin searching the next journal in the ascending order list. When the end of file of the last journal in the list is passed, the search continues at the top of the first journal in the list. Note ---- When the SALESPERSON option is ON in IPOS, one salesperson is recorded for each sales transaction. If option SALESPERSON SAME ENTIRE TRANSACTION is OFF, the index file is not updated and the search for salesperson must be performed using the SEARCH OTHER selection in the electronic journal interface. 2.2 Store (All registers) Statistics and Tender Reporting The selection for a store level report (all registers) has been added to the report menu for REGISTER POS REPORTS and OPOS POS REPORTS. Also, a store report can be displayed on OPOS REGISTER TENDER TOTALS and OPOS REGISTER STATISTICS by pressing at the register number prompt to select all registers. A new personalization option has been added to the IPOS GENERAL PERSONALIZATION screen to allow for store level reporting during store closing. The store report (all registers or all cashiers) will be printed at store close instead of detail reports for each register or cashier. This report is available on a register close, OPOS close, or Night Operator close. Note that if you do a register cashout you will still get a report for each register as you cash the registers out. Also if you do a cashier cashout you will still get a report as you cash out each cashier. The difference occurs on the reports that follow. If you have the new option set ON and do a register cashout then you will only get an ALL CASHIERS report to follow instead of a detail report for each cashier. Likewise, if you do a cashier cashout, then you will get an ALL REGISTERS report to follow without a detail report for each register. 2.3 Global Pricing Maintenance in OPOS The Global Pricing function was introduced as a part of RA V1.03.00. The only method for creating global pricing events under V1.03.00 was by using the PLU.CHG file. For RA V1.03.01, there is a new OPOS menu option for Global Pricing Maintenance on the OPOS POS MANAGEMENT FUNCTIONS menu. This new program displays the current list of global pricing events and allows the user to perform a variety of functions including: 1. add, change, or mark for deletion a global pricing event record 2. create a PLU.CHG file from the current global pricing list 3. print the current global pricing list 4. perform the actual delete operation on all records marked for deletion The reason for marking records for deletion and then requiring the user to confirm the deletion of the marked records is so that the program can create global pricing "delete" records in PLU.CHG before the actual deletion is performed. This would not be possible if the records were physically deleted as they were selected from the global pricing list. All changes to the global pricing list take effect immediately on the PC which is running this maintenance program. In other words, the PLU.CHG created from this program does not need to be processed on the PC that created the PLU.CHG file in order for the global pricing events to be updated. The global pricing events on the PC running the maintenance program have already been updated. The purpose for the creation of the PLU.CHG file is to provide an easy mechanism to create global pricing change records at home office to be sent down to the stores. 2.4 Touch Enablement of SOD (Start of Day) and EOD (End of Day) The programs SOD.EXE and EOD.EXE that perform Start of Day and End of Day operations from a register have been enhanced to provide touch capability if the register number that is passed to the program is configured to run in touch mode. Please refer to TOUCH.DOC in the USER.EXE package on base disk 7 for additional information on RA Touch setup. 2.5 New User Exits for Touch POS Three new user exits have been added to INCUSER.C to provide user exit capability for the POS touch interface that was introduced in RA V1.03.00. Details on the new functions can be found in the function comment blocks in INCUSER.C. The functions have also been added to STUB103.C in the USER.EXE package on base disk 7 to allow for easier integration of the new functions into a copy of INCUSER.C that contains other modifications. 2.6 Support for add or change in PLU.CHG for PLUs, Styles, Depts, Classes For RA V1.03.00, additional functionality was added to UPDATPLU.EXE for processing PLU.CHG Price Management PLU or STYLE records. If a PLU or STYLE ADD record was encountered in PLU.CHG, the system will now determine if the PLU or STYLE already exists on file at the store. If the PLU or STYLE already exists, then the system will convert the ADD record to an CHANGE record and update the PLU or STYLE record appropriately. For RA V1.03.01, this functionality has been extended to Price Management DEPT and CLASS ADD records. If a DEPT or CLASS is already on file then the record will be converted to a CHANGE record. In addition, there is a file created by UPDATPLU.EXE called UPDATPLU.LOG. This file will contain error messages for any PLU CHANGE or PLU PLACE ON SALE records that were sent down in a PLU.CHG file where the PLU did not exist on file at the store. In this case, the PLU.CHG record for this PLU is bypassed. 2.7 Time and Attendance Enhancements RA V1.03.01 contains a new release of Time and Attendance with many enhancements. If you are upgrading from a previous level of Time and Attendance then there is a conversion program call TMUP2.EXE which you must run to convert the RA Time and Attendance data files. You must also re-install all language files for this new release. Language files from previous levels of Time and Attendance will NOT be upgraded to the new release and are NOT compatible with the new release. Please refer to the README.TIM on the V1.03.01 Time and Attendance install disk for additional information. 2.8 Fractional Quantity Sales Support This modification allows for all PLU and Style Reports which reference quantity sales from the item movement file to correctly reflect the sales of fractional quantity. This modification specifically does not address the other quantity fields (such as quantity on hand and quantity ordered) that are contained in the item movement file. Details ------- This modification will address 5 areas of change required for Retail Application to support the modification objectives: 1. Added personalization parameter which will allow the system to keep fractional quantity sales history. 2. The register check-out program now correctly updates quantity sales buckets with fractional quantities. 3. Several reports within the Store Operations program are changed so that fractional quantity sales are printed. 4. Several reports within the Night Operator program are changed so that fractional quantity sales are printed. 5. A conversion utility is being provided to convert existing item movement files to reflect fractional quantity sales. Fractional Sales Quantity Personalization Parameter --------------------------------------------------- There is an added parameter in the Retail Application personalization program to allow for the tracking of fractional quantity sales. The parameter is located in the Price Lookup/Management Options screen. The default for this parameter will be OFF which will indicate that the system will not update or print fractional quantity unit sales. Current installations that upgrade to this release of Retail Application must set this parameter to ON to begin updating the item movement file with fractional quantities. The current value of this parameter will be stored in the CLTCFG.DAT file. The text for this screen will be externalized in the IPOS09.STR file. Register Check-Out Changes -------------------------- The register check-out program REGISTER.EXE has been changed so that it will check the system personalization parameter described above. If the fractional quantity sales parameter is set to OFF then the system will continue to operate as currently functional. If the fractional quantity sales parameter is set to ON, then the system will update the three number of units sold fields (QTY_SALES) in the item movement file (MOVEMENT.DAT) with the total quantity for each item. Thus if the quantity of 1 was entered for the sale of an item then the QTY_SALES field would have a value of 1000 added. If a quantity of 1.25 was entered then a value of 1250 would be added. Returned and exchanged items will have the appropriate quantities subtracted from these fields. Store Operations Report Changes ------------------------------- All Store Operations reports which print the quantity sales have been changed so that they will check the system personalization parameter for fractional sales history. If this parameter is set to OFF the reports will print as currently functional. If the parameter is set to ON then the reports will print the quantity sales with 3 decimal place precision. Thus if the value of quantity sales for a particular line item is 45750 then the report will show quantity sales as 45.750. The following reports will be specifically changed as described above: - PLU Performance Report (Periods 1 though 3) - Gross Margin Report (Periods 1 though 3) - Style Sales Report (Periods 1 though 3) - Style Performance by Department/Class Report (Periods 1 through 3) Night Operator Report Changes ----------------------------- All Night Operator reports which print the quantity sales have been changed so that they will check the system personalization parameter for fractional sales history. If this parameter is set to OFF the reports will print as currently functional. If the parameter is set to ON then the reports will print the quantity sales with 3 decimal place precision. Thus if the value of quantity sales for a particular line item is 45750 then the report will show quantity sales as 45.750. The following reports will be specifically changed as described above: - PLU Performance Report (Periods 1 though 3) - Style Sales Report (Periods 1 though 3) - Style Performance by Department/Class Report (Periods 1 through 3) Conversion Utility ------------------ A conversion utility has been provided so that installations which are upgrading to this version of Retail Application and wish to use fractional quantity will have their current quantity sales updated for 3 decimal place precision support. A utility named QTY3DEC.EXE is provided which will multiply the value in each quantity sales field (QTY_SALES) in the item movement file MOVEMENT.DAT by 1000. Thus a value of 150 in these fields will be changed to 150000. When the utility is run it will first check to see if the Fractional Sales History parameter in CLTCFG.DAT is set to ON. If the parameter is set to OFF, the utility will exit with a DOS error level of 2. No records will be converted. If the parameter is set to ON, then the utility will read each record in the MOVEMENT.DAT file and update the quantity sales fields as described above. Upon successful completion, the application will exit with an error level of 0. If any errors are encountered during the conversion, the application will exit with an error level of 135. Making a backup of the MOVEMENT.DAT file before executing the conversion utility is highly recommended. 2.9 Layaway Initialization Fee Taxability There is a new personalization option in IPOS Layaway Personalization to specify a tax rate for the Layaway Initialization Fee. If a tax rate is specified, then the Layaway Initialization Fee is taxed at the specified rate during a Layaway Sale transaction. On a Layaway Cancel, the tax amount of the Layaway Initialization Fee, in addition to the layaway initialization fee itself, is also deducted from the amount refunded to the customer. The sales tax accounting fields are also updated to properly reflect the tax paid on Layaway Initialization Fees. 2.10 Customer Name Address Block Suppression on Credit Card Transactions There is a new personalization option in IPOS Credit Card/Check Personalization for suppressing the customer name/address block on credit card transaction. If this new option is set ON, then the name/address block will not print for any credit card transactions including refund transactions. 2.11 PC Printer support on the register in non-PCCD mode This enhancement allows the register program to run in IBM mode (not PCCD) but interact with a PC printer as if the register was in PCCD mode. This capability has been added to support such environments as the 4695 integrated touch display and the SurePoint Mobil computer with a belt printer. The function is activated by passing an additional parameter to the register program after the register number. The parameter is PCPRINT. A parameter was used instead of a personalization option because there is the possibility that the register needs to be able to change in and out of this mode dynamically to support the SurePoint Mobil computer environment where the computer may be docked at times and undocked at other times. 3.0 Other Notes 3.1 NT DOS 4694 Client setup instructions Setup instructions for an NT 4.0 server and 4694 NT DOS clients are provided in WINNT.DOC which is in the USER.EXE package on base disk 7. 3.2 Comments concerning Offline Mode Preparing a client with a local hard drive for offline mode ----------------------------------------------------------- In the RA base package, a file is provided called OFFDRIVE.INP. This file is used by the OFFDRIVE.EXE program which copies files from the server onto a register's local hard drive so the register is prepared for offline mode if the server fails. The example OFFDRIVE.INP which is provided contains commands for copying all files from the server's POS and DOS directories. This is a long process and probably not desirable in most situations. While a nightly full backup of the server's POS directory to ONE client with a hard drive is desirable, it should not necessarily be combined with the offline preparation that will occur for ALL clients with hard drives. An enhanced version of OFFDRIVE.INP has been provided in the USER.EXE package on base disk 7. This version of OFFDRIVE.INP copies only the required files to run REGISTER.EXE in offline mode on a client with a hard drive. Preparing an offline floppy for a client without a local hard drive ------------------------------------------------------------------- Due to the fact that the REGISTER.EXE program is not linked with RTLINK, the size of the program has grown significantly. This may cause problems when trying to create an offline floppy disk for use in a client without a hard drive because there may be insufficient room on the floppy to hold all required offline files. Here are some steps you can take to avoid this problem: 1. During the offline floppy creation, files from the \POSSDOS directory on the PC creating the floppy are copied into a \POSSDOS directory on the floppy. You can reduce the number of files copied onto the floppy by limiting the *.SYS driver files in the POSSDOS directory on the PC to only the driver files that are required for your specific register configuration. 2. You can take advantage of the RTLINK feature of compression. This will significantly reduce the file size of the REGISTER.EXE program. Please refer to the RA RTLINK response file RTLPRO.LNK in the USER.EXE package on base disk 7 and refer to the RTLINK documentation for more details on compression. 3.3 Problems with the SureOne POS keyboard There is a known problem with early SureOne POS keyboard controllers in specific environments that include Lantastic or other DOS peer to peer server programs. If you lose keystrokes on a SureOne POS in this environment, then you should upgrade the BIOS of the SureOne to version 6.18. This update will then allow you to view the SureOne keyboard controller level during the booting sequence. If your keybard controller level is 9 or below then you have 2 options to address your problem: 1. Contact IBM support for an updated keyboard controller. This is a hardware change and availability may vary depending on your support contract. 2. Download a copy of the utility called KBFLOW.EXE. This utility is available on a variety of WEB sites and BBS systems. You can find this TSR on the WEB by performing a search on KBFLOW.EXE. It can be found on some of the Novell support pages. KBFLOW.EXE is a DOS TSR which will address this keyboard problem by buffering keystrokes until they can be retrieved from the SureOne keyboard controller. If your keyboard controller level is 10 then you should not be experiencing this problem in the first place. 3.4 New printer station for Receipt and Electronic Journal To address some problems with the Electronic Journal, a new POS printer station was added to RA V1.03.01 called RECEIPT_EJ. This station will cause a print line to get printed on the printer receipt station and logged to the EJ. To maintain compatibility with user exits, the user_print_line() function will not see this new station. Instead, RA base will convert the RECEIPT_EJ station to RECEIPT_STATION before the call to user_print_line(). This will make the modification to the base application transparent to your user_print_line() user exit code. ============================================= IBM Retail Application Release 1.03.00 README ============================================= Please refer to the new Retail Application Release 3 publications for documentation changes that were included in this README for previous levels of Retail Application. See below for information on the Retail Application Support Home Page and additional notes on on Release 3 changes. TABLE OF CONTENTS: 1.0 IBM Retail Application Support Web Page 2.0 IMPORTANT additional Release 3 notes 2.1 RTLink support ordering information 2.2 Changes to installation package disks 2.3 Touch Checkout support 2.4 Sure Point Mobile Inventory Management support 2.5 Other notes Note - There are no APARS in this Refresh that affect Retail Application documentation. ------------------------------------------------------ 1.0 IBM Retail Application Support Web Page There is a support home page on the Web for IBM Retail Application as a part of the Retail & Distribution Solutions support pages. This page contains EFIX files, documents, and demo files for Retail Application. You can also request your Retail Application serial number on-line from this page. The URL for the Retail & Distribution Solutions support home page is: http://www.raleigh.ibm.com/rds/ From the Retail & Distribution Solutions home page you can select the support page for Retail Application. 2.0 IMPORTANT RELEASE 3 NOTES 2.1 RTLink support and ordering information The REGISTER.EXE program provided in this package has been built with the .RTLink(R) Plus V8.0 linker from Pocket Soft, Inc. (.RTLink is a registered trademark of Pocket Soft, Inc.) Extended and/or expanded memory is now required to run the REGISTER.EXE program. Please refer to the RTLINK.DOC provided on disk 1 of the base install package for important details on RTLink. Also, refer to README.USR in the user exit package for details on batch files that have been provided to build with the RTLink or Microsoft linkers. RTLink can be ordered directly from Pocket Soft at a discount for IBM Retail Application users. When you order RTLink you should indicate that you are an IBM Retail Application user to receive the discount. You may contact Pocket Soft directly by any of the following methods: E-Mail info@pocketsoft.com Voice 1-800-826-8086 (USA only) 713-460-5600 Fax 713-460-2651 Mail Pocket Soft, Inc. P.O. Box 821049 Houston, TX 77282-1049 USA 2.2 Changes to installation package disks 1. In previous base install packages for Retail Application, diskette 7 was strictly for user exit coding and batch file examples. Due to the increase in size of the application, diskette 7 now contains files that are required during base installation. In addition, diskette 7 still contains all files needed for user exit coding and sample batch files. However, these files have been ZIPPED into a self extracting EXE file called USER.EXE on diskette 7. You can simply copy USER.EXE from diskette 7 into your development directory and execute USER.EXE to extract all user exit support files and sample batch files. 2. Now that the REGISTER.EXE program uses RTLink it is possible to create one version of this program for use with and without Promotional Events. The REGISTER.EXE program in the base install package now supports Promotional Events. There is no longer a REGISTER.EXE on the Promotional Events Feature install package. The promotional events object file INCEVENT.OBJ is now included with the other base object files. There is no longer an OBJ\INCUSER.OBJ on the Promotional Events Feature install package. Of course a serial number with Promotional Events active is still required for Promotional Events to function. In addition, the REGISTER.EXE program on EFIXs for Release 3 or later will also support Promotional Events. There will no longer be a file called REGISTER.PRO on EFIXs for Release 3 or later. 2.3 Touch Checkout support Touch-screen capability added in this release requires special setup to operate. Steps on setup are described in the TOUCH.DOC file in the user package on disk 7 of the base install package. More extensive documentation is available in the Planning and Install Guide. 2.4 Sure Point Mobile Inventory Management support There is a main menu utility included in the Inventory Management Feature install package which can be used with Sure Point mobile installations to select various Sure Point docked and undocked functions. The required files are PENRAD.BAT, PENRAD.DAT, and PENRAD1.EXE. The menu is invoked by typing PENRAD at the \POS DOS command prompt. 2.5 Other notes 1. There is a new user exit for release 3 called user_switch_task(). This user exit is called constantly many times per second and can be used when you need to check for a specific condition at all times when the register is running. You should be careful when adding code to this user exit since performance can suffer because the user exit is called so often. Please refer to the function notes in incuser.c for more detail on the user exit. 2. User space has been documented in the plu record. The space can be used to store customer specific data for each PLU. See PLU.H for details. 3. When using Windows NT for Retail Application back office and ISP programs, the CONFIG.NT file must be modified by changing the FILES statement to FILES=100. 4. When using the new local backup summary journal function of release 3 with a SureMark POS printer or SureOne POS terminal, the local file is created on the current directory of the C: drive on the client. Therefore, before you change to the LAN drive on a client, you should ensure that the current directory of the client's C: drive is set to where you want the local file to be created. The naming convention of the local file is as follows: LJ_0x.yyy where x is the day of week (Sunday = 1, Monday = 2, etc.) and yyy is the register number. The local files are stored for 7 days. No maintenance of these files is required. They are automatically cleared by the register program when they are over 7 days old. 5. When using the new buffered clean receipt function of release 3 the following limitations will apply: - Line item discounts are always printed by dollar amount on the receipt even if the discount was given by percentage. - Split/at/for items will print the correct price but will not print the split/at/for detail on the receipt. 6. When using the new post item modify function of release 3 the following limitations will apply: - The post modify QUANTITY option will not be available if an employee or preferred customer discount has been applied to the item. ======================================================= IBM Retail Application/DOS Release 1.2 Refresh 4 README ======================================================= TABLE OF CONTENTS: 1.0 Documentation APARS included in this Refresh 1.1 IR32600 - Documentation to expand on the sales tax analysis table section of the RADOS Planning and Installation Guide. ------------------------------------------------------ 1.0 Documentation APARS Included in this Refresh 1.1 IR32600 - Planning and Installation Guide, Page: 3-51 What Prints To The Sales Tax Analysis Table: - Multiple Tax Rates assigned to items. - Tax override codes - Items assigned to .00% taxrates Facts About The Sales Tax Analysis Table: - The sum of the taxable amount in the analysis table will equal the subtotal. - Penny breakage will be added to the last item on the analysis table - The sum of the tax amounts will equal the sales tax field on the receipt. Sales Tax Analysis and Layaway: - The sales tax analysis table will print to the New Layaway and Partial Pickup receipt or only where this is item detail. Additional Information: Function Priority: When tax override and tax exempt are used in a transaction which ever function is engaged last will be the resident procedure used. ======================================================= IBM Retail Application/DOS Release 1.2 Refresh 3 README ======================================================= TABLE OF CONTENTS: 1.0 Updates for the SureOne 4614 2.0 Language upgrade from previous Retail Application refreshes 3.0 New updated IBM Redbook available ------------------------------------------------------ 1.0 Updates for the SureOne 4614 1.1 Appendix Q Hardware Information 10 Easy Steps to IBM Retail Application on SureOne -------------------------------------------------- 1. The SureOne is a PC Cash drawer (PCCD) solution at heart so most setup issues that apply to a PCCD install will also apply to the SureOne. This includes setting up a PC keyboard layout under IPOS keyboard configuration. 2. The SureOne hardware settings should be set to default except that on the first settings screen, only track 2 of the MSR should be enabled. The hardware settings on a SureOne are displayed/changed by pressing F2 during system startup. 3. Here is an example of a CONFIG.SYS for a standalone SureOne POS: DEVICE=C:\DOS\HIMEM.SYS DOS=HIGH FILES=100 BUFFERS=30 4. Here is an example of an AUTOEXEC.BAT for a standalone SureOne POS: SET PATH=C:\DOS SET TEMP=C:\DOS | REM ** C:\DOS\MODE COM3:96,N,8,1,P | REM ** C:\DOS\MODE LPT1=COM3 | C:\DOS\MODE COM3:96,N,8,1 C:\DOS\MODE COM4:96,N,8,2 C:\DOS\SHARE /F:8000 /L:200 REM Load SMARTDRV with NO write caching REM /X is a parameter for SMARTDRV on PC DOS 6.3 or PC DOS 7.0 C:\DOS\SMARTDRV /X 5. The REGISTER WILL RUN AS PC CASH DRAWER option under REGISTER PERSONALIZATION in IPOS should be set to ON. 6. The FAST-FEED PERSONALIZATION under PRINTER PERSONALIZATION (PCCD) in IPOS should have LINES TO FEED set to 8 or higher. No other fields on the screen are required. 7. The CASH-DRAWER PERSONALIZATION under PRINTER PERSONALIZATION (PCCD) in IPOS should have the first CODE set to 28. All other codes on the screen should be blank. 8. If you want the application to detect when the cash drawer is open and prompt for closure, then you will need to set CASH DRAWER COMPULSION under GENERAL PERSONALIZATIONS in IPOS to ON. This option may not work on non-IBM cash drawers. 9. The messaging on the SureOne 2x20 including the "scrolling", "stationary", or "blinking" message is handled in the same manner as on the IBM 4694 via the MESSAGES personalization option in IPOS. 10. The manager key on the SureOne is handled in the same manner as the manager key on the IBM 4694. The use of the manager key is controlled via the MGR AUTHORIZATION PERSONALIZATION in IPOS. Position 1 of the key lock is the "normal" position. Position 2 of the key lock is the "manager" position. 2.0 Language upgrade from previous Retail Application refreshes This refresh of RA/DOS will upgrade your language files from Retail Application V1.02.00. If you are upgrading from a level of Retail Application older than V1.02.00 then you will need to reinstall the language files with the Retail Application language support utility (LANGUAGE.EXE). 3.0 New updated IBM Redbook available There is a new updated IBM Redbook available which contains new information on OS/2 (Warp) installations including LAN Server 4.0. There is also information on the mirroring solution NoStop. This publication provides additional information on installing Retail Application in various LAN environments and under a DOS partition of OS/2 on 4694 hardware. This publication was created in response to the many questions that have been raised in this area. It would be beneficial for you to order a copy. This document will be updated in the future as necessary. The title of the publication is IBM Retail Application/DOS LAN Guidelines. The IBM publication number is SG24-4343-01. ======================================================= IBM Retail Application/DOS Release 1.2 Refresh 2 README ======================================================= TABLE OF CONTENTS: 1.0 Documentation APARS included in this Refresh 1.1 IR29945 - Calculation breakdown for pricing in the Promotional Event feature. 2.0 APARS that affect Retail Application documentation: 2.1 IR29902 - In creating offline diskettes, the C drive is hard- coded into the program in the call to format the floppy 3.0 New language translation for Spain ------------------------------------------------------ 1.0 Documentation APARS Included in this Refresh 1.1 IR29945 Calculation breakdown for pricing in the Promotional Event feature. Understanding the Daily Transaction File ("TLOG") ------------------------------------------------- The discounts given on a transaction are shown in the event giveback string (string type 97). In all cases, this is the only place where the discount amount is shown. Therefore, the item string (string type 01) never reflects a discount given because of a promotional events discount. There is an event giveback string produced for each item which receives a promotional events discount or if a system wide event is executed. This means that if multiple discounts occur on a transaction, multiple event giveback strings will be produced. The following are examples of the way Daily Transaction File strings would appear for the deal examples shown on pages 5-1 through 5-6 of the Promotional Events Feature User's Guide: Price Substitution Example: --------------------------- In this case, the item string (string type 01) would show the item at its full price of $10.00. There would be one event giveback string produced showing PLU number 1111 received a discount of $2.00. Buy Quantity X, Get Y Free Example: ----------------------------------- In this case the item strings would show the items at their full price of either $10.00 or $9.00 depending upon whether item 1111 or item 2222 was sold. Since the benefit quantity was specified to be 1, then only 1 event giveback string would be produced, showing the discount to be either $10.00 or $9.00 depending upon the item which was discounted. Note that if the benefit quantity was greater than 1, the system would produce and event giveback string for each item receiving a discount. Buy Quantity X, Get Y% Off One of Them Example: ----------------------------------------------- Again, the item strings would show the items at their full price of either $10.00 or $9.00 depending upon whether item 1111 or item 2222 was sold. There would only be 1 event giveback string produced for either $5.00 or $4.50 depending upon which item received the discount. Buy Quantity X for Y Example: ----------------------------- As in previous examples, the item strings would show the items at the full price of $10.00. However, because this type of deal is unique in that it does not specify an item or items to receive the discount, the discount is spread against all items in the deal. Therefore, 2 event giveback strings would be produced, each for item 1111 with a discount amount of $1.25 for each item. It should be noted that the amount of discount for each item is calculated by taking the total amount of the discount and dividing it by the number of items receiving a discount. The system does not "weight" the discount by determining the relative value of the item in the deal. Therefore, even if the items in the deal have different price points, they will receive the same discount amount. Trigger/Target Example: ----------------------- This example would show item string for PLU 1111 and 2222 at the full price of $10.00 and $9.00 respectively. A single event giveback string for PLU 2222 in the amount of $8.00 would be produced to reflect the discount. System-Wide Percent Benefit Example: ------------------------------------ In this example a single event giveback string would be produced. The event giveback string would have the item number field blank filled because a system wide event does not apply discounts to specific line items. The amount of the discount would be equal to 10% of the transaction before tax is applied. System-Wide Dollar Benefit Example: ----------------------------------- In this example a single event giveback string would be produced. The event giveback string would have the item number field blank filled because a system wide event does not apply discounts to specific line items. The amount of the discount in the event giveback string would be $5.00. 2.0 APARS that affect Retail Application documentation: 2.1 IR29902 In order to create offline diskettes the drive being used must contain a DOS directory. 3.0 New language translation for Spain Previous levels of Retail Application used the same string translation for both Latin America and Spain. We have recently had a translation performed specifically for Spain. This means that the Latin America translation and the Spain translation are no longer the same. If you want to use the new Spanish translation, you will need to install the translation files via the LANGUAGE utility for country 034 (Spain). ======================================================= IBM Retail Application/DOS Release 1.2 Refresh 1 README ======================================================= TABLE OF CONTENTS: 1.0 APARS that affect RA/DOS documentation: 1.1 IR28325 - In Employee Purchase and Preferred Customer Transactions, discounts are taken off the current price, regardless of whether current price or original price is greater. 1.2 IR29153 - A Partial Pickup Layaway generates two transaction numbers that both can be post voided. ------------------------------------------------------ 1.0 APARS that affect RA/DOS documentation: 1.1 IR28325 During Preferred Customer or Employee Purchase transactions, the application will not apply a discount to the original price field. The discount will always be applied to the current price regardless of whether the current price is less than, greater than, or equal to the original price. This occurs only if the personalization switch for OFF CURRENT PRICE for the employee file and OFF SALE PRICE for the preferred customer file are OFF. 1.2 IR29153 A Partial Pickup Layaway generates two transaction numbers, both of which can be post voided. Once a post void of one of the transaction numbers is processed, the application writes the post voided transaction plus the second partial pickup transaction number to the PV.IX1 file. When attempting to post void the second partial pickup transaction number, the application flags an error message that PICKUP HAS BEEN POST VOIDED. ======================================================================= IBM Retail Application/DOS 1.02.00 README ======================================================================= Please refer to the new Retail/DOS Release 2 publications for all documentation changes that were included in this README for previous levels of Retail/DOS. See below for additional information on DOS errorlevel changes, installation, language support, new LAN installation guide, and compiler support. The README.USR on base install disk 7 provides information for first time user exit coding as well as information on new release 2 user exit migration for programmers who have coded user exits on a previous level of Retail/DOS. ======================================================================= DOS ERRORLEVEL changes for Release 2 ======================================================================= The DOS batch file errorlevel return codes have been changed for Retail/DOS release 2. The purpose for this change was to stop the use of the undocumented ability of DOS to allow errorlevels greater than 255. This change also was needed for support of Retail/DOS in the DOS partition of OS/2. The change to the errorlevels is as follows: OLD ERRORLEVEL NEW ERRORLEVEL -------------- -------------- 999 231 907 139 906 138 905 137 904 136 903 135 902 134 901 133 900 132 All other errorlevels are unchanged because they were already in the supported range. The sample batch files on base install disk 7 have been modified to support this new set of errorlevels. The sample batch files on base disk 7 for running Retail/DOS are as follows: AUTOEXEC.BAT RAD.BAT OPS.BAT COMM.BAT TODOS.BAT POLL.BAT EPOLL.BAT ERRPROG.BAT In addition, a sample CONFIG.SYS is also provided on base disk 7. ======================================================================= Additional Installation Information ======================================================================= You are no longer required to reinstall previously installed language files as a part of the installation process if you are upgrading from version 1.01.01 or higher. This means that any changes you have made to the language files will be preserved with the exception of the handful of specific prompts which are upgraded for V1.02.00 compatibility or to address APARs. This language upgrade support is provided for the BASE and all features EXCEPT Promotional Events, Home Office E-Mail, and Install Configurator. During the BASE installation of V1.02.00, your language files will be upgraded from V1.01.01 to V1.02.00. The program which does this is called UPDATNLS.EXE. This program will read the ASCII file NLS.CHG and apply the required changes to the language database. You may want to review the NLS.CHG file after installation to determine if a prompt which you have previously modified has been affected by the upgrade. If you need to make changes to the updated strings, you can either: 1. Use the CHGFILE.EXE utility provided with Retail/DOS OR 2. Modify the strings in the NLS.CHG file with an ASCII editor and run UPDATNLS.EXE again. The format of the NLS.CHG file is as follows: FILENAME PROMPT# new text where PROMPT# = 0 means the entire prompt file will be replaced. You may modify the text for "new text" and run the UPDATNLS utility again. ----------------------------------------------------------------------- The installation of this level of IBM Retail Application/DOS is not dependent on any previous level of the application. However, if you have already installed a previous level of IBM Retail Application/DOS on your system, this install package is designed to be installed on top of the previous level of Retail/DOS with no loss of POS data. Performing a backup of POS data files before installation is still highly recommended. ------------------------------------------------------------------------- The current level is stated as 1.02.00. This is to be interpreted as version 1 release 2 refresh 0. The EFIX number has not been added since this is a new level. After applying the first EFIX, the level would change to 1.02.00.01. After applying the second EFIX, the level would change to 1.02.00.02. This would continue until the next refresh, release, or version update at which time the EFIX level would be cleared. The current level of IBM Retail Application/DOS will be valuable information in any discussions with IBM support. ----------------------------------------------------------------------------- Note that disks 1 through 6 are installed as part of the base application. Disk 6 contains language support files. Disk 7 contains object code for user exit coding, sample batch files* for running Retail/DOS, and sample* AUTOEXEC.BAT and CONFIG.SYS FILES. These files may be copied to any directory you wish. * Note: The batch files provided are samples only; there is no product support for these files. ======================================================================= Additional Language Support Information ======================================================================= Language support with IBM Retail Application/DOS Base is provided for the following countries: Country Country Code Features ------- ------------ ----------------------------------------------- United States 001 Base and all features French Canada 002 Base Latin America 003 Base and all features except Labor Scheduling France 033 Base Spain 034 Base and all features except Labor Scheduling Denmark 045 Base and all features except Labor Scheduling Germany 049 Base | Turkey 090 Base and all features except Time and | Attendance and Labor Scheduling Portugal 351 Base and all features except Labor Scheduling Arabic 785 Base, Inventory Management feature, and Promotional Events feature To activate the support for a specific country, the country code for that country must be specified in the country personalization screen in Retail/DOS Personalization (IPOS). This is a new personalization parameter for Release 2 of Retail/DOS. The specified country will override the default DOS country code from the CONFIG.SYS for language support. The CONFIG.SYS country code will still be used for date formats. The prompting in IBM Retail Application/DOS can be tailored by the end user via the CHGFILE utility. Please keep a record of all changes that are made to the prompts as these changes could be overwritten in subsequent updates of IBM Retail Application/DOS. With the language upgrade utility for Retail/DOS installation, your language prompt changes are less likely to be overwritten during installs. It is still a good idea to keep track of all prompt changes in the unlikely event that an upgrade affects a prompt which you have modified. Any problems found with the translations should be communicated via the standard IBM support channels. ------------------------------------------------------------------------ Installing and Removing Language Support The program called LANGUAGE.EXE is used to install and remove language support. This program runs automatically as part of the initial Retail/DOS installation procedure; however, it can be run from the DOS prompt at any time after installation. To run this program, do the following: 1. At the \POS prompt, type LANGUAGE and press Enter. The Language Support menu appears: 1. INSTALL A LANGUAGE 2. REMOVE A LANGUAGE 2. Do one of the following: a. Select INSTALL A LANGUAGE and press Enter to add a language to your system. b. Select REMOVE A LANGUAGE and press Enter to remove a language from your system. 3. If you select to INSTALL A LANGUAGE then a menu will be displayed for selection of the BASE or features. Select the base application or the specific feature for which you wish to install a language. 4. At the ENTER COUNTRY CODE, type a country code and press Enter. (The country codes are listed on the screen.) Refer to the above list for specific country support. 5. Press the Escape (Esc) key to return to the Language Support menu. ======================================================================= Additional Compiler Information ======================================================================= The compiler used for Retail/DOS V1.02.00 or later is the Microsoft Visual C/C++ 1.5 Professional Edition Compiler. This compiler is required for user exit coding.