# Database schema: PracticeCS

## DBMS: mssql

Version: 3014.0.127
Tables

Accruable_Benefit |
Accruable_Benefit_Allowance_By_Month | Accruable benefit allowances based on months employed.
Accruable_Benefit_Allowance_By_Staff_Level |
Active_Filter | This table keeps track of filters used in CommonDropDownList controls.
Activity |
Activity_Category |
Additional_Contact |
Address |
Attachment | Associates attachments to an item.
Attachment_Content |
Bank_Account |
Benefit |
Benefit_Factor |
Billing_Decision |
Billing_Decision_Collection | This table would be more properly named [Billing_Decision_Application] and "collected" in column names could be replaced with "applied". This table stores rows that indicate how much of a [Billing_Decision] has been closed and what closed it. The main purpose of this is to track payments all the way down to [Sheet_Entry] so we can compute how much was produced, billed and collected for each sheet entry row. Not all rows in this table are really collections, as collections are only the amounts of billing decision rows that are closed by payments. Other sources can close billings, including credit memos, billing adjustments and negative WIP. ([ledger_entry_KEY], [sheet_entry_KEY]) identifies the [Billing_Decision] row this application is closing. ([from__ledger_entry_KEY], [collection_source__ledger_entry_KEY]) identifies the [Ledger_Entry_Application] row by ([from__ledger_entry_KEY], [to__ledger_entry_KEY]) that caused these applications for "Standard" type applications (see below). This can't directly be a relation to [Ledger_Entry_Application] because only standard type applications would have a record in LEA. This may change in the future to always be able to reference a LEA row (the LEA row would be for a zero amount except for standard type records). ([from__ledger_entry_KEY]) identifies the invoice that had applications to Progress Billings that tricked down to applications against progress relief on the invoice [ledger_entry_KEY] represents. There are three types of Billing_Decision_Collection records: Standard (user-created): ... from__ledger_entry_KEY == ledger_entry_KEY and from__ledger_entry_KEY <> collection_source__ledger_entry_KEY Zero Invoice Closing Adjustment: ... from__ledger_entry_KEY == ledger_entry_KEY and from__ledger_entry_KEY == collection_source__ledger_entry_KEY Progress Relief applications: ... from__ledger_entry_KEY <> ledger_entry_KEY Standard type applications don't have to track the progress relief to a different invoice so [from__ledger_entry_KEY] == [ledger_entry_KEY].
Billing_Decision_Tax_Collection | This table stores the same thing that [Billing_Decision_Collection] does, but for [Billing_Decision_Taxing_Authority] instead of [Billing_Decision].
Billing_Decision_Taxing_Authority |
Billing_Rate_Type |
COMMON_Metadata_About_Columns |
COMMON_Metadata_About_Foreign_Keys |
COMMON_Metadata_About_Keys |
COMMON_Metadata_About_Sprocs |
COMMON_Unique_Identifier_Counter |
Calendar_Category | Storage for a description and color which is assigned to a schedule entry.
Changeset | A changeset is a way to associate a set of record changes with each other and with who, when and where the changes were made. Changeset records should only be inserted or updated by calling the procedures up_Changeset_begin and up_Changeset_end. After insert, records can only be updated while they are active, and only to specify a value for end_date_utc as they are being ended/becoming inactive.
Changeset_Active | Between the time that a Changeset has been begun by up_Changeset_begin and ended by up_Changeset_end it is marked as active and associated with a SQL Server transaction by having a record in this table. When Changesets are used as designed there will never be records for them in this table visible outside of the transaction. If the database is changed outside of the application or without properly beginning and ending a changeset, a changeset may be automatically created and will not be ended, so records will be visible in this table for those changesets. It is safe to delete these stranded records from Changeset_Active.
Changeset_Modified_Table | When history records are created the changeset that created the history and which table history was created for are recorded in Changeset_Modified_Table.
Client |
Client_Date_Cache | A denormalized cache of Production, Billing, Invoicing, Collection and Accounts Receivable numbers by Client, Client Family (principal) and date. During normal operation, records are only inserted into this table which results in more than one record with the same client_KEY, principal__client_KEY and entry_date value. This table is maintained entirely by the triggers that contain maintain_client_date_cache in their name.
Client_Financial_Data |
Client_Financial_Data_Description | Descriptions for Client_Financial_Data values
Client_Shortcut | This table is a data store for the Solutions portlets. It contains information about user-configurable solutions (which are paths to files, folders, or web pages).
Client_Shortcut_Group | This table is a data store for the Solutions portlets. It contains information about user-configurable groups of solutions (which are paths to files, folders, or web pages).
Client_Staff_Grouping |
Client_Status_Event |
Contact |
Contact_Address |
Contact_Category |
Contact_Contact_Category |
Contact_Email |
Contact_Phone |
Credit_Card |
Credit_Card_Type | Tags: read-only Content:
0 | NONE | None | NONE
1 | MC | Master Card | MC
2 | VISA | Visa | VISA
3 | AMEX | American Express | AMEX
4 | DISC | Discover | DISC
Custom_Chart |
Custom_Field |
Custom_Fieldview |
Custom_Fieldview_Type |
Custom_Formula |
Custom_Grouping |
Custom_Portlet |
Custom_Portlet_Type | Tags: read-only Content:
1 | Web_Page
2 | External_News_Feed
3 | Internal_News_Feed
100 | Report Based
Custom_Value |
Dashboard_Layout |
Database_Property |
Datasharing_Group |
Datasharing_Path |
Department | Department is a grouping that Staff can be assigned to.
Department_Grouping_Type | Tags: read-only Content:
998 | 1000 | <ProjectResponsible>'s <Department> | Project | [KEY(Staff department(Project responsible staff(Project)))]
999 | 2000 | <ProjectAssigned>'s <Department> | Project | [KEY(Staff department(Project assigned staff(Project)))]
1000 | 3000 | Specified <Department> |  |
Digit | The Digit table holds the values 0 to 9 which makes it convenient to join against for generating ranges. Tags: read-only Content:
0
1
2
3
4
5
6
7
8
9
Digita_Vat_Period | Digita VAT reporting periods used to associate with VAT Ledger entries.
Education_Accountancy |
Education_Accountancy_Category |
Education_Accountancy_Type |
Education_Credit |
Education_Sponsor |
Email_Address | Holds e-mail addresses to save space and aid in indexing. Each e-mail address must be unique and stored as lower case. It is expected that the e-mail address is a SMTP address and looks similar to "user.name@place.net"
Engagement |
Engagement_Template |
Engagement_Type |
Entity |
Event_Class_Type | Tags: read-only Content:
1 | <Client>
2 | <Engagement>
3 | Invoice
4 | <Project>
5 | <ProjectTask>
6 | Timer
7 | <Interaction>
8 | <Benefit>
9 | <Meeting>
10 | <ToDo>
11 | <ScheduledPhoneCall>
12 | <ScheduledBenefit>
13 | <ScheduleItem>
14 | <CPECourse>
15 | LedgerEntry
16 | SheetEntry
Feed_Channel |
Feed_Channel_Item |
Feed_Channel_Item_Enclosure |
Feed_Channel_Item_Staff_Read |
Feed_Portlet |
File_Transfer | Contains records of File Transfers that have been created on the Portal server
File_Transfer_Event | Events that occured during the life cycle of a File Transfer. These can originate from Practice CS or from the Portal web user interface
File_Transfer_File | Contains files that are part of a File Transfer
Filter |
Filter_Base_Type |
Filter_Line |
Filter_Line_Type | Tags: read-only Content of first 30 of 190 rows:
1 | <Staff> | Staff | staff_KEY | 1
2 | <Staff> Type | Staff_Level | staff_level_KEY
3 | <Office> | Office | office_KEY | 7
4 | <Department> | Department | department_KEY
6 | <Activity> | Activity | activity_KEY | 2
7 | <Activity> Type | Activity_Method | activity_method_KEY
8 | Referral Type | Referral_Type | referral_type_KEY
9 | Referral Source | Referral_Source | referral_source_KEY
10 | <Client> | Client | client_KEY | 4
12 | Industry Code | Client | industry_code
14 | Entity | Entity | entity_KEY
15 | <Engagement> | Engagement | engagement_KEY | 5
16 | Date | Sheet_Entry | entry_date
17 | <Activity> Category | Activity_Category | activity_category_KEY
18 | <Activity> Class | Activity_Class | activity_class_KEY
19 | <Client> Type | Client_Class | client_class_KEY
20 | <Engagement> Template | Engagement_Template | engagement_template_KEY
21 | <Engagement> Type | Engagement_Type | engagement_type_KEY
22 | Bank Account | Bank_Account | bank_account_KEY
23 | Ledger Entry Type | Ledger_Entry_Type | ledger_entry_type_KEY
24 | Recurring Bill | Recurring_Bill | recurring_bill_KEY
25 | Date | Sheet_Entry | sheet_date
26 | Date | Invoice | invoice_date
27 | Date | Invoice | due_date
28 | Date | Ledger_Entry | control_date
29 | Date | Ledger_Entry | entry_date
30 | <Project> | Project | project_KEY | 6
31 | <Project> Template | Project_Template | project_template_KEY
32 | Date | Project | current_due_date
33 | Priority | Priority | priority_KEY
Filter_Range_Type | Tags: read-only Content of first 30 of 184 rows:
1 | 1 | ID | staff_id
2 | 1 | Name | description
3 | 3 | ID | office_id
4 | 3 | Name | description
5 | 2 | ID | staff_level_id
6 | 2 | Name | description
7 | 4 | ID | department_id
8 | 4 | Name | description
9 | 6 | ID | activity_id
10 | 6 | Name | description
13 | 9 | Description | description
14 | 10 | ID | client_id
15 | 10 | Name | description
17 | 7 | Name | description
18 | 17 | ID | activity_category_id
19 | 17 | Name | description
20 | 18 | Name | description
21 | 19 | Name | description
25 | 16 | Date | entry_date
26 | 12 | <IndustryCode> | industry_code
27 | 25 | Date | sheet_date
28 | 26 | Date | invoice_date
29 | 27 | Date | due_date
30 | 28 | Date | control_date
31 | 29 | Date | entry_date
32 | 20 | ID | engagement_template_id
33 | 20 | Name | description
34 | 24 | Name | description
35 | 14 | Name | description
36 | 14 | ID | entity_id
Filter_Select |
Filter_Type | Tags: read-only Content of first 30 of 36 rows:
1 | Staff | <Staff>
2 | Activity | <Activity>
3 | Expense | <Expense>
4 | Client | <Client>
5 | Engagement | <Engagement>
6 | Project | <Project>
7 | Office | <Office>
8 | Sheet_Entry | Time & <Expense> Entry
12 | Invoice | Invoice
13 | Ledger_Entry | Receipt & Adjustment Entry
14 | Engagement_List | <Engagement>
15 | Statement_Selection | Statement Selection
19 | Ledger_Entry | A/R Entry
20 | Billing_Decision |
22 | Billing_Worksheet |
23 | Task | <ProjectTask>
24 | Project_Template | <Project> Template
25 | Production_And_Billing_Posted |
26 | Interaction | <Interaction>
27 | Contact | <Contact>
29 | Project_Template_Definition | <Project> Template
30 | Interaction | <Interaction>
31 | Payroll_Check | Payroll Check
32 | Employee | <Employee>
33 | Billing_Decision_Taxing_Authority |
34 | Integration_Sheet_Entry | Integrated Sheet Entry
35 | Schedule_Item | <ScheduleItem>
37 | Staff_Benefit | <Staff> <Benefit>
38 | Billing_Decision_Collection | Billing Decision Collection
39 | Staff_Education_Credit | <CPECourse>
Firm |
Firm_Dashboard_Layout |
Firm_Date |
Firm_Date_Type | Tags: read-only Content:
1 | 10000 | Year
2 | 10000 | Period
3 | 10000 | Benefit Year
Firm_Shortcut | This table is a data store for the Solutions portlets. It contains information about user-configurable solutions (which are paths to files, folders, or web pages).
Firm_Shortcut_Group | This table is a data store for the Solutions portlets. It contains information about user-configurable groups of solutions (which are paths to files, folders, or web pages).
GL_Entry_Export_Option |
GL_Entry_Export_Type | Tags: read-only Content:
1 | Receipts | 1
2 | Accounts Receivable | 1
3 | Credit Memos | 1
4 | Debit Memos | -1
5 | <ServiceCharges> | -1
6 | Write Offs | 1
7 | Revenue | -1
8 | <SalesTaxes> | -1
9 | <ServiceTaxes> | -1
10 | Progress Billings | -1
11 | Unapplied Receipts | 1
Gofileroom_Workflow | Stores information about GoFileRoom Workflows. Field lengths match the field lengths defined in GoFileRoom Workflow.
History_Action | Tags: read-only Content:
1 | Created
2 | Modified
5 | Created, Deleted
6 | Modified, Deleted
8 | Current
History_Of_Additional_Contact |
History_Of_Attachment |
History_Of_Attachment_Content |
History_Of_Calendar_Category |
History_Of_Client |
History_Of_Client_Financial_Data |
History_Of_Client_Financial_Data_Description |
History_Of_Client_Staff_Grouping |
History_Of_Contact |
History_Of_Contact_Address |
History_Of_Contact_Category |
History_Of_Contact_Contact_Category |
History_Of_Contact_Email |
History_Of_Contact_Phone |
History_Of_Custom_Chart |
History_Of_Custom_Field |
History_Of_Custom_Value |
History_Of_Digita_Vat_Period |
History_Of_Engagement |
History_Of_File_Transfer |
History_Of_File_Transfer_Event |
History_Of_File_Transfer_File |
History_Of_Link |
History_Of_Link_Group |
History_Of_Portal_User |
History_Of_Project |
History_Of_Project_Extension |
History_Of_Schedule_Entry |
History_Of_Schedule_Item |
History_Of_Schedule_Item_Assignment |
History_Of_Schedule_Item_Budget_Remaining_Entry |
History_Of_Schedule_Item_Series |
History_Of_Sheet_Entry |
History_Of_Tag |
History_Of_Tagged_Item |
History_Of_Task |
History_Of_Time_Zone |
History_Of_Timer |
Integration_Application |
Integration_Custom_Value |
Integration_Invoice |
Integration_Invoice_Prior_Payment |
Integration_Sheet_Entry | This table is a holding area for Sheet Entry rows that are imported from a Disconnected Database, before they are verified by a user. There is intentionally no foreign keys to this table, so that rows can still be accepted into the database should the related rows not exist.
Interaction | Holds all of the interactions regardless of type and what they are associated with.
Interaction_Association | SYSTEM TABLE: Defines types of association that a Contact can have to an Interaction. Tags: read-only Content:
0 | Contact | 1 | 0
1 | Staff | 0 | 1
2 | Originator | 0 | 1
3 | Of | 0 | 1
Interaction_Contact | Links an Interaction to zero or more Contacts. Each combination of Interaction and Contact must be unique.
Interaction_Email_Address | Holds the list of e-mail address and which e-mail address fields they came from for a particular interaction.
Interaction_Link | Contains additional information about links to Interaction items.
Interaction_Phone_Number | Links a Phone Call or Phone Message type Interaction to zero or one phone number. Even if other phone numbers change this phone number remains unchanged for historical information.
Interaction_Subtype | SYSTEM TABLE: Defines the subtypes of interactions that can be stored in the Interaction table. Tags: read-only Content:
0 | 0 | E-mail
1 | 1 | Note
2 | 2 | Incoming
3 | 2 | Outgoing
4 | 3 | Please Call Back
5 | 3 | Will Call Back
6 | 3 | Returned Your Call
7 | 4 | Created
8 | 4 | File Uploaded
9 | 4 | File Deleted
10 | 4 | Waiting for Files
11 | 4 | Ready for Download
12 | 4 | Email Notification Sent
13 | 4 | File Downloaded
14 | 4 | File Signed
15 | 4 | File Rejected
16 | 4 | Completed
17 | 4 | Expired
18 | 4 | Canceled
19 | 4 | All Files Purged
Invoice |
Invoice_Office |
Last_Table_Modification |
Ledger_Entry |
Ledger_Entry_Application |
Ledger_Entry_Service_Charge |
Ledger_Entry_Submittal |
Ledger_Entry_Submittal_Result |
Ledger_Entry_Subtype | SYSTEM TABLE: Defines the subtypes of ledger_entrys that can be stored in the Ledger_Entry table.
Ledger_Entry_Type | Tags: read-only Content:
1 | INV | Invoice | 1 | INV
2 | SC | Service Charge | 1 | SC
3 | DM | Debit Memo | 1 | DM
4 | CHK | Check | -1 | CHK
5 | CM | Credit Memo | -1 | CM
6 | NSF | Non-Sufficient Funds | 1 | NSF
7 | WO | Write Off | -1 | WO
8 | CA | Cash | -1 | CA
9 | CC | Credit Card | -1 | CC
10 | CCR | Credit Card Return | 1 | CCR
11 | ACH | Electronic Funds Transfer | -1 | ACH
12 | PWO | Proforma Write Off | -1 | Proforma Write Off
13 | CNA | Reversal (Application) | -1 | CNA
Legacy_Contact_Portal_Mapping | Contains the legacy mappings for contacts to portals that need to be converted.
Link | This table stores information about links to external documents.
Link_Group | This table stores information about groups of links to external documents.
Login_Ticket | Single-use login tickets which can be used in lieu of a password for authentication.
Lost_Reason |
Lost_To |
Monitored_Event |
Monitored_Event_Action |
Month_Info | Basic information about calendar months (in English.) This information is useful for drop down lists, etc and is used mostly in Filtering. Tags: read-only Content:
1 | 1 | 000000000001 j | January
2 | 2 | 000000000002 j | February
3 | 3 | 000000000003 j | March
4 | 4 | 000000000004 j | April
5 | 5 | 000000000005 j | May
6 | 6 | 000000000006 j | June
7 | 7 | 000000000007 j | July
8 | 8 | 000000000008 j | August
9 | 9 | 000000000009 j | September
10 | 10 | 000000000010 i | October
11 | 11 | 000000000011 i | November
12 | 12 | 000000000012 i | December
Observed_Holiday |
Office |
Online_Invoice | Information about Invoices that have been sent to the online bill pay service.
Online_Payment | Information about Payments that have been received from the online bill pay service.
Option_List |
Outlook_Contact_Synchronization_Folder | A list of Outlook? folders to synchronize contacts with for a particular Staff's contact synchronization profile. The combination of (outlook_contact_synchronization_profile_KEY, outlook_store_KEY, entry_id) is unique. "For the Exchange message entrys, entry id includes the full distinguished name of the mailbox, which is not limited in length AFAIK. Since MAPI starts barking when a property size goes above about 4k (you need to open the property as IStream, not with IMAPIProp::GetProps(...), etc), it would be relatively safe to alllocate 8192 chars for the entry ids - if your code breaks, so would Outlook? itself." -- Dmitry Streblechenko (MVP) http://www.dimastr.com/, http://groups.google.com/group/microsoft.public.outlook.program_vba/browse_frm/thread/f768d385c8dd4a27/1df02bd5c153c6bd%231df02bd5c153c6bd
Outlook_Contact_Synchronization_Profile | Stores a Contact Synchronization Profile, a staff-specific set of Outlook? folders and database contact filters to configure contact syncronization.
Outlook_Index_Folder_Firm | A list of Outlook(R) folders to index for firm-specific email. The combination of (firm_KEY, outlook_store_KEY, entry_id) is unique. "For the Exchange message entrys, entry id includes the full distinguished name of the mailbox, which is not limited in length AFAIK. Since MAPI starts barking when a property size goes above about 4k (you need to open the property as IStream, not with IMAPIProp::GetProps(...), etc), it would be relatively safe to alllocate 8192 chars for the entry ids - if your code breaks, so would Outlook itself." -- Dmitry Streblechenko (MVP) http://www.dimastr.com/, http://groups.google.com/group/microsoft.public.outlook.program_vba/browse_frm/thread/f768d385c8dd4a27/1df02bd5c153c6bd%231df02bd5c153c6bd
Outlook_Item | Holds cached Outlook(R) items. "For the Exchange message entrys, entry id includes the full distinguished name of the mailbox, which is not limited in length AFAIK. Since MAPI starts barking when a property size goes above about 4k (you need to open the property as IStream, not with IMAPIProp::GetProps(...), etc), it would be relatively safe to alllocate 8192 chars for the entry ids - if your code breaks, so would Outlook itself." -- Dmitry Streblechenko (MVP) http://www.dimastr.com/, http://groups.google.com/group/microsoft.public.outlook.program_vba/browse_frm/thread/f768d385c8dd4a27/1df02bd5c153c6bd%231df02bd5c153c6bd
Outlook_Store | Holds Outlook(R) StoreID values to save space and aid in indexing. Each store_id must be unique. This table does not support updates, only inserts and deletes. Once a record exists it is read-only. "For the Exchange message stores, entry id includes the full distinguished name of the mailbox, which is not limited in length AFAIK. Since MAPI starts barking when a property size goes above about 4k (you need to open the property as IStream, not with IMAPIProp::GetProps(...), etc), it would be relatively safe to alllocate 8192 chars for the entry ids - if your code breaks, so would Outlook itself." -- Dmitry Streblechenko (MVP) http://www.dimastr.com/, http://groups.google.com/group/microsoft.public.outlook.program_vba/browse_frm/thread/f768d385c8dd4a27/1df02bd5c153c6bd%231df02bd5c153c6bd
Portal_User | Cached portal web service data.
Practice_User |
Print_Option |
Priority | Tags: read-only Content:
998 | 1000 | Low
999 | 2000 | Normal
1000 | 3000 | High
Privilege | Tags: read-only Content of first 30 of 614 rows:
0 | 0 | CSP | <Product_Name> | 10 | 0 | 1 | CSP | 0010
1 | 404 | Setup | Setup Menu | 1340 | 0 | 3 | CSP_Menu_Setup | 0010_0020_1340
2 | 1 | Firm | <Firm> | 1350 | 1 | 4 | CSP_Menu_Setup_Firm | 0010_0020_1340_1350
3 | 1 | Validation | -- Validation Lists Deprecated | 1730 | 1 | 4 | CSP_Menu_Setup_Validation | 0010_0020_1340_1730
4 | 449 | Billing | Billing Data | 2130 | 0 | 4 | CSP_Data_Client_Billing | 0010_1750_1820_2130
5 | 1 | Templates | Templates | 1430 | 0 | 4 | CSP_Menu_Setup_Templates | 0010_0020_1340_1430
6 | 1 | Security | Security Groups | 1400 | 1 | 4 | CSP_Menu_Setup_Security | 0010_0020_1340_1400
7 | 1 | RecurBill | Recurring Bill Descriptions | 1510 | 1 | 4 | CSP_Menu_Setup_RecurBill | 0010_0020_1340_1510
8 | 1 | Clients | <Clients> | 1390 | 1 | 4 | CSP_Menu_Setup_Clients | 0010_0020_1340_1390
9 | 1 | Staff | <Staffs> | 1370 | 1 | 4 | CSP_Menu_Setup_Staff | 0010_0020_1340_1370
10 | 469 | Main | Main Data | 3870 | 0 | 4 | CSP_Data_Staff_Main | 0010_1750_3700_3870
11 | 10 | View | View | 3880 | 1 | 5 | CSP_Data_Staff_Main_View | 0010_1750_3700_3870_3880
12 | 10 | Edit | Edit | 3890 | 1 | 5 | CSP_Data_Staff_Main_Edit | 0010_1750_3700_3870_3890
13 | 585 | Staff | <Staff> <Contacts> | 2435 | 0 | 4 | CSP_Data_Contact_Staff | 0010_1750_2325_2435
14 | 13 | View | View | 2445 | 0 | 5 | CSP_Data_Contact_Staff_View | 0010_1750_2325_2435_2445
15 | 13 | Edit | Edit | 2495 | 0 | 5 | CSP_Data_Contact_Staff_Edit | 0010_1750_2325_2435_2495
16 | 469 | Rates | <Staff> Rates Data | 4210 | 0 | 4 | CSP_Data_Staff_Rates | 0010_1750_3700_4210
17 | 16 | View | View | 4220 | 1 | 5 | CSP_Data_Staff_Rates_View | 0010_1750_3700_4210_4220
18 | 16 | Edit | Edit | 4230 | 1 | 5 | CSP_Data_Staff_Rates_Edit | 0010_1750_3700_4210_4230
19 | 469 | Security | Security Data | 4270 | 0 | 4 | CSP_Data_Staff_Security | 0010_1750_3700_4270
20 | 19 | View | View | 4280 | 1 | 5 | CSP_Data_Staff_Security_View | 0010_1750_3700_4270_4280
21 | 19 | Edit | Edit | 4290 | 1 | 5 | CSP_Data_Staff_Security_Edit | 0010_1750_3700_4270_4290
22 | 469 | Memo | Notes | 4360 | 0 | 4 | CSP_Data_Staff_Memo | 0010_1750_3700_4360
23 | 22 | View | View | 4370 | 1 | 5 | CSP_Data_Staff_Memo_View | 0010_1750_3700_4360_4370
24 | 22 | Edit | Edit | 4380 | 1 | 5 | CSP_Data_Staff_Memo_Edit | 0010_1750_3700_4360_4380
25 | 26 | MOSS | For <Staffs> in Same <Office> | 3740 | 1 | 6 | CSP_Data_Staff_View_Others_MOSS | 0010_1750_3700_3710_3730_3740
26 | 340 | Others | For Other <Staffs> | 3730 | 0 | 5 | CSP_Data_Staff_View_Others | 0010_1750_3700_3710_3730
27 | 345 | Others | For Other <Staffs> | 3810 | 0 | 5 | CSP_Data_Staff_Edit_Others | 0010_1750_3700_3790_3810
28 | 343 | MOSS | For <Staffs> in Same <Office> | 3770 | 1 | 5 | CSP_Data_Staff_Add_MOSS | 0010_1750_3700_3760_3770
29 | 344 | MOSS | For <Staffs> in Same <Office> | 3850 | 1 | 5 | CSP_Data_Staff_Delete_MOSS | 0010_1750_3700_3840_3850
Privilege_Dependency | Lists dependencies of Privileges in addition to the normal parent-child relationship. Tags: read-only Content of first 30 of 317 rows:
1 | 305 | 306
2 | 307 | 308
3 | 196 | 444
4 | 309 | 310
5 | 469 | 9
6 | 87 | 90
7 | 87 | 412
9 | 94 | 164
10 | 87 | 164
11 | 409 | 258
13 | 313 | 314
16 | 315 | 316
17 | 95 | 96
18 | 318 | 97
19 | 318 | 98
20 | 319 | 320
21 | 321 | 322
22 | 325 | 326
25 | 328 | 329
27 | 198 | 199
28 | 102 | 103
29 | 55 | 56
30 | 55 | 57
31 | 55 | 58
32 | 341 | 25
33 | 25 | 31
34 | 25 | 28
35 | 31 | 33
36 | 28 | 33
37 | 341 | 346
Project |
Project_Extension |
Project_Template |
Project_Template_Assignment |
Project_Template_Definition |
Project_Template_Definition_Extension |
Project_Template_Definition_Imported |
Project_Template_Entity |
Project_Template_Extension |
Recorded_Event |
Recorded_Event_Notification |
Recurrence_Expiration_Method | The recurrence expiration methods. Tags: read-only Content:
998 | 1000 | No end date
999 | 2000 | End after count
1000 | 3000 | End by date
Recurrence_Generation_Method | The recurrence generation methods. Tags: read-only Content:
997 | 4000 | Generate all
998 | 1000 | When the current <ScheduleItem> is complete
999 | 2000 | Specified days before next date
1000 | 3000 | When I manually create it
Recurrence_Method | The recurrence methods. Tags: read-only Content:
998 | 1000 | None
999 | 2000 | Use Specific Rule
1000 | 3000 | Use <Project> Template
Recurring_Bill |
Referral_Source |
Report_Based_Portlet | Information about report-based custom portlets.
Report_Category | Tags: read-only Content:
1 | Lists | 1
2 | Production | 2
3 | Collection | 4
4 | Billing | 3
5 | Reconciliation | 5
6 | <Project> Management | 6
9 | <Client> Management | 7
10 | Address Labels | 1
11 | File Folder Labels | 2
12 | Letters | 3
13 | <Staff> Management | 8
Report_Definition |
Report_Definition_Privilege_Dependency |
Report_Definition_Product | Links standard report definitions to a product. Tags: read-only Content of first 30 of 53 rows:
PRCM | 925B4133-9BD6-4780-BF28-623B55D668CD
PRCM | 80573483-ABA0-475B-8BD6-F2EAE1AE0C5B
PRCM | 74ACBFBD-8813-48E9-A19E-FEF1EF881827
PRCS | 47003526-FF42-4F86-A38C-00099AE2ADF9
PRCS | E9DBF8C0-2FF8-49AE-82CD-05794376218B
PRCS | 6672DFEB-32D5-4543-9D94-0704C3C30D31
PRCS | 603D0651-6A90-41F9-9E1D-1550BC71FD71
PRCS | CE717878-243E-4A1E-90F9-1C9BF08AE067
PRCS | 4404FEAA-FB8D-46BE-AC40-225DA51F8F0E
PRCS | C5367657-D997-4893-A7AF-26EA902006B5
PRCS | DB8065B1-A562-4E7D-9B9A-2E6C4C97BB25
PRCS | D2D1052E-BC46-47DF-98C0-319F824E39EB
PRCS | D2839D86-2CAD-44AA-BED1-37AD2EDEBB6D
PRCS | EB7899CA-32CC-448E-B536-37D771DDF40F
PRCS | 522386F5-18B2-40C4-A616-3B70F595EC52
PRCS | 344B13F3-EFD4-4095-A5A8-3F8E4548723B
PRCS | EB081650-23CE-4E64-9F41-43C096DEE592
PRCS | A42705C3-C9ED-4EF5-9403-4B71E6646BA9
PRCS | 7552442B-E566-4C4F-B2FD-6313B4CE471E
PRCS | 4983C7F8-AC59-458E-826F-6E3A4584D647
PRCS | 6991CF01-A7DB-4BCB-BF91-75ABF773A75B
PRCS | D185A6E7-5670-4478-8567-79D42F181511
PRCS | 98FA797E-FAEE-4D01-9627-7E81645E6582
PRCS | 9E8FB2D9-1559-4D5B-B33B-86AE6874CC9A
PRCS | 29CDE26C-E93F-489C-B766-97DA2822C42D
PRCS | 56356A89-F806-4434-B6F3-B8879DA2C0B8
PRCS | 935C4965-B953-4446-89F6-BF78EA298847
PRCS | 86AD4F28-4020-457C-A117-C080C032A6D5
PRCS | 38FFCCF1-E86A-4DD2-AA69-C7BE87B88DE1
PRCS | 1F831DAA-BDF0-4739-94EC-D55057EB8956
Report_Definition_Security_Group |
Report_Definition_Update_List |
Report_Image |
Report_Profile |
Report_Profile_Report_Definition |
Restricted_Clearance_Staff | List of staff that have clearance to the database when it is in restricted access.
Schedule_Entry | Represents all or some of a scheduled assignment. Each block can be scheduled by day or for a particular time. There is nothing unique about a [Schedule_Entry] and it is up to the user interface to reduce the number of overlaps and adjacent entries, but it is possible for such entries to be created due to concurrency.
Schedule_Item | Each item that can be scheduled has a row in this table.
Schedule_Item_Assignment |
Schedule_Item_Assignment_List_Cache | Cache of the staff assignment lists. Assignments are primarily stored in [Schedule_Item_Assignment] and are affected by the content of [Schedule_Item].[staff_assignment_method_KEY], [Staff].[description], [Filter].[description] and [Schedule_Item_Pool] and [Schedule_Item_Assignment]. This cache is maintained by triggers and Schedule_Item_Assignment_List_Cache_Calculation_View.
Schedule_Item_Budget_Remaining_Entry | This table stores the user adjustments to the remaining hours value for Projects/Tasks
Schedule_Item_Date_Index | This table is an index used for fast queries looking up the [Schedule_Item] rows that intersect with a date range.
Schedule_Item_Generation_Date | This table holds the next generation date for a given schedule item series.
Schedule_Item_Last_In_Series | Table that caches the last schedule item key for each series
Schedule_Item_Pending_Reminder | Reminders that have not yet been recorded, indexed by [reminder_date] so that lookups are fast. When a reminder is recorded this record is deleted.
Schedule_Item_Reminder_Recorded_Event | Keeps track of what [Recorded_Event] is the reminder for a [Schedule_Item].
Schedule_Item_Series | Schedule Item Series
Security_Group |
Service_Charge |
Sheet_Entry |
Sheet_Entry_Open_Value_Cache |
Staff |
Staff_Area_Rating |
Staff_Benefit |
Staff_Benefit_Entry |
Staff_Billing_Rate |
Staff_Grouping_Type | Tags: read-only Content:
994 | 1000 | <Client>'s <Partner> | Client | partner__staff_KEY
995 | 2000 | <Client>'s <Manager> | Client | manager__staff_KEY
996 | 3000 | <Client>'s <Associate> | Client | associate__staff_KEY
997 | 4000 | <Engagement>'s Biller | Engagement | biller__staff_KEY
998 | 5000 | <Engagement>'s Reviewer | Engagement | reviewer__staff_KEY
999 | 6000 | <Engagement>'s <Manager> | Engagement | manager__staff_KEY
1000 | 7000 | Specified <Staff> |  |
Staff_Level |
Staff_Locator |
Staff_Rate_Table |
Staff_Report_Definition |
Staff_Security_Group |
Staff_Shortcut | This table is a data store for the Solutions portlets. It contains information about user-configurable solutions (which are paths to files, folders, or web pages).
Staff_Shortcut_Group | This table is a data store for the Solutions portlets. It contains information about user-configurable groups of solutions (which are paths to files, folders, or web pages).
Staff_Skill_Area |
Staff_Skill_Area_Rating |
Staff_Skill_Rating |
Staff_Target_Range | The Staff_Target_Range table holds ranges of dates where different Staff targets (budgets) are effective. This table defines the date range and the target hours for each day of the week within this range. These ranges are specific to a staff and are coupled to a firm year. Unlike tables defined in the past which would only store either [ending_date] or [upper_date_exclusive] this table redundantly stores both of these as well as [lower_date_inclusive] for the performance benefits and defines [upper_date_exclusive] as the value the other two are validated against.
Standard_Text |
Status_Event |
Status_Event_Type |
Table_Information | Assigns an integer key to a table in the database. Tags: read-only Content of first 30 of 208 rows:
3 | Billing_Rate_Type | BRT
5 | dtproperties | dtproperties
6 | Privilege | P
7 | Privilege_Dependency | PD
8 | Security_Group | SG
13 | Staff | S
14 | Staff_Billing_Rate | SBR
16 | Staff_Level | SL
17 | Staff_Rate_Table | SRT
18 | Staff_Security_Group | SSG
19 | Table_Information | TI
21 | Department | D
23 | Firm | Firm
24 | Office | O
25 | Practice_User | PU
32 | Staff_Status | SS
36 | User_Session | US
38 | Activity | A
39 | Activity_Class | AC
40 | Activity_Status | AST
41 | Activity_Category | AG
46 | Filter | F
48 | Filter_Line | FL
49 | Filter_Line_Type | FLT
53 | Filter_Select | FS
54 | Filter_Type | FT
56 | Tax_Area | TA
57 | Tax_Area_Taxing_Authority | TATA
58 | Taxing_Authority | TAU
59 | Taxing_Authority_Type | TAT
Tag | A tag is a non-hierarchical keyword or term assigned to a piece of information. This kind of metadata helps describe an item and allows it to be found again by browsing or searching. Tags are generally chosen informally and personally by the item's creator or by its viewer.
Tagged_Item | Associates Tags to an item.
Target_Date_Method | Tags: read-only Content:
999 | 1000 | Before due date
1000 | 2000 | After received date
Task |
Task_Template |
Task_Template_Assignment |
Tax_Area | A Tax Area is a collection of Taxing Authorites. This holds the list of Tax Areas the Firm has setup.
Tax_Area_Taxing_Authority | Maps the relationship that Tax Areas are made up of a collection of Tax Authorities.
Taxing_Authority | Taxing authorities are governmental bodies empowered to collect tax on goods, services or both. If both goods and services are taxed at different rates then two taxing authorities would be created.
Term | Information about customizable terms.
Time_Zone | Just enough information about Windows Time Zones to be able to record the time zone a user was in when they last edited a datetime field.
Timer |
Tracking_Description |
Update_Data_Change_Log |
Update_Data_Version_History |
User_Preference |
User_Preference_Custom_Field_Column | Contains records for the User Preference settings for Custom Fields
User_Session |
User_Session_Pattern |
Valid_Date | The Valid_Date table holds all of the dates between 1900-01-01 and 2079-01-01 inclusive. Having these dates makes it convenient to join against for generating ranges. Tags: read-only Content of first 30 of 65380 rows:
1900-01-01T00:00:00 | 1
1900-01-02T00:00:00 | 2
1900-01-03T00:00:00 | 3
1900-01-04T00:00:00 | 4
1900-01-05T00:00:00 | 5
1900-01-06T00:00:00 | 6
1900-01-07T00:00:00 | 7
1900-01-08T00:00:00 | 8
1900-01-09T00:00:00 | 9
1900-01-10T00:00:00 | 10
1900-01-11T00:00:00 | 11
1900-01-12T00:00:00 | 12
1900-01-13T00:00:00 | 13
1900-01-14T00:00:00 | 14
1900-01-15T00:00:00 | 15
1900-01-16T00:00:00 | 16
1900-01-17T00:00:00 | 17
1900-01-18T00:00:00 | 18
1900-01-19T00:00:00 | 19
1900-01-20T00:00:00 | 20
1900-01-21T00:00:00 | 21
1900-01-22T00:00:00 | 22
1900-01-23T00:00:00 | 23
1900-01-24T00:00:00 | 24
1900-01-25T00:00:00 | 25
1900-01-26T00:00:00 | 26
1900-01-27T00:00:00 | 27
1900-01-28T00:00:00 | 28
1900-01-29T00:00:00 | 29
1900-01-30T00:00:00 | 30
Web_Page_Portlet |
Won_Reason |