Operation and Diagnostic Guide

Operation and Diagnostic Guide

This section describes the steps required to configure a SQL job that will properly update the results tables to keep the Arkieva Sales Predictor user interface results up-to-date. Additional information is provided on the operation of the service for and where to locate diagnostic information if debugging is required.

Recommended Job Steps

This section describes the steps required for a SQL job to keep the Sales Predictor results table refreshed on a frequency defined by the job’s schedule. The recommended frequency is daily.

  1. Reprocess/reload source table data from transactional data sources
  2. Remap the values of Dependent Attributes from master data
  3. Insert into the ztb_SalesPredictor_Sink table the Customer/Item combinations to reprocess
  4. Monitor the ztb_SalesPredictor_Log table and ztb_SalesPredictor_Results table for the status of the requested data processing operation by the background service
  5. Update the Estimated_Value column
  6. Reload Customer/Item SalesPredictor Dimensions if RLS is configured

📘 Note that a system lock notification can be posted to the application to inform users that records are being processed.

Sample Job Configuration

Contact epeters@arkieva.com for a SQL job sample.

Service

On Start

  1. Logs to EventViewer start
  2. Settings loaded from ztb_SalesPredictor_Settings
  • Note that the service must be restarted and the user interface re-opened for changes to settings to take effect

On Timer

  1. Query the sink ztb_SalesPredictor_Sink table
  2. Reprocesses the Customer/Item records in the ztb_SalesPredictor_Sink table
  • First remove the records from the ztb_SalesPredictor_Sink table and move them into the ztb_SalesPredictor_Log table with a “PROCESSING” status
  • Record by record reprocess the combination
  • Get source data from specified table, if no data mark as “IGNORED” and skip to next record
  • Calculate the statistics for the record, update the record status to “RUNNING”
  • When the processing is completed for the record, update the status to “COMPLETED”
  • If an error occurs during processing, update the status to “ERROR” and skip to the next record

📘 Note that the timer will fire by default once/minute after the service start. This value is configurable in the service config file.

On Stop

  1. Logs to EventViewer stop

Diagnostics

Logging events are published to Windows EventViewer. Log into the web server, open EventViewer, go to Application logs and find Arkieva Sales Predictor.

    • Related Articles

    • Configuration and Setup Guide

      Database Schema The following tables must exist in the SQL server with the correct schema and default data for the Arkieva Sales Predictor to properly function. Ztb_SalesPredictor_DependentAttributes Ztb_SalesPredictor_DisplayPreferences ...

    • Data Anomaly Detection

      Why Detect anomalies? Anomaly detection refers to the problem of finding patterns in data that do not conform to expected behavior. In the domain of supply chain management (SCM), anomaly detection is a key factor in making better forecast decisions. ...

    • Sales Predictor

      The Arkieva Sales Predictor is a Sales and/or Customer Relationship Management tool. Its purpose is to flag the most probable and most profitable sales lead opportunities based on analysis of historical data patterns by Customer and Item. The results ...

    • Beacon

      Why beacons? Workstream hierarchy is a concept stating that everything downstream is dependent on something further upstream. Meaning you will need to know what your demand plan is before you can plan for inventory, but you cannot get information for ...

    • General Navigation of Arkieva

      Overview of the various navigational commands in Arkieva. {` `} Launching Arkieva Splash Screen Arkieva is installed to a web server and launched from the client intranet (Internet Explorer is highly recommended). The Arkieva version number, build ...