TapeTrack Documentation

Because there is more to tape management than you ever realized

User Tools

Site Tools

Trace: • journal • ttstats
billing:ttstats

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
billing:ttstats [2026/08/18 03:13] – [Processing Result] Scott Cunliffebilling:ttstats [2026/08/18 03:34] (current) – old revision restored (2026/08/18 03:18) Scott Cunliffe
Line 145: Line 145:
 An empty file may be valid when the Customer had no relevant activity. It should be investigated before being excluded from billing. An empty file may be valid when the Customer had no relevant activity. It should be investigated before being excluded from billing.
  
-==== Incorrect Customer Is Processed ==== 
  
-Check that: 
- 
-  * The correct TTSTATS file was supplied using the ''-i'' argument. 
-  * The filename corresponds to the Customer-ID contained in the file. 
-  * The correct Customer Description Map was used. 
-  * The correct Package Map was used. 
-  * A file from another billing period or environment was not selected. 
  
 ==== Billing Quantities Are Incorrect ==== ==== Billing Quantities Are Incorrect ====
Line 173: Line 165:
 | 11 | Round up to the next 10 | 20 | | 11 | Round up to the next 10 | 20 |
  
-==== No Billing XML Is Produced ==== 
- 
-Check that: 
- 
-  * The ''-i'' argument specifies a valid TTSTATS file. 
-  * The process account has permission to read the file. 
-  * The Customer exists in the Customer Description Map. 
-  * The Customer exists in the Package Map. 
-  * The assigned package exists in the Billing Rules. 
-  * The statistics match at least one Billing Rule. 
-  * ''TMSS10LogStatsProcess'' completed without errors. 
- 
-Redirect diagnostic messages to an error file. 
- 
-Windows example: 
- 
-  TMSS10LogStatsProcess -i US01.ttstats -M customer_map.txt -P package_map.txt -c default.ttsdef > Billing_US01.xml 2> Billing_US01_error.txt 
- 
-Review ''Billing_US01_error.txt'' for file, mapping and configuration errors. 
  
 ==== Charges Are Duplicated ==== ==== Charges Are Duplicated ====
Line 206: Line 179:
  
   * Generate a new TTSTATS file for every billing period.   * Generate a new TTSTATS file for every billing period.
-  * Use the Customer-ID and billing period in the filename. 
-  * Store each billing period in a separate directory. 
   * Do not manually edit generated TTSTATS files.   * Do not manually edit generated TTSTATS files.
-  * Record the extraction start and end dates. 
-  * Review extraction logs before processing billing. 
-  * Prevent the same file from being processed twice. 
-  * Retain the TTSTATS file with its billing XML and invoice reference. 
   * Restrict write access to authorized billing administrators.   * Restrict write access to authorized billing administrators.
-  * Archive completed billing files as read-only records.+  * Archive completed billing files as read-only records if required.
  
 ===== Security ===== ===== Security =====
Line 236: Line 203:
   * [[billing:package_map|Package Map]]   * [[billing:package_map|Package Map]]
   * [[billing:billing_rules|Billing Rules]]   * [[billing:billing_rules|Billing Rules]]
-  * [[billing:tapetrack_xslt|TapeTrack XML Stylesheet]]+  * [[billing:stylesheet|TapeTrack XML Stylesheet]]
   * [[billing:billing_process|Billing Process]]   * [[billing:billing_process|Billing Process]]
   * [[billing:billing_xml|Billing XML]]   * [[billing:billing_xml|Billing XML]]
billing/ttstats.1787022829.txt.gz · Last modified: 2026/08/18 03:13 by Scott Cunliffe