Integration Guide

Table Of Contents

Customizing the PSS System Software

______________________________________________________________________________

WaveWorks PSS, Integration Guide, 1.10 Page 110

9.5.6 UE_PostProcessTaxFile

This function is called after PSS has processed the entire Tax Table File, all updates to thePSS

database have been completed, and the file has been closed. It receives the file path of the tax

table file as an argument. The file path for the processed file will be different than the name the

file had for UE_PreProcessTaxFile and depends on the success of PSS processing.

The base PSS software handles the following return codes from the User Exit as follows:

UE_CONTINUE: PSS processes the file as if no Pre-Processing was performed

UE_DONE: PSS performs no file processing

UE_ERROR: PSS logs an error then proceeds as with UE_DONE

9.5.7 UE_PreProcessPOSTransFile

This function is called before any processing of a POS Transaction File is performed.

The POS Transaction file defines a completed transaction at the POS terminal. Arrival of the file

indicates completion of the shopping trip. Base logic clears the trip from the list of current

shopping trips and moves the trip into shopping trip history. The information in the file is used

to calculate a shopper's rescan level

The base PSS software handles the following return codes from the User Exit as follows:

UE_CONTINUE: PSS processes the file as if no preprocessing was performed

UE_DONE: PSS performs NO file processing

UE_ERROR: PSS logs an error then proceeds as with UE_DONE

9.5.8 UE_PreProcessPOSTransRecord

This function is called before processing the current header or detail record read from a POS

Transaction File.

The base PSS software handles the following return codes from the User Exit as follows:

UE_CONTINUE: PSS processes the RECORD as if no Pre-Processing was performed

UE_DONE: PSS performs NO RECORD processing and proceeds to the next record

UE_ERROR: PSS logs the error an proceeds as with UE_CONTINUE.