CounterPoint SQL V8.3.9 Update Guide · following the instructions outlined in the CounterPoint SQL...

Update Guide

© 2009 Radiant Systems, Inc. All rights reserved. iii

Table of Contents Introduction ................................................................................................................................................ 7

Software updates ..................................................................................................................................... 8

Updating to V8.3.9 ....................................................................................................................................... 9

Updating a Multi-Site environment ....................................................................................................... 9

Updating an Offline V2 environment .................................................................................................... 9

Pre-installation steps ................................................................................................................................. 9

Step 1: Stop Rad Sync service (V8.3.7 only) .......................................................................................... 10

Step 2: Test database constraints (V8.3.7 only) ..................................................................................... 11

Step 3: Post tickets.............................................................................................................................. 12

Step 4: Settle credit cards .................................................................................................................... 13

Step 5: Publish CPOnline orders (optional) ............................................................................................. 13

Step 6: Review custom modifications .................................................................................................... 13

Point of Sale data model changes (V8.3.7 only) .................................................................................. 13

Step 7: Back up your data .................................................................................................................... 14

Step 8: Back up your company files ...................................................................................................... 14

Step 9: Stop CPDialup service ............................................................................................................... 14

Installation steps .................................................................................................................................... 15

Step 1: Upgrade to MSSQL 2005 (optional) ............................................................................................ 15

Step 2: Install prerequisites on server ................................................................................................... 16

Step 3: Install prerequisites on workstations .......................................................................................... 19

Step 4: Update CounterPoint SQL ......................................................................................................... 20

Step 5: Allow all users to update workstations (optional) ........................................................................ 21

Step 6: Install the current Service Pack ................................................................................................. 21

Step 7: Update each live company database .......................................................................................... 22

Step 8: Update registration file ............................................................................................................. 23

Post-installation steps ............................................................................................................................. 23

Step 1: Update pre-defined data ........................................................................................................... 23

Step 2: Update menu codes ................................................................................................................. 24

Removed menu items ....................................................................................................................... 24

Renamed menu items ....................................................................................................................... 24

New menu items .............................................................................................................................. 25

Step 3: Update CounterPoint Version in CPOnline ................................................................................... 25

Step 4: Restart CPDialup service ........................................................................................................... 25

Step 5: Update MSR device files (V8.3.7 only) ........................................................................................ 26

Update Guide

© 2009 Radiant Systems, Inc. All rights reserved. iv

Step 6: Schedule history conversion ...................................................................................................... 26

Step 7: Provision the server database (Offline V2 only) ........................................................................... 29

Step 8: Update Offline V2 workstations (Offline V2 only) ......................................................................... 30

Step 9: Rebuild offline databases (Offline V2 only) ................................................................................. 31

Step 10: Enable "smart mouse" setting on workstations .......................................................................... 31

Updating customizations ............................................................................................................................. 33

Database schema changes ...................................................................................................................... 34

BOGO/twofer pricing ............................................................................................................................... 34

Pricing stored procedure changes ......................................................................................................... 34

Custom price rules ............................................................................................................................... 35

Custom loyalty point earning rules ........................................................................................................ 35

Custom triggers .................................................................................................................................. 36

Hold and Recall price modifications ....................................................................................................... 36

Price justification data .......................................................................................................................... 36

Custom and customized reports ............................................................................................................... 36

OPOS Point of Sale forms ........................................................................................................................ 37

Point of Sale data model changes (V8.3.7 only) ..................................................................................... 37

Update Pre-defined Data ......................................................................................................................... 37

Delta-tracked tables ................................................................................................................................ 37

Custom stored procedures ....................................................................................................................... 38

Prompt for custom payment fields ............................................................................................................ 38

Validated returns .................................................................................................................................... 38

Ticket Entry customizations (V8.3.7 only) ................................................................................................. 39

Stored procedures ............................................................................................................................... 39

Database triggers ................................................................................................................................ 39

Absent child records ............................................................................................................................ 39

Ticket posting customizations (V8.3.7 only) .............................................................................................. 40

Crystal receipts and Point of Sale forms (V8.3.7 only) ................................................................................ 40

Fixing custom Crystal reports and receipts (V8.3.7 only) ............................................................................ 41

Custom Point of Sale maintenance forms (V8.3.7 only) .............................................................................. 43

Custom indexes for Point of Sale tables (V8.3.7 only) ................................................................................ 43

Data Dictionary considerations (V8.3.7 only) ............................................................................................. 44

Drawer sessions and events (V8.3.7 only) ................................................................................................. 44

Improved performance for posting receivings (V8.3.7 only) ........................................................................ 45

Modified commission calculation stored procedure (V8.3.7 only) ................................................................ 45

Modified finance charge calculation stored procedures (V8.3.7 only) ........................................................... 45

Table of Contents

© 2009 Radiant Systems, Inc. All rights reserved. v

Modified pricing stored procedures (V8.3.7 only) ....................................................................................... 45

Quick assembly transactions (V8.3.7 only) ................................................................................................ 45

Suppressing the authorization codes dialog (V8.3.7 only) ........................................................................... 46

Suppressing the ticket completion confirmation (V8.3.7 only) .................................................................... 46

Database Comparison ................................................................................................................................ 47

Tables ................................................................................................................................................... 47

New Tables ......................................................................................................................................... 48

Modified Tables ................................................................................................................................... 49

Dropped Tables ................................................................................................................................... 75

Views .................................................................................................................................................... 76

New Views ...................................................................................................................................... 76

Modified Views .................................................................................................................................... 77

Stored Procedures .................................................................................................................................. 99

New Stored Procedures ...................................................................................................................... 100

Modified Stored Procedures ................................................................................................................ 101

Dropped Stored Procedures ................................................................................................................ 108

Functions ............................................................................................................................................. 109

V8.3.8 Point of Sale data model changes ................................................................................................... 111

Table changes ...................................................................................................................................... 111

Additional views ................................................................................................................................... 113

Primary key changes ............................................................................................................................. 113

Data type changes ................................................................................................................................ 114

Maintenance columns dropped ............................................................................................................... 114

Reserved tables for custom columns ...................................................................................................... 114

V8.3.8 Point of Sale table structure ........................................................................................................... 115

Header tables ....................................................................................................................................... 115

Line tables ........................................................................................................................................... 116

Payment tables..................................................................................................................................... 116

Ticket History tables ............................................................................................................................. 117

© 2009 Radiant Systems, Inc. All rights reserved. 7

Introduction You’ve invested a significant amount of time, money, and hard work in your computer systems and in CounterPoint. The CounterPoint Subscription Service (CSS) is the best way to protect that investment and get the most out of CounterPoint. CSS ensures that you can take advantage of the latest features and enhancements in each new version of CounterPoint as soon as it is released.

The CounterPoint SQL Update Guide includes detailed instructions for updating your system from V8.3.7 or V8.3.8 to V8.3.9.

The CounterPoint SQL Update Guide is intended for existing CounterPoint systems. If you are installing a new CounterPoint system, refer to the CounterPoint SQL Installation Guide.

Update Guide


Software updates As a registered CSS subscriber, you have the option of receiving each new version of CounterPoint SQL on DVD or downloading it from the CounterPoint Web site. When you receive or download a new version, however, it does not necessarily include the latest corrections and updates. To obtain the most up-to-date version of CounterPoint, download and install the current Service Pack.

CounterPoint Service Packs contain the latest software updates and enhancements. You can obtain the current Service Pack from our Web site at www.counterpointpos.com/support/software.html. Installation Instructions for the Service Pack appear on the Web site.

You must be a registered CSS subscriber to access the Support area of the CounterPoint Web site.

The CounterPoint SQL Service Pack is updated on our Web site as often as updates become available. You should periodically download and install the current Service Pack to ensure that you are running the latest software.

Each Service Pack includes the Service Pack Log and the Reported Problem Log. The Service Pack Log describes enhancements and corrections in the Service Pack, while the Reported Problem Log documents problems reported in the current software. We encourage you to install all Service Packs, regardless of whether the Service Pack Log includes anything that seems to be of interest to you.

You can receive automatic e-mail notifications regarding new Service Packs by subscribing to our Service Pack e-mail list. To subscribe to this list, use the submission form in the Support area of our Web site at www.counterpointpos.com/support/software_email.htm.

You can view your current CounterPoint version and Service Pack level at any time by selecting About CounterPoint from the Help menu in CounterPoint SQL.

http://www.counterpointpos.com/support/software.html�

http://www.counterpointpos.com/support/software_email.htm�


Updating to V8.3.9 You can update your existing CounterPoint SQL system to V8.3.9 from V8.3.7 or V8.3.8.

If you are currently running CounterPoint SQL V8.3.6 or earlier, you must first update your system to V8.3.7 by following the instructions outlined in the CounterPoint SQL V8.3.7 Update Guide.

Updating a Multi-Site environment

If you are using CounterPoint SQL in a Multi-Site environment, follow the steps outlined in the Multi-Site Online Help to update to CounterPoint SQL V8.3.9.

Updating an Offline V2 environment

Previously, when you updated an Offline V2 environment to a new version of CounterPoint, you were required to suspend all CounterPoint operations until your server and all of your offline workstations were updated.

As of this Service Pack, if you are updating from V8.3.8, users will be able to continue working in offline mode on registered Offline V2 workstations while you update your server database, reducing downtime during the update process. Any tickets entered in offline mode will be converted to the new data format when you update your offline workstations.

If you are updating from V8.3.7, you cannot work in offline mode while the server database is being updated, as tickets entered in offline mode in a V8.3.7 database will not be converted properly to the new V8.3.9 data format.

Pre-installation steps Before you install CounterPoint SQL V8.3.8, complete the following steps:

Step 1: Stop Rad Sync service (V8.3.7 only) Step 2: Test database constraints (V8.3.7 only) Step 3: Post tickets Step 4: Settle credit cards Step 5: Publish CPOnline orders Step 6: Review custom modifications Step 7: Back up your data Step 8: Back up your company files Step 9: Stop CPDialup service

Update Guide


Step 1: Stop Rad Sync service (V8.3.7 only) Skip this step if you are updating from V8.3.8.

If you are updating from V8.3.7 and using Offline V2, you cannot work in offline mode while the server database is being updated, as tickets entered in offline mode in a V8.3.7 database will not be converted properly to the new V8.3.9 data format.

Before you update to V8.3.9, you must verify that each of your offline workstations is fully synchronized with your server, and then stop the Rad Sync service on your server and all offline workstations.

Follow these steps to verify the data status of your offline workstations and stop the Rad Sync service:

1. On each offline workstation, right-click the CounterPoint Services status icon and select Status to display the CounterPoint Services Status window.

2. Verify that the Data Status for the workstation is Synched.

If it is not, click the Sync Now button to immediately extract all tickets and other offline data from the offline workstation for upload to the server, and then download and apply any updated configuration data from the server.

Repeat steps 1 and 2 for each of your offline workstations.

3. When all of your workstations are Synched, access the Control Panel on each offline workstation, double-click Administrative Tools, double-click Services, right-click the Rad Sync service, and then select Stop.

Repeat this step for each offline workstation.

4. Access the Control Panel on your server, double-click Administrative Tools, double-click Services, right-click the Rad Sync service, and then select Stop.

Updating to V8.3.9


Step 2: Test database constraints (V8.3.7 only) Skip this step if you are updating from V8.3.8.

CounterPoint SQL V8.3.8 included a number of new database constraints that were introduced in conjunction with the changes to the Point of Sale data model that were made in that version. If you are updating from V8.3.7, before you update to V8.3.9, you must ensure that your data is compliant with these database constraints.

The CounterPoint SQL DVD includes a script that will test your database for violations of these constraints and alert you to the presence of records that are non-compliant. If the test script encounters database constraint violations, you MUST correct the non-compliant records before you proceed with the update process.

Depending on the size of your database(s), the test script can take considerable time to complete. We recommend that you do not run these scripts during normal operating hours or while other SQL applications are running. Although the test script will not actually update your database(s), it will take significantly less time to execute if your SQL Server is idle.

Follow these steps to test your database for constraint violations before you update to V8.3.9:

1. Copy the TestUpdateFrom8.3.7.sql file from the \SQLScripts directory on the CounterPoint SQL DVD to the \Scripts subdirectory of your top-level CounterPoint SQL directory (e.g., C:\CounterPoint\Scripts).

2. From a workstation on which the CounterPoint SQL Database Utilities are installed, select Start > Programs > CounterPoint SQL > SQL Script Utility to start the SQL Script Utility.

3. Select the appropriate company database from the Alias-Company list.

4. Select Open from the File menu, open the TestUpdateFrom8.3.7.sql script, and then select Execute from the Script menu.

5. Click OK from the Confirmation dialog to run the TestUpdateFrom8.3.7.sql script.

Depending on the size of your database, this script may take considerable time to execute.

Update Guide


6. When the script is finished, search the Results tab or the TestUpdateFrom8.3.7.txt file in the \Scripts subdirectory of your top-level directory for any database constraint violations in your database. Each violation is identified by the !!! Warning: message.

To find database constraint violations quickly, select Find from the Edit menu (or press CTRL+F) and enter !!! in the Find what field to search for any warning messages.

If no warnings are listed, your database is compliant with all database constraints and you can continue with the update process.

If you encounter any warnings, back up your database, and then correct each violation that the TestUpdateFrom8.3.7.sql script has identified.

Do NOT attempt to correct non-compliant records without backing up your database. Having a current backup on hand ensures that you will be able to restore your database to its previous state if you encounter any problems while correcting database constraint violations.

The exact steps you must take to correct each violation depend on the nature of the constraint. Typically, however, you will need to insert data into columns with values that are currently invalid. For example, a column contains invalid data if it has a NULL value where one is not allowed, or if its value is not one of the column’s acceptable mapping values.

You can use System > Utilities > Column Description Report to generate a report that describes each column’s valid mapping values.

7. When you finish correcting the constraint violations in your database, run the TestUpdateFrom8.3.7.sql script again to verify that the database is now compliant with all database constraints. If the script still returns warning messages, correct any remaining violations.

Repeat this step until the TestUpdateFrom8.3.7.sql script does not return ANY warning messages. You may need to perform this step several times to ensure that your database is compliant. DO NOT continue with the update process until you have corrected all database constraint violations.

Step 3: Post tickets Post all unposted tickets by using Point of Sale > Tickets > Post.

Updating to V8.3.9


Step 4: Settle credit cards If you have unsettled credit card transactions on file, generate the PRE-SETTLEMENT LIST (Point of Sale > Credit Cards > Pre-Settlement List) for all stores and all drawers, and then use Point of Sale > Credit Cards > Settle to settle all credit card transactions and generate the SETTLEMENT JOURNAL.

Step 5: Publish CPOnline orders (optional) Skip this step if you are not using CPOnline.

If you are using CPOnline and you have defined a publishing code that publishes order status information, use Ecommerce > Publish to publish updated orders to your CPOnline store.

Step 6: Review custom modifications Before you update your system, carefully review any custom modifications that you have made. We strongly recommend that you maintain clear, plain-language records of your custom modifications, including any applicable screen shots, reports, SQL queries, descriptions of schema changes, and so forth. These records will assist you in recreating or revising your custom modifications after any update, if necessary.

Refer to Updating customizations for detailed information about integrating your custom modifications into V8.3.9.

Point of Sale data model changes (V8.3.7 only)

In V8.3.8, the tables in the CounterPoint SQL database that store ticket and ticket history data were completely redesigned. These schema changes render existing customizations that rely on Point of Sale tables inoperable. Customizations affected by these changes include, but are not limited to:

• Custom columns in Point of Sale tables

• Stored procedures and triggers in Ticket Entry

• Stored procedures and triggers in ticket posting

• Custom indexes for Point of Sale tables

• Custom Point of Sale maintenance forms

• Crystal receipts and Point of Sale forms

• Custom reports

In addition, a number of configuration changes that are not typically considered "customizations" may be affected by the changes to the Point of Sale data model that occurred in V8.3.8, including:

• Label jobs that rely on Point of Sale data

• CPOnline publishing codes that publish ticket history

• Point of Sale device settings

• Custom LookUp windows

• Custom Zoom layouts

• Custom form groups

If you are updating from V8.3.7, the update process attempts to modify your configuration to comply with the new Point of Sale data model. However, due to the nature and extent of the changes, you should carefully review all modifications you have made to CounterPoint after you complete the update process to verify that your system behaves as expected.

Update Guide


Step 7: Back up your data Before you update your database, it is critical that you make a backup copy of each live CounterPoint SQL database. In the event of a failure during the update process, you will need to restore your database from your backup copy.

Step 8: Back up your company files To ensure that you retain all of your custom Data Dictionary settings, custom forms, reports, actions, and so forth, in case you need to restore them, back up the contents of your company directory (e.g., C:\CounterPoint\MyCompany).

In addition, back up the existing Registration.ini file in your top-level directory (e.g., C:\CounterPoint).

Step 9: Stop CPDialup service Skip this step if you are not using CPDialup.

If you are using CPDialup to process credit cards, you must stop the CPDialup service before installing the new version of CounterPoint.

Follow these steps to stop the CPDialup service:

1. From the Windows Control Panel, double-click Administrative Tools, and then double-click Services.

2. Right-click the CPDialup service (i.e., CPDialupFDMSNorth, CPDialupFDMSSouth, CPDialupLynk, CPDialupVital, or CPDialupPaymentech) and select Stop.

If you are running CPDialup from one or more workstations, instead of from your server, stop the CPDialup service on those workstations.

Updating to V8.3.9


Installation steps Once you have completed the necessary Pre-installation steps, you must complete the following steps to update your CounterPoint software and your database(s) to V8.3.9:

Step 1: Upgrade to MSSQL 2005 (optional) Step 2: Install prerequisites on server Step 3: Install prerequisites on workstations Step 4: Update CounterPoint SQL Step 5: Allow all users to update workstations Step 6: Install the current Service Pack Step 7: Update each live company database Step 8: Update registration file

