The information in this article applies to:
This article provides information regarding how Transaction Processing is implemented within Tabs3 and PracticeMaster software. If a non-exclusive task is interrupted while using Client Server version (CSV) software, in most cases you simply need to rerun the task with the same options. However, it may be useful to understand exactly how the transaction processing is implemented for integration purposes and potential troubleshooting situations.
This table explains the column headings for the other tables.
|
Interrupted Task |
Represents the task being performed when the interruption occurred. |
|
Integration |
This column is used to differentiate between the specific resolutions required when integrating with other Tabs3/PracticeMaster software products. |
|
Database Transaction Notes |
Explains how transaction processing is implemented within each task. |
|
Resolution |
Includes the step(s) necessary to resume your work after the interruption has occurred. |
The following tables include the various tasks where transaction processing has been implemented.
Note: Keep in mind that Exclusive Functions do not implement Transaction Processing.
|
Interrupted Task |
Integration |
Database Transaction Notes |
Resolution |
|
Fee Entry |
N/A |
The fee entry is a single database transaction. |
Re-enter the fee. |
|
Cost Entry |
Disabled |
The cost entry and the journal entries are a single database transaction. |
Re-enter the cost. |
|
GLS |
The cost entry is one database transaction, and the GLS journal entries are a separate database transaction. |
Manually reverse any GLS journal entries that were created, then re-enter the cost. |
|
|
Payment Entry |
Disabled |
The payment entry is a single database transaction. |
Re-enter the payment |
|
GLS |
The payment entry and any journal entries that can be created without user interaction are one database transaction. GLS journal entries that require user interaction are a separate database transaction. |
Verify what was actually saved before the interruption. Check for the payment entry as well as any journal entries. If the payment was not saved, simply re-enter it. Manual journal entries may need to be entered. |
|
|
GLS |
When applying a payment to multiple matters with the GLS message box coming up, each payment entry made to each separate matter is a separate database transaction. |
Delete and re-enter the payment(s). |
|
|
Adjust Flat Fee Clients |
N/A |
Each completed client is a single database transaction. |
Rerun the Adjust Flat Fee Clients function. |
|
Adjust Split Fee Clients |
N/A |
Each completed Main client is a single database transaction. |
Rerun the Adjust Split Fee Clients function. |
|
Change WIP Transactions |
N/A |
Each completed client is a single database transaction. |
Rerun the Change WIP Transactions function with the same settings. |
|
Change Client Options |
N/A |
Each completed client is a single database transaction. |
Rerun the Change Client Options function with the same settings. |
|
Create Validation Files |
N/A |
The whole function is one database transaction. |
Recreate the validation files. |
|
Merge Data Capture Transactions |
N/A |
Each successfully merged line item is a separate database transaction. |
Rerun the Merge Data Capture Transactions function to merge the remaining entries. |
|
Merge Tabs3 Remote Data |
N/A |
Each successfully merged line item is a separate database transaction. |
Rerun the Merge Tabs3 Remote Data function to merge the remaining entries. |
|
Write-Up/Down |
N/A |
The entire function is one database transaction. |
Rerun the Write-Up/Write-Down Fees and Costs function. |
|
Update Statements |
N/A |
Each completed client is a single database transaction. |
Run a Data File Integrity Check. If clean, rerun Update Statements to process the remaining clients. |
|
Undo Single/Multiple Updated Statements |
N/A |
Each completed client is a single database transaction. |
Rerun the Undo Single/Multiple Updated Statements function. |
|
Unbill Final Statements |
N/A |
Each completed client is a single database transaction. |
Rerun the Unbill Final Statements function. |
|
Transfer A/R and Transactions |
N/A |
The entire function is one database transaction. |
Rerun the Transfer Transactions function. |
|
Delete a Range of Clients |
N/A |
Each successfully deleted client is one database transaction. |
Rerun the Delete a Range of Clients function with the same settings. |
|
Renumber Client (Version 15 & later) |
N/A |
Each successfully renumbered client is one database transaction. |
Rerun the Renumber Client function using the same old and new client. |
|
Changing the address of the main client for a multi-matter client |
N/A |
Saving the changes to the main client is one database transaction. Applying the changes to the other matters is separate database transaction. |
Resave the original change to the main client. |
|
Payment Adjustment |
N/A |
The entire function is one database transaction. |
Rerun the Payment Adjustment function. |
|
Rename Statement Template |
N/A |
The entire function is one database transaction. |
Rerun the Rename Statement Template function. |
|
Change the description of a Transaction Code (tcode). |
N/A |
The entire function is one database transaction. |
Repeat the change to the transaction code. |
|
Write Off Client |
N/A |
The entire function is one database transaction. |
Rerun the Write Off Client function. |
|
Reverse Write Off |
N/A |
The entire function is one database transaction. |
Rerun the Reverse Write Off function. |
|
Interrupted Task |
Database Transaction Notes |
Resolution |
|
Check Out Briefcase |
Each item checked out is a database transaction. |
Rerun the Check Out Briefcase function. |
|
Check In Briefcase |
Each item checked in is a database transaction. |
Rerun the Check In Briefcase function to pick up where you left off. |
| Create Linked Calendar Records | The entire function is one database transaction. | Recreate the calendar record. |
|
Process Calendar Plan Template |
Each calendar record is a database transaction. |
Go into View Calendar Plan Template and delete the template, selecting to delete the associated items. Then rerun the Process Calendar Plan Template function. |
|
Generate CompuLaw Dates |
Each calendar record is a database transaction. |
Go into View Calendar Plan Template and delete the template, selecting to delete the associated items. Then rerun the Generate CompuLaw Dates function. |
|
Convert to Fee |
Each successfully converted record is a separate database transaction. |
Rerun the Convert to Fee function to pick up where you left off. |
|
Process Timer Records |
Each successfully processed record is a separate database transaction. |
Rerun the Process Timer Records function to pick up where you left off. |
|
Interrupted Task |
Database Transaction Notes |
Resolution |
|
None Currently |
N/A |
N/A |
|
Interrupted Task |
Integration |
Database Transaction Notes |
Resolution |
|
Print Checks |
N/A |
Each successfully printed check is a separate database transaction. |
Rerun the Print Checks function with the same settings to pick up where it left off. |
|
Void/Reprint Unposted Checks |
N/A |
The entire function is a singe database transaction. |
Rerun the Void/Reprint Unposted Checks function with the same settings. |
|
Post Checks |
N/A |
Each successfully posted check is a separate database transaction. |
Rerun the Post Checks function with the same settings to post the remaining checks. |
|
Void Posted Checks |
N/A |
The entire function is a single database transaction. |
Rerun the Void Posted Checks function with the same settings. |
|
Transfer Invoices |
N/A |
Each successfully transferred invoice is a separate database transaction. |
Rerun the Transfer Invoices function with the same settings to transfer the remaining invoices. |
|
Select Invoices to Save/Purge |
N/A |
Each item successfully set is a separate database transaction. |
Rerun the Select Invoices to Save/Purge function with the same settings to set the remaining invoices. |
|
Entering an Invoice/Manual Check |
N/A |
The Invoice/Manual Check is a single database transaction. |
Evaluate the GLS information for the invoice to make sure it's complete. Resave the entry to get the Tabs3 Cost entry to come up if needed. |
|
Interrupted Task |
Integration |
Database Transaction Notes |
Resolution |
|
Print Checks |
N/A |
The entire check run is one database transaction. |
Reprint the entire run of checks. |
|
Writing a check to FIRM |
Tabs3/GLS |
The Tabs3 and GLS entries are created when the TAS check is printed, making it all one database transaction. |
Reprint the check. |
|
GLS only |
The GLS entries are created when the TAS check is printed, making it all one database transaction. |
Reprint the check. |
|
|
Create APS 1099 Merge File |
N/A |
The entire function is one database transaction. |
Rerun the Create APS 1099 Merge File function. |
|
Select Trust Transaction to Save/Purge |
N/A |
Each item successfully set is a separate database transaction. |
Rerun the function with the same settings to set the remaining records. |
|
Void Check |
N/A |
Each check that is successfully voided is a separate database transaction. |
Rerun the function with the same settings to void the remaining entries. |
KB Article R11175 - Transaction Processing
THE INFORMATION PROVIDED IN THE SOFTWARE TECHNOLOGY, INC. KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. SOFTWARE TECHNOLOGY, INC. DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL SOFTWARE TECHNOLOGY, INC. OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF SOFTWARE TECHNOLOGY, INC. OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.
© 1999-2010 Software Technology, Inc. All rights
reserved. Terms of Use
The maker of Tabs3 and PracticeMaster
Tabs3, PracticeMaster, and the “pinwheel” symbol (
) are registered trademarks of Software Technology, Inc.
e-Mail Suggestions for the Knowledge Base to: kb@Tabs3.com
Technical Support via e-mail is not available.
Knowledge Base: http://support.Tabs3.com
Web Site: http://www.Tabs3.com