Home > System Administration > Overnight Processing > Concepts > Available Tasks

Available Tasks

There are many tasks which can be run from by the Schedule Processor/Process Jobs function. Many of these are reports and you can find explanations of these in the appropriate help section. See Report List.

The following tasks are available for scheduling. Host Updates can also be scheduled.


Marks rebate claims as processed so they are not reclaimed.




Creates account adjustments for selected accounts.


Auto declare Z Reads.


Refreshes the stock levels for all open store stocktakes. Set the Job Type of ‘Default’, enter a Sequence Number, and select a Procedure of ‘Auto Refresh Stock Levels’ from the drop down list box. The Default Parameter field needs to have a value, to ensure that the process runs without the requirement of any user interaction. Type ‘A’ into the field, and Save the details.




Utility to check BE Configuration Settings that should be set to ensure PCI Compliance.




To calculate periodic average cost automatically.

When Process Job is started for COGS Periodic Average Calculation, the average is calculated for all items of all locations having the same tax system and the same currency code as of ‘ALL’ location.

Formula :

Total Cost of SOH of all locations at the beginning of the period)+ (Cost of all Good Receiving of all locations for the current period)-(Cost of all Good Return of all locations for the current period)}÷ {(Total SOH QTY of all locations at the beginning of the Period)+( Total QTY of all Good of all locations Receiving for the current period)-(Total QTY of all Good Return of all locations for the current period)




This job will convert statistics for a location from one currency to another. See Local Currency Statistics for further details.


Converts the stats using the Account Exchange Rate.


Customer Display Formats.


Deletes audit details (from AUDIT table) which are older than the specified number of days.


Deletes the audits of data changes (from AUDITCHG table) which have a SERVER date / time more than X days older than the current time (when the report is run). X is the parameter passed to the delete function.


Deletes expired booking transactions.


Deletes old accepted banking records.


Deletes processed B2B transactions (from B2BSENDFILE) which are older than the specified number of days.


Deletes old DAILYSALES records.


Allows deletion of expired fast key panels.


Deletes old goods receipt records.


Deletes the processed incoming transactions (from INCOMINGTRANS) which are older than the specified number of days. Note, this is the raw transaction files. This is not the processed daily sales and statistics.


Deletes old messages.


Deletes old operator statistics.


Deletes POS process status records (from PROCESSSTATUS table) which are older than the specified number of days.


Deletes old purchase order records.


Deletes requests for reports (from REPORTREQUESTS table) which are older than the specified number of days.


Deletes reports (from REPORTS table) which are older than the specified number of days.


Delete server performance statistics (from SERVERSTATS table) which are older than the specified number of days.


Deletes old session log records.


Marks supplier items with a certain deletion date as deleted.


Deletes the temporary statistics records (from STATSBUCKET table) which are older than the specified number of days. These are the records which are used to build trading statistics data.


Deletes old STATDEPT records.


Deletes old STATITEM records.


Deletes old processed STOCKAUDIT records.


Deletes old processed STOCKAUDITSUMMARY records.


Deletes old processed stock take records.


Deletes any ticket batches (from TKTDET and TKTHDR tables) which are older than the specified number of days.


Deletes the old processed till outgoing requests (from TILLOUTREQUEST and TILLOUTREQUESTDETAIL tables) which are older than the specified number of days.


Deletes old till reads.


Deletes old TILLSTATUS records.


Deletes old, banked trading periods.


Deletes old transfer records.






Marks expired costs/sells as no longer available.




This function supports the exporting of sales and invoice data to the Navision General Ledger system. specify the location, start and end date values to be used for the export. The location parameter can be a single store or a lo-cation group. Totals are included for all stores within the location group, grouped by store.

Each time the export function is run the following files are produced for each location for which the export is run:

  • A sales file containing the sales and voucher (gift certificate) information for example 132201SAL2010013101.csv

  • A coupon file for example COP2010013101.csv

  • Inventory file for example INV2010013101.csv.

  • A POI file – containing information from each purchase order raised for vendors with the appropriate cross references / G/L account codes defined, for example POI2010013101.csv

  • Up to 2 transfer files – 1 each for transfers received and sent for example 132201TRF2010013101.csv or 132201TRR2010013101.csv

  • Log files for each record in the sales file.

In System Settings, the Navision Export tab specifies the options for the export of sales and invoice data to the Navision accounts interface.

Note: The user-defined fields must be defined before the Navision options can be set – since some of the options are to specify which user-defined fields are to be used.

The user-defined fields (DataEntryBasic UserDefFields) that must be set up are:

• ITEM – a field for Dimension D. This must be a STRING value.

• LOCATION – fields for Dimension A and Dimension B values.

• SUPPLIER – the Navision ID for the supplier. This value must be a STRING or NUMERIC value.

Additionally, Location Accounts must be defined for the following:

• Item categories – Sales account (SAO records); Return account (SAR); Transfer account (TFR / TRR / POI); COGS account (TFR / TRR / POI); In-transit account (CUO).

• Taxes – G/L account CR and G/L account DR

• Discounts

• Tender (all tender types accepted in the store)

• General / Intra-location account (used for transfers).

In Discounts, an option on the Basic tab specifies which discounts are to be treated as coupons. If checked the discount is treated as a coupon.


Updates the required File Versions table.






Generates ticket batches for items that have a sell price change during the specified date range. For details about the 'Sell To Be Converted For 2nd Currency' see Multiple Currencies.


Generates ticket batches for items that have had a change that requires a new ticket. These changes are identified after the Set Store Costs/Sells process has been run. For details about the 'Sell To Be Converted For 2nd Currency' see Multiple Currencies.


This task will generate actual transactions from inventory templates. For example, it can generate stocktakes every Monday for beverage items. The store simply updates the stocktake transaction without needing to create the transaction.


Looks for any costs or sells that are effective during the specified date range and marks those records as available.














Export language.








This will generate data for POS which can be used for Prepared POS Reloads.




This task looks for normal costs which start during the specified date range and proposes new sell prices for them. The sell prices are generated with the same effective date as the costs on which they are based. Usually there is a delay between proposing sell prices and actually making them available with the Get New Costs/Sells tasks. However, in some circumstances sell prices are proposed and made effective in the same session. If the Proposed Sell Report was run at the end of the session along with the other reports, it would produce incorrect results. For this reason, it is strongly recommended that the Proposed Sell Report be scheduled immediately after this task. See Proposing Sell Prices.




Transaction Extracts.




Monitors that the services are running correctly.




Looks for any items that have had a cost or sell change (effective or expired) during the specified date ranges and updates the store range details to reflect those changes.






Suggest Purchase Orders.


Calculates the required min/max stock levels for the specified items based on rates of sale and required stock levels. Requires From/To Sales Periods parameters to be completed for the scheduled job to calculate the rate of sales.








This is an EOD function which can be used to move clock in/out information  to the statistics area. When it is run it will examine all clock in information which has not yet been processed. For each record it will look up the job type. This tells the system the type of job, for example fulltime, parttime, casual, and so on. It also gives an hourly rate and an On Cost%. If no job type is specified, the system will assume fulltime hours. It will update the hours but won't be update the value.

Using these numbers, the system is able to update the hours and values of labour for use in Trading Statistics and various reports.

Note: This process does not take into account overtime and the sorts of adjustments that only a payroll system can provide. It should be used as an estimate only.






This process will identify items that have changed since the last time the process was run and make a request to the system to send the items to the POS. You can use this process instead of doing a full till reload.


Tells the system that configuration files have been updated


This task will take the details of transactions made by loyalty members and non-members and build a set of statistics which can be used by various reports. The task is run for a weekly statistics periods. for example MERCHANTEOD UPDATEMEMBERSTATS 2005.07. All transactions within that period will be examined. The process should be run at the end of a statistical period. You can run the process during the statistic period but each time you run it, the process will delete any existing statistics for that period and recreate them.

There are two settings that can control how this process runs.

Firstly, the system uses the Non-Member Customer Types on the Loyalty tab of System Settings to determine who is a member or a non-member. This is a comma-delimited list of customer types, for example NEW,TEMP. (Don't use any spaces!) Any transaction made without customer details counts as a non-member transaction. Any transaction made to a customer whose customer type is in the Non-Member Customer Types list, is also counted as a non-member. Any transaction made to a customer whose customer type is NOT in this list is treated as a member.

The statistics track the number of visits. If you are in retail and you make two separate sales, these are generally counted as two separate visits. However, in a pub a customer is most likely going to make several sales during their visit. In this case, we really only want to count this as one visit, not multiple visits. The Multiple Sales In One Day Count As One Visit on the Loyalty tab of System Settings allows control over how a visit is calculated. If the option is checked on, multiple sales within one trading day count as only one visit.


A snapshot of each item at each location is kept in the STORERNG table. This also contains the current stock on hand as well as last invoice cost, average cost and current sell price. This is fine in order to get a current valuation but does not provide the means to examine trends in stock. This process is run once at the end of the week (month) and moves the stock snapshot from STORERNG to the statistics tables. To optimise storage requirements, the item level details are only recorded if an item statistics record (STATITEM) already exists. (If it doesn't then no stock was sold so the stock details will be assumed to be the same as last week.) Stock details are always recorded at the summary statistics level (STATDEPT). This means a quick snapshot can be obtained by summing the required STATDEPT records. As this process is run each week (month), the statistics records can be used to observe trends in stock. Only items that are marked as stocked (STORERNG.ysnStocked = 'T') are reported.


Upgrades Loyalty members to equivalent categories.


Uploads files for viewing in Report Manager.

Converted from CHM to HTML with chm2web Pro 2.85 (unicode)