Step 1: Upgrade to MSSQL 2005 (optional) Skip this step if you are not updating from V8.3.7.

CounterPoint SQL requires Microsoft SQL Server 2005 with SP2. If you are updating from V8.3.7 and you are using MSSQL 2000 or MSDE, you must upgrade your database engine to MSSQL 2005 or SSE before you update your CounterPoint SQL database to V8.3.9.

CounterPoint supports all editions of Microsoft SQL Server (MSSQL) 2005, including Enterprise Edition, Standard Edition, and Workgroup Edition, as well as Microsoft SQL Server 2005 Express Edition (SSE), which is included with CounterPoint.

To update to MSSQL 2005 Standard Edition, Workgroup Edition, or Enterprise Edition, follow the instructions in the accompanying documentation.

MSSQL 2005 Standard Edition, Workgroup Edition, and Enterprise Edition must be purchased separately.

If you do not install one of these editions of MSSQL 2005, you will be prompted to install SSE when you install the CounterPoint SQL prerequisites on your server.

When you update your company database, it will be converted to the SQL Server 2005 format automatically.

Once you have converted a database to the SQL Server 2005 format, you cannot use it with MSSQL or MSDE 2000. Make sure to back up your database before upgrading it.

Update Guide


Step 2: Install prerequisites on server Before you update to CounterPoint SQL V8.3.9, you must install the following components on your server:

• Microsoft .NET Framework 3.5 SP1

• Microsoft SQL Server Native Client

• SQL Server Management Objects

• SQLXML4

The CounterPoint SQL Prerequisites installer will install all of these components automatically. In addition, if you have not installed a default instance of another edition of Microsoft SQL Server, the installer will prompt you to install SQL Server 2005 Express Edition (SSE).

Follow these steps to install the CounterPoint SQL prerequisites on your server:

1. Log into your server as an Administrator.

2. If you intend to install SSE on your server, select Start > Settings > Control Panel, double-click Add or Remove Programs, select Microsoft SQL Server Native Client, click the Remove button, and then click Yes from the confirmation dialog.

If you do not remove the version of Microsoft SQL Server Native Client that is pre-installed on your server, you will be unable to install SSE.

3. Insert the CounterPoint DVD into your DVD drive, click CounterPoint SQL Enterprise or CounterPoint SQL Express, depending on which edition of CounterPoint you are updating, and then click Prerequisites to start the CounterPoint SQL Prerequisites installer.

OR

Download the Complete DVD file from the CounterPoint Web site at www.counterpointpos.com/support/downloads_cpsql.htm, extract the archive, double-click launch.exe, select the edition of CounterPoint you are updating, and then click Prerequisites to start the CounterPoint SQL Prerequisites installer.

OR

Download the Update file from the CounterPoint Web site at www.counterpointpos.com/support/downloads_cpsql.htm, extract the archive, browse to the \CPSQLPrereqs subdirectory, and then double-click the CPSQLPrereqs.exe file to start the CounterPoint SQL Prerequisites installer.

http://www.counterpointpos.com/support/downloads_cpsql.htm�

http://www.counterpointpos.com/support/downloads_cpsql.htm�

Updating to V8.3.9


4. Select the Server option from the Server? dialog, and then click Next.

If a message indicates that MSSQL 2000 or earlier is installed on your server, click OK to close the message, remove the existing version of MSSQL from your server or upgrade it to MSSQL 2005, and then start the CounterPoint SQL Prerequisites installer again.

5. Click Next from the Welcome dialog.

If a default instance of MSSQL 2005 is not installed, the SQL Server 2005 dialog appears, prompting you to install SSE.

Select the Install SQL Server 2005 Express check box and click Next.

6. Click Next from the Start Installation dialog to install the CounterPoint SQL prerequisites.

7. If Microsoft .NET Framework 3.5 SP1 is not installed on your server, it is installed automatically, followed by Microsoft SQL Server Native Client, as indicated by the corresponding progress bars.

Update Guide


8. Once .NET Framework and SQL Server Native Client are installed, if you chose to install SSE, the SQL Server 2005 Express installer starts automatically. Follow these steps to install SSE:

• Click Next from the Welcome dialog to display the Components to be Installed dialog.

• Make sure the SQL Server 2005 Express Database Engine check box is selected.

• Select the SQL Server 2005 Backward Compatibility check box if you intend to use CounterPoint’s Data Migration utility or one of CounterPoint’s export accounting interfaces.

• Select the SQL Server Management Studio Express check box to install the SQL Server Management Studio Express (SSMSE) database management tool. SSMSE allows you to create, back up, restore, and maintain SQL databases using a graphical interface.

We strongly recommend that you install SSMSE on your server.

• Click Next to proceed to the Start Installation dialog, and then click Next to install the SSE database engine and the other SSE components you selected.

• Follow the on-screen instructions to accept the License Agreement and complete your Registration Information for the SQL Server 2005 Backward Compatibility components and SQL Server Management Studio Express.

• When the SSE database engine and other components you selected are installed, the Installation Complete dialog appears. Click Finish to close the SQL Server 2005 Express installer.

9. Next, SQL Server Management Objects is installed automatically, followed by SQLXML4, if it is not installed, as indicated by the corresponding progress bars.

10. When all of the CounterPoint SQL prerequisites are installed, the Installation Complete dialog appears. Click Finish to close the installer.

11. If you are prompted to restart your computer, click OK to complete the installation of the CounterPoint SQL prerequisites.

A .log file for each installed SSE component is generated in the \Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files subdirectory of your local drive. If you encounter any difficulties during the installation of SSE, review these log files in Notepad or another text editor.

Updating to V8.3.9


Step 3: Install prerequisites on workstations Skip this step if you are using Radiant POS terminals for your workstations.

Follow these steps to install the CounterPoint SQL prerequisites on your workstations:

1. Copy the \CPSQLPrereqs directory from the CounterPoint SQL DVD to the \WorkstationFiles subdirectory of the top-level directory on your server (e.g., C:\CounterPoint\WorkstationFiles).

2. From a workstation, browse to this directory on your server and double-click CPSQLPrereqs.exe to start the CounterPoint SQL Prerequisites installer.

3. Select Workstation or Offline V2 Workstation from the Server? dialog, depending on the type of workstation you are updating, and then click Next.

4. Click Next from the Welcome dialog.

5. Click Next from the Start Installation dialog to install the CounterPoint SQL prerequisites.

If Microsoft .NET Framework 3.5 SP1 is not installed on your workstation, it is installed automatically.

Next, SQL Server Management Objects is installed automatically, followed by SQLXML4, if it is not installed, as indicated by the corresponding progress bars.

6. When all of the CounterPoint SQL prerequisites are installed, the Installation Complete dialog appears. Click Finish to close the installer.

7. If you are prompted to restart your computer, click OK to complete the installation of the CounterPoint SQL prerequisites.

Repeat steps 2 through 7 for each of your workstations.

Update Guide


Step 4: Update CounterPoint SQL Follow these steps to update your CounterPoint SQL software:

In a network environment, you must perform the following steps at your server.

1. Log in to your server as an Administrator.

2. Start the SQL Server service, if it is not running already.

3. Insert the CounterPoint SQL DVD into your DVD drive, click CounterPoint SQL Enterprise or CounterPoint SQL Express, depending on which edition of CounterPoint you are updating, and then click CounterPoint SQL to start the installation process.

OR

Browse to the directory to which you downloaded and extracted the Complete or Update archive and double-click setup.exe to start the installation process.

4. From the Welcome dialog, click Next.

5. Read the Software License Agreement, select the Agree option, and then click Next to display the Select Components dialog.

6. Select the Server Files check box.

7. Click Next to proceed to the Select Top-Level Directory dialog.

8. Specify your existing Top-Level Directory or click Browse to search for it.

You must update CounterPoint in an existing V8.3.7 or V8.3.8 top-level directory. If you specify a new top-level directory, some components of your system, such as data dictionary entries and label jobs, will not be updated successfully.

9. Click Next and specify the program group to which you want to add the Radiant Management Console and Radiant Log Viewer from the Select Start Menu Program Group dialog.

10. Click Next to begin installing the updated server files. Follow the on-screen prompts and instructions to complete the installation.

11. When the server files are installed, you are prompted to run the CounterPoint SQL Workstation Setup installer.

If you run CounterPoint or the CounterPoint utilities on your server, select the Run workstation setup check box and click Finish, and then follow the on-screen instructions to update the workstation files on your server.

Once you have updated CounterPoint on your server, you do not have to install the software on each workstation. CounterPoint’s automatic workstation update feature ensures that all of your workstations are updated after you update your server.

A user with Administrator rights must log in to CounterPoint on each workstation in order to update it. When a user with Administrator rights logs in, the workstation detects the updated software on your server and installs it automatically.

You cannot run CounterPoint on each workstation until it has been updated.

If you want to allow all users to update your workstations to the new version of CounterPoint, instead of only users with Administrator rights, proceed to Step 5: Allow all users to update workstations.

If you prefer that only administrators are able to update your workstations, skip to Step 6: Install the current Service Pack.

Updating to V8.3.9


Step 5: Allow all users to update workstations (optional) If you haven't done so previously, follow these steps to configure CounterPoint to allow users without Administrator rights to update your workstations to each new version:

1. Browse to the top-level CounterPoint directory on your server (e.g., C:\CounterPoint).

2. Double-click RunAsSPCAdmin.exe.

3. In the Path\Application.exe field, enter the UNC path to the top-level directory on your server, followed by InstallWorkstation.exe (e.g., \\MyServer\CounterPoint\InstallWorkstation.exe).

4. If your CounterPoint server and workstations are not part of a network domain, select the Local option and enter localhost in the corresponding field.

5. If your CounterPoint server and workstations are in a network domain, select the Domain option and enter the name of your domain in the corresponding field.

6. Enter the Username and Password of a user who has Administrator rights to the server and all workstations (i.e., the network domain administrator).

7. In the Current Encryptfile field, enter the UNC path to the top-level directory on your server, followed by WorkstationUpdate.spc (e.g., \\MyServer\CounterPoint\WorkstationUpdate.spc).

8. Select the Optional settings check box, and then enter the following in the Program options field: /M="./workstationsetup.var"

9. Leave the default settings for the remaining options.

10. Click the Save Cryptfile button, click OK to close the Info dialog that appears, and then close the runasspcadmin window.

With these settings, the next time any user logs in to a workstation, the workstation detects the updated CounterPoint software on your server and installs it automatically.

Step 6: Install the current Service Pack When you finish installing CounterPoint V8.3.8, download and run the current CounterPoint SQL Service Pack (cpsqlsp.exe) to ensure that you have the latest software updates and enhancements.

You can download the current Service Pack from our Web site at www.counterpointpos.com/support/software_cpsql.htm.

You must be a registered CSS subscriber to access the Support area of the CounterPoint Web site.

http://www.counterpointpos.com/support/software_cpsql.htm�

Update Guide


Step 7: Update each live company database You can update your database from any server or workstation on which the SQL Script Utility is installed. This process updates your database to include changes that were made for the current release and converts your existing data into the new structure.

Database changes are implemented in each new version and may include the addition of tables, columns, indexes, and other elements. The UpdateFrom8.3.x.sql scripts alter your database to create new tables, columns, and indexes and to convert existing data into the new structure.

The UpdateFrom8.3.x.sql scripts will not update your historical Point of Sale data (i.e., posted tickets and other documents). Instead, historical Point of Sale data will be updated over time by the CounterPoint History Conversion scheduled task, which you will configure during the Post-installation steps.

For each database (i.e., company), perform the following steps:

1. Make sure all users have exited CounterPoint.

2. Select Start > Programs > CounterPoint SQL > SQL Script Utility to start the SQL Script Utility. This utility is only available if you installed the CounterPoint SQL utilities.

3. Select your company from the Alias-Company list.

4. Select File > Open, browse to the \Scripts subdirectory of your top-level directory, and then open the appropriate UpdateFrom8.3x.sql script to update your version of CounterPoint.

The following table lists the scripts you must execute and the order in which you must apply them to update your database from each version:

If you are updating from Run these scripts

V8.3.8 • UpdateFrom8.3.8.sql V8.3.7 • UpdateFrom8.3.7.sql

• UpdateFrom8.3.8.sql

5. Select Execute from the Update menu.

6. From the Database Login dialog, enter your User ID and Password (e.g., sa and CounterPoint8), and then click OK.

A progress indicator appears at the top of the SQL Script Utility window to track the script’s progress. When the script is finished, the Information dialog appears. Click OK to close this dialog.

Do not interrupt this script or any subsequent scripts while they are in progress!

7. If you have customized your database with new fields, tables, triggers, or other custom elements, verify that these elements are intact. To verify your customizations, do the following:

• Start CounterPoint SQL, log in to your database, and then select System > Utilities > Databa.se Customizations Report to display the Database Customizations Report utility.

• Select Standard database and click Compare to compare your database to the standard CounterPoint database and display the differences between the two in your default Web browser.

• If the Database Customizations Report utility identifies any unintended structural discrepancies, such as missing primary keys, take the necessary steps to resolve them before proceeding to the next step.

• If the Database Customizations Report utility does not identify any discrepancies other than expected custom database modifications, proceed to the next step.

Updating to V8.3.9


Step 8: Update registration file You must install an updated, version-specific registration file for CounterPoint SQL V8.3.9.

If you are a registered CSS subscriber, you can obtain an updated registration file from your CounterPoint Business Partner.

If you have chosen to have CSS software updates shipped directly to you, instead of to your CounterPoint Business Partner, you can download an updated registration file from the CounterPoint Web site at www.counterpointpos.com/support/software_regfile_cpsql.htm.

To update your registration file, copy your new Registration.ini file to your top-level CounterPoint directory (e.g., C:\CounterPoint), overwriting the existing file.

Your CounterPoint software and database (except for historical Point of Sale data) are now updated to V8.3.9.

Post-installation steps After you update CounterPoint and your database(s) to V8.3.8, complete the following steps to finish the update process:

Step 1: Update pre-defined data Step 2: Update menu codes Step 3: Update CounterPoint Version in CPOnline Step 4: Restart CPDialup service Step 5: Update MSR device files (V8.3.7 only) Step 6: Schedule history conversion Step 7: Provision the server database (Offline V2 only) Step 8: Update Offline V2 workstations (Offline V2 only) Step 9: Rebuild offline databases (Offline V2 only) Step 10: Enable “smart mouse” setting on workstations

Step 1: Update pre-defined data From the CounterPoint SQL main menu, select System > Utilities > Pre-defined data to display the Update Pre-defined Data utility, and then click Update to create and update pre-defined label jobs, form groups, and other pre-defined data.

http://www.counterpointpos.com/support/software_regfile_cpsql.htm�

Update Guide


Step 2: Update menu codes If you have defined any menu codes, you must edit them to reflect the new, removed, and renamed CounterPoint SQL menu items.

To update your menu codes, select Setup > System > Menu Codes, select a menu code, and then click Menu Editor.

You can use the Verify Menu command from the Menu Codes window (Setup > System > Menu Codes) or the Menu Editor to compare your menu codes to the standard CounterPoint SQL main menu and report the differences.

Removed menu items

The following commands have been removed from V8.3.9:

• Inventory > Reports > Stock Status

• System > Messages

• Setup > System > Configuration > Workstation Preferences

Renamed menu items

The following commands have been renamed in V8.3.9:

• Inventory > Reports > Sales Kits (formerly Inventory > Reports > Kits)

• System > Gift Cards > Edit Gift Cards (formerly System > Gift Certificates > Edit Gift Certificates)

• System > Gift Cards > Close Gift Cards (formerly System > Gift Certificates > Close Gift Certificates)

• System > Gift Cards > Gift Card List (formerly System > Gift Certificates > Gift Certificate List)

• System > Gift Cards > Maintain Gift Cards (formerly System > Gift Certificates > Maintain Gift Certificates)

• System > Reports > History > Closed Gift Cards (formerly System > Reports > History > Closed Gift Certificates)

• System > Reports > Journal > Closed Gift Cards (formerly System > Reports > Journal > Closed Gift Certificates)

• Setup > System > Gift Card Codes (formerly Setup > System > Gift Certificate Codes)

