bv annalysis

Subject: Multi BV log analyser
Summary: Tool (called BV Parser) to convert / analyse single and multiple GBxx (Save)BVInf.dat log files. BVparser.exe reads in (Save)BVInf.dat files and stores the result in an Excel format file. Default the transaction overview is provided, as options a dashboard and a consolidated overview (in case of multiple logs) can be selected.
Region Distribution: Americas

Asia Pacific
EMEA
Japan
Audience: NCR
NCR & Distributers
NCR & Service Partners
All (Including Customers)
Reason for Release: Support Issue
Change to Service Philosophy

New Feature
Revision Record:
Revision
Reason for change
Date
A
First publication
10th May

1. Introduction

Introduction Introduction Introduction Introduction Introduction Introduction Introduction Introduction Introduction
The (Save)BVInf.dat log contains the information of the notes which went through the BV (Bill Validator). The note information is organized / consolidated by transaction.

The (Save)BVInf.dat is a circulair log which means that continuously the oldest data is overwritten. The number of days contained by the log is dependent on the transaction volume. In general the log contains around 5’500 notes which would mean that with e.g. a volume of 1’000 notes / day the log contain a little bit more than 5 days of transaction information.

The (Save)BVInf.dat log can be pulled onsite through diagnostics / sysapp (and is named BVInf.dat) or remotely in which case the file first needs to be generated which is at most deployments done by running an utility during startup which generates the file (which is in that case named SaveBVInf.dat).
For an easy processing of a single / multiple files, it would be best to include the unitid (e.g. serial #, etc.) in the log name: (Save)BVInf_<unitid>.dat .

Related posts

Leave a Comment