TapeTrack Documentation

Because there is more to tape management than you ever realized

User Tools

Site Tools


billing:journal

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:journal [2026/08/18 03:36] – [Viewing Journal Information] Scott Cunliffebilling:journal [2026/08/18 03:44] (current) – [See Also] Scott Cunliffe
Line 79: Line 79:
 </WRAP> </WRAP>
  
-===== Validation ===== 
- 
-The Journal and extraction should be validated before production billing is processed. 
- 
-Check that: 
- 
-  * The correct Journal database is being used. 
-  * The Framework Server recorded activity during the billing period. 
-  * The extraction date range is correct. 
-  * The server date, time and time zone are correct. 
-  * A ''.ttstats'' file was generated for each expected Customer. 
-  * The generated files are not unexpectedly empty. 
-  * The extraction process completed without errors. 
-  * The Journal was backed up before any administrative maintenance. 
-  * The extracted quantities are reasonable for the billing period. 
- 
-A billing control record should include: 
- 
-^ Control ^ Example ^ 
-| Framework Server | Production TapeTrack Server | 
-| Billing period | ''2026-07-01 to 2026-07-31'' | 
-| Extraction utility | ''TMSS10LogStatsExtractDB'' | 
-| Extraction date | ''2026-08-01'' | 
-| Output directory | ''C:\TapeTrack\Billing\2026-07\Input'' | 
-| Customer files created | ''US01.ttstats'', ''US02.ttstats'' | 
-| Extraction status | Completed | 
-| Reviewer | Authorized billing administrator | 
  
 ===== Troubleshooting ===== ===== Troubleshooting =====
  
-==== No TTSTATS Files Are Created ==== 
  
-Check that: 
  
-  * ''TMSS10LogStatsExtractDB'' completed successfully. 
-  * The correct Journal database was selected. 
-  * Journal records exist within the selected date range. 
-  * The output directory exists. 
-  * The extraction account can read the Journal. 
-  * The extraction account can write to the output directory. 
-  * The date range was entered in the expected format. 
- 
-==== Customer TTSTATS File Is Missing ==== 
- 
-Confirm that: 
- 
-  * The Customer exists in TapeTrack. 
-  * The Customer had Journal activity during the billing period. 
-  * The Customer-ID is correct. 
-  * The extraction covered the complete billing period. 
-  * The file was not moved, renamed or archived. 
-  * The extraction log does not contain an error for the Customer. 
- 
-A missing Customer file may be valid if the Customer had no relevant Journal activity. This should be confirmed before excluding the Customer from billing. 
- 
-==== TTSTATS File Is Empty ==== 
- 
-Check that: 
- 
-  * Journal activity exists for the Customer. 
-  * The selected date range includes the activity. 
-  * The correct production Journal was processed. 
-  * The server date and time zone are correct. 
-  * The Customer activity is of a type included in the statistics extraction. 
- 
-==== Billing Activity Is Missing ==== 
- 
-Compare: 
- 
-  - The operational event in TapeTrack. 
-  - The corresponding Journal entry. 
-  - The generated ''.ttstats'' file. 
-  - The Billing Rules applied by ''TMSS10LogStatsProcess''. 
-  - The resulting billing XML. 
- 
-This identifies the stage at which the activity was excluded. 
- 
-^ Activity Location ^ Likely Issue ^ 
-| Missing from TapeTrack | Operational event was not recorded. | 
-| Present in TapeTrack but missing from Journal | Framework Server or Journal recording issue. | 
-| Present in Journal but missing from TTSTATS | Extraction date range or extraction issue. | 
-| Present in TTSTATS but missing from billing XML | Package Map or Billing Rules issue. | 
-| Present in billing XML but missing from QuickBooks | XMLQuickBooks mapping or import issue. | 
- 
-==== Billing Activity Is Duplicated ==== 
- 
-Check that: 
- 
-  * Extraction date ranges do not overlap. 
-  * The same ''.ttstats'' file was not processed twice. 
-  * The same billing XML was not submitted twice. 
-  * Duplicate Billing Rules are not matching the same statistic. 
-  * Previously processed files were moved to an archive directory. 
  
 ==== Journal Cannot Be Read ==== ==== Journal Cannot Be Read ====
Line 186: Line 98:
 If the Journal appears damaged or unreadable, contact TapeTrack Support before attempting repairs. If the Journal appears damaged or unreadable, contact TapeTrack Support before attempting repairs.
  
-===== Backup and Retention ===== 
- 
-The Journal supports operational history and billing reconstruction and should be included in the Framework Server backup process. 
- 
-The backup and retention policy should consider: 
- 
-  * Customer contract requirements. 
-  * Accounting record-retention requirements. 
-  * The ability to reproduce billing statistics. 
-  * Audit and dispute periods. 
-  * Available storage. 
-  * TapeTrack Support recommendations. 
-  * Applicable legal and regulatory requirements. 
- 
-Retain the following billing records together where possible: 
- 
-  * Billing period details. 
-  * Journal backup or reference. 
-  * Customer ''.ttstats'' files. 
-  * Customer Description Map. 
-  * Package Map. 
-  * Billing Rules. 
-  * Stylesheet. 
-  * Billing XML. 
-  * QuickBooks invoice number. 
-  * Processing and approval logs. 
  
 ===== Recommended Practices ===== ===== Recommended Practices =====
Line 217: Line 103:
   * Treat the Journal as an authoritative operational record.   * Treat the Journal as an authoritative operational record.
   * Do not manually edit the Journal database.   * Do not manually edit the Journal database.
-  * Back up the Journal as part of the Framework Server backup. 
   * Use non-overlapping billing extraction periods.   * Use non-overlapping billing extraction periods.
   * Record the exact extraction date range.   * Record the exact extraction date range.
-  * Review extraction logs before processing billing. 
   * Investigate missing or empty Customer files.   * Investigate missing or empty Customer files.
-  * Retain the extracted TTSTATS files with the billing output.+  * Retain the extracted TTSTATS files with the billing output if required.
   * Restrict database access to authorized administrators.   * Restrict database access to authorized administrators.
   * Contact TapeTrack Support before attempting Journal repair.   * Contact TapeTrack Support before attempting Journal repair.
Line 235: Line 119:
   * TapeTrack administrators.   * TapeTrack administrators.
   * Authorized billing staff requiring access.   * Authorized billing staff requiring access.
-  * The account running ''TMSS10LogStatsExtractDB''.+  * The account running [[cli:TMSS10LogStatsExtractDB]].
   * The account running authorized backup processes.   * The account running authorized backup processes.
  
Line 244: Line 128:
   * [[cli:tmss10logstatsprocess|TMSS10LogStatsProcess]]   * [[cli:tmss10logstatsprocess|TMSS10LogStatsProcess]]
   * [[object:customer|Customer-ID]]   * [[object:customer|Customer-ID]]
-  * [[billing:customer_ttstats|Customer TTSTATS File]]+  * [[billing:ttstats|Customer TTSTATS File]]
   * [[billing:customer_map|Customer Description Map]]   * [[billing:customer_map|Customer Description Map]]
   * [[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/journal.1787024169.txt.gz · Last modified: 2026/08/18 03:36 by Scott Cunliffe