• Setup > Inventory > Barcode Types (formerly Setup > Inventory > Barcode ID's)

• Setup > Inventory > Reports > Barcode Types (formerly Setup > Inventory > Reports > Barcodes ID's)

Updating to V8.3.9


New menu items

Drag the following menu items from the Default Menu tree to the Custom Menu tree to make them available from your custom menus:

• Point of Sale > Gift Registries > Manage Gift Registries

• Point of Sale > Gift Registries > Print Blank Registry Form

• Point of Sale > Gift Registries > Gift Registry Reports

• Point of Sale > Reports > Point of Sale Exceptions

• Inventory > Forecast

• Inventory > Views > Inventory Detail

• Inventory > Reports > Inventory Grid Overview

• Inventory > Reports > Sell-Through Rate

• Purchasing > Purchase Requests > Forecast-driven Replenishment

• System > Utilities > Purge Messages

• Setup > System > Message Groups

• Setup > System > Workstations

• Setup > Inventory > Adjustment Reason Codes

• Setup > Point of Sale > Discount Codes

• Setup > Point of Sale > Gift Registry Occasions

Step 3: Update CounterPoint Version in CPOnline Skip this step if you are not using CPOnline.

If you are using CPOnline, select your version of CounterPoint from the CounterPoint Version setting on the Store Setup page of CPOnline Store Management.

Step 4: Restart CPDialup service Skip this step if you are not using CPDialup.

If you are using CPDialup to process credit cards, you must restart the CPDialup service. To do this, follow these steps:

1. From the Control Panel, double-click Administrative Tools, and then double-click Services.

2. Right-click the CPDialup service (i.e., CPDialupFDMSNorth, CPDialupFDMSSouth, CPDialupLynk, CPDialupVital, or CPDialupPaymentech) and select Start.

If you are running CPDialup from one or more workstations, instead of from your server, you must copy the updated CPDialup service from your server to those workstations, and then restart the service on each one.

Update Guide


Step 5: Update MSR device files (V8.3.7 only) Skip this step if you are updating from V8.3.8.

CounterPoint SQL supports multi-track GOPOS and keyboard wedge MSR devices, which read track 1 and track 2 of swiped cards simultaneously.

If you are updating from V8.3.7 and you used one of the pre-defined MSR device (.xml) files to configure an MSR, you must load the updated device file before using your MSR in Ticket Entry or Touchscreen Ticket Entry.

Follow these steps to load the updated device file(s) for your MSR(s):

1. From the CounterPoint SQL main menu, select Setup > Point of Sale > Devices to display the Devices window.

2. Click the Configure button on the MSR row, and then click the Load device button.

3. Select the .xml file that corresponds to your MSR and the track you want to read (e.g., Track2Keyboard (Wedge).MSR.xml), and then click Open.

4. Click OK to close the MSR dialog.

5. Click Close to save your device settings and close the Devices window.

Repeat these steps for each workstation that is equipped with an MSR.

Step 6: Schedule history conversion To reduce the amount of time that is required to update a CounterPoint SQL database, the UpdateFrom8.3.x.sql scripts do not update historical data (i.e., posted tickets and other documents). Instead, your history will be updated over time by the CounterPoint History Conversion scheduled task, which you must configure to run at a specific time each day.

Depending on the amount of history in your database, this process may take days or even weeks. You will be able to use CounterPoint during this time, although you will not be able to access all of your historical data until the conversion process is complete.

Follow these steps to schedule the CounterPoint History Conversion task to update your historical data to the V8.3.9 format:

1. Select Start > Programs > CounterPoint > System Configuration Utility to display the System Configuration Utility window, and then click the Scheduled Tasks button.

2. From the CounterPoint Scheduled Tasks window, click New to define a new scheduled task.

3. Select your company from the Alias-Company list, and then select CounterPoint History Conversion from the Task list.

Updating to V8.3.9


4. On the Main tab, select or enter (in 24-hour format) the Start Time for the task. For example, select 0:00 to start the task at midnight each day.

Although you can use CounterPoint while the history conversion task is running, we recommend that you configure the task to start during non-business hours to prevent performance-related issues.

5. Specify the Windows user name you want to use to run the scheduled task in the Run As field, and then enter that user's Password.

Update Guide


6. On the Parameters tab, enter the number of hours you want the history conversion utility to run each day in the Run time (hrs) field.

7. If you would like notification messages to be sent to the appropriate recipient(s) when the history conversion task starts and ends each day, as well as whenever the task encounters an error, specify your Email server, the From email address you want to use, and the To email address for each recipient, separated by semicolons.

8. In the Batch size field, enter the number of days you want the history conversion task to convert in each batch. We recommend that you set this value between 50 and 500.

If you leave the Batch size field blank, the scheduled task will update 100 days of history in each batch.

9. Click OK to save the task and return to the CounterPoint Scheduled Tasks window.

10. Click Close to close the CounterPoint Scheduled Tasks window.

11. If your company database is configured to use SQL authentication, start the Company Names editor (Start > CounterPoint SQL > System Configuration Utility > Companies), edit your database connection string, and select the Allow saving password check box on the Connection tab of the Data Link Properties dialog.

Each day, beginning at the scheduled Start Time, the history conversion task will update as many batches of documents in history as possible within the allotted run time. Depending on the amount of history in your database, this process may take days or even weeks. You will be able to use CounterPoint during this time, although you will not be able to access all of your historical data until the conversion process is complete.

If the task converts an entire batch within the scheduled time, it will begin processing another batch. If the task is unable to complete a batch within the remaining time, it will "roll back" the incomplete batch, and then pick up from where it left off the next time the task is run.

Updating to V8.3.9


If the history conversion task is unable to update a document in a batch for any reason, the entire batch will be "rolled back" and an error message will be sent to each To email address you specified for the task. You must correct whatever problem is preventing the batch from being updated before the history conversion task will be able to complete the batch.

If the history conversion task encounters an error, you can change the Batch size for the task to 1 to configure the task to convert one document at a time. With this setting, you will receive an error message for each document that cannot be updated. Each error message will identify the specific row that is preventing the document from being updated. After you correct the problem, set the Batch size for the scheduled task back to its previous value.

All conversion errors, along with progress messages and other warnings, are also written to the Radiant.Retail.Utilities.HistoryConversion.log file in the \Bin subdirectory of your CounterPoint workstation directory (e.g., C:\Program Files\CounterPoint\Bin).

When all of your history is updated, the task sends a message to each To email address, indicating that the conversion process is complete. At some point thereafter, run the Post 8.3.9 History Conversion Cleanup.sql script (and the Post 8.3.8 History Conversion Cleanup.sql script, if you are updating from V8.3.7) in the \Scripts subdirectory of your top-level directory as an Administrator to remove all unnecessary conversion objects and tables from your database.

The CounterPoint Data Mart Update scheduled task will not run until all of your history is converted to the V8.3.9 format.

Step 7: Provision the server database (Offline V2 only) If you are using Offline V2, after you update your CounterPoint software and database to V8.3.9, you must re-provision your server database by following these steps:

1. Click the Windows Start button and select Program Files > CounterPoint SQL > Radiant Management Console to start the Radiant Management Console.

2. Select Provision Database from the Tools menu to display the Provision Database dialog.

3. Specify your Top-Level Directory or click the button to browse to the top-level directory on your server, and then enter or select the Company Alias for the company database you are provisioning.

4. Enter sa in the SQL User field and CounterPoint8 in the SQL Password field.

If you created a new SQL login for the purpose of provisioning and managing the Offline V2 database on your server, enter the name and password for that login in the SQL User and SQL Password fields.

5. Click Go to re-provision your database. This process can take a considerable amount of time, depending on the size of your database.

A message appears when the provisioning process is complete. Click OK to close this message.

Update Guide


Step 8: Update Offline V2 workstations (Offline V2 only) If you are using Offline V2, once you have updated your Offline V2 server, you must update the Offline V2 components on your offline workstations.

Follow these steps to update your Offline V2 workstations:

1. If you are updating Offline V2 in a WAN environment, copy your top-level directory (e.g., C:\CounterPoint) from your server to a local computer that is accessible by all of your offline workstations.

2. From an offline workstation, browse to \OfflineFiles subdirectory of the top-level directory (e.g., C:\CounterPoint) on your server and double-click OfflineInstall.exe to start the Offline Installation installer.

If you are deploying Offline V2 in a WAN environment, browse to the \OfflineFiles subdirectory of the local top-level directory you created in step 1 of this procedure and double-click OfflineInstall.exe.

3. Click Next from the Welcome dialog to proceed to the Select Server Top-Level Directory dialog, and then enter the path to the Top-Level Directory on your server or click the Browse button to locate the top-level directory.

You can specify a UNC path or a mapped drive in the Top-Level Directory field.

If you are deploying Offline V2 in a WAN environment, specify or browse to the local top-level directory that you created in step 1 of this procedure.

4. Click Next, and then specify the program group to which you want to add the CounterPoint SQL Offline shortcut (e.g., Start > Programs > CounterPoint SQL).

5. Click Next to proceed to the Start Installation dialog, and then click Next to start the CounterPoint SQL Workstation Setup installer.

6. Click Next from the Welcome dialog, and then make sure the Program Files check box is selected on the Select Components dialog.

7. Select the Utilities check box if you want to install the CounterPoint SQL utilities, including the Radiant Management Console, on the offline workstation.

The CounterPoint SQL utilities allow unrestricted access to the CounterPoint database. You may not want to install them on a workstation, unless it will be used only by a system administrator.

8. Select the Dashboard check box if you want to allow users to access the Dashboard while the workstation is operating in normal (i.e., non-offline mode).

The Dashboard is not available in offline mode.

9. Click Next, and then specify the Destination Directory for CounterPoint SQL (e.g., C:\Program Files\CounterPoint).

10. Click Next, and then specify the program group to which you want to add the CounterPoint SQL shortcuts (e.g., Start > Programs > CounterPoint SQL).

11. Click Next, and then follow the on-screen instructions to complete the installation of CounterPoint SQL.

12. When CounterPoint is installed, the Installation Complete dialog appears. If you would like to create CounterPoint shortcuts—one for normal operations and one for offline mode—on the workstation’s desktop, select the Create shortcut on desktop check box.

13. Click Finish to return to the Offline Installation installer, which installs all necessary offline files and copies CounterPoint’s top-level files from the server.

Updating to V8.3.9


14. When the Offline V2 files are installed, the Installation Complete dialog appears. Click Finish to start the CPServices installer automatically.

15. Click Next from the Welcome dialog, and then specify the program group to which you want to add the Radiant Management Console and Radiant Log Viewer shortcuts (e.g., Start > Programs > CounterPoint SQL).

16. Click Next to proceed to the Start Installation dialog, and then click Next to begin installing Radiant CounterPoint Services.

A series of progress bars keeps you apprised of the status of the installation.

17. When CPServices is installed, the Installation Complete dialog appears. Click OK to close the dialog.

Repeat steps 2 through 17 for each of your offline workstations.

Step 9: Rebuild offline databases (Offline V2 only) If you are using Offline V2, you must rebuild your offline databases after you have updated your server and each offline workstation.

Follow these steps to rebuild the offline databases in your Offline V2 environment:

1. On your server or on a workstation that is connected to your server, select Start > Programs > CounterPoint SQL > Radiant Management Console to start the Radiant Management Console.

2. Select your server from the Object Explorer tree.

All connections defined using the Remember this password option will automatically appear in the Object Explorer tree when you start the Radiant Management Console. If you do not see your server in the Object Explorer tree, click Connect and select the server from the Server History dialog.

3. From the Object Explorer tree, select a store that includes one or more offline workstations, and then click the button to rebuild the local database on each of that store’s offline workstations.

Repeat step 3 for each store that includes one or more offline workstations.

Step 10: Enable "smart mouse" setting on workstations The Smart Mouse setting that was previously available on the Workstation Preferences window in CounterPoint SQL is no longer available. If you were using this setting to automatically move the pointer to the default button of each dialog in CounterPoint, you can instead enable the equivalent setting on the Mouse Properties property sheet of the Windows Control Panel.

To enable this setting, select Start > Settings > Control Panel, double-click Mouse, select the Pointer Options tab, and select the Snap To check box.

Repeat this step for each workstation on which you wish to enable this setting.


Updating customizations If you are updating a CounterPoint SQL system that has been customized, you must ensure that the custom modifications that were implemented in your old version are appropriate and function correctly in V8.3.9. This section of the CounterPoint SQL Update Guide highlights some of the changes that may have an impact on your customizations and describes specific areas of the software you should consider before updating. These topics are not intended to be an exhaustive "to do" list, but should serve as a suitable starting point to enable you to make a smooth transition to V8.3.9.

You should have records of the custom modifications that have been made to your system. Review the details of those records before reading the topics in this section.

You should also generate and print the Database Customizations Report (System > Utilities > Database Customizations Report) to be sure you have a record of all your customizations. This report lists database schema changes, triggers, stored procedures, and other information that you should document. It is easy to forget exactly how your system has been modified and this report is a useful tool for tracking those changes.

Review the Database Comparison topics for detailed information about the differences between the default V8.3.8 and V8.3.9 database schema. For a comparison between the V8.3.7 and V8.3.9 database schema, refer to the CompareDBResultsFrom837.html file on the CounterPoint SQL DVD.

In addition, you may wish to print screen shots of certain customizations, such as custom maintenance or view forms, to verify that the new system matches your old version.

Database schema changes BOGO/twofer pricing Custom and customized reports OPOS Point of Sale forms Update Pre-defined Data Delta-tracked tables Custom stored procedures Prompt for custom payment fields Validated returns Ticket Entry customizations (V8.3.7 only) Ticket posting customizations (V8.3.7 only) Crystal receipts and Point of Sale forms (V8.3.7 only) Fixing custom Crystal reports and receipts (V8.3.7 only) Custom Point of Sale maintenance forms (V8.3.7 only) Custom indexes for Point of Sale tables (V8.3.7 only) Data Dictionary considerations (V8.3.7 only) Drawer sessions and events (V8.3.7 only) Improved performance for posting receivings (V8.3.7 only) Modified commission calculation stored procedure (V8.3.7 only) Modified finance charge calculation stored procedures (V8.3.7 only) Modified pricing stored procedures (V8.3.7 only) Quick assembly transactions (V8.3.7 only) Suppressing the authorization codes dialog (V8.3.7 only) Suppressing the ticket completion confirmation (V8.3.7 only)

Update Guide


Database schema changes Typically, database schema changes you have made will be retained during the update process, because those changes are part of the database. However, you must take the appropriate steps to ensure that your customizations are incorporated into the UpdateFrom8.3.x.sql scripts before you begin the update. For example, if you added a trigger that depends on a particular database column and that column is removed by the update script, your trigger will not work.

Refer to the Database Comparison topics for detailed information about the differences between the V8.3.8 and V8.3.9 database schema.

Refer to the CompareDBResultsFrom837.html file in the root directory of the CounterPoint SQL DVD for detailed information about the differences between the V8.3.7 and V8.3.9 database schema.

Point of Sale data model changes (V8.3.7 only) In V8.3.8, extensive changes were made to the Point of Sale data model. CounterPoint only supports custom fields in Point of Sale transaction tables for which there is a corresponding EXT table (i.e., header, line, payment, cell, and serial number tables).

Custom columns are not supported in Point of Sale transaction tables for which there is not a corresponding EXT table (i.e., tax, package tracking, note, stored value card, gift certificate, and audit log tables).

If you are updating from V8.3.7 and you have added custom columns to V8.3.7 Point of Sale (PS) tables for which custom columns are still supported, the UpdateFrom8.3.7.sql script and the history conversion task will move your custom columns and their contents to the appropriate EXT table. After you update your database, you should add all future custom columns to one of these EXT tables (e.g., PS_DOC_HDR_EXT).

If you have added custom columns to tables for which they are no longer supported, those columns will be dropped and the data stored in them will be lost when you update to V8.3.9. You must take the necessary steps to preserve the data in your custom columns.

In addition, any custom constraints you may have added to any Point of Sale tables (including constraints on custom columns) will be lost when you update to V8.3.8. Similarly, if you have added SQL-calculated columns to any Point of Sale tables, they will also be lost during the update. You may be able to manually restore your constraints and SQL-calculated columns to the appropriate V8.3.8 tables after you update your database.

BOGO/twofer pricing As detailed in the current Release Notes, CounterPoint now allows you to define "BOGO" (e.g., "buy one, get one free" or "buy one, get one for 50% off") and "twofer" (e.g., "2 for $1.00" or "3 for $5.00) price rules. If you customized a previous version of CounterPoint to simulate BOGO/twofer pricing, you may wish to disable or remove those modifications and use the BOGO/twofer pricing that is built in to V8.3.8 instead.

Implementing the BOGO/twofer pricing feature required major changes to the price and loyalty point calculation process. If you have made any customizations related to price or loyalty point calculations, in all likelihood, they will no longer work after you update to V8.3.9.

Specific, known issues related to these pricing changes are outlined below:

Pricing stored procedure changes The USP_GET_PRICE stored procedure that was used in previous versions of CounterPoint SQL has been renamed to USP_PRICE_GET_PRICE. If you have customized the USP_GET_PRICE stored procedure in a previous version, it will be renamed automatically when you update your database.

Similarly, if you have implemented USER_BEFORE_GET_PRICE and USER_AFTER_GET_PRICE stored procedures in your database, they will be renamed USER_BEFORE_PRICE_GET_PRICE and USER_AFTER_PRICE_GET_PRICE when you update your database.

Updating customizations


In addition, the parameters for the following pricing stored procedures have been changed to accommodate BOGO/twofer pricing. If you have customized any of these stored procedures, you must update them to match the new parameters.

• USP_PRICE_GET_PRICE

• USER_BEFORE_PRICE_GET_PRICE

• USER_AFTER_PRICE_GET_PRICE

• USP_GET_PRICE_AND_POINTS

• USER_BEFORE_GET_PRICE_AND_POINTS

• USER_AFTER_GET_PRICE_AND_POINTS

Refer to the Database Comparison topics for detailed information about stored procedure changes.

Custom price rules In previous versions, if you created custom stored procedures for inclusion in price rules, the names of the parameters you included in those stored procedures did not matter, only that they appeared in the correct order. In this version, you must update your custom price rule stored procedures to use the following parameter names:

• @SessionId

• @LineSessionId

• @GrpCod

• @GrpTyp

• @RulSeqNo

• @ItemNumter

• @CustomerNumber

• @StkLocID

• @PrcLocID

• @AbsLineQtySold

• @UnitFlag

• @SaleDateTime

• @UnitPrice

• @PricingBreakDesc

Custom loyalty point earning rules If you have created custom stored procedures for inclusion in loyalty point earning rules, you must update them to use the following parameters:

• @CustNo

• @ItemNo

• @QtySoldInStkU

• @ExtPrice

• @PtsEarned

Update Guide


Custom triggers If you have implemented custom triggers on the IM_PRC_WRK table and/or the IM_PRC_WRK_CELL table, you should verify that your triggers still work as expected.

Hold and Recall price modifications If you have implemented custom stored procedures to modify prices on Point of Sale documents during a Hold and Recall action, you should verify that they still work as expected.

If your customizations update prices by recording a price override, they should continue to work. However, if your customizations changed prices without performing a price override, they will no longer function.

To modify prices during a Hold and Recall action, you must change data in the PS_DOC_LIN_PRICE table (e.g., UNIT_PRC). When a Point of Sale document is recalled, CounterPoint will recalculate line-level prices (e.g., CALC_PRC, PRC, EXT_PRC, and so forth) based on the new PS_DOC_LIN_PRICE values.

In addition, each line item may now have multiple prices. If your Hold and Recall customizations assume that only one price value exists per line, you should update them accordingly.

Price justification data If you have customized any process that reads or writes price justification data (e.g., PRC_GRP_COD, PRC_GRP_DESCR, PRC_RUL_DESCR and so forth), you must update your customizations to accommodate the following changes:

• The PS_DOC_LIN_PRICE_COST table has been renamed to PS_DOC_LIN_PRICE

• Each Point of Sale document line may now have more than one record in the PS_DOC_LIN_PRICE table

• Price justification fields have been removed from many views (including VI_PS_DOC_LIN)

Custom and customized reports As always, you should review your custom reports and any standard reports you have modified—whether they are based on stored procedures or tables—and update them to accommodate any relevant database schema changes.

If you are updating from V8.3.7, custom reports that rely on Point of Sale (PS) tables require particular attention, as they will no longer work after you update to V8.3.9, due to the extensive Point of Sale data model changes that were made in V8.3.8. If you do not take the appropriate action to update your custom .rpt files, you will encounter errors when CounterPoint attempts to use them.

Follow the steps outlined in Fixing custom Crystal reports and receipts to update your custom reports to work in V8.3.9.

If you only use standard (i.e., non-customized) reports, you do not have to take any additional steps.



OPOS Point of Sale forms As always, if you have customized OPOS (.xml) Point of Sale forms, review those modifications and update them to accommodate any relevant database schema changes.

Refer to the Database Comparison topics for detailed information about the differences between the V8.3.8 and V8.3.9 database schema.

Refer to the CompareDBResultsFrom837.html file in the root directory of the CounterPoint SQL DVD for detailed information about the differences between the V8.3.7 and V8.3.9 database schema.

Point of Sale data model changes (V8.3.7 only) If you are updating from V8.3.7, OPOS receipts and other Point of Sale forms should not be affected by the Point of Sale data model changes that were made in V8.3.8. However, if a custom OPOS form refers to a column that has been dropped, you will need to remove or replace that field. Again, you should carefully review your custom OPOS forms to determine whether you need to modify them.

In particular, the views from which OPOS receipts obtain their data have been renamed to replace TKT with DOC (e.g., VI_PS_TKT_HDR_RCPT was renamed VI_PS_DOC_HDR_RCPT). If you have added custom fields to the V8.3.7 views, you should add them to the renamed views.

Update Pre-defined Data The Update Pre-defined Data utility (System > Utilities > Update pre-defined data) does not remove existing form groups or label jobs. If you have modified a form group or label job and you want to restore the original, unmodified version, you must delete the existing form group or label job before running the Update Pre-defined Data utility.

The FORM GROUPS report (Setup > Point of Sale > Reports > Form Groups) allows you to print all components of a form group. You can use this report as a reference to assist you in redefining your form groups, if necessary.

Similarly, the LABEL JOBS report (Setup > System > Reports > Label Jobs) allows you to print detailed information about label jobs.

Delta-tracked tables Special handling is required for triggers on Multi-Site delta-tracked tables. The following tables are delta-tracked tables in V8.3.9:

• Customers - AR_CUST

• Inventory - IM_INV

• Inventory Cell - IM_INV_CELL

• Gift Certificates - SY_GFC

• Store Credits - SY_STC

• Receiving History - PO_RECVR_HIST

• Receiving History Lines - PO_RECVR_HIST_LIN

• RTV History - PO_RTV_HIST

Update Guide


Custom stored procedures You can now define up to three custom stored procedures that CounterPoint SQL will execute whenever a user saves or deletes a record from any standard maintenance window, such as the Items window, the Customers window, the Purchase Requests Enter window, and so forth. This feature allows you to apply custom database functions to a record or perform other special actions each time the record is updated.

For each maintenance window, you can create the following custom stored procedures, where TableName is the name of the underlying database table:

• USER_TableName_BEGIN_TRANSACTION is executed immediately after a user saves or deletes a record and CounterPoint begins the corresponding SQL transaction.

• USER_TableName_BEFORE_COMMIT_TRANSACTION is executed immediately before the SQL transaction is committed to the database.

• USER_TableName_AFTER_COMMIT_TRANSACTION is executed immediately after the SQL transaction is committed to the database.

If you had been using triggers to hook into such operations, you may be able to simplify your customizations by using these stored procedure hooks instead.

Prompt for custom payment fields You can include custom fields on the payment Validations dialog by adding a custom column to the PS_DOC_PMT_EXT table, and then adding the column to the Standard form for the PS_TE_PMT table in the Data Dictionary.

If you previously wanted to prompt for custom fields on the Validations dialog and have implemented a workaround instead, you may disable or remove those modifications and use the built-in feature instead.

Validated returns You can use the Validated returns function in Ticket Entry and Touchscreen Ticket Entry to process validated returns for items for which a ticket is on file.

If you customized a previous version of CounterPoint to allow validated returns, you may wish to disable or remove those modifications and use the built-in validated returns feature instead.



Ticket Entry customizations (V8.3.7 only) Due to the changes made to the Point of Sale data model in V8.3.8, any custom behavior you may have implemented in Ticket Entry in V8.3.7 will no longer function after you update to V8.3.9.

If you have created custom stored procedures, triggers, or other database functions to execute before or after a Point of Sale document is saved or printed, or during a hold-and-recall action, you must update those customizations to accommodate the new Point of Sale table structure and other database changes.

Stored procedures All standard Ticket Entry stored procedures have been renamed to include the TE designator. For example, the USP_COMMIT_PS_DOC_BAL stored procedure is now USP_PS_TE_COMMIT_DOC. As a result, calls to corresponding USER_BEFORE and USER_AFTER stored procedures were also renamed.

If you have defined any custom stored procedures that perform some special action immediately before or after any standard stored procedures in Ticket Entry, you must rename them to match V8.3.9 naming conventions. Refer to the CompareDBResultsFrom837.html file on the CounterPoint SQL DVD for more information about new, dropped, and modified stored procedures.

In addition, the @StrId, @StaId, and @TktNo parameters have been dropped and replaced by the @DocId parameter in all Ticket Entry stored procedures that previously accepted them. You must modify your custom stored procedures accordingly.

Database triggers If you have created custom database triggers in any Point of Sale (PS) tables, they will be dropped when you update to V8.3.9.

After you update your database, you should carefully evaluate the new Point of Sale table structure and decide whether you want to recreate your database triggers or replace them with custom stored procedures. Bear in mind that, due to the division of Point of Sale data that occurred in V8.3.8, you may have to create triggers in multiple tables to reproduce the behavior of a single trigger in previous versions.

Absent child records If you previously used UPDATE statements to update ticket data, you may have to modify your customizations to UPDATE or INSERT data, as appropriate, to accommodate the possibility of "child" records that don't exist.

For example, you might use a hold-and-recall action to add ship-to addresses to tickets. Previously, you could have used an UPDATE statement to update the PS_TKT_HDR table. Since ship-to information is now stored in the PS_DOC_CONTACT table, if a ticket did not already have a ship-to address, you must use an INSERT statement to add one.

Update Guide


Ticket posting customizations (V8.3.7 only) Due to the Point of Sale data model changes that were made in V8.3.8, any custom stored procedures or triggers you implemented in V8.3.7 to "hook" into the ticket posting process will no longer function after you update to V8.3.9.

If you have created custom stored procedures, triggers, or other database functions to execute before or after a Point of Sale document is posted, or during the posting process, you must update those customizations to accommodate the new Point of Sale table structure and other database changes.

For example, if you have defined any of the following custom stored procedures, you must modify them to accept the appropriate parameters (i.e., @DocId instead of @TktNo):

• USER_BEFORE_PS_DOC_POST_RUN

• USER_PS_DOC_POST_TRX

• USER_AFTER_PS_DOC_POST_RUN

In addition, if you have defined any USER_BEFORE or USER_AFTER stored procedures to hook into the various steps in the ticket posting process, you must update them to match the renamed USP_COPY stored procedures and modify them to accept the appropriate parameters.

Finally, custom database triggers in PS tables will be dropped when you update to V8.3.9. You should carefully evaluate the new Point of Sale table structure and decide whether you want to recreate your database triggers or replace them with custom stored procedures. Bear in mind that, due to the division of Point of Sale data that occurred in V8.3.8, you may have to create triggers in multiple tables to reproduce the behavior of a single trigger in previous versions.

Crystal receipts and Point of Sale forms (V8.3.7 only) If you are updating from V8.3.7, custom Crystal Reports format (.rpt) receipts and other Point of Sale forms will no longer function after you update to V8.3.9 due to the changes to the Point of Sale data model that were made in V8.3.8, . If you do not take the appropriate action to update the corresponding .rpt files, you will encounter errors when CounterPoint attempts to use them.

Follow the steps outlined in Fixing custom Crystal reports and receipts to update your custom Crystal Reports format receipts to work in V8.3.9.

If you only use standard (i.e., non-customized) Crystal Reports format receipts, you do not have to take any additional steps.



Fixing custom Crystal reports and receipts (V8.3.7 only) If you are updating from V8.3.7, follow these steps to update your custom Crystal receipts and reports to work with V8.3.9:

1. From a workstation on which you installed the CounterPoint uilities, browse to the \Bin subdirectory of the CounterPoint workstation directory (e.g., C:\Program Files\CounterPoint\Bin).

2. Double-click the ReplaceTablesInCrystalReports.exe file to start the Crystal Replace Tables utility.

3. Select the CPSQL alias for your CounterPoint SQL database, enter its Connection string, or click the button to select your database from the Data Link Properties dialog.

If you select your database from the Data Link Properties dialog and your SQL server is configured to use SQL authentication, you must specify the User name (e.g., sa) and Password for the database connection and select the Allow saving password check box on the Connection tab of the Data Link Properties dialog.

The database you choose must be updated to the current schema and must include all of your custom database modifications.

4. Click the Load table list button, and then double-click the ReplaceTablesInCrystalReports.ini file, which is located in the \Bin subdirectory of your CounterPoint workstation directory.

5. In the Directory field, enter the path to the directory that contains your custom reports (e.g., C:\CounterPoint\MyCompany\Reports), or click the button to browse to the directory.

6. In the Reports field, enter the name of the custom report file you want to update, or type *.rpt to update all custom reports in the specified directory.

7. Click the Run button to start the replacement process.

The Crystal Replace Tables utility updates all references to Point of Sale tables in the specified .rpt file(s) to comply with the new Point of Sale data model and saves each updated .rpt file in the \Replaced subdirectory of the Directory you specified.

When the replacement process is finished, the Crystal Replace Tables utility indicates the number of reports that were processed and the number of reports that were changed, along with any errors that occurred.

8. Test the revised .rpt files to verify that they will function properly. You can use the Verify tab of the Verify Reports utility to test the modified reports.

9. For each of your custom reports that is based on a stored procedure, use the SQL Script Utility (Start > Programs > CounterPoint SQL > SQL Script Utility) or another SQL editor to modify the stored procedure for the report as follows:

• Change table references to the appropriate tables. Refer to the Point of Sale table structure topics and the CompareDBResultsFrom837.html file on the CounterPoint SQL DVD for detailed information about the differences between the V8.3.7 and V8.3.9 database schema.

• Modify joins from VI_PS_DOC_HDR to other live ticket views to join on DOC_ID, instead of on STR_ID, STA_ID, and TKT_NO.

• Modify joins from VI_PS_DOC_LIN to VI_PS_DOC_LIN_CELL or VI_PS_DOC_LIN_SER to join on DOC_ID and LIN_SEQ_NO, instead of on STR_ID, STA_ID, TKT_NO and SEQ_NO.

• Modify joins from VI_PS_xxx_HIST to other historical ticket views to join on BUS_DAT and DOC_ID, instead of on EVENT_NO, STR_ID, STA_ID, and TKT_NO.

Update Guide


• Modify joins from VI_PS_xxx_HIST_LIN to VI_PS_xxx_HIST_LIN_CELL or VI_PS_xxx_HIST_LIN_SER to join on BUS_DAT, DOC_ID and LIN_SEQ_NO, instead of on EVENT_NO, STR_ID, STA_ID, TKT_NO and SEQ_NO.

• Change any obsolete parameters to the appropriate V8.3.8 parameters (e.g., @PS_TKT_HDR_Filter should be @VI_PS_DOC_HDR_Filter).

10. Use the Crystal Reports Designer to reset the datasource location (Database > Set Datasource Location) for each main report and subreport, if applicable, to the appropriate SQL server and database. You may have to reset individual objects for each subreport, in which case you should reset tables first, followed by views, and then stored procedures.

11. Use the Crystal Reports Designer to modify the links in each main report, the links from each main report to any subreports, and the links in each subreport as follows:

• Modify links from VI_PS_DOC_HDR to other live ticket views to link on DOC_ID, instead of on STR_ID, STA_ID, and TKT_NO.

• Modify links from VI_PS_DOC_LIN to VI_PS_DOC_LIN_CELL or VI_PS_DOC_LIN_SER to link on DOC_ID and LIN_SEQ_NO, instead of on STR_ID, STA_ID, TKT_NO and SEQ_NO.

• Modify links from VI_PS_xxx_HIST to other historical ticket views to link on BUS_DAT and DOC_ID, instead of on EVENT_NO, STR_ID, STA_ID, and TKT_NO.

• Modify links from VI_PS_xxx_HIST_LIN to VI_PS_xxx_HIST_LIN_CELL or VI_PS_xxx_HIST_LIN_SER to link on BUS_DAT, DOC_ID and LIN_SEQ_NO, instead of on EVENT_NO, STR_ID, STA_ID, TKT_NO and SEQ_NO.

12. For each link from a main report to a subreport that you modified, edit the subreport and modify the record selection formula (Report > Selection Formulas > Record) to reflect those changes, and then delete any text related to duplicate links or links you removed.

13. For each column listed in the Subreport Links window for which the Selected data in subreport based on field check box is not selected, select a view, instead of a table, from the Subreport parameter field to use field.

14. For each subreport you updated in step 13, right-click each formula field that appears in the Field Explorer and select Edit to display the Formula Editor, and then replace each table in the formula with the corresponding view.

15. Select Database > Show SQL Query for each main report and all subreports. If the Reset button appears on the SQL query dialog, click it, and then click OK.

16. For each report, use the Verify Database command in the Crystal Reports Designer to check the report for errors. Take the appropriate action to correct each error.

17. Preview each custom report in the Crystal Reports Designer to ensure that no errors appear on the report. If the report spans multiple pages, check each page for errors.

As a result of datatype changes in V8.3.8, you may encounter the following violations of CounterPoint's reporting standards when you preview your custom reports:

• Dollar signs that precede a monetary value - To remove the dollar sign from a field, right-click the field in the Crystal Reports Designer, select Format Field, select the Number tab, and clear the Display Currency Symbol check box.

• Parentheses around negative values - To replace the parentheses with a negative sign, right-click each affected field, select Format Field, select the Number tab, click the Customize button, and change the Negatives setting from (123) to -123.



18. Compare each custom report to the same report in V8.3.7 to ensure that the report is producing similar results.

19. When you are satisfied that your revised .rpt files function as you expect, copy them from the \Replaced subdirectory into the directory that contains your custom reports.

Repeat these steps for your custom Crystal receipts, which are typically located in the \PSForms subdirectory of your company directory (e.g., C:\CounterPoint\MyCompany\PSForms).

Custom Point of Sale maintenance forms (V8.3.7 only) If you created custom maintenance forms that rely on Point of Sale (PS) tables in V8.3.7, they will no longer work after you update to V8.3.9 due to the changes to the Point of Sale data model that were made in V8.3.8.

If your custom form only allows users to view data, you should be able to update the form to work in V8.3.9 by following these steps:

1. Using the Menu Editor (Setup > System > Menu Codes), change the Table for your custom form from the previous PS table (e.g., PS_TKT_HDR or PS_TKT_LIN) to the equivalent V8.3.8 view (e.g., VI_PS_DOC_HDR or VI_PS_DOC_LIN).

2. Using the Custom Form editor, which is accessible from the Data Dictionary window (Setup > System > Configuration > Data Dictionary), add the DOC_ID column to your custom form.

If your custom form is based on a historical view (e.g., VI_PS_TKT_HIST), you must also add the BUS_DAT column to it.

3. Review your custom form layout and update any fields whose names have changed.

At this point, you should be able to access your custom form and view data.

Custom maintenance forms that allow users to add or update data in Point of Sale tables may need additional changes to work with V8.3.9.

Please contact Professional Services at [email protected] for assistance in updating such forms.

Custom indexes for Point of Sale tables (V8.3.7 only) Due to the changes to the Point of Sale data model that were made in V8.3.8, if you defined custom indexes for any Point of Sale (PS) tables in your V8.3.7 CounterPoint database(s), they will be dropped when you update to V8.3.9.

After you update your database, you may recreate your custom indexes to accommodate the new Point of Sale table structure.

mailto:[email protected]�

Update Guide


Data Dictionary considerations (V8.3.7 only) The update process attempts to retain all custom data dictionary entries, including those that affect Point of Sale behavior. However, due to the extent of the changes that were made to the Point of Sale data model in V8.3.8, we cannot guarantee that all data dictionary changes you may have made will work as expected.

After you update to V8.3.9, you should carefully review your custom data dictionary entries to verify that they have been converted into the new Point of Sale table structure. You may need to make additional data dictionary modifications to restore previous custom behavior.

Data dictionary entries in physical tables no longer have any effect in Ticket Entry. If you want your data dictionary changes to affect Ticket Entry, modify the data dictionary entries in one of the following PS_TE_ tables, as appropriate.

• PS_TE_HDR • PS_TE_LIN • PS_TE_LIN_CELL • PS_TE_LIN_SER • PS_TE_PMT • PS_TE_NOTE • PS_TE_AUDIT_LOG • PS_TE_GFC • PS_TE_PKG_TRK_NO • PS_TE_SVC • PS_TE_TAX

If you want your data dictionary changes to affect the View Tickets window or Point of Sale reports, modify the data dictionary entries in the appropriate VI_PS_DOC_ view (e.g., VI_PS_DOC_HDR or VI_PS_DOC_LIN) instead.

As always, data dictionary changes you make to the virtual tables will affect Ticket Entry, the View Tickets window, and the corresponding reports.

Drawer sessions and events (V8.3.7 only) CounterPoint SQL V8.3.8 introduced the concept of drawer sessions and drawer events, which organize all drawer-related activity into logical groups for the purpose of cash accountability. As a result, the PS_DRW_SESSION, PS_DRW_SESSION_EVENT, and PS_DRW_SESSION_EVENT_DETAIL were added to database.

In addition, the PS_DRW, PS_DRW_CLS_HIST, and PS_USR_DRW tables were modified. In particular, the PS_DRW.STAT column was dropped, which means that status values are no longer tracked for individual drawers. If you are updating from V8.3.7 and your database includes customizations that rely on this column, you must modify them to use the PS_DRW_SESSION.STAT column instead.

Finally, the PS_DRW_CLS table was dropped. If your V8.3.7 database includes customizations that rely on the PS_DRW_CLS table, you must modify them accordingly, as they will no longer work.

If your customizations simply read data from the PS_DRW_CLS table, you can use the VI_PS_DRW_CLS view instead. If your customizations wrote data to the PS_DRW_CLS table, you must modify them to write to the appropriate drawer session tables instead (i.e., PS_DRW_SESSION, PS_DRW_SESSION_EVENT, and PS_DRW_SESSION_EVENT_DETAIL).

Similarly, if you had triggers in PS_DR_CLS, you can likely recreate them in the new tables to attain similar results.



Improved performance for posting receivings (V8.3.7 only) In V8.3.8, the receivings posting process (Purchasing > Receivings > Post) was optimized to improve performance, particularly during the posting of allocated receivings or receivings with large quantities of gridded items. As a result, any custom triggers you created in your V8.3.7 database to "hook" into this process may fire at different times than they did in previous versions and may not perform as expected.

Modified commission calculation stored procedure (V8.3.7 only) The USP_CALC_COMMIS stored procedure, which calculates commissions for tickets, was modified in conjunction with the Point of Sale data model changes that were made for V8.3.8.

If your V8.3.7 database includes custom stored procedures that run before or after USP_CALC_COMMIS, or a modified version of USP_CALC_COMMIS itself, you must modify them to accommodate these changes.

Modified finance charge calculation stored procedures (V8.3.7 only) The USP_AR_ASSESS_FCH and USP_CREATE_FCH_TRX stored procedures, which calculate finance charges for AR customers, were modified in V8.3.8.

If your V8.3.7 database includes custom stored procedures that run before or after USP_AR_ASSESS_FCH and USP_CREATE_FCH_TRX, or modified versions of these stored procedures themselves, you must modify them to accommodate these changes.

Modified pricing stored procedures (V8.3.7 only) The USP_PRICE_GET_PRICE and USP_GET_PRICE_AND_POINTS stored procedures, which calculate prices and loyalty points for tickets, were modified in conjunction with the Point of Sale data model changes that were made for V8.3.8.

If your V8.3.7 database includes custom stored procedures that run before or after USP_PRICE_GET_PRICE or USP_GET_PRICE_AND_POINTS, or modified versions of these stored procedures themselves, you must modify them to accommodate these changes.

Quick assembly transactions (V8.3.7 only) To support the Bills of Material feature, the CounterPoint SQL database schema was updated in a V8.3.7 Service Pack to accommodate quick assembly transactions.

Quick assembly transactions create inventory history transactions using a new set of tables. The Inventory History view includes these tables and a flag for the quick assembly transaction type.

If you are updating from V8.3.7 and you have customized the Inventory History view (VI_INV_HIST) or created any custom views that are based on specific transaction types, you may have to modify them to accommodate the new tables and transaction type.

Update Guide


Suppressing the authorization codes dialog (V8.3.7 only) You can now suppress the authorization codes dialog that normally appears whenever a user authorizes a credit or debit card for payment in Ticket Entry and Touchscreen Ticket Entry.

If you customized the Text Dictionary in V8.3.7 to suppress this message (PSAUTHMESSAGE), you do not need to take any action to suppress it after you update to V8.3.9, as the Suppress EDC authorization code information dialog check box on the Tickets-2 tab of the Stores window will be selected by default.

If you would like the authorization codes dialog to appear when a user authorizes a credit or debit card, clear this check box.

Suppressing the ticket completion confirmation (V8.3.7 only) You can suppress the confirmation dialog that normally appears when a user completes a ticket in Ticket Entry and Touchscreen Ticket Entry.

If you customized the Text Dictionary in V8.3.7 to suppress this message (PSTECONFTKTCOMP), you must select the Suppress ticket completion confirmation dialog check box on the Tickets-2 tab of the Stores window (Setup > Point of Sale > Stores) to continue to suppress it after you update to V8.3.9.


Database Comparison Use the following links to review detailed information about the differences between the standard V8.3.8 and V8.3.9 CounterPoint SQL database schema, including the tables, views, stored procedures, and functions that have been added, modified or dropped.

Refer to the CompareDBResultsFrom837.htm file in the root directory of the CounterPoint SQL DVD for a summary of database schema changes between V8.3.7 and V8.3.9.

Tables Views Stored Procedures Functions

Tables New Tables Modified Tables Dropped Tables

Update Guide


New Tables DM_LOC_HIST

DM_LOC_HIST_SUBSCRIBE

DM_STATS_STR_USR_DAY

DM_TRX_LOC_ITEM_SEAS

DM_TRX_LOG_DAY

IM_ADJ_REAS_COD

IM_DYNMINMAX_WRK

IM_FORCST_SEAS_HDR

IM_FORCST_SEAS_LIN

IM_FORCST_WRK

IM_INV_GRID_OVERVIEW_WRK

IM_ITEM_EC_DEL

PS_DEV_CFG

PS_DEV_LOGCL

PS_DEV_LOGCL_INST

PS_DEV_LOGCL_INST_PROP

PS_DEV_LOGCL_PROP

PS_DEV_PHYS

PS_DEV_PHYS_INST

PS_DEV_PHYS_LOGCL

PS_DEV_PHYS_TYP

PS_DEV_PORT_TYP

PS_DEV_TMPLT

PS_DEV_TMPLT_LOGCL

PS_DEV_TMPLT_LOGCL_PROP

PS_DEV_TMPLT_PHYS

PS_DEV_TMPLT_TYP

PS_DISC_COD

PS_DOC_DISC

PS_DOC_LIN_KIT

PS_DOC_LIN_PRICE

PS_DOC_PMT_RCPT

PS_GFT_RGSTRY_EC_DEL

PS_GFT_RGSTRY_EVNT_TYP

PS_GFT_RGSTRY_HDR

PS_GFT_RGSTRY_LIN

PS_GFT_RGSTRY_LIN_MSD

PS_LWY_HIST_DISC

PS_LWY_HIST_LIN_KIT

PS_LWY_HIST_LIN_PRICE

PS_LWY_HIST_PMT_RCPT

PS_ORD_HIST_DISC

PS_ORD_HIST_LIN_KIT

PS_ORD_HIST_LIN_PRICE

PS_ORD_HIST_PMT_RCPT

PS_TKT_HIST_DISC

PS_TKT_HIST_LIN_KIT

PS_TKT_HIST_LIN_PRICE

PS_TKT_HIST_PMT_RCPT

PS_TRX_LOG

PS_VOID_HIST_DISC

PS_VOID_HIST_LIN_KIT

PS_VOID_HIST_LIN_PRICE

PS_VOID_HIST_PMT_RCPT

SY_DB

SY_DB_LOC

SY_DB_MAINT_SCHED

SY_DB_STR

SY_KEY

SY_KEY_CTR

SY_MAIL

SY_MAIL_GRP

SY_MAIL_GRP_USR

SY_MAIL_RECPNT

SY_WORKSTATION

Database Comparison


Modified Tables AR_CATEG_COD

PS_FRM_ID Column dropped

PS_HDR_CUST_FLD_FRM_ID Column added

AR_CUST



DB_CTL

DB_VER Columns Numeric-Scale from 2 to

DB_VER Columns Numeric-Precision-Radix from 10 to

DB_VER Precision from 5 to

DB_VER Data Type changed from decimal to varchar

DB_VER Domain changed from T_VER to T_VER_STR

EC_CTL

LST_ITEM_PUB_UTC_DT Column added

ORD_DISC_MISC_CHRG_NO Column dropped

DF_EC_CTL_ORD_DISC_MISC_CHRG_NO Default dropped

CK_EC_CTL_ORD_DISC_MISC_CHRG_NO Check dropped

CK_EC_CTL_ORD_INSUFF_QTY_METH Check changed from [ORD_INSUFF_QTY_METH]='B' OR [ORD_INSUFF_QTY_METH]='A' OR [ORD_INSUFF_QTY_METH]='O' to

to [ORD_INSUFF_QTY_METH]='O' OR [ORD_INSUFF_QTY_METH]='A'

IM_ADJ_HIST

LIN_GUID Column added

REAS_COD Column added

Update Guide


IM_ADJ_TRX

LIN_GUID Column added

REAS_COD Column added

FK_IM_ADJ_TRX_IM_ADJ_REAS_COD ForeignKeys added

IM_CATEG_COD


PS_LIN_CUST_FLD_FRM_ID Column added

TRGT_PFT_PCT Column added

CK_IM_CATEG_COD_TRGT_PFT_PCT Check added

IM_CNT_HIST

IM_CNT_HIST_X3 Indexes added

IM_CTL

COPY_ITEM_COPY_GRID_DIM Column dropped

COPY_ITEM_PROMPT_BARCOD Column dropped

COPY_ITEM_PROMPT_GRID_DIM Column dropped

COPY_ITEM_PROMPT_SUBST_ITEM Column dropped

MRGN_BTW_MIN_AND_TRGT_MRGN_COLOR Column added

MRGN_LESS_THAN_MIN_MRGN_COLOR Column added

MRGN_MEET_EXCEED_TRGT_MRGN_COLOR Column added

DF_IM_CTL_COPY_ITEM_COPY_GRID_DIM Default dropped

DF_IM_CTL_COPY_ITEM_PROMPT_BARCOD Default dropped

DF_IM_CTL_COPY_ITEM_PROMPT_GRID_DIM Default dropped

DF_IM_CTL_COPY_ITEM_PROMPT_SUBST_ITEM Default dropped

DF_IM_CTL_MRGN_BTW_MIN_AND_TRGT_MRGN_COLOR Default added

DF_IM_CTL_MRGN_LESS_THAN_MIN_MRGN_COLOR Default added

DF_IM_CTL_MRGN_MEET_EXCEED_TRGT_MRGN_COLOR Default added

CK_IM_CTL_COPY_ITEM_COPY_GRID_DIM Check dropped

CK_IM_CTL_COPY_ITEM_PROMPT_BARCOD Check dropped

CK_IM_CTL_COPY_ITEM_PROMPT_GRID_DIM Check dropped

CK_IM_CTL_COPY_ITEM_PROMPT_SUBST_ITEM Check dropped

Database Comparison


IM_INV

ANNL_HLD_COST Column added

ANNL_HLD_COST_PERC Column added

EOQ Column added

EOQ_CALC_ON Column added

ORD_COST_PER_ORDER Column added

REORD_PNT Column added

SFTY_STK Column added

SRVC_LEVL Column added

CK_IM_INV_LST_AVG_COST Check changed from [LST_AVG_COST]>=0 to

to [LST_AVG_COST]>=0 AND [LST_AVG_COST]<=99999999

CK_IM_INV_LST_COST Check changed from [LST_COST]>=0 to to [LST_COST]>=0 AND [LST_COST]<=99999999

CK_IM_INV_STD_COST Check changed from [STD_COST]>=0 to to [STD_COST]>=0 AND [STD_COST]<=99999999

IM_INV_CELL

CELL_STAT Column added

EOQ Column added




DF_IM_INV_CELL_CELL_STAT Default added

CK_IM_INV_CELL_CELL_STAT Check added

Update Guide


IM_ITEM

ECOMM_DISC_ON_SAL Column added

ECOMM_ITEM_IS_DISCNTBL Calculation changed from to case when [IS_DISCNTBL]='N' then 'N' else case when [ECOMM_DISC_ON_SAL]='Y' then 'Y' else 'S' end end

ECOMM_ITEM_IS_DISCNTBL Domain changed from T_FLG to

ECOMM_LST_CHNG_UTC_DT Column added

ECOMM_NXT_PUB_TYP Column added

IS_DISCNTBL Column added



IM_ITEM_X9 Indexes added

DF_IM_ITEM_ECOMM_DISC_ON_SAL Default added

DF_IM_ITEM_ECOMM_ITEM_IS_DISCNTBL Default dropped

DF_IM_ITEM_IS_DISCNTBL Default added

CK_IM_ITEM_ALT_1_PRC_1 Check changed from [ALT_1_PRC_1] IS NULL OR [ALT_1_PRC_1]>=0 to

to [ALT_1_PRC_1] IS NULL OR [ALT_1_PRC_1]>=0 AND [ALT_1_PRC_1]<=99999999

CK_IM_ITEM_ALT_1_REG_PRC Check changed from [ALT_1_REG_PRC] IS NULL OR [ALT_1_REG_PRC]>=0 to

to [ALT_1_REG_PRC] IS NULL OR [ALT_1_REG_PRC]>=0 AND [ALT_1_REG_PRC]<=99999999







Database Comparison












CK_IM_ITEM_ECOMM_DISC_ON_SAL Check added

CK_IM_ITEM_ECOMM_ITEM_IS_DISCNTBL Check dropped

CK_IM_ITEM_IS_DISCNTBL Check added

CK_IM_ITEM_LST_COST Check changed from [LST_COST] IS NULL OR [LST_COST]>=0 to

to [LST_COST] IS NULL OR [LST_COST]>=0 AND [LST_COST]<=99999999

CK_IM_ITEM_PRC_1 Check changed from [PRC_1]>=0 to to [PRC_1]>=0 AND [PRC_1]<=99999999

CK_IM_ITEM_REG_PRC Check changed from [REG_PRC] IS NULL OR [REG_PRC]>=0 to

to [REG_PRC] IS NULL OR [REG_PRC]>=0 AND [REG_PRC]<=99999999

CK_IM_ITEM_STAT Check changed from [STAT]='D' OR [STAT]='A' to

to [STAT]='V' OR [STAT]='D' OR [STAT]='A'

Update Guide


IM_KIT_COMP

ADJ_PRC_LVL Column added

COMP_PROMPT Column added

PRC_ADJ_TYP Column added

SUBS_TYP Column added

DF_IM_KIT_COMP_ADJ_PRC_LVL Default added

DF_IM_KIT_COMP_PRC_ADJ_TYP Default added

DF_IM_KIT_COMP_SUBS_TYP Default added

CK_IM_KIT_COMP_ADJ_PRC_LVL Check added

CK_IM_KIT_COMP_PRC_ADJ_TYP Check added

CK_IM_KIT_COMP_SUBS_TYP Check added

IM_KIT_PAR

CK_IM_KIT_PAR_KIT_TYP Check changed from [KIT_TYP]='T' to

to [KIT_TYP]='M' OR [KIT_TYP]='T'

IM_LOC


FORC_USE_XFER_IN Column added

TR_IM_LOC_INS Trigger text changed

DF_IM_LOC_ANNL_HLD_COST_PERC Default added

DF_IM_LOC_FORC_USE_XFER_IN Default added

CK_IM_LOC_FORC_USE_XFER_IN Check added

Database Comparison


IM_PRC

CK_IM_PRC_ALT_1_PRC_1 Check changed from [ALT_1_PRC_1] IS NULL OR [ALT_1_PRC_1]>=0 to












CK_IM_PRC_ALT_1_REG_PRC Check changed from [ALT_1_REG_PRC] IS NULL OR [ALT_1_REG_PRC]>=0 to








CK_IM_PRC_ALT_2_PRC_4 Check changed from [ALT_2_PRC_4] IS to [ALT_2_PRC_4] IS NULL OR

Update Guide


NULL OR [ALT_2_PRC_4]>=0 to

[ALT_2_PRC_4]>=0 AND [ALT_2_PRC_4]<=99999999





















Database Comparison






















CK_IM_PRC_ALT_5_PRC_4 Check changed from [ALT_5_PRC_4] IS NULL OR [ALT_5_PRC_4]>=0


Update Guide


to







CK_IM_PRC_PRC_1 Check changed from [PRC_1] IS NULL OR [PRC_1]>=0 to

to [PRC_1] IS NULL OR [PRC_1]>=0 AND [PRC_1]<=99999999











CK_IM_PRC_REG_PRC Check changed from [REG_PRC] IS NULL OR [REG_PRC]>=0 to

to [REG_PRC] IS NULL OR [REG_PRC]>=0 AND [REG_PRC]<=99999999

Database Comparison


IM_PRC_RUL

REQ_FULL_GRP_FOR_BOGO_TWOFER Column added

USE_BOGO_TWOFER Column added

DF_IM_PRC_RUL_REQ_FULL_GRP_FOR_BOGO_TWOFER Default added

DF_IM_PRC_RUL_USE_BOGO_TWOFER Default added

CK_IM_PRC_RUL_REQ_FULL_GRP_FOR_BOGO_TWOFER Check added

CK_IM_PRC_RUL_USE_BOGO_TWOFER Check added

IM_PRC_WRK

ORIG_LIN_MIX_MATCH_CONTRIB Column added

ORIG_PRIOR_LIN_ITEM_TOT_QTY Column added

ORIG_PRIOR_LIN_MIX_MATCH_GRP_TOT Column added

PRIOR_LIN_ITEM_TOT_QTY Column added

PRIOR_LIN_MIX_MATCH_GRP_TOT Column added

IM_PRC_WRK_CELL

UNIT_PRC Column dropped

IM_QASSEM_HIST_COMP

IM_QASSEM_HIST_COMP_X1 Indexes added

IM_SER

CK_IM_SER_SER_COST Check added

IM_SUBCAT_COD

MIN_PFT_PCT Column added




CK_IM_SUBCAT_COD_MIN_PFT_PCT Check added

CK_IM_SUBCAT_COD_TRGT_PFT_PCT Check added

Update Guide


PO_CTL

CONSOL_LINS_METH Column added

DF_PO_CTL_CONSOL_LINS_METH Default added

CK_PO_CTL_CONSOL_LINS_METH Check added

PO_RECVR_HIST_LIN

NEW_PRC_1 Column added

OLD_PRC_1 Column added

CK_PO_RECVR_HIST_LIN_NEW_PRC_1 Check added

CK_PO_RECVR_HIST_LIN_OLD_PRC_1 Check added

PO_RECVR_HIST_LIN_MSD

FK_PO_RECVR_HIST_LIN_MSD_PO_RECVR_HIST_LIN ForeignKeys dropped

PO_RECVR_HIST_MSD

FK_PO_RECVR_HIST_MSD_PO_RECVR_HIST ForeignKeys dropped

PO_RECVR_LIN

NEW_PRC_1 Column added

CK_PO_RECVR_LIN_NEW_PRC_1 Check added

PO_RTV_HIST_MSD

FK_PO_RTV_HIST_MSD_PO_RTV_HIST ForeignKeys dropped

PO_VEND_ITEM

CK_PO_VEND_ITEM_UNIT_COST Check changed from [UNIT_COST] IS NULL OR [UNIT_COST]>=0 to

to [UNIT_COST] IS NULL OR [UNIT_COST]>=0 AND [UNIT_COST]<=99999999

CK_PO_VEND_ITEM_VEND_LIST_PRC Check changed from [VEND_LIST_PRC] IS NULL OR [VEND_LIST_PRC]>=0 to

to [VEND_LIST_PRC] IS NULL OR [VEND_LIST_PRC]>=0 AND [VEND_LIST_PRC]<=99999999

Database Comparison


PS_DOC_HDR

CK_PS_DOC_HDR_DOC_TYP Check changed from [DOC_TYP]='R' OR [DOC_TYP]='L' OR [DOC_TYP]='O' OR [DOC_TYP]='Q' OR [DOC_TYP]='V' OR [DOC_TYP]='H' OR [DOC_TYP]='T' to

to [DOC_TYP]='F' OR [DOC_TYP]='R' OR [DOC_TYP]='L' OR [DOC_TYP]='O' OR [DOC_TYP]='Q' OR [DOC_TYP]='V' OR [DOC_TYP]='H' OR [DOC_TYP]='T'

PS_DOC_HDR_EC

EC_DISC_COD Column dropped

PS_DOC_HDR_TOT

TOT_HDR_DISC Column added

TOT_HDR_DISCNTBL_AMT Column added

TOT_LIN_DISC Column added

DF_PS_DOC_HDR_TOT_TOT_HDR_DISCNTBL_AMT Default added

Update Guide


PS_DOC_LIN

CALC_EXT_PRC Column added

COST_ENTD Column added

COST_OF_SLS_PCT Column added

DISP_EXT_PRC Column added

GFT_RGSTRY_ID Column added

GROSS_DISP_EXT_PRC Column added

GROSS_EXT_PRC Column added

HAS_PRC_OVRD Column added


IS_KIT_PAR Column added

KIT_LVL Column dropped

MIX_MATCH_COD Column added

MIX_MATCH_CONTRIB Column added

MIX_MATCH_PRC_BASED_ON Column added

PAR_LIN_GUID Column added

PRC_OVRD_REAS Column added

PRESUMED_COST Column added

USR_ENTD_PRC Column added

DF_PS_DOC_LIN_HAS_PRC_OVRD Default added

DF_PS_DOC_LIN_IS_DISCNTBL Default added

DF_PS_DOC_LIN_IS_KIT_PAR Default added

DF_PS_DOC_LIN_MIX_MATCH_PRC_BASED_ON Default added

DF_PS_DOC_LIN_USR_ENTD_PRC Default added

CK_PS_DOC_LIN Check added

CK_PS_DOC_LIN_COST_ENTD Check added

CK_PS_DOC_LIN_HAS_PRC_OVRD Check added

CK_PS_DOC_LIN_IS_DISCNTBL Check added

CK_PS_DOC_LIN_IS_KIT_PAR Check added

CK_PS_DOC_LIN_KIT_LVL Check dropped

CK_PS_DOC_LIN_MIX_MATCH_PRC_BASED_ON Check added

Database Comparison


CK_PS_DOC_LIN_PRC Check changed from [PRC] IS NULL OR [PRC]>=-9999999 AND [PRC]<=9999999 to </td>

to [PRC] IS NULL OR [PRC]>=-99999999 AND [PRC]<=99999999

CK_PS_DOC_LIN_USR_ENTD_PRC Check added

PS_LWY_HIST



PS_LWY_HIST_AUDIT_LOG

DF_PS_LWY_HIST_AUDIT_LOG_DOC_TYP Default added

PS_LWY_HIST_AUDIT_LOG_TOT

DF_PS_LWY_HIST_AUDIT_LOG_TOT_TOT_TYP Default added

PS_LWY_HIST_LIN
















Update Guide



STD_COST Column added


DF_PS_LWY_HIST_LIN_HAS_PRC_OVRD Default added

DF_PS_LWY_HIST_LIN_IS_DISCNTBL Default added

DF_PS_LWY_HIST_LIN_IS_KIT_PAR Default added

DF_PS_LWY_HIST_LIN_MIX_MATCH_PRC_BASED_ON Default added

DF_PS_LWY_HIST_LIN_USR_ENTD_PRC Default added

CK_PS_LWY_HIST_LIN_COST_ENTD Check added

CK_PS_LWY_HIST_LIN_HAS_PRC_OVRD Check added

CK_PS_LWY_HIST_LIN_IS_DISCNTBL Check added

CK_PS_LWY_HIST_LIN_IS_KIT_PAR Check added

CK_PS_LWY_HIST_LIN_KIT_LVL Check dropped

CK_PS_LWY_HIST_LIN_MIX_MATCH_PRC_BASED_ON Check added

CK_PS_LWY_HIST_LIN_PRC Check changed from [PRC] IS NULL OR [PRC]>=-9999999 AND [PRC]<=9999999 to </td>


CK_PS_LWY_HIST_LIN_STD_COST Check added

CK_PS_LWY_HIST_LIN_USR_ENTD_PRC Check added

PS_ORD_HIST



PS_ORD_HIST_AUDIT_LOG

DF_PS_ORD_HIST_AUDIT_LOG_DOC_TYP Default added

PS_ORD_HIST_AUDIT_LOG_TOT

DF_PS_ORD_HIST_AUDIT_LOG_TOT_TOT_TYP Default added

Database Comparison


PS_ORD_HIST_EC


PS_ORD_HIST_LIN



















DF_PS_ORD_HIST_LIN_HAS_PRC_OVRD Default added

DF_PS_ORD_HIST_LIN_IS_DISCNTBL Default added

DF_PS_ORD_HIST_LIN_IS_KIT_PAR Default added

DF_PS_ORD_HIST_LIN_MIX_MATCH_PRC_BASED_ON Default added

DF_PS_ORD_HIST_LIN_USR_ENTD_PRC Default added

CK_PS_ORD_HIST_LIN_COST_ENTD Check added

CK_PS_ORD_HIST_LIN_HAS_PRC_OVRD Check added

CK_PS_ORD_HIST_LIN_IS_DISCNTBL Check added

CK_PS_ORD_HIST_LIN_IS_KIT_PAR Check added

Update Guide


CK_PS_ORD_HIST_LIN_KIT_LVL Check dropped

CK_PS_ORD_HIST_LIN_MIX_MATCH_PRC_BASED_ON Check added

CK_PS_ORD_HIST_LIN_PRC Check changed from [PRC] IS NULL OR [PRC]>=-9999999 AND [PRC]<=9999999 to </td>


CK_PS_ORD_HIST_LIN_STD_COST Check added

CK_PS_ORD_HIST_LIN_USR_ENTD_PRC Check added

PS_ORD_HIST_PMT_CHK

PK_PS_ORD_HIST_PMT_CHK Index columns changed from PMT_SEQ_NO, BUS_DAT, DOC_ID

to BUS_DAT, DOC_ID, PMT_SEQ_NO

PS_REAS_COD

SCRAP_REASON_COD Column added

VAL_SCRAP_INV Column added

FK_PS_REAS_COD_IM_ADJ_REAS_COD ForeignKeys added

DF_PS_REAS_COD_VAL_SCRAP_INV Default added

CK_PS_REAS_COD_VAL_SCRAP_INV Check added

PS_STA

USE_PS Column dropped

DF_PS_STA_USE_PS Default dropped

CK_PS_STA_USE_PS Check dropped

PS_STA_CFG_PS


PS_PMT_CUST_FLD_FRM_ID Column added

Database Comparison


PS_STR_CFG_PS

MAX_DISC_AMT Column added

MAX_DISC_PCT Column added



DF_PS_STR_CFG_PS_USE_ITEM_TOT_QTY_FOR_PRC Defaults changed from ('N') to to ('Y')

CK_PS_STR_CFG_PS_EDC_PROCESSOR Check changed from [EDC_PROCESSOR]='L' OR [EDC_PROCESSOR]='P' OR [EDC_PROCESSOR]='V' OR [EDC_PROCESSOR]='S' OR [EDC_PROCESSOR]='F' to

to [EDC_PROCESSOR]='M' OR [EDC_PROCESSOR]='L' OR [EDC_PROCESSOR]='P' OR [EDC_PROCESSOR]='V' OR [EDC_PROCESSOR]='S' OR [EDC_PROCESSOR]='F'

PS_TKT_HIST



PS_TKT_HIST_EC


PS_TKT_HIST_LIN









Update Guide



IS_SCRAP_RET_LIN Column added










DF_PS_TKT_HIST_LIN_HAS_PRC_OVRD Default added

DF_PS_TKT_HIST_LIN_IS_DISCNTBL Default added

DF_PS_TKT_HIST_LIN_IS_KIT_PAR Default added

DF_PS_TKT_HIST_LIN_IS_SCRAP_RET_LIN Default added

DF_PS_TKT_HIST_LIN_MIX_MATCH_PRC_BASED_ON Default added

DF_PS_TKT_HIST_LIN_USR_ENTD_PRC Default added

CK_PS_TKT_HIST_LIN_COST_ENTD Check added

CK_PS_TKT_HIST_LIN_HAS_PRC_OVRD Check added

CK_PS_TKT_HIST_LIN_IS_DISCNTBL Check added

CK_PS_TKT_HIST_LIN_IS_KIT_PAR Check added

CK_PS_TKT_HIST_LIN_IS_SCRAP_RET_LIN Check added

CK_PS_TKT_HIST_LIN_KIT_LVL Check dropped

CK_PS_TKT_HIST_LIN_MIX_MATCH_PRC_BASED_ON Check added

CK_PS_TKT_HIST_LIN_PRC Check changed from [PRC] IS NULL OR [PRC]>=-9999999 AND [PRC]<=9999999 to </td>


CK_PS_TKT_HIST_LIN_STD_COST Check added

CK_PS_TKT_HIST_LIN_USR_ENTD_PRC Check added

Database Comparison


PS_TKT_PST_LIN_WRK

EXT_COST Column added

UNIT_COST Column added

PS_VOID_HIST



PS_VOID_HIST_LIN



















DF_PS_VOID_HIST_LIN_HAS_PRC_OVRD Default added

DF_PS_VOID_HIST_LIN_IS_DISCNTBL Default added

DF_PS_VOID_HIST_LIN_IS_KIT_PAR Default added

DF_PS_VOID_HIST_LIN_MIX_MATCH_PRC_BASED_ON Default added

DF_PS_VOID_HIST_LIN_USR_ENTD_PRC Default added

Update Guide


CK_PS_VOID_HIST_LIN_COST_ENTD Check added

CK_PS_VOID_HIST_LIN_HAS_PRC_OVRD Check added

CK_PS_VOID_HIST_LIN_IS_DISCNTBL Check added

CK_PS_VOID_HIST_LIN_IS_KIT_PAR Check added

CK_PS_VOID_HIST_LIN_KIT_LVL Check dropped

CK_PS_VOID_HIST_LIN_MIX_MATCH_PRC_BASED_ON Check added

CK_PS_VOID_HIST_LIN_PRC Check changed from [PRC] IS NULL OR [PRC]>=-9999999 AND [PRC]<=9999999 to </td>


CK_PS_VOID_HIST_LIN_STD_COST Check added

CK_PS_VOID_HIST_LIN_USR_ENTD_PRC Check added

SY_ACCTG_INTFC

CK_SY_ACCTG_INTFC_ACCTG_SYS Check changed from [ACCTG_SYS]='CUSTOM' OR [ACCTG_SYS]='XPASSPORT' OR [ACCTG_SYS]='XPEACH2K5' OR [ACCTG_SYS]='XFNEDGE' OR [ACCTG_SYS]='XMIP50' OR [ACCTG_SYS]='XDYNSL60' OR [ACCTG_SYS]='XSOLIV50' OR [ACCTG_SYS]='XQB2K' OR [ACCTG_SYS]='XACCPAC5' OR [ACCTG_SY to

to [ACCTG_SYS]='CUSTOM' OR [ACCTG_SYS]='XPASSPORT' OR [ACCTG_SYS]='XPEACH2K9' OR [ACCTG_SYS]='XPEACH2K5' OR [ACCTG_SYS]='XFNEDGE' OR [ACCTG_SYS]='XMIP50' OR [ACCTG_SYS]='XDYNSL60' OR [ACCTG_SYS]='XSOLIV50' OR [ACCTG_SYS]='XQB2K' OR [ACCTG_S

SY_CALNDR

SEAS_10 Column added

SEAS_10_END_DAT Column added




Database Comparison



SEAS_7 Column added


SEAS_8 Column added


SEAS_9 Column added


CK_SY_CALNDR_SEAS_10_END_DAT Check added






SY_COMP

ALLOW_OTHR_STR_GFT_RGSTRY Column added

GFT_RGSTRY_VAL_MONS Column added

MAIL_AUTO_PURGE_DAYS Column added

MAIL_REFRSH_SECS Column added

RESTRICT_TO_REGISTERED_WORKSTATIONS Column added

USE_GFT_RGSTRY Column added

DF_SY_COMP_ALLOW_OTHR_STR_GFT_RGSTRY Default added

DF_SY_COMP_GFT_RGSTRY_VAL_MONS Default added

DF_SY_COMP_MAIL_AUTO_PURGE_DAYS Default added

DF_SY_COMP_MAIL_REFRSH_SECS Default added

DF_SY_COMP_RESTRICT_TO_REGISTERED_WORKSTATIONS Default added

DF_SY_COMP_USE_GFT_RGSTRY Default added

CK_SY_COMP_ALLOW_OTHR_STR_GFT_RGSTRY Check added

CK_SY_COMP_GFT_RGSTRY_VAL_MONS Check added

CK_SY_COMP_RESTRICT_TO_REGISTERED_WORKSTATIONS Check added

CK_SY_COMP_USE_GFT_RGSTRY Check added

Update Guide


SY_CUSTOM_FRM

FRM_ID Precision from 10 to 19

FRM_ID Data Type changed from int to bigint

FRM_ID Domain changed from T_INT to T_INT_BIG

RS_UTC_DT Column added

SY_CUSTOM_FRM_X_RS_UTC_DT Indexes added

SY_CUSTOM_FRM_X1 Index columns changed from FRM_NAM to FRM_NAM, FRM_ID

DF_SY_CUSTOM_FRM_RS_UTC_DT Default added

SY_EDC_HIST

CK_SY_EDC_HIST_CARD_TYP Check changed from [CARD_TYP]='DB' OR [CARD_TYP]='JC' OR [CARD_TYP]='DI' OR [CARD_TYP]='DC' OR [CARD_TYP]='AX' OR [CARD_TYP]='MC' OR [CARD_TYP]='VI' OR [CARD_TYP]='??' to

to [CARD_TYP]='EB' OR [CARD_TYP]='DB' OR [CARD_TYP]='JC' OR [CARD_TYP]='DI' OR [CARD_TYP]='DC' OR [CARD_TYP]='AX' OR [CARD_TYP]='MC' OR [CARD_TYP]='VI' OR [CARD_TYP]='??'

Database Comparison


SY_EDC_TRX

CK_SY_EDC_TRX_CARD_TYP Check changed from [CARD_TYP]='DB' OR [CARD_TYP]='JC' OR [CARD_TYP]='DI' OR [CARD_TYP]='DC' OR [CARD_TYP]='AX' OR [CARD_TYP]='MC' OR [CARD_TYP]='VI' OR [CARD_TYP]='??' to

to [CARD_TYP]='EB' OR [CARD_TYP]='DB' OR [CARD_TYP]='JC' OR [CARD_TYP]='DI' OR [CARD_TYP]='DC' OR [CARD_TYP]='AX' OR [CARD_TYP]='MC' OR [CARD_TYP]='VI' OR [CARD_TYP]='??'

SY_PAY_COD

PRT_DECLINE_RCPT Column added



DF_SY_PAY_COD_PRT_DECLINE_RCPT Default added

CK_SY_PAY_COD_PRT_DECLINE_RCPT Check added

SY_PS_SEC_COD

ALLOW_MAX_DISC_OVRD Column added

ALLOW_TKT_DISC Column added

DF_SY_PS_SEC_COD_ALLOW_MAX_DISC_OVRD Default added

DF_SY_PS_SEC_COD_ALLOW_TKT_DISC Default added

CK_SY_PS_SEC_COD_ALLOW_MAX_DISC_OVRD Check added

CK_SY_PS_SEC_COD_ALLOW_TKT_DISC Check added

Update Guide


SY_SEC_COD

ALLOW_MRGN_DRVN_PRCG Column added

ALLOW_WKSTN_PREFS Column dropped

DF_SY_SEC_COD_ALLOW_MRGN_DRVN_PRCG Default added

DF_SY_SEC_COD_ALLOW_WKSTN_PREFS Default dropped

CK_SY_SEC_COD_ALLOW_MRGN_DRVN_PRCG Check added

CK_SY_SEC_COD_ALLOW_WKSTN_PREFS Check dropped

SY_TIMCRD_LIN

PROCESSED Column added

SY_USR

ALLOW_SEND_POPUPMAIL Column added

IS_MAIL_MGR Column added

DF_SY_USR_ALLOW_SEND_POPUPMAIL Default added

DF_SY_USR_IS_MAIL_MGR Default added

CK_SY_USR_ALLOW_SEND_POPUPMAIL Check added

CK_SY_USR_IS_MAIL_MGR Check added

SY_USR_PREF

MAIL_NEW_MAIL_FONT Column added

MAIL_NEW_MAIL_SND Column added

MAIL_POPUP_MAIL_SND Column added

MAIL_RPLY_FRW_MAIL_FONT Column added

MAIL_VIEW_READ_PANE Column added

DF_SY_USR_PREF_MAIL_NEW_MAIL_FONT Default added

DF_SY_USR_PREF_MAIL_RPLY_FRW_MAIL_FONT Default added

DF_SY_USR_PREF_MAIL_VIEW_READ_PANE Default added

CK_SY_USR_PREF_MAIL_VIEW_READ_PANE Check added

Database Comparison


SY_WRKGRP

BTN_MENU_FONT Column added

BTN_MENU_ROUND_CRNRS Column added

BTN_MENU_SIZE Column added

BTN_MENU_STYLE Column added

BTN_MENU_TXT_POS Column added

DF_SY_WRKGRP_BTN_MENU_FONT Default added

DF_SY_WRKGRP_BTN_MENU_ROUND_CRNRS Default added

DF_SY_WRKGRP_BTN_MENU_SIZE Default added

DF_SY_WRKGRP_BTN_MENU_STYLE Default added

DF_SY_WRKGRP_BTN_MENU_TXT_POS Default added

CK_SY_WRKGRP_BTN_MENU_ROUND_CRNRS Check added

CK_SY_WRKGRP_BTN_MENU_STYLE Check added

CK_SY_WRKGRP_BTN_MENU_TXT_POS Check added

Dropped Tables PS_DOC_LIN_PRICE_COST

PS_LWY_HIST_LIN_PRICE_COST

PS_ORD_HIST_LIN_PRICE_COST

PS_TKT_HIST_LIN_PRICE_COST

PS_VOID_HIST_LIN_PRICE_COST

Update Guide


Views New Views Modified Views

New Views

VI_DM_EXCPT_STR_MGR_DAY

VI_DM_EXCPT_STR_USR_DAY

VI_DM_TRX_LOG_DAY_FUNC

VI_IM_ITEM_CELL_WITH_INV

VI_IM_ITEM_GRID_DIMS_ORDERED

VI_INV_HIST_CELL

VI_INV_HIST_CELL_DIMS

VI_INV_HIST_CELL_QTY

VI_PO_LOWEST_COST_VEND

VI_PS_CUSTOM_SCHEMA

VI_PS_DOC_HDR_DISC

VI_PS_DOC_HDR_DISC_RCPT

VI_PS_DOC_LIN_DISC

VI_PS_DOC_LIN_DISC_RCPT

VI_PS_GFT_RGSTRY_HIST_ANL

VI_PS_GFT_RGSTRY_LIN

VI_PS_ITEM_LOC_MONTHLY_HIST

VI_PS_LWY_HDR_DISC_RCPT

VI_PS_LWY_HIST_DISC

VI_PS_LWY_HIST_LIN_DISC

VI_PS_LWY_HIST_LIN_DISC_RCPT

VI_PS_ORD_HIST_DISC

VI_PS_ORD_HIST_DISC_RCPT

VI_PS_ORD_HIST_LIN_DISC

VI_PS_ORD_HIST_LIN_DISC_RCPT

VI_PS_TKT_HIST_DISC

VI_PS_TKT_HIST_DISC_RCPT

VI_PS_TKT_HIST_LIN_DISC

VI_PS_TKT_HIST_LIN_DISC_RCPT

VI_PS_TRX_LOG

VI_PS_VALIDATED_RETURNS_DISC

VI_PS_VALIDATED_RETURNS_LIN_PRICE

VI_PS_VOID_HIST_DISC

VI_PS_VOID_HIST_DISC_RCPT

VI_PS_VOID_HIST_LIN_DISC

VI_PS_VOID_HIST_LIN_DISC_RCPT

VI_RECEIPT_HEADER

VI_RECEIPT_LINE_ITEMS

VI_SY_MAIL_INBOX

VI_SY_MAIL_SENTITEMS

VI_WORK_CENTER

Database Comparison


Modified Views VI_AR_CUST_RCPT



VI_AR_CUST_WITH_ADDRESS



VI_IM_CATEG_SUBCAT

View Text changed

MIN_PFT_PCT Column added


VI_IM_INV_CELL


EOQ Column added




VI_IM_ITEM_GRID_DIMS

View Text changed

DIM_COUNT Column added

DisplayDim1SeqNo Column added



Update Guide


VI_IM_ITEM_RCPT








VI_IM_ITEM_WITH_INV








VI_IM_ITEM_WITH_INV_AND_INV_TOTS








Database Comparison


VI_IM_ITEM_WITH_INV_TOTS








VI_IM_LOC_WITH_ADDRESS


FORC_USE_XFER_IN Column added

VI_IM_SUBST_ITEMS








VI_INV_CELL


EOQ Column added




VI_INV_CELL_DIFF

View Text changed

Update Guide


VI_INV_HIST

View Text changed

UNIT_CALC_PRC Columns Numeric-Scale from 8 to 11

UNIT_CALC_PRC Precision from 23 to 38

UNIT_PRC Columns Numeric-Scale from 8 to 11

UNIT_PRC Precision from 23 to 38

UNIT_PRC_1 Columns Numeric-Scale from 8 to 11

UNIT_PRC_1 Precision from 23 to 38

UNIT_REG_PRC Columns Numeric-Scale from 8 to 11

UNIT_REG_PRC Precision from 23 to 38

UNIT_RETL Columns Numeric-Scale from 8 to 11

UNIT_RETL Precision from 23 to 38

VI_INV_HIST_QTY

View Text changed

UNIT_CALC_PRC Columns Numeric-Scale from 8 to 11

UNIT_CALC_PRC Precision from 23 to 38

UNIT_PRC Columns Numeric-Scale from 8 to 11

UNIT_PRC Precision from 23 to 38

UNIT_PRC_1 Column added

UNIT_REG_PRC Columns Numeric-Scale from 8 to 11

UNIT_REG_PRC Precision from 23 to 38

UNIT_RETL Columns Numeric-Scale from 8 to 11

UNIT_RETL Precision from 23 to 38

Database Comparison


VI_INV_PRC



EOQ Column added






VI_INV_PRC_CATEG



EOQ Column added






VI_INV_PRC_CELL

View Text changed

INV_ALT_1_PRC_1 Column added






INV_ALT_1_REG_PRC Column added



Update Guide




























Database Comparison


VI_PO_ITEM_PICKER








VI_PO_ITEM_PICKER_RESULTS








VI_PS_DOC_HDR

View Text changed


HDR_DISC_COD Column added

HDR_DISCS Column added

LWY_TOT_DISC Column added

LWY_TOT_HDR_DISC Column added

LWY_TOT_HDR_DISCNTBL_AMT Column added

LWY_TOT_LIN_DISC Column added

ORD_TOT_DISC Column added

ORD_TOT_HDR_DISC Column added

ORD_TOT_HDR_DISCNTBL_AMT Column added

ORD_TOT_LIN_DISC Column added

Update Guide


SAL_TOT_DISC Column added

SAL_TOT_HDR_DISC Column added

SAL_TOT_HDR_DISCNTBL_AMT Column added

SAL_TOT_LIN_DISC Column added

TOT_DISC Column added




VI_PS_DOC_HDR_RCPT

View Text changed

DISC_COD Column added


GROSS_SUB_TOT_INC_HDR_DISC Column added



















Database Comparison


VI_PS_DOC_LIN

View Text changed






HDR_DISC_AMT Column added



KIT_ADJ_PRC_LVL Column added

KIT_COMP_DIM_1_UPR Column added



KIT_COMP_ITEM_NO Column added

KIT_COMP_QTY Column added

KIT_COMP_QTY_UNIT_FLG Column added

KIT_COMP_UPCHARGE Column added


KIT_PRC_ADJ_TYP Column added

KIT_SUBS_TYP Column added

LIN_DISC_AMT Column added

MIX_MATCH_CONTRIB Precision from 19 to 15

MIX_MATCH_CONTRIB Data Type changed from money to decimal

MIX_MATCH_CONTRIB Domain changed from T_DEC4 to T_MIX_MATCH_GRP_VAL

PAR_ITEM_NO Column added


PRC_BRK_DESCR Column dropped

PRC_GRP_COD Column dropped

PRC_GRP_DESCR Column dropped

PRC_GRP_TYP Column dropped

Update Guide


PRC_JUST_STR Column dropped

PRC_RUL_DESCR Column dropped

PRC_RUL_SEQ_NO Column dropped


VI_PS_DOC_LIN_RCPT

View Text changed


DISC_COD Column added




GROSS_DISP_EXT_PRC_INC_HDR_DISC Column added

















LIN_LVL_DISC_AMT Column added

MIX_MATCH_CONTRIB Precision from 19 to 15

MIX_MATCH_CONTRIB Data Type changed from money to decimal

Database Comparison


MIX_MATCH_CONTRIB Domain changed from T_DEC4 to T_MIX_MATCH_GRP_VAL











VI_PS_DOC_PMT

View Text changed

AVS_RESULT Column added

CVV_RESULT Column added

ENTRY_METH Column added

ERROR_MSG Column added

PROCESSOR_MSG Column added

PROCESSOR_REF_NO Column added

PROCESSOR_TRANS_ID Column added

RCPT_ACCT_TYP Column added

RCPT_AMT Column added

RCPT_AUTH_COD Column added

RCPT_CARD_NO_MSK Column added

RCPT_CARD_TYP Column added

RCPT_LANG Column added

RCPT_MSG Column added

RCPT_STR_ID Column added

RCPT_TERM_ID Column added

RCPT_TRANS_DAT Column added

RCPT_TRANS_TIM Column added

Update Guide


TRANS_APPROVED Column added

TRANS_STAT Column added

TRANS_TYP Column added

UNIQUE_TRANS_ID Column added

VI_PS_DOC_PMT_RCPT

AVS_RESULT Column added

CVV_RESULT Column added

ENTRY_METH Column added

ERROR_MSG Column added

PROCESSOR_MSG Column added

PROCESSOR_REF_NO Column added

PROCESSOR_TRANS_ID Column added

RCPT_ACCT_TYP Column added

RCPT_AMT Column added

RCPT_AUTH_COD Column added

RCPT_CARD_NO_MSK Column added

RCPT_CARD_TYP Column added

RCPT_LANG Column added

RCPT_MSG Column added

RCPT_STR_ID Column added

RCPT_TERM_ID Column added

RCPT_TRANS_DAT Column added

RCPT_TRANS_TIM Column added

TRANS_APPROVED Column added

TRANS_STAT Column added

TRANS_TYP Column added

UNIQUE_TRANS_ID Column added

Database Comparison


VI_PS_FILL_BO




















VI_PS_LWY_HIST

View Text changed









Update Guide


VI_PS_LWY_HIST_LIN

View Text changed































Database Comparison


VI_PS_ORD_HIST

View Text changed










VI_PS_ORD_HIST_LIN

View Text changed


















Update Guide















VI_PS_STA

View Text changed



USE_PS Column dropped

VI_PS_STR

View Text changed





VI_PS_STR_RCPT





Database Comparison


VI_PS_TKT_HIST

View Text changed










VI_PS_TKT_HIST_LIN

View Text changed


















Update Guide
















VI_PS_VALIDATED_RETURNS_HDR

View Text changed

CUST_PO_NO Column added

TAX_COD Column added

VI_PS_VALIDATED_RETURNS_LIN

View Text changed



LIN_LOY_PTS_EARND Column added


PRC Data Type changed from money to decimal

PRC Domain changed from T_UNIT_MONEY to

Database Comparison


VI_PS_VOID_HIST

View Text changed









VI_PS_VOID_HIST_LIN

View Text changed



















Update Guide














VI_PS_VOID_HIST_PMT

View Text changed

CR_CARD_NO_KID Column added

VI_STR_PAY_COD

PRT_DECLINE_RCPT Column added



VI_SY_STC_HIST_WITH_CUST



VI_SY_STC_WITH_CUST



VI_SY_TIMCRD_DETL

PROCESSED Column added

Database Comparison


VI_SY_USR_WITH_ADDRESS



VI_TIMCRD_USRS



VI_TKT_HIST_CUST
























Update Guide










Database Comparison


Stored Procedures New Stored Procedures Modified Stored Procedures Dropped Stored Procedures

Update Guide


New Stored Procedures USP_AGG_DM_STATS_STR_USR_DAY

USP_AGG_DM_STATS_STR_USR_DAY_DRW

USP_AGG_DM_STATS_STR_USR_DAY_LIN

USP_AGG_DM_STATS_STR_USR_DAY_TIMCRD

USP_AGG_DM_TRX_LOG

USP_AGG_DM_TRX_LOG_CHAR

USP_COPY_PS_DOC_DISC_TO_HIST

USP_COPY_PS_DOC_DISC_TO_LWY_HIST

USP_COPY_PS_DOC_DISC_TO_ORD_HIST

USP_COPY_PS_DOC_DISC_TO_VOID_HIST

USP_COPY_PS_DOC_LIN_KIT_TO_HIST

USP_COPY_PS_DOC_LIN_KIT_TO_LWY_HIST

USP_COPY_PS_DOC_LIN_KIT_TO_ORD_HIST

USP_COPY_PS_DOC_LIN_KIT_TO_VOID_HIST

USP_COPY_PS_DOC_LIN_PRICE_TO_HIST

USP_COPY_PS_DOC_LIN_PRICE_TO_LWY_HIST

USP_COPY_PS_DOC_LIN_PRICE_TO_ORD_HIST

USP_COPY_PS_DOC_LIN_PRICE_TO_VOID_HIST

USP_COPY_PS_DOC_PMT_RCPT_TO_HIST

USP_COPY_PS_DOC_PMT_RCPT_TO_LWY_HIST

USP_COPY_PS_DOC_PMT_RCPT_TO_ORD_HIST

USP_COPY_PS_DOC_PMT_RCPT_TO_VOID_HIST

USP_FORCST_AGG_DM_ADJ_LOC_ITEM_SEAS

USP_FORCST_AGG_DM_QA_LOC_ITEM_SEAS

USP_FORCST_AGG_DM_QXI_LOC_ITEM_SEAS

USP_FORCST_AGG_DM_QXO_LOC_ITEM_SEAS

USP_FORCST_AGG_DM_SAL_LOC_ITEM_SEAS

USP_FORCST_AGG_DM_XFI_LOC_ITEM_SEAS

USP_FORCST_AGG_DM_XFO_LOC_ITEM_SEAS

USP_FORCST_HIST_DATA

USP_GET_NEXT_GEN_ID

USP_IM_CREATE_DYNMINMAX

USP_IM_FORCST_CREATE_SEAS_HOLTS

USP_IM_SET_FORCST_WRK

USP_MS_POPULATE_SY_DB

USP_PRICE_CALC_PRICE_FOR_ONE_RULE

USP_PRICE_FIND_AN_APPLICABLE_RULE_GRP

USP_PRICE_FIND_AN_APPLICABLE_RULE_GRP_CLOSE_SEARCH

USP_PRICE_FIND_AN_APPLICABLE_RULE_IN_A_GRP

USP_PRICE_FIND_AN_APPLICABLE_RULE_IN_A_GRP_CLOSE_SEARCH

USP_PRICE_GET_PRICE

USP_PRICE_GET_UNIT_PRICE_FOR_ONE_BRK_LEVEL

USP_PRICE_SEARCH

USP_PS_TE_COMMIT_GFTRGSTRY_QTY_FILLED

USP_PS_TE_UNCOMMIT_GFTRGSTRY_QTY_FILLED

USP_REGEN_SY_KEY_CTR

USP_RPT_AR_STMNT_ITEM

USP_RPT_IM_INV_GRID_OVERVIEW

USP_RPT_IM_SELLTHRU

USP_RPT_IM_SELLTHRU_CELL_DIMS

USP_RPT_INV_ANL_ITEM_CELL

USP_SY_MAIL_PURGE

Database Comparison


Modified Stored Procedures USP_AGG_MASTER

StoredProcedure Text changed

USP_AR_COMMON_RENUMANDMERGE_CUST


USP_BUILD_DM_CALNDR


USP_CAN_DEL_AR_CUST


USP_CAN_DEL_GRID_DIM


USP_CAN_DEL_IM_ITEM


USP_CAN_DEL_MDL_STK


USP_COPY_PS_DOC_HDR_EC_TO_HIST


USP_COPY_PS_DOC_HDR_EC_TO_ORD_HIST


USP_COPY_PS_DOC_HDR_TO_HIST


Update Guide


USP_COPY_PS_DOC_HDR_TO_LWY_HIST


USP_COPY_PS_DOC_HDR_TO_ORD_HIST


USP_COPY_PS_DOC_HDR_TO_VOID_HIST


USP_COPY_PS_DOC_LIN_TO_HIST


USP_COPY_PS_DOC_LIN_TO_LWY_HIST


USP_COPY_PS_DOC_LIN_TO_ORD_HIST


USP_COPY_PS_DOC_LIN_TO_VOID_HIST


USP_COPY_PS_DOC_PMT_CR_CARD_TO_HIST


USP_COPY_PS_DOC_PMT_CR_CARD_TO_LWY_HIST


USP_COPY_PS_DOC_PMT_CR_CARD_TO_ORD_HIST


USP_COPY_PS_DOC_PMT_CR_CARD_TO_VOID_HIST


Database Comparison


USP_COPY_PS_DOC_TO_HIST


USP_COPY_PS_DOC_TO_LWY_HIST


USP_COPY_PS_DOC_TO_ORD_HIST


USP_COPY_PS_DOC_TO_VOID_HIST


USP_CREATE_DRW_SESSION


USP_CREATE_PRC_RUL


USP_DEL_TKT


USP_GET_DRW_SESSION_ID


USP_GET_POINTS


@PriceType Parameters dropped

@PtsEarnCustomSP Parameters added

@PtsEarned Parameters dropped

@PtsEarnOnPrcOvrd Parameters added

@PtsEarnOnSaleItems Parameters added

@PtsEarnPtsPerAmt Parameters added

Update Guide


@PtsEarnPtsPerStkUnit Parameters added

@PtsEarnRuleDescr Parameters Ordinal-Position from 9 to 6

@PtsEarnRulesChecked Parameters Ordinal-Position from 10 to 7

@PtsEarnRuleSeqNo Parameters Ordinal-Position from 8 to 5

@PtsEligible Parameters dropped

@PtsProgram Parameters Ordinal-Position from 5 to 3

@PtsProgramDescr Parameters Ordinal-Position from 6 to 4

@PtsRedeemEligible Parameters added

@PtsRedeemRuleDescr Parameters Ordinal-Position from 13 to 15

@PtsRedeemRulesChecked Parameters Ordinal-Position from 14 to 16

@PtsRedeemRuleSeqNo Parameters Ordinal-Position from 12 to 14

@UnitPrice Parameters dropped

USP_GET_PRC_BASIS_VALUES


USP_GET_PRICE_AND_POINTS


@Debug Parameters added

@DoMultiCellPrices Parameters added

@EffectivePrice Parameters dropped

@EnteredPriceType Parameters dropped

@ExtPrice Parameters added

@ExtPriceOnSale Parameters added

@GroupsChecked Parameters Ordinal-Position from 12 to 9

@PrcCalcDetail Parameters added

@Price1 Parameters Ordinal-Position from 16 to 13

@PriceType Parameters dropped

@PricingBreakDescr Parameters dropped

@PricingGroupDescr Parameters dropped

@PricingRuleDescr Parameters dropped

@PricingRuleGroupId Parameters dropped

Database Comparison


@PricingRuleSeqNo Parameters dropped

@PtsEarnCustomSP Parameters added

@PtsEarned Parameters dropped

@PtsEarnOnPrcOvrd Parameters added

@PtsEarnOnSaleItems Parameters added

@PtsEarnPtsPerAmt Parameters added

@PtsEarnPtsPerStkUnit Parameters added

@PtsEarnRuleDescr Parameters Ordinal-Position from 22 to 18

@PtsEarnRulesChecked Parameters Ordinal-Position from 23 to 19

@PtsEarnRuleSeqNo Parameters Ordinal-Position from 21 to 17

@PtsEligible Parameters dropped

@PtsProgram Parameters Ordinal-Position from 18 to 15

@PtsProgramDescr Parameters Ordinal-Position from 19 to 16

@PtsRedeemEligible Parameters added

@PtsRedeemRuleDescr Parameters Ordinal-Position from 26 to 27

@PtsRedeemRulesChecked Parameters Ordinal-Position from 27 to 28

@PtsRedeemRuleSeqNo Parameters Ordinal-Position from 25 to 26

@QtyOnSale Parameters added

@RegularPrice Parameters Ordinal-Position from 14 to 11

@RulesChecked Parameters Ordinal-Position from 13 to 10

@ThisLineMixMatchContrib Parameters Ordinal-Position from 17 to 14

@UnitPrice Parameters Ordinal-Position from 5 to 4

@UnitRetailValue Parameters Ordinal-Position from 15 to 12

USP_PO_RECVR_INV_UPD


USP_PS_TE_COMMIT_DOC


Update Guide


USP_PS_TE_COMMIT_GFCS


USP_PS_TE_COMMIT_STCS


USP_PS_TE_UNCOMMIT_DOC


USP_PS_TE_UNCOMMIT_GFCS


USP_PS_TE_UNCOMMIT_STCS


USP_RENUMBER_ITEM


USP_RENUMBER_VEND


USP_RPT_AR_LOY_PT_HIST


USP_RPT_AR_STMNT_BY_GRP


@CustOrderBy Parameters Ordinal-Position from 5 to 6

@GroupOrderBy Parameters Ordinal-Position from 6 to 7

@OmitZeroDocs Parameters added

@RunMode Parameters Ordinal-Position from 7 to 8

Database Comparison


USP_RPT_DRW_CURNCY_COD


USP_RPT_DRW_SUMMARY


USP_RPT_DRW_SUMMARY_TND


USP_RPT_HOT_COLD_SET_RANK


USP_RPT_IM_PHYSICAL_COUNT


USP_RPT_INV_ANL_ITEM


USP_RPT_PO_ADV_ADJ_QTY


USP_RPT_PO_ADV_ADJ_QTY_VEND


@IsInVendUnit Parameters added

USP_RPT_PO_ADV_QRY


@DaysOfSupplyMultiplier Parameters added

@DebugPrint Parameters Ordinal-Position from 14 to 16

@ItemPickerCalculation Parameters added

@SQL1 Parameters Ordinal-Position from 12 to 14

@SQL2 Parameters Ordinal-Position from 13 to 15

Update Guide


USP_RPT_PO_ADV_QTY


@DebugPrint Parameters Ordinal-Position from 16 to 20

@ItemPickerCalculation Parameters added

@Units Parameters added

@Vendor Parameters added

@VendorMeth Parameters added

USP_RPT_PO_RTV


USP_RPT_PS_CUST_SPEC_PURCH


USP_RS_PROCESS_TKT


USP_SET_IM_PRC_RPT_WRK_ITEMS


Dropped Stored Procedures USP_COPY_PS_DOC_LIN_PRICE_COST_TO_HIST

USP_COPY_PS_DOC_LIN_PRICE_COST_TO_LWY_HIST

USP_COPY_PS_DOC_LIN_PRICE_COST_TO_ORD_HIST

USP_COPY_PS_DOC_LIN_PRICE_COST_TO_VOID_HIST

USP_GET_PRICE

USP_SEARCH_PRC_RULES

Database Comparison


Functions fnCalcLeadTimeByLoc

Function added

fnCalcLeadTimeByVend

Function added

fnEscapeTextForXML

Function added

fnGetCellDescr

Function added

fnGetLastReplicationTime

Function added

fnGetQtyUnit

Function added

fnMsCompleteSite

Function added

fnSubstituteProfitCenter

Function Text changed


V8.3.8 Point of Sale data model changes In V8.3.8, the tables in the CounterPoint SQL database that store ticket and ticket history data were completely redesigned to optimize performance, to reduce the size of each ticket record stored in history, and to minimize replication issues in Multi-Site environments. These schema changes also improved the scalability of CounterPoint SQL, allowing for more consistent performance during ticket-related activities (e.g., posting tickets, viewing tickets in history, and so forth) as the number of concurrent users increases.

The following topics provide a brief overview of the major changes to the Point of Sale data model that occurred in V8.3.8:

Table changes Additional views Primary key changes Data type changes Maintenance columns dropped Reserved tables for custom columns Other changes

Refer to the Database Comparison topics for detailed information about the differences between the default V8.3.8 and V8.3.9 database schema.

Table changes Previously, CounterPoint stored all data that could appear in an unposted Point of Sale document in 11 different tables, each of which corresponded to a particular category of data. In V8.3.8, many of those tables were divided into a parent table and one or more related, dependent tables.

The parent table for each data category (e.g., header, lines, payments, and so forth) contain only critical, "core" data that is used by most documents, regardless of type. Less important columns and columns that apply only to certain types of documents (e.g., orders, layaways, pay-on-account transactions, and so forth) now reside in the corresponding dependent tables.

For example, because profile fields do not apply to every Point of Sale document, they are not stored in the Point of Sale document header table (PS_DOC_HDR). Instead, they are stored in the PS_DOC_HDR_PROF table. Similarly, since loyalty points are only tracked for customers who are enrolled in a loyalty program, loyalty point data for each line item is stored in the PS_DOC_LIN_LOY table, instead of in PS_DOC_LIN.

Because the parent and dependent tables store data for all Point of Sale documents (i.e., not just tickets), the PS_TKT prefix has been replaced by PS_DOC in each table name.

Update Guide


The following table lists the parent table and dependent tables that make up each category of data in the Point of Sale data model, along with the names of the V8.3.7 tables that each table or group of tables replaces.

Refer to the Point of Sale table structure topics for detailed diagrams that illustrate the Point of Sale data model.

Data Category V8.3.7 Database Table V8.3.8 Database Table(s)

Header PS_TKT_HDR PS_DOC_HDR PS_DOC_CONTACT PS_DOC_HDR_PROF PS_DOC_HDR_TOT PS_DOC_HDR_MISC_CHRG PS_DOC_HDR_PAY_IOA PS_DOC_HDR_HOLD_QUOT PS_DOC_HDR_ORIG_DOC PS_DOC_HDR_DOC_STAT PS_DOC_HDR_EC PS_DOC_HDR_LOY_PGM PS_DOC_HDR_EXT

Lines PS_TKT_LIN PS_DOC_LIN PS_DOC_LIN_PRICE_COST PS_DOC_LIN_PROMPT PS_DOC_LIN_PO PS_DOC_LIN_LOY PS_DOC_LIN_EXT

Cells PS_TKT_CELL PS_DOC_LIN_CELL PS_DOC_LIN_CELL_EXT

Serial numbers PS_TKT_SER PS_DOC_LIN_SER PS_DOC_LIN_SER_PROMPT PS_DOC_LIN_SER_EXT

Payments PS_TKT_PMT PS_DOC_PMT PS_DOC_PMT_CHK PS_DOC_PMT_CR_CARD PS_DOC_PMT_APPLY PS_DOC_PMT_PROMPT PS_DOC_PMT_EXT

Notes PS_TKT_NOTE PS_DOC_NOTE

Audit log PS_TKT_AUDIT_LOG PS_DOC_AUDIT_LOG PS_DOC_AUDIT_LOG_TOT

Gift certificates PS_TKT_GFC PS_DOC_GFC

Stored value cards PS_TKT_SVC PS_DOC_SVC

Package tracking #s PS_TKT_PKG_TRK_NO PS_DOC_PKG_TRK_NO

Tax PS_TKT_TAX PS_DOC_TAX

V8.3.8 Point of Sale data model changes


Additional views To ease the transition to the revised Point of Sale data model and to simplify the process of updating customizations, V8.3.8 included a number of additional views that closely match the Point of Sale tables in V8.3.7 and earlier versions.

For each Point of Sale table in V8.3.7, a nearly identical view appeared in V8.3.8. Each view name begins with the VI_ prefix, followed by the name of the V8.3.8 parent table that replaces the equivalent V8.3.7 table. For example, the VI_PS_DOC_HDR view corresponds to the PS_TKT_HDR table in V8.3.7.

Each view contains all of the useful columns that were present in the corresponding V8.3.7 table, each of which has the same name, data type, and usage as it did in V8.3.7. This means that the views recombine the parent and dependent tables for those data categories that were split in V8.3.8 (e.g., VI_PS_DOC_HDR combines all of the tables that make up Point of Sale document header information).

Certain obscure columns were dropped from the new views, so they are not exactly the same as the corresponding V8.3.7 tables.

In addition, these views return all columns that are physically stored in the V8.3.8 tables, using the original, physical column names, wherever possible. For example, because V8.3.8 physically stores the BUS_DAT column, the VI_PS_TKT_HIST view will return that column as BUS_DAT.

Essentially, these views can be used as "drop-in" replacements for the corresponding V8.3.7 tables in custom reports, stored procedures, triggers, and other database objects that read data.

Because views cannot generally be updated, they cannot be used in customizations that write data to the database.

Refer to the CompareDBResultsFrom837.html file in the root directory of the CounterPoint SQL DVD for a list of the views that were added to the CounterPoint SQL database.

Primary key changes The primary key of the Point of Sale document header table (i.e., PS_DOC_HDR) is now DOC_ID, instead of [STR_ID, STA_ID, TKT_NO]. The DOC_ID value is automatically generated and assigned to each Point of Sale document by CounterPoint.

A TKT_NO (i.e., Ticket number) value must still be entered or auto-assigned for each Point of Sale document and the STR_ID, STA_ID, and TKT_NO columns still appear in the main table for each Point of Sale data category. However, these columns do not appear in some dependent tables, so queries that require these values may need to join to the corresponding parent table to obtain them.

For better performance, we strongly recommend that you use DOC_ID instead of STR_ID, STA_ID, and TKT_NO for joins in stored procedure and queries.

For Point of Sale history tables (e.g., PS_TKT_HIST), the primary key is now [BUS_DAT, DOC_ID]. The BUS_DAT value is the date on which each sale is considered to have occurred (i.e., the date on which distributions are made), making it essentially identical to the POST_DAT value in previous versions.

Update Guide


Data type changes To reduce storage requirements, the following data types were defined within the Point of Sale data model for V8.3.8:

• T_DOC_ID (defined as bigint) is used as the base primary key for all Point of Sale document tables and is used as part of the base primary key for all Point of Sale history tables.

• T_UNIT_MONEY (defined as money) is used for per-unit cost, price, and retail value in Point of Sale line tables.

• T_DEC4 (defined as money) is used in cases for which 4 decimal places of precision is required, including weight, cube, numeric user prompts, currency exchange rates, and so forth.

• T_BIT (defined as bit) is used for TRUE/FALSE values in drawer session tables and is intended as the eventual replacement for T_BOOL.

• T_SMALLINT (defined as smallint) is used for Store and Station number fields.

• T_GUID (defined as uniqueidentifier) replaces T_STR_GUID in all Point of Sale document tables.

Maintenance columns dropped The following maintenance columns were dropped from all Point of Sale tables in V8.3.8:

• LST_MAINT_DT

• LST_MAINT_USR_ID

• LST_LCK_DT

• ROW_TS

To determine which user last modified a Point of Sale document or when it was modified, use the audit log records instead.

If your queries demand a value that is unique across all Point of Sale documents, you may be able to use DOC_GUID or DOC_ID, instead of ROW_TS.

Reserved tables for custom columns Previously, you could add custom columns to standard Point of Sale tables (e.g., PS_TKT_HDR or PS_TKT_LIN) in order to store custom field values for each Point of Sale document.

In this version, the revised Point of Sale data model includes tables that are specifically reserved for custom columns, which are identified by the _EXT suffix. CounterPoint now only supports custom fields in Point of Sale tables for which there is a corresponding EXT table (i.e., the header, line, payment, cell, and serial number tables).

In addition, EXT tables have also been added for the corresponding history tables. If you want to retain the data in any custom columns you add to the EXT tables for unposted Point of Sale documents when those documents are posted, add the same columns to the corresponding EXT tables in history.

Custom columns are not supported in Point of Sale tables for which there is not a corresponding EXT table (i.e., tax, package tracking, note, stored value card, gift certificate, and audit log tables). Further, if you create a table with the _EXT suffix, it will be ignored.


V8.3.8 Point of Sale table structure If you are updating from V8.3.7, use the following links to review detailed diagrams that illustrate the new CounterPoint SQL Point of Sale table structure.

Header tables Line tables Payment tables Ticket History tables

These diagrams reflect the Point of Sale table structure in V8.3.8. Refer to the Database Comparison topics for information about additional table changes that were made between V8.3.8 and V8.3.9.

Header tables This diagram illustrates the relationship between the main Point of Sale document header table (PS_DOC_HDR) and each of its dependent tables.

Refer to the PS_DOC_HDR_Diagram.jpg file in the root directory of the CounterPoint SQL DVD for an expanded diagram, including columns, of the PS_DOC_HDR table and its dependent tables.

Click each table in the diagram for a brief description of the table and a list of the columns it includes.

For detailed information about each column in these tables, refer to the PS_ColumnDescriptionReport.txt file in the root directory of the CounterPoint SQL DVD.

Update Guide


Line tables This diagram illustrates the relationship between the main Point of Sale document line table (PS_DOC_LIN) and each of its dependent tables.

Refer to the PS_DOC_LIN_Diagram.jpg file in the root directory of the CounterPoint SQL DVD for an expanded diagram, including columns, of the PS_DOC_LIN table and its dependent tables.



Payment tables This diagram illustrates the relationship between the main Point of Sale document payment table (PS_DOC_PMT) and each of its dependent tables.

Refer to the PS_DOC_PMT_Diagram.jpg file in the root directory of the CounterPoint SQL DVD for an expanded diagram, including columns, of the PS_DOC_PMT table and its dependent tables.



Index


Ticket History tables This diagram illustrates the relationship between the main ticket history table (PS_TKT_HIST) and each of its dependent tables.

Refer to the PS_TKT_HIST_Diagram.jpg file in the root directory of the CounterPoint SQL DVD for an expanded diagram, including columns, of the PS_TKT_HIST table and its dependent tables.



CounterPoint SQL V8.3.9 Update Guide · following the instructions outlined in the CounterPoint SQL...

Documents

Transcript of CounterPoint SQL V8.3.9 Update Guide · following the instructions outlined in the CounterPoint SQL...