| SchemaSpy Analysis of slot9.WORLD.TSTA | Generated by SchemaSpy |
| Generated by SchemaSpy on Mon Sep 20 21:05 MDT 2021 | |
| Database Type: Oracle - Oracle Database 11g Release 11.2.0.3.0 - Production |
|
XML Representation Insertion Order Deletion Order (for database loading/purging scripts) |
| Table / View | Children | Parents | Columns | Comments |
|---|---|---|---|---|
| ACCESS_LOGS | 4 | 13 | Define list of URLs to monitor for access to log | |
| ACCESS_MODULES | 2 | 7 | Define list of modules (and associated request parameter) to monitor access | |
| ACCESS_URLS | 4 | 9 | Define list of URLs to monitor and what type of access to log | |
| ACTIVITIES | 1 | 2 | 9 | This table stores the activity information in the OFFICER DAILY LOG |
| ACTIVITY_CATEGORY_CODES | 1 | 9 | This table defines the categories for OFFICER DAILY LOG activities | |
| ACTIVITY_CODE_AGENCIES | 2 | 6 | This table maps valid activity codes to agencies | |
| ACTIVITY_CODES | 4 | 9 | This table defines the activity codes for the OFFICER DAILY LOG | |
| ACTIVITY_HEADERS | 1 | 6 | 19 | This table stores an header activity information in the OFFICER DAILY LOG |
| ACTIVITY_RESULT_CODES | 3 | 1 | 6 | This table is not currently used |
| ACTIVITY_RESULTS | 2 | 9 | This table is not currently used | |
| ACTIVITY_TEMP_CODE_AGENCIES | 2 | 6 | This table defines the valid activity templates for an agency | |
| ACTIVITY_TEMPLATE_ACTIVITIES | 2 | 2 | 8 | This table stores activity templates created by Admins for the OFFICER DAILY LOG |
| ACTIVITY_TEMPLATE_CODES | 2 | 1 | 9 | This table stores template codes for OFFICER DAILY LOG activities |
| ACTIVITY_TEMPLATE_RESULTS | 3 | 9 | This table is not currently used | |
| ACTIVITY_TIME_CATEGORY_CODES | 2 | 8 | This table defines the valid time categories for activities within the OFFICER DAILY LOG | |
| ADDRESS_ASSOC_CNT_VW | 3 | |||
| ADDRESS_ATTACHMENTS | 2 | 10 | This table stores attachments added to a MASTER ADDRESS in the application | |
| ADDRESS_COLLAPSE_LOG | 59 | This table stores a log entry for multiple MASTER ADDRESS records being collapsed into a single record | ||
| ADDRESS_COMMON_NAMES | 2 | 10 | This table stores common names for a MASTER ADDRESS. (e.g. McDonalds, Fed Ex, DIA) | |
| ADDRESS_COMMON_NAMES_VW | 29 | |||
| ADDRESS_IMAGES | 2 | 9 | This table stores associations to images added to a MASTER ADDRESS in the application | |
| ADDRESS_TYPE_CODES | 3 | 4 | This table defines the valid types of addresses | |
| ADDRESSES | 28 | 27 | 58 | This table stores MASTER ADDRESSES entered in the application or through CAD imports |
| ADDRESSES_NOT_DUPLICATES | 2 | 8 | This table stores addresses that are similar but have been flagged as not duplicates so they don't accidentally get collapsed into one | |
| ADDRESSES_SEARCH_VW | 43 | |||
| AFFILIATE_CODES | 3 | 1 | 9 | This table allows for agency affiliates to be defined. This table is not currently used in the application |
| AGENCY_ADMINISTRATORS | 2 | 7 | This table stores the administrator ids for an agency | |
| AGENCY_API_KEYS | 3 | 9 | Associates API keys with agencies for external systems (such as google maps). | |
| AGENCY_ATTACHMENT_INTERFACES | 2 | 2 | 12 | This table specifies if an agency uses an external system for managing attachments by assigning an attachment interface |
| AGENCY_CASE_SUPERVISORS | 2 | 6 | This table stores the user assigned to be case supervisors for an agency | |
| AGENCY_CODES | 174 | 18 | 61 | This table stores the agency information |
| AGENCY_CODES_EXT_AUTH | 5 | 14 | This table configures agencies for external authentication | |
| AGENCY_CODES_TEMP | 2 | Global Temp Table | ||
| AGENCY_CREDENTIALS | 1 | 8 | Stores Encrpyted Credentials for Various Services at an Agency Level | |
| AGENCY_EXT_SERVER_RELATIONS | 1 | 8 | This table stores the relationship between an agency an external server | |
| AGENCY_FEATURES | 3 | 9 | This table stores the features within the application being used by an agency | |
| AGENCY_NIBR_CITIES | 3 | 8 | This table defines the NIBR city codes for an agency to be used in the application | |
| AGENCY_NUM_GENERATIONS | 5 | 15 | This table defines number generations for INCIDENTS, ARRESTS, etc. in the application for an agency | |
| AGENCY_OFFENSES | 3 | 10 | This table defines local offenses for the agency that can be mapped to state offenses or used with no state reporting | |
| AGENCY_PARENT_VW | 3 | |||
| AGENCY_ROLE_JS_USERS | 2 | 9 | This table defines the roles allowed to run Jasper Server reports associated with RMS | |
| AGENCY_ROUTING | 2 | 9 | This table defines source and target agency combinations for routing within the application for an agency | |
| AGENCY_SEARCH_INT_COUNTS | 2 | 3 | 10 | This table tracks the max number of times an agency may query an external search interface |
| AGENCY_SEARCH_INTERFACES | 2 | 8 | This table defines which search interfaces (JailTracker, InterDex, LEAP, etc.) are enabled for an agency | |
| AGENCY_SEARCH_OPTIONS | 3 | 8 | Stores The search options at the agency level unless overridden by the USER_SEARCH_OPTIONS | |
| AGENCY_SUB_MAINT | 1 | 12 | This table defines different configuration options and switches for the Online RMS for a given agency | |
| AGENCY_SUBSCRIPTIONS_VW | 7 | |||
| AGENCY_USER_TYPE_COUNTS | 3 | 10 | This table is used to store user subscription types along with an allotted count of users | |
| AGENCY_WORKGROUPS | 3 | 8 | This table defines workgroups for an agency that can be assigned to a case in the application | |
| AGNCY_SRCH_INT_COUNT_HISTORY | 2 | 10 | This table tracks the history of search interface credits added to an agency | |
| ALL_ADDRESS_COMMON_NAMES_VW | 29 | |||
| APPLICATION_COLUMN_AUDITS | 1 | 2 | Legacy table. This table is not currently used | |
| APPLICATION_SEQUENCES | 1 | 12 | This is an Interact Administration table | |
| APPLICATION_TABLES | 6 | 2 | 17 | This is an Interact Administration table |
| ARREST_ADDRESS_SEARCH_VW | 51 | |||
| ARREST_ATTACHMENTS | 2 | 10 | This table stores attachments added to an ARREST in the application | |
| ARREST_BUSINESSES | 4 | 9 | This table stores an association with a MASTER BUSINESSES, referred to as organizations in the application, added to an ARREST. | |
| ARREST_CASES | 2 | 7 | This table stores an association between a field arrest and a Case. | |
| ARREST_CFS_SEARCH_VW | 51 | |||
| ARREST_CHARGE_CODE_MODS | 3 | 9 | This table is used to join Arrest Charge Codes to a Module | |
| ARREST_CHARGE_CODES | 5 | 1 | 9 | This table defines the valid charge codes for ARRESTS |
| ARREST_CHARGE_FLAGS | 3 | 9 | This table is not currently used | |
| ARREST_CHARGE_NARRATIVES | 4 | 10 | This table stores charging language narratives for charges on field arrests. | |
| ARREST_CHARGE_VW | 6 | |||
| ARREST_CHARGES | 2 | 6 | 23 | This table stores the charge information added to an ARREST in the application |
| ARREST_DELETE | 1 | 10 | This table stores a copy of the ARREST information for an ARREST that was deleted in the application | |
| ARREST_DISPATCHES | 2 | 6 | This table stores an association between a dispatch record (referred to as Calls For Service in the application) and an ARREST as created in the application. | |
| ARREST_DISPOSITION_SEARCH_VW | 37 | |||
| ARREST_IMAGES | 2 | 9 | This table stores associations to images added to an ARREST in the application | |
| ARREST_JAIL_SEARCH_VW | 21 | |||
| ARREST_LIVESCAN_VW | 31 | |||
| ARREST_LOG | 3 | 9 | This table stores the log entries for changes to property, disposition, etc. on an ARREST as done within the application | |
| ARREST_NARRATIVE_SEARCH_VW | 36 | |||
| ARREST_NARRATIVES | 3 | 9 | The text of the ARREST narrative itself is stored in EJS_NOTES. This table stores the association between the ARREST and the note_id from EJS_NOTES | |
| ARREST_OFFICERS | 3 | 8 | This table stores the association to an officer added to an ARREST in the application | |
| ARREST_ORG_SEARCH_VW | 46 | |||
| ARREST_PEOPLE | 1 | 5 | 10 | This table stores the association to MASTER PEOPLE added to an ARREST in the application |
| ARREST_PERSON_ROLES | 2 | 6 | This table stores roles assigned to the a person added to an ARREST in the application | |
| ARREST_PERSON_SEARCH_VW | 46 | |||
| ARREST_PROPERTIES | 1 | 9 | 20 | This table stores the association to PROPERTIES added to an ARREST in the application |
| ARREST_PROPERTIES_AUDIT | 8 | 20 | This table stores the changes made to ARREST property in the application | |
| ARREST_PROPERTY_SEARCH_VW | 48 | |||
| ARREST_QUESTIONS | 3 | 8 | This table stores the answers to the ARREST questions entered in the application | |
| ARREST_REF_NUMBERS | 3 | 9 | This table stores reference numbers and types added to an ARREST in the application | |
| ARREST_REQQUES_VW | 3 | |||
| ARREST_SEARCH_VW | 34 | |||
| ARREST_STATUS_CODES | 1 | 4 | This table defines the valid statuses that can be assigned to an ARREST in the application | |
| ARREST_TYPE_CODES | 1 | 6 | This table is not currently used | |
| ARREST_TYPES | 2 | 8 | This table is not currently used | |
| ARREST_VEHICLE_SEARCH_VW | 55 | |||
| ARREST_WARRANTS | 9 | 21 | This table stores the association with a warrant that is added to an ARREST in the application | |
| ARRESTEE_DISPOSITION_CODES | 1 | 2 | 5 | This table defines the valid disposition codes that can be assigned to an arrestee in the application |
| ARRESTEE_WEAPONS | 2 | 9 | This table stores an association between a weapon and an arrestee | |
| ARRESTEES | 9 | 18 | This table stores the MASTER PERSON selected as the arrestee on an INCIDENT report in the application | |
| ARRESTS | 24 | 32 | 72 | This table stores the ARREST header information as entered in the application |
| ASSIGNMENT_CODE_AGENCIES | 2 | 6 | This table defines the assignment codes that are valid for an agency for use in the OFFICER DAILY LOG in the application | |
| ASSIGNMENT_CODES | 4 | 2 | 12 | This table defines the valid assignment codes for the OFFICER DAILY LOG in the application |
| ASSIGNMENT_EQUIPMENT | 2 | 10 | This table stores the equipment used in an OFFICER DAILY LOG assignment in the application | |
| ASSIGNMENT_HOME_VW | 11 | |||
| ASSIGNMENT_LOGS | 2 | 4 | 15 | This table stores log entries for assignments in the OFFICER DAILY LOG in the application |
| ASSIGNMENT_ORGS | 1 | 4 | 15 | This table stores the organization information for an assignment in the OFFICER DAILY LOG in the application |
| ASSIGNMENT_SHIFT_CODE_AGENCIES | 2 | 6 | This table defines the shift codes that are valid for an agency to be used in an assignment in the OFFICER DAILY LOG in the application | |
| ASSIGNMENT_SHIFT_CODES | 4 | 10 | This table defines the valid shift codes to be used in an assignment in the OFFICER DAILY LOG in the application | |
| ASSIGNMENT_SUB_BEATS | 1 | 6 | This table stores the sub beat for the assignment in the OFFICER DAILY LOG in the application | |
| ASSIGNMENT_TEMPLATES | 1 | 1 | 9 | This table defines templates for assignments that can be used in the OFFICER DAILY LOG in the application |
| ASSIGNMENT_VEHICLES | 1 | 9 | 28 | This table stores vehicles used in an assignment in the OFFICER DAILY LOG in the application |
| ASSIGNMENTS | 6 | 8 | 20 | This table stores assignment information added to the OFFICER DAILY LOG in the application |
| ASSOCIATE_DETAILS_VW | 12 | |||
| ATC_AGENCIES | 2 | 6 | This tables defines the time categories for a given agency for the scheduling module | |
| ATTACHMENT_INTERFACES | 1 | 11 | This table define the external interfaces where attachements can be stored outside of the RMS database | |
| ATTACHMENTS | 35 | 3 | 14 | This table stores attachments added to INCIDENTS, CITATIONS, ARRESTS, etc. in the application |
| ATTACHMENTS_VW | 8 | |||
| AUDIT_ACTION_CODES | 3 | 2 | 5 | Legacy table. This table is not currently used |
| AUDIT_RECORDS | 7 | This table stores all auditing information for table inserts, updates and deletes. | ||
| AUDIT_REPORTS | 1 | 7 | Stores configuration information for reports auditing | |
| AUDIT_SEARCHES | 3 | 8 | Stores configuration information for search auditing | |
| BI_AGENCY_INFORMATION_VW | 27 | |||
| BI_CALLS_FOR_SERVICE_VW | 75 | |||
| BI_CITATIONS_VW | 58 | |||
| BI_INCIDENTS_VW | 50 | |||
| BI_OFFENSE_VW | 29 | |||
| BI_RECORD_COUNTS_VW | 6 | |||
| BI_USER_INFORMATION_VW | 19 | |||
| BI_USER_STORAGE_VW | 10 | |||
| BLOOD_TYPE_CODES | 1 | 5 | THis table defines the valid blood types for MASTER PEOPLE | |
| BOLO_DESCRIPTOR_CODES | 4 | 2 | 10 | This table defines the valid descriptors for Be On The Lookout people and vehicles associated with an INCIDENT |
| BOLO_PEOPLE | 3 | 13 | This table stores person information if a MASTER PERSON isn't known for an INCIDENT | |
| BOLO_VEHICLES | 3 | 13 | This table stores vehicle information if a MASTER VEHICLE isn't known for an INCIDENT | |
| BOND_TYPE_CODES | 5 | 6 | This table defines the valid bond types for charges on an ARREST | |
| BUS_ADDR_ALARM_VW | 21 | |||
| BUS_ADDR_BUS_REL_VW | 21 | |||
| BUS_ADDR_EMP_VW | 26 | |||
| BUS_ADDR_PEOP_VW | 27 | |||
| BUS_ADDR_PERMIT_VW | 20 | |||
| BUS_PER_VEHICLE_VW | 5 | |||
| BUSINESS_ADDR_PHONES | 3 | 8 | This table stores the phone numbers of the MASTER BUSINESS | |
| BUSINESS_ADDRESS_VW | 15 | |||
| BUSINESS_ADDRESSES | 2 | 3 | 13 | This table stores the association to MASTER ADDRESSES added to the MASTER BUSINESS in the application |
| BUSINESS_ALARMS | 3 | 21 | This table stores alarms associated with the MASTER BUSINESS | |
| BUSINESS_ATTACHMENTS | 2 | 10 | This table stores attachments added to the MASTER BUSINESS in the application | |
| BUSINESS_COLLAPSE_LOG | 13 | This table stores a log entry for multiple MASTER BUSINESS records being collapsed into a single record | ||
| BUSINESS_IMAGES | 2 | 10 | This table stores associations to images added to the MASTER BUSINESS in the application | |
| BUSINESS_PROPERTIES | 4 | 10 | This table stores properties associated with the MASTER BUSINESS | |
| BUSINESS_PROPERTY_VW | 33 | |||
| BUSINESS_RELATIONS | 4 | 12 | This table stores parent-child relationships between MASTER BUSINESSES | |
| BUSINESS_RMS_SEARCH_VW | 100 | |||
| BUSINESS_VEHICLES | 4 | 10 | This table stores the association to a MASTER VEHICLES added to the MASTER BUSINESS in the application | |
| BUSINESS_VEHICLES_VW | 23 | |||
| BUSINESSES | 31 | 3 | 17 | This table stores MASTER BUSINESSES (referred to as Organizations in the application) entered in the application |
| BUSINESSES_NOT_DUPLICATES | 2 | 8 | This table is not currently used | |
| BUSINESSES_SEARCH_VW | 26 | |||
| CALENDAR_ASSIGNMENT_SERIES | 1 | 3 | 8 | This table store a grouping of assignments added to a calendar in the scheduling module in the application |
| CALENDAR_ASSIGNMENTS | 4 | 19 | This table store the assignments added to a calendar in the scheduling module in the application | |
| CALENDAR_ASSIGNMENTS_AUDIT | 19 | This table stores assignment audit information for a calendar | ||
| CALENDAR_SHIFT_USERS | 2 | 8 | This table stores the users assigned to a shift on a calendar in the scheduling module in the application | |
| CALENDAR_SHIFTS | 2 | 1 | 17 | This table stores the shifts assigned to a calendar in the scheduling module in the application |
| CALENDAR_TEMPLATE_DAYS | 1 | 12 | This table defines the days within a template to be used in creating a calendar in the scheduling module in the application | |
| CALENDAR_TEMPLATE_WEEKS | 1 | 1 | 8 | This table defines the weeks within a template to be used in creating a calendar in the scheduling module in the application |
| CALENDAR_TEMPLATES | 2 | 9 | This table defines templates to be used in creating a calendar in the scheduling module in the application | |
| CALENDARS | 2 | 10 | This table stores the calendars created in the Scheduling module in the application | |
| CALENDARS_CALENDAR_USER_TYPES | 3 | 7 | This table defines the user types that can be used in a calendar in the application | |
| CALENDER_LOG | 10 | This table stores the log information for actions taken on calendar in the scheduling module in the application | ||
| CALL_DISPOSITION_CODES | 2 | 1 | 4 | This table defines the valid disposition codes for CALLS FOR SERVICE |
| CALL_RECEIVED_CODES | 1 | 8 | This table defines the valid received codes for CALLS FOR SERVICE | |
| CALL_TYPE_CODES | 4 | 9 | This table defines the valid types of CALLS FOR SERVICE (e.g. Burglary, Battery, Car Jacking) | |
| CASE_ACTIVITY_ARRESTS | 2 | 7 | This table tracks the case activity field arrest associations | |
| CASE_ACTIVITY_ASSIGNMENTS | 2 | 7 | This table tracks the officers assigned to a case activity | |
| CASE_ACTIVITY_FLDINTS | 2 | 7 | This table tracks the case activity field interview associations | |
| CASE_ACTIVITY_NAMES | 3 | 9 | This table tracks the case activity field interview associations | |
| CASE_ACTIVITY_NARRATIVES | 2 | 9 | This table tracks the case activity narratives associations | |
| CASE_ACTIVITY_VEHICLES | 2 | 7 | This table tracks the case activity field interview associations | |
| CASE_ACTIVITY_WARRANTS | 2 | 7 | This table tracks the case activity warrant associations | |
| CASE_ASSIGNMENT_HISTORIES | 6 | 18 | This table stores the officers assigned to a case in the application | |
| CASE_ATTACHMENTS | 2 | 10 | This table stores attachments added to a Case in the application | |
| CASE_FIELD_INTS | 2 | 7 | Associates field contacts to cases | |
| CASE_GROUP_OFFICERS | 2 | 7 | This table stores Case Group Officers. | |
| CASE_IMAGES | 2 | 9 | This table stores associations to images added to a Case in the application | |
| CASE_LOG | 6 | 13 | This table stores a log of the notifications and comments on a case. Also logs case hours changes. | |
| CASE_OFFICER_GROUPS | 1 | 1 | 7 | This table stores Case Officer Groups. Allows the user to quickly select associate multiple officers to a case activity |
| CASE_ROLE_CODES | 6 | This table is not currently used | ||
| CASE_SEARCH_ADDRESS_VW | 25 | |||
| CASE_SEARCH_FIELD_CONTACT_VW | 15 | |||
| CASE_SEARCH_INCIDENTS_VW | 15 | |||
| CASE_SEARCH_NAMES_VW | 25 | |||
| CASE_SEARCH_OFFENSES_VW | 17 | |||
| CASE_SEARCH_OFFICERS_VW | 16 | |||
| CASE_TYPE_CODES | 2 | 3 | 10 | This table is not currently used |
| CERTIFICATION_CERT_PREREQ | 2 | 8 | This table stores Certification Requirments | |
| CERTIFICATION_COURSE_PREREQ | 2 | 8 | This table stores Certification Requirments | |
| CERTIFICATION_EMPLOYEE | 2 | 9 | This table stores Employees who have completed certifications | |
| CERTIFICATION_RANK | 2 | 8 | This table stores Certifications | |
| CERTIFICATIONS | 5 | 1 | 10 | This table stores Certifications |
| CHAIN_OF_CUSTODIES | 5 | 23 | This table stores the chain of custody for a piece of evidence | |
| CHARGE_CATEGORY_CODES | 4 | 6 | This table defines the valid categories for charges | |
| CHARGE_CLASS_CODES | 4 | 1 | 9 | This table defines the valid classes for charges |
| CHARGE_CODE_MODULES | 3 | 9 | This table is used to join Charge Codes to a Module | |
| CHARGE_CODE_TOKENS | 1 | 3 | 10 | This table stores associations between charge codes and tokens. Tokens (ejs codes) are additional fields added to charges on criminal complaints. |
| CHARGE_CODES | 10 | 4 | 44 | This table defines the valid charge codes |
| CHARGE_LANGUAGE_TEMPLATES | 1 | 1 | 7 | This table stores narrative templates used for charging language templates |
| CHARGE_OFFENSE_VW | 25 | |||
| CHARGE_TEMPLATES | 2 | 7 | This table stores associations between CHARGE_CODES and NARRATIVE_TEMPLATES | |
| CHART_PERMISSIONS | 1 | 10 | This table defines the permissions for charts viewed on the home page of the application | |
| CITATION_ADDRESS_VW | 48 | |||
| CITATION_ADDRESSES | 6 | 13 | This table stores the association to MASTER ADDRESSES added to the citation in the application | |
| CITATION_ATTACHMENTS | 2 | 10 | This table stores attachments added to a CITATION in the application | |
| CITATION_BUSINESS_VW | 31 | |||
| CITATION_BUSINESSES | 4 | 9 | This table stores the association to MASTER BUSINESSES (referred to as organizations in the application) added to the citation | |
| CITATION_DCNS | 1 | 3 | This table is not currently used | |
| CITATION_DELETE | 13 | This table store the citation information when the citation is deleted in the application | ||
| CITATION_EMPLOYEE_VW | 35 | |||
| CITATION_EMPLOYEES | 4 | 10 | This table stores the association to employees added to the citation in the application | |
| CITATION_IMAGES | 2 | 9 | This table stores associations to images added to a Citation in the application | |
| CITATION_METHODS | 2 | 7 | This table stores the violation methods added to a citation in the application | |
| CITATION_OFFICERS | 4 | 13 | This table stores the association to officers added to the citation in the application | |
| CITATION_PEOPLE | 9 | 16 | This table stores the association to MASTER PEOPLE added to the citation in the application | |
| CITATION_PERSON_VW | 38 | |||
| CITATION_RACIAL_INFO | 8 | 15 | This table stores the racial profiling information for a person on a citation | |
| CITATION_RACIAL_PROFILE_VW | 33 | |||
| CITATION_REPORTS | 3 | 11 | This table stores external report identifiers and types (e.g. accident, court case) added to an citation in the application | |
| CITATION_ROAD_CONDITIONS | 2 | 7 | This table is not currently used | |
| CITATION_STATUS_CODES | 5 | This table defines the valid statue codes for a citation | ||
| CITATION_TYPE_CODES | 1 | 1 | 8 | This table defines the valid types for a citation |
| CITATION_VEHICLE_VW | 35 | |||
| CITATION_VEHICLES | 3 | 8 | This table stores the association to a vehicle added to the citation in the application | |
| CITATION_VIOLATIONS | 6 | 14 | This table stores the violations added to the citation in the application | |
| CITATION_VISIBILITIES | 2 | 7 | This table is not currently used | |
| CITATION_VW | 29 | |||
| CITATION_XREFS | 2 | 8 | This table stores external ids for a citation from external applications or interfaces. Data is uploaded through the Citation XML import | |
| CITATION_XREFS_VW | 3 | |||
| CITATIONS | 21 | 15 | 36 | This table stores the main citation information as entered in the application |
| COLLAPSE_LOG_ENTRIES | 1 | 17 | This table stores a log entry for each set of master indices rows that are collapsed into one | |
| COLLAPSE_PROPERTY_LOG_ENTRIES | 9 | This table stores a log entry for property records that are collapsed into one | ||
| COLLAPSE_VEHICLE_DESC_LOG | 1 | 26 | This table stores a log entry for the vehicle description for collapsed vehicles | |
| COLLAPSE_VEHICLE_LOG_ENTRIES | 1 | 16 | This table stores a log entry for vehicle records that are collapsed into one | |
| COLLAPSED_MASTER_NAMES | 1 | 19 | This tables stores master name information for collapsed people. | |
| COMMON_PLACE_NAMES | 3 | 1 | 9 | This table stores a configurable standard list of common place names (e.g. McDonalds, Fed Ex, DIA) |
| COURSE | 6 | 5 | 25 | This table stores Courses |
| COURSE_ATTACHMENTS | 2 | 11 | This table stores attachments added to a Course | |
| COURSE_EMPLOYEE_GROUPS | 2 | 8 | This table stores Course Employee Groups | |
| COURSE_IMAGES | 2 | 10 | This table stores image attachments added to course records | |
| COURSE_INST_EMP_ATTACHMENTS | 2 | 11 | This table stores attachments added to a Course | |
| COURSE_INST_EMP_IMAGES | 2 | 10 | This table stores image attachments added to course records | |
| COURSE_INSTANCE | 2 | 6 | 30 | This table stores Instances of a Course. |
| COURSE_INSTANCE_EMPLOYEE | 2 | 2 | 13 | This table stores Employees Enrolled in a course |
| COURSE_PREREQUISITES | 2 | 8 | This table stores Course Prerequisites | |
| COURT_APPEARANCE_ATCHMNTS | 2 | 10 | This table stores court appearance attachment associations. | |
| COURT_APPEARANCE_IMAGES | 2 | 9 | This table stores court appearance image attachment associations. | |
| COURT_APPEARANCE_OFFS | 2 | 8 | This table stores court appearance officer associations. | |
| COURT_APPEARANCE_SEARCH_VW | 36 | |||
| COURT_APPEARANCES | 4 | 7 | 17 | This table stores court appearance records. |
| COURT_CASE_APP_SEARCH_VW | 46 | |||
| COURT_CASE_APPEARANCES | 2 | 8 | This table stores court case appearance associations. | |
| COURT_CASE_ARRESTS | 2 | 8 | This table stores court case arrests associations. | |
| COURT_CASE_ATTACHMENTS | 2 | 10 | This table stores court case attachment associations. | |
| COURT_CASE_CITATIONS | 2 | 8 | This table stores court case arrests associations. | |
| COURT_CASE_COMPLAINTS | 2 | 8 | This table stores court case criminal complaint associations. | |
| COURT_CASE_DELETE | 12 | This table stores court case delete records. | ||
| COURT_CASE_IMAGES | 2 | 9 | This table stores court case image attachment associations. | |
| COURT_CASE_INCS | 2 | 8 | This table stores court case incident associations. | |
| COURT_CASE_OFFS | 2 | 8 | This table stores court case officer associations. | |
| COURT_CASE_PEOPLE | 2 | 10 | This table stores court case people (defendant) associations. | |
| COURT_CASE_REFS | 3 | 10 | This table stores court case reference numbers. | |
| COURT_CASE_SEARCH_VW | 32 | |||
| COURT_CASES | 10 | 3 | 12 | This table stores court case records. |
| COURT_LOCATION_CODES | 6 | 5 | 27 | This table defines valid court locations to be used as a court or receiving agency or both on a Court Paper (referred to as civil process) in the application |
| COURT_PAPER_ATTACHMENTS | 2 | 10 | This table stores attachments added to the court paper | |
| COURT_PAPER_FEES | 2 | 1 | 15 | This table stores the fees associated with the person being served on a court paper |
| COURT_PAPER_FEES_AUDIT | 2 | 15 | Table stores updates of court paper fee collections. | |
| COURT_PAPER_IMAGES | 2 | 9 | This table stores association to images added to the court paper | |
| COURT_PAPER_LOCATIONS | 3 | 11 | This table stores the court appearance location if added to a court paper in the application | |
| COURT_PAPER_LOGS | 3 | 15 | 38 | This table stores the log entries for actions taken on a court paper in the application |
| COURT_PAPER_OFFICERS | 4 | 12 | Table stores all officers assigned to a court paper. | |
| COURT_PAPER_PARTIES | 7 | 3 | 10 | Table stores all people and organizations associated to a court paper. |
| COURT_PAPER_PARTY_ROLES | 3 | 8 | Table stores all roles for people and organizations associated to a court paper. | |
| COURT_PAPER_PAYMENT_PARTIES | 2 | 7 | This table associates a court paper fee collection to one or many service parties | |
| COURT_PAPER_PAYMENTS | 2 | 3 | 13 | Table stores court paper fee collections. |
| COURT_PAPER_PAYMENTS_AUDIT | 1 | 3 | 12 | Table stores updates of court paper fee collections. |
| COURT_PAPER_REFS | 3 | 9 | This tables stores reference numbers and types added to the court paper in the application | |
| COURT_PAPER_SERVICE_ADDRS | 2 | 10 | Table stores service addresse for people and organizations associated to a court paper. | |
| COURT_PAPER_SERVICE_DETAILS | 3 | 9 | Table stores all service details for people and organizations associated to a court paper. | |
| COURT_PAPER_UNKNWN_DETAILS | 6 | 13 | This table adds court paper unknown party details | |
| COURT_PAPERS | 10 | 11 | 26 | This table stores court papers (referred to as Civil Process) in the application |
| CP_DEL_LOG | 2 | 5 | 17 | This table stores log of deleted court papers |
| CP_DEL_LOG_PARTIES | 3 | 9 | This table stores log of deleted court papers parties | |
| CP_DEL_LOG_REFS | 3 | 9 | This table stores log of deleted court papers reference numbers | |
| CP_DELETE_PARTY | 3 | 8 | Stores information about deleted court paper people / organizations. Tied to a log entry. | |
| CP_DELETE_PAYMENT | 3 | 10 | Stores information about deleted court paper payments. Tied to a log entry. | |
| CP_DELETE_SERVICE_ADDR | 4 | 8 | Stores information about deleted court paper service addresses. Tied to a log entry. | |
| CP_PAYMENT_PARTIES_LOG | 1 | 9 | This table logs adding and removing service parties a fee collection is made for | |
| CPN_LOC_CATEGORIES | 3 | 8 | This table stores one or more categories (like Clery place codes) associated with a standard common place name. | |
| CRIMINAL_COMP_ATTACHMENTS | 2 | 11 | This table stores attachments added to criminal complaint records | |
| CRIMINAL_COMP_CHARGE_TOKENS | 2 | 9 | This table stores token values added to criminal complaint charges | |
| CRIMINAL_COMP_IMAGES | 2 | 10 | This table stores image attachments added to criminal complaint records | |
| CRIMINAL_COMPLAINT_ARRESTS | 2 | 9 | This table stores arrest associations to criminal complaint records. | |
| CRIMINAL_COMPLAINT_CHARGES | 1 | 2 | 12 | This table stores charge associations to criminal complaint records. |
| CRIMINAL_COMPLAINT_DELETE | 15 | This table stores a delete log for criminal complaint records. | ||
| CRIMINAL_COMPLAINT_INCIDENTS | 2 | 9 | This table stores incident associations to criminal complaint records. | |
| CRIMINAL_COMPLAINT_SEARCH_VW | 43 | |||
| CRIMINAL_COMPLAINT_SUBMIT_LOG | 10 | This table stores court appearance records. | ||
| CRIMINAL_COMPLAINTS | 8 | 22 | 36 | This table stores criminal complaint records. |
| CSAU_CODES | 2 | 2 | 5 | This table defines valid CSAU codes that can be assigned to an offense in the application |
| DATASET_HEADER_VW | 13 | |||
| DATASETID_GTT | 1 | This table is used for UCR Reporting | ||
| DAYS_OF_MO_CODES | 2 | This table assigns a record id to each day of the month. The record id is used in the Calendars in the application | ||
| DEGREE_TYPE_CODES | 2 | 5 | This table defines the valid educational degrees to be used on MASTER PEOPLE records | |
| DEL_DISPATCH_EVENT_CASES | 14 | This table stores duplicate dispatch event case information from the PRINTRAK interface | ||
| DEL_DISPATCH_EVENT_OFFICERS | 21 | This table stores duplicate dispatch event officer information from the PRINTRAK interface | ||
| DEL_DISPATCH_EVENTS | 65 | This table stores duplicate dispatch events from the PRINTRAK interface | ||
| DELIMITED_LOCATION_ALL | 2 | |||
| DELIMITED_LOCATION_INTERSECT | 2 | |||
| DEPARTMENT_EQUIPMENT | 2 | 6 | 19 | This table defines equipment used in the OFFICER DAILY LOG in the application |
| DEPARTMENT_VEHICLES | 15 | 27 | 54 | This table defines vehicles used in the OFFICER DAILY LOG in the application |
| DIR_LIST | 2 | Legacy table. This table is not currently used | ||
| DISPATCH_ERRORS | 9 | This table stores errors generated by the Logisys CAD interface | ||
| DISPATCH_EVENT_ATTACHMENTS | 2 | 10 | This table stores attachments added to a dispatch event | |
| DISPATCH_EVENT_CASES | 2 | 11 | This table stores the association to an Incident on the dispatch event. Association can be made manually in the application or is created via the CAD-RMS interface | |
| DISPATCH_EVENT_IMAGES | 2 | 9 | This table stores image attachments added to dispatch events | |
| DISPATCH_EVENT_OFFICERS | 1 | 20 | This table stores the association to an officer added to a dispatch event manually in the application or through the CAD-RMS interface | |
| DISPATCH_EVENT_PEOPLE | 3 | 24 | 50 | This table stores information about people involved with an event. |
| DISPATCH_EVENT_PEOPLE_VW | 48 | |||
| DISPATCH_EVENT_TYPES | 1 | 8 | This table defines the valid dispatch event types (e.g. POLICE, FIRE, EMS) | |
| DISPATCH_EVENT_VEHICLES | 1 | 2 | 31 | This table stores the vehicle information related to a Call for Service. |
| DISPATCH_EVENT_VEHICLES_VW | 34 | |||
| DISPATCH_EVENTS | 10 | 6 | 65 | This table stores dispatch event information (referred to as Calls For Service in the application) as created in the application or loaded through the CAD-RMS interface |
| DISPATCH_PERSON_MISC_IDS | 6 | 16 | This table stores identification information about people involved with an event, such as drivers license #s . | |
| DISPATCH_PERSON_ROLES | 3 | 8 | This table stores the roles of people involved with an event. | |
| DISPATCH_PERSON_VEHICLES | 2 | 7 | This table stores the association between vehicles and people related to a Call for Service. | |
| DISPATCH_SEARCH_VW | 55 | |||
| DISPATCH_VW | 41 | |||
| DOMESTIC_VIOLENCE_VICTIMS | 4 | 11 | This table stores the association to a MASTER PERSON if that MASTER PERSON is added as a victim of domestic violence to an ARREST in the application | |
| DS_DEBUG | 5 | This table store debug and log information for DS_ICR and DS_NIBR packages. Contains milestone events or errors in the DS_ICR and DS_NIBR process | ||
| DS_IBR_EXTSYS_FIELDS_VW | 20 | |||
| DS_IBR_FIELD_SYSTEMS | 1 | 4 | 21 | This table defines the Record Layouts. Defines the format, layout of the Attachment File. This should mirror each EXTERNAL_SYSTEM_CODES.CODE(s) Record Layout Work Sheet |
| DS_IBR_FIELD_VALUES | 1 | 14 | This table stores the Row Based representation of each Fields Values of the Record Layout for all Segments | |
| DS_IBR_FIELD_VALUES_FAST_VW | 22 | |||
| DS_IBR_FIELD_VALUES_VW | 21 | |||
| DS_IBR_FIELDS | 1 | 9 | This parent table defines the fields used in a Record Layout for each Segment. The Fields can be reused between EXTERNAL_SYSTEM_CODES.CODE | |
| DS_IBR_MIGRATION_ERRORS | 9 | Stores Incidents that Failed to Reject And Move to New DataSet | ||
| DS_IBR_MODIFY_VALUES_VW | 15 | |||
| DS_IBR_SEGMENT_DETAILS | 2 | 10 | This table defines the Segment Details, Attributes used in the Record Layout of each Segment. Segment Level, Legment Length, etc | |
| DS_IBR_SEGMENTS | 3 | 6 | This parent table defines all Segments used in Record Layout for Attachment File that is sent to the FBI, State | |
| DS_ICR_ADDL_PROPERTY_ITEMS_GTT | 49 | This table stores additional Property Items for Additional for Staging transformation from DS_ICR_ADDL_PROPERTY_ITEMS into its Final (or close to) NIBRS (or given EXTERNAL_SYSTEM_CODES.CODE) Format | ||
| DS_ICR_ADDRESSES | 1 | 28 | This table stores Addresses Segment based on a given EXTERNAL_SYSTEM_CODES.CODE populated from DS_ICR Package when Incident is Approved in the application | |
| DS_ICR_ARRESTS | 1 | 33 | This table stores ARRESTS Segment based on a given EXTERNAL_SYSTEM_CODES.CODE populated from DS_ICR Package when Incident is Approved in the application | |
| DS_ICR_ARRESTS_GTT | 77 | This table stores ARRESTS (Group A) Segment Staging Table. Stores transformation from DS_ICR_ARRESTS into its Final (or close to) NIBRS (or given EXTERNAL_SYSTEM_CODES.CODE) Format | ||
| DS_ICR_CAT_QUERIES | 8 | Defines queries that can be used to summarize IBR data for administrators | ||
| DS_ICR_DATA_SETS | 3 | 26 | This parent table stores all Data Sets. Data Sets are unique per Root Agency. If there is no Root Agency then for each Distinct Agency | |
| DS_ICR_FILE_REFERENCES | 5 | 13 | This table stores relationships between a Data Set and its related Attachment File that is sent to the FBI, State | |
| DS_ICR_GROUPB_GTT | 38 | This table stores Group B Arrestee Segment Staging transformation from DS_ICR_ARRESTS (Group B Only) into its Final (or close to) NIBRS (or given EXTERNAL_SYSTEM_CODES.CODE) Format | ||
| DS_ICR_HEADER_FILES | 8 | 15 | This table stores the Data submission Header Files Information | |
| DS_ICR_HEADER_MESSAGES | 4 | 10 | This table stores the Data submission Header Messages Information | |
| DS_ICR_HEADERS | 10 | 3 | 35 | This table stores the Administrative Segment based on a given EXTERNAL_SYSTEM_CODES.CODE populated from DS_ICR Package when Incident is Approved in the application |
| DS_ICR_HEADERS_GTT | 51 | This table stores Administrative Segment Staging transformation from DS_ICR_HEADERS into its Final (or close to) NIBRS (or given EXTERNAL_SYSTEM_CODES.CODE) Format | ||
| DS_ICR_INC_QRY_SEL_TEMP | 2 | This table is a Global Temporary Table used for Batching, Processing Incident(s) when Approved and and moving the Incident(s) into an Open Data Set | ||
| DS_ICR_INCIDENT_ERRORS | 8 | This table stores Incident Errors when processing for DS_ICR and DS_NIBR | ||
| DS_ICR_INSERT_QUEUE | 2 | 10 | This Table Stores Queued Incident Reports for IBR Processing | |
| DS_ICR_MORE_DATA | 1 | 28 | This table stores More (Additional) Data Segment based on a given EXTERNAL_SYSTEM_CODES.CODE populated from DS_ICR Package when Incident is Approved in the application | |
| DS_ICR_OFFENDERS | 1 | 13 | This table stores Offenders Segment based on a given EXTERNAL_SYSTEM_CODES.CODE populated from DS_ICR Package when Incident is Approved in the application | |
| DS_ICR_OFFENDERS_GTT | 35 | This table stores Offenders Segment Staging transformation from DS_ICR_OFFENDERS into its Final (or close to) NIBRS (or given EXTERNAL_SYSTEM_CODES.CODE) Format | ||
| DS_ICR_OFFENSES | 1 | 28 | This table stores Offenses Segment based on a given EXTERNAL_SYSTEM_CODES.CODE populated from DS_ICR Package when Incident is Approved in the application | |
| DS_ICR_OFFENSES_GTT | 44 | This table stores Offenses Segment Staging transformation from DS_ICR_OFFENSES into its Final (or close to) NIBRS (or given EXTERNAL_SYSTEM_CODES.CODE) Format | ||
| DS_ICR_ORI_GTT | 20 | ORI Segment Staging Table. Stores transformed ORI and AGENCY_CODES details into its Final (or close to) NIBRS (or given EXTERNAL_SYSTEM_CODES.CODE) Format. | ||
| DS_ICR_PROPERTY_DRUGS_GTT | 9 | DS_ICR_PROPERTY_DRUGS_GTT | ||
| DS_ICR_PROPERTY_ITEMS | 1 | 35 | This table stores Property Items Segment based on a given EXTERNAL_SYSTEM_CODES.CODE populated from DS_ICR Package when Incident is Approved in the application | |
| DS_ICR_PROPERTY_ITEMS_GTT | 81 | This table stores Property Items Segment Staging transformation from DS_ICR_PROPERTY_ITEMS into its Final (or close to) NIBRS (or given EXTERNAL_SYSTEM_CODES.CODE) Format | ||
| DS_ICR_SEGMENTS | 2 | 16 | DS ICR Table used for re-usable IBR segments storing key data , IBR_SEGMENT and data fields | |
| DS_ICR_VICTIM_SUSPECTS_GTT | 8 | DS_ICR_VICTIM_SUSPECTS_GTT | ||
| DS_ICR_VICTIMS | 1 | 57 | This table stores Victims Segment based on a given EXTERNAL_SYSTEM_CODES.CODE populated from DS_ICR Package when Incident is Approved in the application | |
| DS_ICR_VICTIMS_GTT | 76 | This table stores Victims Segment Staging transformation from DS_ICR_VICTIMS into its Final (or close to) NIBRS (or given EXTERNAL_SYSTEM_CODES.CODE) Format | ||
| DS_ICR_ZERO_GTT | 14 | This table stores Zero Segment Staging transformation from DS_ICR_ZERO into its Final (or close to) NIBRS (or given EXTERNAL_SYSTEM_CODES.CODE) Format | ||
| DS_NIBR_PIVOT | 64 | |||
| DS_NIBR_PIVOT_GTT | 64 | This table is used for UCR Reporting | ||
| DS_NIBRS_ARRESTS_VW | 22 | |||
| DS_NIBRS_GROUPB_VW | 22 | |||
| DS_NIBRS_HEADERS_VW | 15 | |||
| DS_NIBRS_OFFENDERS_VW | 14 | |||
| DS_NIBRS_OFFENSES_VW | 18 | |||
| DS_NIBRS_PROPERTY_VW | 18 | |||
| DS_NIBRS_VICTIMS_VW | 25 | |||
| DV_ASSIGNMENTS | 2 | 2 | 13 | This table stores assignments added to a department vehicle |
| DV_ATTACHMENTS | 2 | 10 | This table stores attachments added to a department vehicle | |
| DV_CRASH_ATTACHMENTS | 2 | 10 | This table stores attachments added to a department vehicle | |
| DV_CRASH_DELETE_LOG | 1 | 10 | This table stores DV_CRASHES delete logs | |
| DV_CRASH_IMAGES | 2 | 9 | This table stores image attachments added to department vehicles | |
| DV_CRASH_INCIDENTS | 4 | 8 | Join table Between DV_CRASHES and INCIDENTS | |
| DV_CRASH_INSURANCE | 3 | 17 | This table stores Crash insurance info | |
| DV_CRASH_INSURANCE_VW | 42 | |||
| DV_CRASH_REFERENCES | 3 | 10 | This table stores reference numbers and types added to a Fleet Crashes | |
| DV_CRASH_REFERENCES_VW | 33 | |||
| DV_CRASH_SERVICE_RECORDS_VW | 45 | |||
| DV_CRASH_SERVICE_REPAIRS_VW | 37 | |||
| DV_CRASH_TOWS | 4 | 21 | This table stores tow information added to a vehicle crash | |
| DV_CRASH_TOWS_VW | 44 | |||
| DV_CRASHES | 7 | 15 | 29 | This Table Stores Crash Reports for fleet vehicles |
| DV_CRASHES_VW | 33 | |||
| DV_EQUIPMENT | 2 | 11 | This table stores equipment added to a department vehicle | |
| DV_FUEL_OIL | 12 | 29 | This table stores department vehicle fuel and oil change records | |
| DV_IMAGES | 2 | 9 | This table stores image attachments added to department vehicles | |
| DV_INSPECTIONS | 5 | 14 | This table stores department vehicle inspections | |
| DV_INSURANCE | 1 | 1 | 11 | This table stores department vehicle insurance info |
| DV_INSURANCE_CLAIM | 3 | 12 | This table stores department vehicle insurance claims | |
| DV_MISC_IDS | 5 | 15 | This table stores misc ids for department vehicles | |
| DV_OFFICERS | 4 | 12 | This table stores officers assignments to department vehicles | |
| DV_REQUEST_ATTACHMENTS | 2 | 10 | This table stores attachments added to a department vehicle service requests | |
| DV_REQUEST_IMAGES | 2 | 9 | This table stores image attachments added to vehicle service requests | |
| DV_ROLE_RESTRICTIONS | 3 | 9 | This table stores vehicle category relations to role codes to restrict vehicles to roles. | |
| DV_SERVICE_ATTACHMENTS | 2 | 10 | This table stores attachments added to a department vehicle | |
| DV_SERVICE_IMAGES | 2 | 9 | This table stores image attachments added to vehicle service records | |
| DV_SERVICE_RECORDS | 4 | 3 | 22 | This table stores service/maintanence records on department vehicles |
| DV_SERVICE_REPAIRS | 3 | 11 | This table stores service repair records on department vehicle services | |
| DV_SERVICE_REQUEST | 2 | 8 | 17 | This table stores service request records for a department vehicle |
| DV_STORAGE_LOCATIONS | 3 | 12 | This table stores storage location associations to department vehicles | |
| E_WARRANTS | 16 | 12 | 39 | This table stores warrant information created in the application |
| E_WARRANTS_AUDIT | 38 | This table is a shadow table for E_WARRANTS | ||
| EDUCATION | 1 | 3 | 13 | This table stores the education information including degree type added to a MASTER PERSON in the application |
| EDUCATION_STATUSES | 3 | 11 | This table stores the valid education statuses that can be assigned to the education information on a MASTER PERSON | |
| EJS_AUDITS | 3 | 10 | Legacy table. This table is not currently used | |
| EJS_CODE_NIBRS_MAPPINGS | 5 | 10 | This table defines valid values or conditions based on values selected or applicable to NIBRS_CODE_EJS_MAPPINGS (and is a child table to NIBRS_CODE_EJS_MAPPINGS). For example, a NIBRS Code of 200, a property loss of 8 - unknown, can only allow a value of 8 - unknown for a valid property status. If only one value is valid the application will default it for the user and not prompt them for entry. | |
| EJS_CODES | 1,090 | 16 | This admin table is a dynamic code table design that allows a code table to be created logically and then related to many different base tables versus having hundreds of simple code tables | |
| EJS_CODES_AGENCIES | 3 | 7 | This table defines agency specific codes and is an extension of EJS_CODES | |
| EJS_CODES_EXTRN_MULTI_LINKS | 3 | 10 | This table can join ejs codes (codes in EJS_CODES) to codes in other code tables | |
| EJS_CODES_RELATIONS | 4 | 4 | 5 | This table defines relationships between EJS_CODES used throughout the application |
| EJS_CODES_RELATIONS_AGENCIES | 5 | 9 | This table stores agency specific code relations | |
| EJS_COMMENTS | 7 | 8 | This table stores comments added by a user to different records throughout the application (e.g. disposition comment on a field ARREST) | |
| EJS_DB_CONFIG_NOTES | 6 | This is an Interact Administration table | ||
| EJS_DEBUG | 2 | This is an Interact Administration table | ||
| EJS_FTP | 3 | 2 | 15 | This is an Interact Administration table |
| EJS_IMPORT_VW | 8 | |||
| EJS_INC_REPORT_VALIDATIONS | 2 | 3 | 16 | This table defines the different INCIDENT report validation and checks |
| EJS_INC_VALDN_VAR_VALUES | 8 | This table stores the different validation values for a given INCIDENT that need to be met | ||
| EJS_INC_VLDN_ERR_VARIABLES | 1 | 8 | This table stores the different variables available for each validation error | |
| EJS_INC_VLDN_ERRORS | 1 | 10 | This table stores the different validation errors for a given INCIDENT. This is queried when the validations are run for an INCIDENT report | |
| EJS_JOB_LOG | 7 | Legacy table. This table is not currently used | ||
| EJS_JOB_QUEUES | 17 | Legacy table. This table is not currently used | ||
| EJS_MENU_NODES | 1 | 13 | This is a system table used for the menu bar in the application | |
| EJS_MODULE_TEXT | 2 | 13 | Legacy table. This table is not currently used | |
| EJS_NIBRS_DATA_ELEMENTS | 13 | Application table driven lists of values. | ||
| EJS_NOTES | 18 | 7 | This table stores large narratives created throughout the application such as an Incident Narrative. The Note Id is related to the area of the application being used | |
| EJS_NOTES_ANNOTATED | 1 | 2 | 7 | Table to hold a annotated note record |
| EJS_NOTES_ANNOTATIONS | 1 | 7 | Table to hold individual narrative annotations | |
| EJS_NOTES_FLASHBACK | 15 | This table is used to recover EJS Notes (narratives) that may have been changed or lost | ||
| EJS_NOTES_VW | 7 | |||
| EJS_PERMISSION_CATEGORIES | 3 | 8 | System Table for defining access to application areas | |
| EJS_PERMISSIONS | 9 | 11 | System Table for defining access to application areas | |
| EJS_REPORT_PARAMETERS | 1 | 10 | This table is an administrative table that is configured under Administration Reports | |
| EJS_REPORTS | 2 | 7 | 24 | This table is an administrative table that is configured under Administration Reports |
| EJS_ROLE_PERM_CATS | 3 | 8 | The table stores the permission categories available to a given role. This is controlled from Administration->Permissions | |
| EJS_ROLE_PERMISSION_VW | 6 | |||
| EJS_STATE_CODE_MAPPINGS | 1 | 4 | This table is used with interfaces and maps external system codes to the Online RMS codes | |
| EJS_SUB_MAINT | 2 | 17 | This table defines different configuration options and switches for the Online RMS for a given schema | |
| EJS_TABLE_AUDIT_ACTIONS | 3 | 8 | Legacy table. This table is not currently used | |
| EJS_TABLE_AUDITING | 2 | 11 | Legacy table. This table is not currently used | |
| EJS_TABLE_AUDITS | 2 | 1 | 2 | Legacy table. This table is not currently used |
| EJS_TABLE_COLUMN_AUDITS | 1 | 3 | Legacy table. This table is not currently used | |
| EJS_TAG_SCREEN_PARAMS | 4 | 5 | Legacy table. This table is not currently used | |
| EJS_WEB_SERVICE_AGENCIES | 2 | 7 | Agencies using an EJS_WEB_SERVICES | |
| EJS_WEB_SERVICES | 3 | 2 | 23 | Setup information for calling a SOAP or REST web service using HTTP. |
| EJS_XML_BLOBS | 8 | This table is used for loading XML documents into the database | ||
| EJS_XML_DEFAULT_VALUES | 1 | 11 | This table is an administration table that is used for processing XML documents being loaded into the database | |
| EJS_XML_DEST_COLUMN_VW | 9 | |||
| EJS_XML_DOC_ATTACHMENTS | 2 | 10 | This table is an administration table that is used for processing XML documents being loaded into the database | |
| EJS_XML_DOC_ERROR_VW | 12 | |||
| EJS_XML_DOC_ERRORS | 2 | 8 | This table is an administration table that is used for processing XML documents being loaded into the database | |
| EJS_XML_DOC_KEY_CODES | 1 | 1 | 5 | This table is an administration table that is used for processing XML documents being loaded into the database |
| EJS_XML_DOC_KEYS | 2 | 4 | This table is an administration table that is used for processing XML documents being loaded into the database | |
| EJS_XML_DOC_KEYS_VW | 15 | |||
| EJS_XML_DOC_NARRATIVES | 2 | 9 | This table is an administration table that is used for processing XML documents being loaded into the database | |
| EJS_XML_DOC_QUEUE | 1 | 6 | This table is an administration table that is used for processing XML documents being loaded into the database | |
| EJS_XML_MATCH_SCREEN_PARAMS | 2 | 1 | 4 | This table is an administration table that is used for processing XML documents being loaded into the database |
| EJS_XML_MATCH_SCREENS | 3 | 3 | This table is an administration table that is used for processing XML documents being loaded into the database | |
| EJS_XML_PARENT_TAG_VALUES | 2 | 4 | 15 | This table is an administration table that is used for processing XML documents being loaded into the database |
| EJS_XML_ROW_TAG_KEYS | 1 | 5 | This table is an administration table that is used for processing XML documents being loaded into the database | |
| EJS_XML_ROW_TAGS | 2 | 2 | 8 | This table is an administration table that is used for processing XML documents being loaded into the database |
| EJS_XML_SUMMARY_TAGS | 3 | 5 | This table is an administration table that is used for processing XML documents being loaded into the database | |
| EJS_XML_TAG_CATEGORY_CODES | 3 | 1 | 5 | This table is an administration table that is used for processing XML documents being loaded into the database |
| EJS_XML_TAG_NAMES | 6 | 5 | 13 | This table is an administration table that is used for processing XML documents being loaded into the database |
| EJS_XML_TAG_VALUES | 4 | 12 | This table is an administration table that is used for processing XML documents being loaded into the database | |
| EJS_XML_TRACE_LOG | 1 | 6 | This table is an administration table that is used for processing XML documents being loaded into the database | |
| EJS_XML_VALUES_VW | 14 | |||
| EJS_XREFS | 2 | 5 | This table is an administration table that is used for processing XML documents being loaded into the database | |
| EJSXML_DOCS | 6 | 4 | 16 | This table stores all XML documents leaving and coming into the RMS database from an interface using our table driven XML processing. (CAD, Citation, Arrest, Master indexes, etc) |
| EJSXML_DOCS_PRE_XSLT | 8 | This table contains XML to/from an interface before an XSLT is applied. | ||
| EJSXML_DOCS_VW | 11 | |||
| EMAILS | 4 | 12 | This table stores email addresses added to a MASTER PERSON in the application | |
| EMP_ASSIGNMENT_K9_DOGS | 2 | 12 | This table is not currently used | |
| EMP_INFO_TYPE_CODE_ROLES | 4 | 10 | This table stores the employee information type code relations to role codes | |
| EMP_LANGUAGE_VW | 24 | |||
| EMP_LANGUAGES | 6 | 13 | This table stores the languages spoken added to an employee in the application | |
| EMP_RANK_TITLE_CODES | 2 | 2 | 6 | This table defines the valid ranks that can be added to an employee |
| EMP_RISK_LEVELS | 1 | 10 | This table is not currently used | |
| EMP_SCHEDULES | 2 | 3 | This table stores the association between an employee and a schedule | |
| EMP_SENIORITY_VW | 17 | |||
| EMP_SERVICE_ASSIGN_CODES | 4 | 2 | 8 | This table defines the valid service assign codes that can be added to an employee |
| EMP_SERVICE_HISTORIES | 4 | 16 | This table stores the history of service assigned to an employee | |
| EMP_SERVICE_HISTORY_VW | 34 | |||
| EMP_STATUS_CODES | 1 | 4 | This table is not currently used | |
| EMP_SUB_ASSIGN_CODES | 3 | 1 | 5 | This table is not currently used |
| EMP_VW | 28 | |||
| EMPLOYEE_ADDR_PHONES | 3 | 8 | This table stores phone numbers added to the employee | |
| EMPLOYEE_ADDRESSES | 2 | 3 | 14 | This tables stores an association to a MASTER ADDRESS added to the employee |
| EMPLOYEE_AFFILIATIONS | 3 | 12 | This table stores the employee affiliations | |
| EMPLOYEE_ATTACHMENTS | 2 | 10 | This table stores attachments added to the employee | |
| EMPLOYEE_CLASSIFICATIONS | 3 | 12 | This table stores the employee classifications | |
| EMPLOYEE_CONTACTS | 4 | 17 | This table stores employee contacts | |
| EMPLOYEE_EDUCATION | 3 | 11 | This table stores the employee education records | |
| EMPLOYEE_GROUP_EMPLOYEES | 2 | 8 | This table stores the employees associations to employee groups | |
| EMPLOYEE_GROUPS | 2 | 8 | This table stores employee group records | |
| EMPLOYEE_IMAGES | 4 | 12 | This table stores the association to images added to the employee. The image itself is stored in IMAGES | |
| EMPLOYEE_INFO | 2 | 2 | 12 | This table stores the employee information records |
| EMPLOYEE_INFO_ATTACHMENTS | 2 | 11 | This table stores attachments added to a employee information records | |
| EMPLOYEE_INFO_IMAGES | 2 | 10 | This table stores image attachments added to employee information records | |
| EMPLOYEE_INFO_TYPE_CODES | 2 | 7 | This table stores the employee information type codes | |
| EMPLOYEE_MEDICAL | 2 | 15 | This table stores medical information added to the employee | |
| EMPLOYEE_MISC_IDS | 6 | 17 | This table stores the employee identification records | |
| EMPLOYEE_SALARY_VW | 40 | |||
| EMPLOYEE_SKILLS | 3 | 13 | This table stores the employee skills records | |
| EMPLOYEES | 40 | 23 | 54 | This table stores the employee information. RMS users can be flagged as an employee in the admin screens |
| EMPLOYMENTS | 4 | 19 | This table stores the association between MASTER PEOPLE and MASTER BUSINESSES along with occupation information when the MASTER PERSON is added to the business as an employee | |
| EMULATION_HISTORY | 10 | This table stores the history of the emulation users for the RMS | ||
| ENROLLMENT_STATUS_CODES | 1 | 5 | This table is not currently used | |
| ENROLLMENTS | 1 | 5 | 14 | This table is not currently used |
| ERROR_CODE_NOTIFICATIONS | 2 | 3 | Legacy table. This table is not currently used | |
| ERROR_CODES | 3 | 6 | Legacy table. This table is not currently used | |
| EVIDENCE | 5 | 14 | 31 | This table stores the piece of evidence information added in the application |
| EVIDENCE_AUDIT_REP_DETAILS | 4 | 11 | This table stores the audit report details when a user generates an audit report for evidence in the application | |
| EVIDENCE_AUDIT_REPORTS | 1 | 3 | 13 | This table stores the report information when a user generates an audit report for evidence in the application |
| EVIDENCE_COC_MOST_RECENT_VW | 90 | |||
| EVIDENCE_CUSTODY_VW | 79 | |||
| EVIDENCE_DELETE | 10 | This table store the a piece of evidence information when the evidence is deleted in the application | ||
| EVIDENCE_DESTINATION_CODES | 1 | 1 | 7 | This table defines the valid destination codes for a piece of evidence in the application |
| EVIDENCE_LABEL_CELLS | 3 | 12 | a cell/field in an evidence label | |
| EVIDENCE_LABEL_ROWS | 1 | 1 | 7 | a row in an evidence label |
| EVIDENCE_LABELS | 1 | 3 | 17 | Custom printed evidence labels |
| EVIDENCE_LOCATION_CODES | 8 | 3 | 9 | This table defines the valid location codes for a piece of evidence in the application |
| EVIDENCE_OFFICERS | 2 | 9 | This tables stores the association to an officer added to a piece of evidence in the application | |
| EVIDENCE_PROCESSINGS | 3 | 9 | This table stores the processing codes added to a piece of evidence (i.e. finger prints, drug analysis) in the application | |
| EVIDENCE_STATUS_VW | 83 | |||
| EXPORT_DESTINATIONS | 2 | 3 | 11 | This table is used to define export formats. This table is not used at this time |
| EXPORT_FIELD_DESTINATIONS | 3 | 13 | This table is used to define export formats. This table is not used at this time | |
| EXPORT_FIELDS | 2 | 5 | 14 | This table is used to define export formats. This table is not used at this time |
| EXPORT_FILES | 3 | 2 | 10 | This table is used to define export formats. This table is not used at this time |
| EXPORT_PARAMETERS | 2 | 7 | This table is used to define export formats. This table is not used at this time | |
| EXPORT_RECORDS | 1 | 1 | 12 | This table is used to define export formats. This table is not used at this time |
| EXPORT_TRANSACTION_LOGS | 14 | This table is used to define export formats. This table is not used at this time | ||
| EXT_SEARCH_AGENCIES | 2 | 2 | 10 | This table is not currently used |
| EXT_SEARCH_FIELDS | 2 | 10 | This table is not currently used | |
| EXT_SEARCH_LOGIN_HISTORY | 2 | 16 | This table is not currently used | |
| EXT_SEARCH_LOGINS | 3 | 13 | This table is not currently used | |
| EXT_SEARCH_MNEMONICS | 2 | 9 | This table is not currently used | |
| EXT_SEARCH_NOMATCH_RESULTS | 7 | This table is not currently used | ||
| EXT_SEARCH_PARAMETERS | 2 | 2 | 17 | This table is not currently used |
| EXT_SEARCH_RESULTS | 3 | 16 | This table is not currently used | |
| EXT_SEARCH_ROLES | 2 | 7 | This table is not currently used | |
| EXT_SEARCH_TYPES | 4 | 8 | This table is not currently used | |
| EXT_SEARCH_TYPES_FOR_AGENCY | 2 | 7 | This table is not currently used | |
| EXT_SEARCH_VALID_CODES | 2 | 9 | This table is not currently used | |
| EXT_SEARCH_VALUES | 2 | 9 | This table is not currently used | |
| EXT_SEARCHES | 3 | 2 | 9 | This table is not currently used |
| EXTERNAL_INFO_REQUEST_PARAMS | 3 | 11 | This table is used for external searches. This table is not used at this time | |
| EXTERNAL_INFO_REQUESTS | 3 | 3 | 13 | This table is used for external searches. This table is not used at this time |
| EXTERNAL_INFO_RESPONSE_IMAGES | 4 | 8 | This table is used for external searches. This table is not used at this time | |
| EXTERNAL_INFO_RESPONSES | 2 | 1 | 17 | This table is used for external searches. This table is not used at this time |
| EXTERNAL_SYSTEM_AGENCIES | 3 | 11 | This table is used for external searches. This table is not used at this time | |
| EXTERNAL_SYSTEM_AGENCIES_VW | 12 | |||
| EXTERNAL_SYSTEM_CODES | 10 | 1 | 10 | This table is used for external searches. This table is not used at this time |
| EXTERNAL_SYSTEM_DELETES | 2 | 11 | This table stores external system delete transaction information. | |
| EXTERNAL_SYSTEM_EXPUNGEMENTS | 1 | 9 | This table stores external system expungement transaction information. | |
| EXTERNAL_SYSTEM_MAPPINGS | 2 | 7 | This table is used for external searches. This table is not used at this time | |
| FEATURE_PERMISSIONS | 3 | 8 | This table defines different permissions grouped together for an application feature. This table is populated from the agency administration page in the application | |
| FIELD_DATA_ELEMENTS | 1 | 2 | 8 | This table defines custom field elements |
| FIELD_INT_SEARCH_GANG_VW | 20 | |||
| FIELD_INT_SEARCH_LOCATION_VW | 24 | |||
| FIELD_INT_SEARCH_MIN_VW | 14 | |||
| FIELD_INT_SEARCH_OFFICER_VW | 22 | |||
| FIELD_INT_SEARCH_ORG_VW | 19 | |||
| FIELD_INT_SEARCH_PERSON_VW | 24 | |||
| FIELD_INT_SEARCH_VEHICLE_VW | 24 | |||
| FIELD_INTERVIEW_ATTACHMENTS | 2 | 10 | This table stores attachments added to a field interview (referred to as FIELD CONTACTS in the application) | |
| FIELD_INTERVIEWS | 15 | 4 | 15 | This table stores the field interview information (referred to as FIELD CONTACTS in the application) |
| FINGERPRINT_CODES | 1 | 5 | This table defines the valid fingerprint codes used throughout the application | |
| FLDINT_ADD_VW | 24 | |||
| FLDINT_ADDRESSES | 2 | 8 | This table stores the association to MASTER ADDRESSES added to the field interview (referred to as FIELD CONTACTS) in the application | |
| FLDINT_BUSINESSES | 2 | 7 | This table stores the association to MASTER BUSINESSES added to the field interview (referred to as FIELD CONTACTS) in the application | |
| FLDINT_DELETE | 12 | This table stores the field interview information when the field interview (referred to as FIELD CONTACTS) is deleted in the application | ||
| FLDINT_DISPATCHES | 2 | 7 | This table stores an association between a DISPATCH (Calls For Service) and a FIELD INTERVIEW (Field Contact). | |
| FLDINT_GANG_VW | 11 | |||
| FLDINT_GANGS | 2 | 7 | This table stores the association to MASTER GANGs added to a field interview (referred to as FIELD CONTACTS) in the application | |
| FLDINT_IMAGES | 2 | 9 | This table stores the association to images added to a field interview (referred to as FIELD CONTACTS) in the application. The image itself is stored in IMAGES | |
| FLDINT_INTELL | 1 | 8 | This table is not currently used | |
| FLDINT_INTELL_VW | 9 | |||
| FLDINT_NARRATIVES_VW | 7 | |||
| FLDINT_OFF_VW | 15 | |||
| FLDINT_OFFICERS | 3 | 8 | This table stores the association to an officer added to a field interview (referred to as FIELD CONTACTS) in the application | |
| FLDINT_PEOPLE | 3 | 8 | This table stores the association to MASTER PEOPLE added to a field interview (referred to as FIELD CONTACTS) in the application | |
| FLDINT_VEH_VW | 21 | |||
| FLDINT_VEHICLES | 4 | 9 | This table stores the association to MASTER VEHICLES added to a field interview (referred to as FIELD CONTACTS) in the application | |
| FLEET_DASHBOARD_COST_VW | 17 | |||
| FLEET_DASHBOARD_MAINTENANCE_VW | 16 | |||
| FLEET_DASHBOARD_SERVICE_VW | 20 | |||
| FLEET_MAINTENANCE_LOG | 4 | 14 | This table is not currently used | |
| FLEET_MILEAGE_LOG | 3 | 14 | This table is not currently used | |
| FREE_TEXT_CODES | 6 | This table is not currently used | ||
| GANG_ASSOCIATIONS | 4 | 12 | This table stores the associations between GANGS | |
| GANG_ATTACHMENTS | 2 | 10 | This table stores attachments added to a MASTER GANG in the application | |
| GANG_IMAGES | 2 | 9 | This table stores the association to images added to a MASTER GANG in the application. The image itself is in IMAGES | |
| GANG_LEVEL_CODES | 1 | 5 | This table defines the valid levels for a MASTER GANG (e.g. National, Local) | |
| GANG_NAMES | 3 | 11 | This table stores the names added to a MASTER GANG in the application | |
| GANG_PEOPLE | 2 | 4 | 11 | This table stores the association to the MASTER PEOPLE added to the gang in the application |
| GANG_PERSON_REASONS | 3 | 9 | This table stores the reason the MASTER PERSON is in the gang | |
| GANG_REASON_CODES | 1 | 5 | This table defines the valid reason codes when adding a person to a gang in the application | |
| GANG_SEARCH_VW | 36 | |||
| GANG_SOLR_SEARCH_VW | 26 | |||
| GANGS | 8 | 4 | 13 | This table stores the MASTER GANG information added in the application |
| GIS_TEMP | 17 | This table is not currently used | ||
| GIS_TEMP_SESSIONS | 8 | This table is not currently used | ||
| GUEST_LOG_ENTRIES | 2 | 9 | This table is not currently used | |
| GUN_MAKE_CODES | 1 | 10 | This table defines the valid makes of guns for the application | |
| HOME_AGENCY_AUDIT | 3 | 10 | This table is used to audit the changing of a users home agency within the application | |
| HYBRID_TRANSACTIONS | 13 | This table is used for the RMS to Enterprise Product | ||
| HYBRID_TRANSFERS | 7 | This table is used for the RMS to Enterprise Product | ||
| HYBRID_TRIGGER_TABLES | 4 | This table is used for the RMS to Enterprise Product | ||
| IJIS_USER_PROFILE_AFFILIATES | 2 | 7 | Legacy table. This table is not currently used | |
| IJIS_USER_PROFILE_OAUTH | 3 | 9 | This table is used for the LEAP interface | |
| IJIS_USER_PROFILE_ROLES | 2 | 8 | This table stores the roles that a particular user has. This table is populated under the security table of a user's profile | |
| IJIS_USER_PROFILE_WORKGROUPS | 3 | 8 | This table stores the workgroups that a particular user has. This table is populated under the security table of a user's profile | |
| IJIS_USER_PROFILES | 47 | 12 | 46 | This table stores a user's profile and is accessed under user admin and from the user's profile within the application, clicking on the user's name in the upper left of the header page |
| IMAGES | 43 | 1 | 13 | This table stores images added to items such as ARRESTS, citations, etc. throughout the application |
| IMP_LOC_CODES | 2 | 1 | 8 | This table defines the valid location codes for vehicle impounds in the application |
| IMP_VEH_BUSINESSES_VW | 30 | |||
| IMP_VEH_OFFICERS_VW | 32 | |||
| IMPORT_FILES | 1 | 2 | 10 | This table is used by the PrintTrak Interface |
| IMPORT_PARAMETERS | 2 | 8 | This table is used by the PrintTrak Interface | |
| IMPORT_RECORDS | 1 | 9 | This table is used by the PrintTrak Interface | |
| IMPOUND | 13 | 19 | 40 | This table stores the impound information added to a vehicle in the application |
| IMPOUND_ATTACHMENTS | 2 | 10 | This table stores attachments added to the tow impound | |
| IMPOUND_BUSINESSES | 4 | 10 | This table stores the association to MASTER BUSINESSES (referred to as organizations) added to the impound record along with the role the organization plays | |
| IMPOUND_DELETE_LOG | 2 | 11 | This table stores Logs of Impound records that were deleted by users | |
| IMPOUND_HOLD_OFFS | 4 | 11 | This table stores the association to the officer if a holding officer was added in the application | |
| IMPOUND_HOLDS | 5 | 16 | This table stores the hold information for a MASTER VEHICLE | |
| IMPOUND_IMAGES | 2 | 9 | This table stores image attachments added to the tow impound | |
| IMPOUND_INVENTORY | 1 | 8 | This table stores inventory items found in the vehicle being impounded that are entered in the application. There is no link to MASTER PROPERTY | |
| IMPOUND_LOG | 3 | 11 | This table stores the log entries for activities done to a vehicle tow and impound in the application | |
| IMPOUND_OFFICERS | 4 | 9 | This table stores the association to officers added to the vehicle impound in the application | |
| IMPOUND_PEOPLE | 7 | 12 | This table stores the association to MASTER PEOPLE added to the vehicle impound along with the role the person plays | |
| IMPOUND_REASONS | 3 | 8 | This table stores the reasons added to the vehicle impound in the application | |
| IMPOUND_VEHICLE_VW | 26 | |||
| INC_CASE_ACTIVITIES | 11 | 8 | 19 | This table stores activities added to a case in the application |
| INC_CASE_ACTIVITY_NOTIFIES | 2 | 8 | This table stores who a notification was sent to for an activity note added to a case in the application | |
| INC_CASE_INC_STATUS_VW | 13 | |||
| INC_CASE_INCIDENTS | 3 | 9 | This table stores the association between cases and INCIDENTS | |
| INC_CASE_INCIDENTS_VW | 32 | |||
| INC_CASE_OFFICERS_VW | 24 | |||
| INC_CASE_ROUTING | 1 | 4 | 6 | This table is not currently used |
| INC_CASE_SUB_ROUTES | 1 | 4 | This table is not currently used | |
| INC_CASE_WORKGROUPS | 3 | 9 | This table stores the workgroup information added to a case in the application | |
| INC_CASE_XREFS | 2 | 8 | This table stores external ids for an INCIDENT from external applications or interfaces. Data is uploaded through the Incident XML import | |
| INC_CASE_XREFS_VW | 3 | |||
| INC_COMMENT_GROUP_COMMENTS | 5 | 15 | Table to hold disapproval comments for a section of a report | |
| INC_COMMENT_GROUPS | 3 | 2 | 7 | Table to hold disapproval comment groups for incident reports |
| INC_FLD_CONTACT_ADDRESSES_VW | 16 | |||
| INC_NARRATIVE_PEOPLE | 4 | 9 | Join Table between INCIDENT_PEOPLE and INC_SUPP_NARRATIVE | |
| INC_OFF_CRIME_TARGETS_VW | 8 | |||
| INC_OFF_LATEST_APPR_VW | 31 | |||
| INC_PAGE_INDEXES | 2 | 12 | This table is a utility table used to capture when a user last visited an INCIDENT in the application | |
| INC_PAGE_VISITS | 8 | This table is a utility table used to capture when a user last visited an INCIDENT in the application | ||
| INC_PER_FORCES | 3 | 8 | This table stores the excessive forces taken for a MASTER PERSON association with an INCIDENT | |
| INC_PER_SUP_VW | 12 | |||
| INC_PROP_LATEST_APPR_VW | 28 | |||
| INC_REVIEW_ROUTE_AGENCIES | 2 | 7 | Associates Incident Review Routes With Agencies | |
| INC_REVIEW_ROUTE_EXCLUDES | 2 | 7 | Allows individual offenses to be excluded from incident review routes | |
| INC_REVIEW_ROUTE_INSTANCES | 1 | 9 | 24 | In instance of a level of an incident route |
| INC_REVIEW_ROUTE_LEVELS | 4 | 13 | Describes a level of an incident review route | |
| INC_REVIEW_ROUTE_NIBRS | 2 | 7 | Allows you to associate NIBRS codes to a route. | |
| INC_REVIEW_ROUTE_OFFENSES | 2 | 7 | Allows you to associate individual offenses with a route | |
| INC_REVIEW_ROUTES | 5 | 2 | 11 | Parent table for incident review routes |
| INC_REVIEW_TYPES | 2 | 8 | Join Table between INC_REVIEW_ROUTES and EJS_CODES | |
| INC_SUPP_NARR_APPR_UPDATES | 10 | This table is used to track updated narratives on approved incidents | ||
| INC_SUPP_NARRATIVES | 3 | 4 | 14 | This table stores the association to the narratives added to an INCIDENT supplement. The narrative itself is stored in EJS_NOTES |
| INC_USER_RESTORE_POINTS | 5 | 14 | This table stores user return points into an INCIDENT to return a user to an INCIDENT in the application | |
| INC_VAL_COND_AGNC_CDE | 2 | 7 | This table is used for INCIDENT rule validations executed in the application | |
| INC_VAL_COND_PROP_CDE | 2 | 7 | This table is used for INCIDENT rule validations executed in the application | |
| INC_VAL_PROP_ATTR_CDE | 2 | 7 | This table is used for INCIDENT rule validations executed in the application | |
| INC_VALID_ATTRIBUTES | 1 | 2 | 10 | This tables stores attributes for INCIDENT rule validations executed in the application |
| INC_VALID_CONDITIONS | 2 | 8 | 19 | This table stores conditions for INCIDENT rule validation executed in the application |
| INC_VALID_PROPERTIES | 2 | 4 | 11 | This table stores properties for INCIDENT rule validations executed in the application |
| INC_VEH_OFFENSES | 4 | 9 | This table stores the association between vehicles and offenses on an INCIDENT | |
| INCIDENT_ACTIONS | 3 | 10 | This tables stores the INCIDENT follow up action assigned to an INCIDENT during approval in the application | |
| INCIDENT_ACTIVITY_AUDIT | 4 | 19 | This table stores the audit information when a user views or prints an INCIDENT in the application | |
| INCIDENT_ADDRESS_VW | 51 | |||
| INCIDENT_ADDRESSES | 12 | 22 | This table stores the association to a MASTER ADDRESS added to an INCIDENT in the application or uploaded from the CAD-RMS Interface | |
| INCIDENT_ARRESTS | 3 | 8 | This table stores the association to a Field Arrest added to an INCIDENT in the application | |
| INCIDENT_ASSISTS | 5 | 11 | This table stores the information for when a user indicates an INCIDENT was for assisting another agency in the application | |
| INCIDENT_ATTACHMENTS | 3 | 12 | This table stores attachments added to an INCIDENT in the application | |
| INCIDENT_BAIR_EXTRACT_VW | 27 | |||
| INCIDENT_BOLO_PEOPLE_VW | 25 | |||
| INCIDENT_BOLO_VEHICLES_VW | 15 | |||
| INCIDENT_BUSINESS_VW | 31 | |||
| INCIDENT_BUSINESSES | 6 | 4 | 10 | This tables stores associations to MASTER BUSINESSES (referred to as organizations) added to the INCIDENT in the application |
| INCIDENT_CASE_OFFICERS | 5 | 13 | This table stores the association to officers added to a case in the application | |
| INCIDENT_CASE_OFFICERS_VW | 51 | |||
| INCIDENT_CASE_RWSCH_VW | 16 | |||
| INCIDENT_CASE_SEARCH_MIN_VW | 11 | |||
| INCIDENT_CASE_SEARCH_VW | 56 | |||
| INCIDENT_CASE_STATUS_HISTORY | 2 | 8 | This table stores the history of the status changes for a case made in the application | |
| INCIDENT_CASE_VW | 31 | |||
| INCIDENT_CASES | 17 | 9 | 26 | This table stores the case information created in the application |
| INCIDENT_CITATION_VW | 23 | |||
| INCIDENT_CITATIONS | 3 | 9 | This table stores the association between an citation and an INCIDENT | |
| INCIDENT_CLASSIFICATION | 1 | 3 | 9 | This table stores the classification given to an INCIDENT in the application |
| INCIDENT_CLEAR_STATUS_HISTORY | 2 | 10 | This table is not currently used | |
| INCIDENT_CLEARANCE_STATUS | 2 | 10 | This table is not currently used | |
| INCIDENT_COMBO_MO_NARR_VW | 41 | |||
| INCIDENT_COMBO_MO_VW | 40 | |||
| INCIDENT_COMBO_OFCR_VW | 58 | |||
| INCIDENT_COMBO_PER_VW | 32 | |||
| INCIDENT_COMBO_VEH_VW | 32 | |||
| INCIDENT_COMBO_VW | 32 | |||
| INCIDENT_CRIME_TARGET_VW | 67 | |||
| INCIDENT_DELETE | 7 | 22 | This tables stores the INCIDENT information when an INCIDENT is deleted from the application | |
| INCIDENT_DELETE_SEARCH_VW | 14 | |||
| INCIDENT_DELETE_VW | 14 | |||
| INCIDENT_DISPATCH_VW | 48 | |||
| INCIDENT_EMPLOYEES | 7 | 13 | This table stores the association to employees added to the INCIDENT in the application | |
| INCIDENT_EVIDENCE_VW | 52 | |||
| INCIDENT_FLDINTS | 3 | 8 | This tables stores the association to field interviews (referred to as field contacts) added to the INCIDENT in the application | |
| INCIDENT_GANG_VW | 21 | |||
| INCIDENT_GANGS | 5 | 11 | This table stores the association to MASTER GANGs added to the INCIDENT in the application | |
| INCIDENT_GIS_VW | 40 | |||
| INCIDENT_IBR_MAX_DATES_VW | 3 | |||
| INCIDENT_IMAGES | 2 | 11 | This table stores the association to images added to the INCIDENT in the application. The images itself is stored in IMAGES | |
| INCIDENT_IMPOUNDS | 3 | 8 | This table stores associations between incidents and tow impounds | |
| INCIDENT_INTERNAL_LOCATIONS | 12 | This table is not currently used | ||
| INCIDENT_LOCATIONS | 5 | 12 | This table stores the associations to additional MASTER ADDRESSES along with their role that are added to the INCIDENT in the application | |
| INCIDENT_NAME_VW | 6 | |||
| INCIDENT_NOTIFY_HISTORY | 5 | 12 | This tables stores a history of people notified of an INCIDENT in the application | |
| INCIDENT_OFF_CRIME_TARGETS_VW | 27 | |||
| INCIDENT_OFFENSE_ADDRESSES_VW | 159 | |||
| INCIDENT_OFFENSE_MO_VW | 35 | |||
| INCIDENT_OFFENSE_VW | 30 | |||
| INCIDENT_OFFICER_VW | 31 | |||
| INCIDENT_PEOPLE | 13 | 13 | 24 | This table stores the associations to MASTER PEOPLE added to an INCIDENT in the application |
| INCIDENT_PEOPLE_OFFENSES | 4 | 9 | This table stores the association between the MASTER PERSON and the offense added to an INCIDENT in the application | |
| INCIDENT_PEOPLE_SEARCH_VW | 27 | |||
| INCIDENT_PEOPLE_VW | 39 | |||
| INCIDENT_PERSON_OFFENSES_VW | 52 | |||
| INCIDENT_PERSON_ROLE_HISTORIES | 1 | 7 | This table stores role histories for incident people | |
| INCIDENT_PERSON_ROLES | 2 | 8 | This table stores the roles for a MASTER PERSON added to an INCIDENT in the application | |
| INCIDENT_PROPERTIES | 1 | 15 | 30 | This tables stores the association with MASTER PROPERTIES added to an INCIDENT in the application |
| INCIDENT_PROPERTY_VW | 67 | |||
| INCIDENT_RECOVERY_VW | 51 | |||
| INCIDENT_ROUTE_DEF_AGNCY | 2 | 6 | The table stores route default agencies for routing INCIDENT notifications | |
| INCIDENT_ROUTE_DEFAULTS | 1 | 4 | 10 | This table stores the route defaults for routing INCIDENT notifications |
| INCIDENT_ROUTE_ORIG_AGENCIES | 2 | 6 | This table stores original agencies for routing INCIDENT notifications | |
| INCIDENT_ROUTE_STATUSES | 3 | 7 | This table stores the route statues for routing INCIDENT notifications | |
| INCIDENT_ROUTE_VW | 9 | |||
| INCIDENT_ROUTES | 2 | 5 | 12 | This table stores the notification route template information for routing INCIDENTS based on agency and offenses |
| INCIDENT_SEARCH_VW | 28 | |||
| INCIDENT_SECURITY_LEVEL_CODES | 6 | 7 | This table defines the valid security level codes that can be added to an INCIDENT in the application | |
| INCIDENT_SUPP_NARRATIVE_VW | 23 | |||
| INCIDENT_SUPP_TEMP | 3 | This table is a global temp table used by the application | ||
| INCIDENT_SUPP_VW | 27 | |||
| INCIDENT_SUPPLEMENT_DRUGS | 8 | 15 | This table is not currently used | |
| INCIDENT_SUPPLEMENT_MARIJ | 6 | 12 | This table is not currently used | |
| INCIDENT_SUPPLEMENT_NOTES_VW | 6 | |||
| INCIDENT_SUPPLEMENT_PRECHEMS | 4 | 11 | This table is not currently used | |
| INCIDENT_SUPPLEMENTS | 56 | 10 | 35 | This tables stores the supplement information for each supplement of an INCIDENT, including supplement 0 - the initial INCIDENT report |
| INCIDENT_TAB_VALIDATIONS | 3 | 8 | This table is not currently used | |
| INCIDENT_TYPE_OFFENSES | 3 | 8 | This table relates incident type codes to offense codes. | |
| INCIDENT_TYPES | 3 | 8 | This table stores the type assigned to the INCIDENT in the application | |
| INCIDENT_VEHICLE_VW | 39 | |||
| INCIDENT_VEHICLES | 1 | 11 | 25 | This table stores the association to MASTER VEHICLES and their role added to an INCIDENT in the application |
| INCIDENT_VICTIM_NAME_VW | 13 | |||
| INCIDENT_WARNING_NOTIFY_LOG | 3 | 10 | Log for notifications sent from the Incident Warnings Module | |
| INCIDENT_WARNINGS | 2 | 11 | This table stores incident warnings messages. Admin use only. | |
| INCIDENT_WARRANTS | 3 | 8 | This table stores the association between a warrant and an INCIDENT | |
| INCIDENT_WORKGROUPS | 4 | 10 | This table stores the workgroup information added to an INCIDENT in the application | |
| INCIDENT_XREFS | 3 | 9 | This table stores external ids for a INCIDENTS from external applications or interfaces. Data is uploaded through the Incident XML import | |
| INCIDENT_XREFS_VW | 18 | |||
| INCIDENTS | 19 | 7 | 34 | This table stores the INCIDENT header information entered in the application or uploaded from the CAD-RMS interface |
| INJURIES | 3 | 8 | This table stores injuries recorded for a person on an INCIDENT in the application | |
| INSTALL | 1 | 23 | Installation information about the application | |
| INSTALL_SUBSYSTEMS | 6 | 1 | 9 | Legacy table. This table is not currently used |
| INTERFACE_JOBS | 1 | 7 | Legacy table. This table is not currently used | |
| INTERFACE_MONITORING | 2 | 8 | This table is used by XML documents procedures that load XML into the database | |
| INTERFACE_XML_DOCS | 2 | 7 | This table is used by XML documents procedures that load XML into the database | |
| ITEM_CATEGORY_CODES | 2 | 3 | 9 | This table defines the valid categories that can be assigned to an inventory item in the application |
| ITEM_CUST_HIST_VW | 24 | |||
| ITEM_CUSTODIES | 12 | 21 | This table stores the new custody information for an individual inventory item that was part of a CUSTODY_EVENT change in the application | |
| ITEM_CUSTODY_EVENTS | 3 | 1 | 7 | This table stores the event information for a selection of inventory items changing custody done in the application |
| ITEM_DESCRIPTOR_LOCATIONS | 2 | 7 | This table is not currently being used | |
| ITEM_DESCRIPTORS | 3 | 12 | 28 | This table stores the description information for inventory items added in the application. When adding multiple items in bulk, one descriptor row is created and linked to all the inventory item instances |
| ITEM_DESCRIPTORS_VW | 35 | |||
| ITEM_ENTRIES | 1 | 2 | 11 | This table stores the information for inventory items added in the application. Inventory items are added as 1 piece or multiple pieces and a row is entered in the table for the transaction |
| ITEM_ENTRY_INSTANCES | 2 | 6 | This table stores the join between the inventory instances and the inventory entry. If inventory items are added in bulk, all instances created are joined to a single inventory entry | |
| ITEM_GUN_DESCRIPTORS | 7 | 12 | This table stores the gun specific attributes if the inventory item is a weapon added in the application | |
| ITEM_GUN_DESCRIPTORS_VW | 42 | |||
| ITEM_INSP_SEARCH_VW | 18 | |||
| ITEM_INSP_VW | 10 | |||
| ITEM_INSPECTION_ITEMS | 10 | 20 | This table stores the inventory items inspected during an inspection run in the application | |
| ITEM_INSPECTION_RUNS | 3 | 11 | This table stores the inventory inspection run details set up in the application | |
| ITEM_INSPECTIONS | 1 | 1 | 8 | This table stores inventory inspections set up in the application |
| ITEM_INST_CUSTODY_DESC_VW | 48 | |||
| ITEM_INST_CUSTODY_VW | 49 | |||
| ITEM_INST_ENT_ROLLUP_VW | 18 | |||
| ITEM_INST_ROLLUP_VW | 17 | |||
| ITEM_INSTANCES | 5 | 23 | 45 | This table stores the individual inventory items added in the application |
| ITEM_LINE_CODES | 1 | 2 | 8 | This table defines the valid line codes that can be assigned to an inventory item in the application |
| ITEM_LOCATION_MANAGERS | 2 | 7 | This table defines the managers for an agency assigned to an inventory location | |
| ITEM_LOCATIONS | 8 | 3 | 10 | This table defines the valid locations that can be assigned to an inventory item in the application |
| ITEM_LOG_ENTRIES | 6 | 12 | This table stores log entries for out of service and self checkout entries for inventory items in the application or manually entered log entries | |
| ITEM_LOG_VW | 14 | |||
| ITEM_MAKE_CODES | 4 | 2 | 8 | This table defines the valid make codes that can be assigned to an inventory item in the application |
| ITEM_MODEL_CODES | 3 | 2 | 8 | This table defines the valid model codes that can be assigned to an inventory item in the application |
| ITEM_ORDERS | 5 | 2 | 12 | This table stores the order information for inventory items as created in the application |
| ITEM_ORGANIZATIONS | 3 | 1 | 7 | This table stores the valid organizations that an inventory item can be sent to in the application |
| ITEM_QUANTITY_CODES | 3 | 3 | 9 | This table defines the valid quantity codes that can be used when creating inventory in the application |
| ITEM_SIZE_CODES | 1 | 2 | 8 | This table defines the valid size codes that can be assigned to an inventory item in the application |
| ITEM_STYLE_CODES | 2 | 3 | 9 | This table defines the valid style codes that can be assigned to an inventory item in the application |
| ITEM_SUB_LOCATIONS | 3 | 1 | 8 | This table defines the valid sub-locations (e.g. room #1, shelf A) for an inventory location that can be assigned to an inventory item in the application |
| ITEM_SUB_TYPE_CODES | 3 | 2 | 8 | This table defines sub types of an inventory type that can be added in the application (e.g. motorcycles, cars are sub-types of type vehicle) |
| ITEM_TYPE_CODES | 7 | 6 | This table defines the valid types of inventory that can be added in the application | |
| ITEM_VEHICLE_DESCRIPTORS | 2 | 8 | This table stores the vehicle specific attributes if the inventory item is a vehicle added in the application | |
| ITEM_VEHICLE_DESCRIPTORS_VW | 40 | |||
| ITEM_VENDORS | 6 | 1 | 18 | This table defines the valid vendors that can be added to the inventory order information when adding inventory in the application |
| IX_PERSON_SUMMARY_VW | 36 | |||
| JAIL_PEOPLE | 7 | 32 | This table stores birth places for a MASTER PERSON as entered in the application | |
| JS_BAIR_CFS_VW | 39 | |||
| JS_BAIR_MO_FIELDS_VW | 36 | |||
| JS_BAIR_PERSON_VW | 46 | |||
| JS_BASE64_IMAGES_VW | 7 | |||
| JS_CALLS_FOR_SERVICE_VW | 37 | |||
| JS_CITATION_VW | 74 | |||
| JS_CIVIL_PROCESS_LOG_VW | 25 | |||
| JS_CIVIL_PROCESS_PARTY_VW | 41 | |||
| JS_CIVIL_PROCESS_VW | 16 | |||
| JS_DOMESTIC_VIOLENCE_VW | 41 | |||
| JS_DS_NIBRS_ARRESTS_VW | 34 | |||
| JS_DS_NIBRS_GROUPB_VW | 34 | |||
| JS_DS_NIBRS_HEADERS_VW | 27 | |||
| JS_DS_NIBRS_OFFENDERS_VW | 26 | |||
| JS_DS_NIBRS_OFFENSES_VW | 30 | |||
| JS_DS_NIBRS_PROPERTY_VW | 30 | |||
| JS_DS_NIBRS_VICTIMS_VW | 37 | |||
| JS_EMULATION_HISTORY_VW | 4 | |||
| JS_EVIDENCE_VW | 89 | |||
| JS_FIELD_ARREST_CHARGE_VW | 74 | |||
| JS_FIELD_ARREST_VW | 64 | |||
| JS_FIELD_CONTACT_ADDRESS_VW | 31 | |||
| JS_FIELD_CONTACT_GANG_VW | 16 | |||
| JS_FIELD_CONTACT_OFFICERS_VW | 23 | |||
| JS_FIELD_CONTACT_VW | 40 | |||
| JS_FLEET_DASH_MAINT_VW | 15 | |||
| JS_FLEET_VEHICLES_VW | 33 | |||
| JS_INCIDENT_24HR_VW | 4 | |||
| JS_INCIDENT_ADDRESS_VW | 60 | |||
| JS_INCIDENT_CASE_SUMMARY_VW | 66 | |||
| JS_INCIDENT_CASE_VW | 81 | |||
| JS_INCIDENT_EVIDENCE_VW | 79 | |||
| JS_INCIDENT_OFFENSE_RANK_VW | 32 | |||
| JS_INCIDENT_OFFENSE_VW | 56 | |||
| JS_INCIDENT_OFFNDR_EVIDENCE_VW | 104 | |||
| JS_INCIDENT_PROPERTY_VW | 62 | |||
| JS_ODU_CLERY_VW | 10 | |||
| JS_OFFICER_DAILY_ACTIVITY_VW | 45 | |||
| JS_OFFICER_DAILY_EQUIPMENT_VW | 24 | |||
| JS_OFFICER_DAILY_VEHICLE_VW | 35 | |||
| JS_OFFICER_DAILY_VW | 84 | |||
| JS_PERMIT_BUSINESS_VW | 37 | |||
| JS_PERMIT_PEOPLE_VW | 37 | |||
| JS_PERMIT_PROPERTY_VW | 65 | |||
| JS_PERMIT_VEHICLE_VW | 61 | |||
| JS_PERMITS_VW | 34 | |||
| JS_SCHEDULING_VW | 34 | |||
| JS_USER_ASSIGNMENT_VW | 31 | |||
| JS_USERS_VW | 28 | |||
| JS_VEHICLE_TOW_IMPOUND_VW | 55 | |||
| JS_WARRANT_OFFENSE_CHARGE_VW | 30 | |||
| JS_WARRANT_VW | 33 | |||
| JT_JAIL_FACILITIES | 3 | 8 | This table defines the Jail Tracker facilities and is used for querying JailTracker from the person search | |
| JT_WEB_SERVICES | 1 | 14 | This Table Defines the Jail Tracker Web Service Settings. It can be defined at the schema, Agency or Sub Agency Level | |
| JUDGES | 1 | 1 | 13 | Legacy table. This table is not currently used |
| K9_ACTIVITY | 5 | 14 | This table is not currently used | |
| K9_ATTACHMENTS | 1 | 10 | This table is not currently used | |
| K9_BREED_CODES | 1 | 3 | This table is not currently used | |
| K9_CLINIC_CODES | 3 | This table is not currently used | ||
| K9_DEPLOYMENT | 5 | 19 | This table is not currently used | |
| K9_DOGS | 5 | 3 | 15 | This table is not currently used |
| K9_DOGS_VW | 7 | |||
| K9_IMAGES | 1 | 9 | This table is not currently used | |
| K9_MEDICAL | 13 | This table is not currently used | ||
| K9_MISC_IDS | 8 | 17 | This table is not currently used | |
| K9_TRAINING | 4 | 14 | This table is not currently used | |
| LANGUAGES | 7 | 17 | This table stores the languages associated with a MASTER PERSON in the application | |
| LEGAL_SEARCH_ADDRESSES | 2 | 8 | This table is not currently used | |
| LEGAL_SEARCH_INDEX | 2 | 9 | 20 | This table is not currently used |
| LEGAL_SEARCH_PEOPLE | 1 | 10 | This table is not currently used | |
| LIENHOLDERS | 5 | 19 | This table store lien information for a lien placed on a MASTER VEHICLE in the application | |
| LSI_ADDRESSES_VW | 46 | |||
| LSI_PEOPLE_VW | 29 | |||
| LSI_VW | 26 | |||
| MAP_EVENT_TYPE_CODES | 3 | 10 | Stores different map event types which can be selected by the user | |
| MAP_EVENT_TYPES_TEMP | 2 | Temporary table used for querying on map event types. | ||
| MAP_EVENT_VW | 11 | |||
| MAP_ICONS | 4 | 10 | Stores information needed to generate icons for mapping. | |
| MAP_SHAPE_ADDRESSES | 2 | 6 | Indexes shapes to addresses. | |
| MAP_SHAPE_POINTS | 1 | 4 | This table is used for mapping and a shape is defined for an agency on the agency admin page | |
| MAP_SHAPE_USERS | 4 | 8 | Relates map shapes to users as to assign service areas | |
| MAP_SHAPES | 3 | 3 | 11 | This table is used for mapping and a shape is defined for an agency on the agency admin page |
| MAP_USER_SCREENS | 8 | 13 | Allows custom forms to be set up for use in RMS mapping. | |
| MAPPED_ARREST_CHARGES_VW | 2 | |||
| MAPPED_CITY_STATE_CODES_VW | 2 | |||
| MAPPED_ETHNICITY_ST_CODES_VW | 2 | |||
| MAPPED_RACE_STATE_CODES_VW | 2 | |||
| MAPPING_TYPE_CODES | 2 | 6 | This table defines the type of mapping being used in EJS_STATE_CODE_MAPPINGS | |
| MASTER_INDEX_DELETE_LOG | 10 | This table logs master index records that have been deleted. | ||
| MASTER_INDEX_SECURITY_CODES | 7 | 8 | This table defines the different security levels used for each of the master indexes | |
| MASTER_INDX_AUDITING | 11 | Legacy table. This table is not currently used | ||
| MASTER_NAMES | 14 | 5 | 19 | This tables stores names added to a MASTER PERSON in the application |
| MASTER_PEOPLE | 3 | 8 | 20 | This table stores the MASTER PERSON information added in the application |
| MASTER_PEOPLE_NOT_DUPLICATES | 2 | 8 | This table stores people that are similar but have been flagged as not duplicates so they don't accidentally get collapsed into one | |
| MASTER_PERSON_TEMP | 2 | Global Temp Table For Master Person IDs | ||
| MASTER_REPORT_PREFERENCES | 1 | 4 | 13 | Master Report Preferences Header, Footer, Alignment |
| MASTER_REPORT_REFERENCES | 3 | 8 | Master Report References for Report References (Header/Footer) Can be Agency Specific | |
| MASTER_REPORTS | 11 | 3 | 16 | This table defines the master reports that can be generated fro the Forms and Reports module in the application |
| METHOD_CODES | 1 | 5 | This table defines the valid method codes that can be added to a citation in the application | |
| MICR_INCIDENT_HEADER_VW | 27 | |||
| MILITARY_SERVICE | 8 | 19 | This table stores military service information added to a MASTER PERSON in the application | |
| MILITARY_STATUS_CODES | 1 | 5 | This table defines the valid status codes for military service added to a MASTER PERSON in the application | |
| MISC_ID_CLASS_CODES | 2 | 1 | 4 | This table defines the valid class codes for miscellaneous ids |
| MISC_ID_CLASSES | 6 | 11 | This table stores the class information for a miscellaneous id added to a MASTER PERSON in the application | |
| MISC_ID_CODES | 6 | 5 | This table defines the valid codes for miscellaneous ids | |
| MISC_ID_REST_CODES | 2 | 1 | 4 | This table defines the valid restriction codes for a miscellaneous id |
| MISC_ID_RESTRICTIONS | 6 | 11 | This table stores restriction information for miscellaneous ids added to a MASTER PERSON in the application | |
| MISC_IDS | 12 | 8 | 18 | This table stores miscellaneous identifiers added to a MASTER PERSON in the application (e.g. passport number, air force serial number) |
| MO_INCIDENT_OFFENSE_VW | 12 | |||
| MO_MEANS_CODES | 1 | 5 | This table defines the valid means codes for modus operandi on an offense added to an INCIDENT in the application | |
| MO_METHOD_OF_ENTRY_CODES | 1 | 5 | This table defines the valid method of entry codes for modus operandi on an offense added to an INCIDENT in the application | |
| MO_POINT_OF_ENTRY_CODES | 1 | 5 | This table defines the valid point of entry codes for modus operandi on an offense added to an INCIDENT in the application | |
| MO_POINT_OF_EXIT_CODES | 1 | 5 | This table defines the valid point of exit codes for modus operandi on an offense added to an INCIDENT in the application | |
| MO_TRADEMARK_CODES | 1 | 5 | This table defines the valid trademark codes for modus operandi on an offense added to an INCIDENT in the application | |
| MODUS_OPERANDI | 11 | 18 | This table stores the modus operandi associated with an offense added to an INCIDENT in the application | |
| MY_CASE_SEARCH_VW | 18 | |||
| N_INCIDENT_PERSON_OFFENSES_VW | 52 | |||
| NARRATIVE_SEARCH_ACCESS | 2 | 7 | This table is not currently used | |
| NARRATIVE_SEARCH_RESULTS | 15 | This table is not currently used | ||
| NARRATIVE_SEARCHES | 1 | 21 | This table is not currently used | |
| NARRATIVE_TEMP_OFFENSES | 2 | 6 | This table maps offense codes to narrative templates | |
| NARRATIVE_TEMPLATES | 1 | 6 | 13 | This table defines the narrative templates that can be added to an INCIDENT or field ARREST in the application |
| NEGOTIABLE_INSTRUMENT_CODES | 4 | Legacy table. This table is not currently used | ||
| NEW_NOTIFICATIONS_VW | 14 | |||
| NIBR_SUBMISSION_FORMAT_TYPES | 1 | 2 | 6 | Legacy table. This table is not currently used |
| NIBRS_CODE_EJS_MAPPINGS | 3 | 3 | 8 | This table stores the acceptable values for drop down lists when completing an INCIDENT. For example, the NIBRS Code of 200 can only have specific Bias Codes available. When completing an INCIDENT report the application will query this table and only present values that are valid for the defined offense. If only one value can be reported the value will be defaulted and the user will not be required to select the value |
| NIBRS_CODES | 7 | 5 | 9 | This table defines the valid NIBRS Codes |
| NIBRS_CRIME_TARGETS | 3 | 4 | This table defines the target entity for a given NIBRS offense. For example, a NIBRS offense of 13A is a crime against a PERSON | |
| NIBRS_DATE_RECOV_REQ_VW | 6 | |||
| NIBRS_EST_DRUG_QUANT_REQ_VW | 6 | |||
| NIBRS_LESSER_OFFENSES | 2 | 7 | This table defines the lesser included NIBRS offenses | |
| NIBRS_OFFENSES | 2 | 7 | This table defines the state offense code and related NIBRS offense | |
| NIBRS_PROP_LOSS_VW | 6 | |||
| NIBRS_PROP_MAPPINGS | 5 | 11 | This table defines valid property types based on the given NIBRS offense and attempted or completed values or property status codes | |
| NIBRS_PROP_VALUE_REQ_VW | 6 | |||
| NIBRS_TAB_COLS | 4 | 20 | This is a system table used by the application for dynamically presenting lists of values for a related NIBRS offense | |
| NOTIFICATION_AUDITS | 2 | 18 | Stores audited notification data | |
| NOTIFICATION_DEF_MASTERS | 9 | 3 | 25 | This table defines the behavior of a notification and is a template used when creating a notification |
| NOTIFICATION_DETAILS | 3 | 2 | 23 | This table stores the actual notifications sent to users and is accessible from the home page |
| NOTIFICATION_DETAILS_DATA | 1 | 7 | This table stores data as a clob for any extra data too large for the NOTIFICATION_DETAILS table | |
| NOTIFICATION_DTL_ROLES | 2 | 7 | This table defines the roles that are able to access a sent notification | |
| NOTIFICATION_TYPES | 3 | 7 | This table defines the types of notifications that can be sent from the application | |
| NOTIFY_DETAIL_DISABLE_ALERTS | 2 | 7 | This table defines the notification alerts that are to be disabled. This is available by selecting the flashing notifications when new ones arrive and select disable | |
| NOTIFY_PRIORITY_CODES | 2 | 9 | This table defines the different types of priorities available to assign a notification when creating a new notification template | |
| NOTIFY_ROLES | 2 | 5 | This table defines the roles in which a notification will be sent when created | |
| OFFENDER_REQQUES_VW | 3 | |||
| OFFENDER_SUSPICIONS | 5 | 11 | This table stores suspicion information added to an offender on an INCIDENT in the application | |
| OFFENSE_ACTIVITIES | 5 | 11 | This table stores activity information added to an offense on an INCIDENT in the application | |
| OFFENSE_ANSWER | 12 | |||
| OFFENSE_ANSWER1 | 13 | |||
| OFFENSE_CIRCUMSTANCES | 6 | 12 | This table stores circumstance information added to an offense on an INCIDENT in the application | |
| OFFENSE_CODES | 14 | 1 | 14 | This table defines the offense codes to be used on INCIDENTS in the application |
| OFFENSE_COND_QANSCHOICES_VW | 8 | |||
| OFFENSE_CONDITIONAL_QUES_VW | 7 | |||
| OFFENSE_GANGS | 5 | 11 | This table stores the association for MASTER GANGs and offenses on an INCIDENT | |
| OFFENSE_GROUP_OFFENSES | 2 | 8 | This table stores Offense Groups. | |
| OFFENSE_GROUPS | 1 | 1 | 8 | This table stores Offense Groups. |
| OFFENSE_HOMICIDE_CIRCUMSTANCES | 6 | 12 | This table stores homicide circumstances for an offense added to an INCIDENT in the application | |
| OFFENSE_REQQUES_VW | 4 | |||
| OFFENSE_SPREADSHEET_VW | 20 | |||
| OFFENSE_STATUS_CODES | 4 | 2 | 5 | This table defines offense statuses and NIBRS clearance information to be used on offenses on an INCIDENT in the application |
| OFFENSES | 39 | 18 | 35 | This table stores offenses added to an INCIDENT supplement in the application |
| OFFICER_CASE_LOAD | 1 | 1 | 9 | This table stores the case load assigned to an officer in the application |
| OFFICER_CASE_LOAD_BY_MONTHS | 1 | 6 | This table is not currently used | |
| OFFICER_CASE_VW | 18 | |||
| OFFICER_COLLAPSE_LOG | 8 | This table stores log information for collapsing multiple officer rows into one | ||
| OFFICER_EMPLOYEE_VW | 12 | |||
| OFFICER_IDS_TEMP | 2 | Global Temp Table | ||
| OFFICER_INCIDENTS | 4 | 11 | This table stores the association of officers and role the officer plays when added to an INCIDENT in the application | |
| OFFICER_ROLE_CODES | 3 | 2 | 5 | This table defines the valid role codes to be assigned to an officer on an INCIDENT in the application |
| OFFICERS | 43 | 3 | 22 | This table stores officer information created in the application |
| ORG_DESCRIPTOR_CODES | 9 | This table defines the valid descriptors for organizations (referred to as agencies) in the application (e.g. State, District) | ||
| PARAMETER_INSTANCE_ATTRIBUTES | 1 | 10 | Administration table used for reporting | |
| PAWN_PROPERTIES | 3 | 9 | This table is not currently used | |
| PAWN_PROPERTY_VW | 35 | |||
| PAWN_TICKET_IMAGES | 3 | 10 | This table is not currently used | |
| PAWN_TICKETS | 4 | 2 | 12 | This table is not currently used |
| PEOPLE | 46 | 1 | 9 | This table stores the MASTER PERSON information added in the application |
| PEOPLE_ADDRESS_VW | 20 | |||
| PEOPLE_BUSINESSES | 4 | 12 | This table stores the association to a MASTER PERSON added to a MASTER BUSINESS along with the role in the application | |
| PEOPLE_COMBO_ADDR_PHONES_VW | 41 | |||
| PEOPLE_COMBO_ADR_PH_VW | 41 | |||
| PEOPLE_COMBO_ADR_VW | 41 | |||
| PEOPLE_COMBO_PH_VW | 41 | |||
| PEOPLE_COMBO_VW | 57 | |||
| PEOPLE_JAIL_SEARCH_VW | 56 | |||
| PEOPLE_MASTER_NAME_VW | 17 | |||
| PEOPLE_MISC_ID_VW | 8 | |||
| PEOPLE_PHONE_VW | 11 | |||
| PEOPLE_PHYS_DESC_VW | 15 | |||
| PEOPLE_PROPERTIES | 4 | 10 | This table stores the association to a MASTER PERSON added to a MASTER PROPERTY along with the role in the application | |
| PEOPLE_PROPERTY_VW | 38 | |||
| PEOPLE_RELATIONS | 8 | 22 | This table stores the association between multiple MASTER PEOPLE with a relationship code | |
| PEOPLE_SEARCH_ONEADDRESS_VW | 56 | |||
| PEOPLE_SEARCH_VW | 46 | |||
| PEOPLE_SMT_VW | 8 | |||
| PEOPLE_VEHICLE_VW | 17 | |||
| PEOPLE_VEHICLES | 4 | 10 | This table stores the association to a MASTER PERSON added to a MASTER VEHICLE in the application | |
| PEOPLE_WARRANTS | 5 | 12 | This table stores the association to a MASTER PERSON added to a warrant in the application | |
| PERMIT_ATTACHMENTS | 2 | 10 | This table stores attachments added to a permit | |
| PERMIT_BUSINESSES | 4 | 11 | This table stores the association of a permit added to a MASTER BUSINESS in the application | |
| PERMIT_BUSINESSES_VW | 22 | |||
| PERMIT_IMAGES | 2 | 9 | This table stores image attachments added to permits | |
| PERMIT_PEOPLE | 4 | 11 | This table stores the association of a permit added to a MASTER PERSON in the application | |
| PERMIT_PEOPLE_VW | 24 | |||
| PERMIT_PROPERTIES | 2 | 9 | This table stores the association of a permit added to a MASTER PROPERTY in the application | |
| PERMIT_PROPERTIES_VW | 45 | |||
| PERMIT_VEHICLES | 2 | 10 | This table stores the association of a permit added to a MASTER VEHICLE in the application | |
| PERMIT_VEHICLES_VW | 38 | |||
| PERMITS | 7 | 9 | 29 | This table store the permit information created in the application |
| PERSON_ADDR_HISTORY | 2 | 15 | This table stores the history of MASTER ADDRESSES added over time to a MASTER PERSON in the application | |
| PERSON_ADDR_PHONES | 1 | 8 | This table stores phone numbers associated with a specific address added to a MASTER PERSON in the application | |
| PERSON_ADDRESSES | 5 | 18 | This table stores the association to MASTER ADDRESSES added to a MASTER PERSON in the application | |
| PERSON_ASSOC_CNT_VW | 3 | |||
| PERSON_ATTACHMENTS | 4 | 11 | This table stores attachments added to a MASTER PERSON in the application | |
| PERSON_CAUTIONS | 3 | 14 | This table stores caution codes added to a MASTER PERSON in the application | |
| PERSON_CAUTIONS_VW | 11 | |||
| PERSON_COLLAPSE_LOG_VW | 14 | |||
| PERSON_DUP_SEARCH_VW | 16 | |||
| PERSON_FINGERPRINTS | 4 | 9 | This table stores fingerprints captured for a MASTER PERSON in the application | |
| PERSON_FINGERPRINTS_VW | 7 | |||
| PERSON_GEO_VW | 12 | |||
| PERSON_IMAGES | 4 | 13 | This table stores the link to images added to a MASTER PERSON in the application. The image itself is stored in IMAGES | |
| PERSON_INDICATOR_VW | 19 | |||
| PERSON_SPECIAL_NEEDS | 3 | 9 | This table stores special needs information added to a MASTER PERSON in the application | |
| PERSONNEL_CERT_SEARCH_VIEW | 42 | |||
| PERSONNEL_COURSE_SEARCH_VIEW | 52 | |||
| PERSONNEL_SEARCH_VIEW | 37 | |||
| PHONES | 5 | 4 | 16 | This table stores phone numbers added to a MASTER PERSON in the application |
| PHOTO_LINEUP | 2 | 1 | 10 | This table is used to store Photo Linups created by users |
| PHOTO_LINEUP_CASES | 2 | 8 | Associates Photo Lineups To a Case | |
| PHOTO_LINEUP_DELETE | 2 | 12 | This table is used to store photo linup delete log | |
| PHOTO_LINEUP_IMAGE_TEMP | 4 | PHOTO_LINEUP_IMAGE_TEMP | ||
| PHOTO_LINEUP_IMAGES | 2 | 10 | This table is used to store Images that are a part of a photo lineup | |
| PHOTO_LINEUP_LIBRARY | 1 | 7 | General use images for photo lineups. | |
| PHYDESC_PERIMAGE_VW | 15 | |||
| PHYSICAL_DESC_SEARCH_VW | 27 | |||
| PHYSICAL_DESCRIPTIONS | 1 | 15 | 26 | This tables stores the physical description entered for a MASTER PERSON in the application |
| PLAN_TABLE | 21 | This table is not currently used | ||
| PLANTIFF_CODES | 5 | This table defines the valid plaintiff codes for warrants | ||
| POD_AFFILIATES | 2 | 7 | TABLE LINKING AFFILATE CODES TO PSEUDO ORG DESCRIPTORS | |
| PRINT_OPTION_VALUES | 3 | 9 | This table defines the print options and templates when printing an INCIDENT report | |
| PRINT_TEMPLATE_OPTIONS | 3 | 3 | 7 | This table defines the sections of an INCIDENT included in each print template for printing an INCIDENT in the application |
| PRINT_TEMPLATES | 1 | 3 | 11 | This table defines the print templates supported for printing INCIDENTS in the application |
| PROFILE_SCREEN_ITEM_PARAMS | 2 | 8 | This is an application table used to support the home page custom layout settings | |
| PROFILE_SCREEN_ITEMS | 1 | 2 | 10 | This table defines custom screen setup. Users have the ability customize their home page and this table stores the settings |
| PROPERTIES | 17 | 21 | 51 | This table stores the property information for MASTER PROPERTIES added in the application |
| PROPERTIES_ASSOC_CNT_VW | 3 | |||
| PROPERTIES_AUDIT | 51 | This table stores audit information for MASTER PROPERTIES | ||
| PROPERTIES_NOT_DUPLICATES | 2 | 8 | This table stores property that are similar but have been flagged as not duplicates so they don't accidentally get collapsed into one | |
| PROPERTY_ATTACHMENTS | 2 | 10 | This tables stores attachments added to a MASTER PROPERTY in the application | |
| PROPERTY_CASH | 3 | 12 | This table stores cash amount and quantity added to a MASTER PROPERTY in the application | |
| PROPERTY_DETAIL_TYPE_CODES | 1 | 5 | This table defines the detail type codes for details added to a MASTER PROPERTY in the application | |
| PROPERTY_DETAILS | 2 | 10 | This table stores additional details added to a MASTER PROPERTY in the application | |
| PROPERTY_DETAILS_VW | 29 | |||
| PROPERTY_HOLD_CUSTODIES | 4 | 11 | Stores Chain of Custody Information for Properties | |
| PROPERTY_HOLD_LOCATIONS | 1 | 1 | 8 | Stores Location Definitions for Property Locations |
| PROPERTY_HOLD_SEARCH_VW | 60 | |||
| PROPERTY_HOLDS | 2 | 8 | 20 | Driving Table for Property Lost and Found |
| PROPERTY_IMAGES | 2 | 9 | This table stores the link to images added to the MASTER PROPERTY in the application. The image is stored in IMAGES | |
| PROPERTY_INV_ROLE_CNT_VW | 3 | |||
| PROPERTY_REQQUES_VW | 3 | |||
| PROPERTY_RMS_SEARCH_VW | 70 | |||
| PROPERTY_SEARCH_VW | 55 | |||
| PROPERTY_TYPE_CODES | 1 | 4 | 8 | This table defines the valid type codes assigned to a MASTER PROPERTY in the application |
| PROPERTY_TYPE_DRUGS_VW | 4 | |||
| PROPERTY_TYPE_GUNS_VW | 4 | |||
| PROPERTY_TYPE_NOT_DRUG_GUN_VW | 4 | |||
| PROPERTY_XREFS | 2 | 9 | This table stores external ids for a property from external applications or interfaces. Data is uploaded through the Property XML import | |
| PSEUDO_ORG_DESCRIPTORS | 4 | 1 | 18 | TABLE CONTAINING ORGANIZATIONAL MAPPING INFORMATION AND ESTABLISHING THE HIERARCHICAL RELATIONSHIP OF ENTRIES IN THE AGENCY_CODES TABLE AND THE AFFILIATES TABLE - AKA: POD |
| PW_INCIDENT_ADDRESS_VW | 31 | |||
| QUESTION_ANSWERS | 1 | 1 | 9 | This table defines the answer choices for a custom question that can be associated with different modules in the application |
| QUESTION_TYPES | 1 | 5 | 12 | This table defines the valid types of questions and the module the questions are associated with |
| QUESTION_TYPES_VW | 10 | |||
| QUESTIONS | 2 | 1 | 8 | This table defines the custom questions that can be associated with different modules in the application |
| QUICK_LINK_USERS | 2 | 7 | This table stores quick links that a user decides to use and enable for use on the home page | |
| QUICK_LINKS | 1 | 5 | 15 | This table defines the quick links that can be displayed on the home page of the application |
| RELATED_ORGS_VW | 2 | |||
| RELEASE_TYPE_CODES | 6 | This table is not currently used | ||
| REPORT_AGENCIES | 2 | 6 | This table defines the reports that are valid for an agency within the Forms and Reports module in the application | |
| REPORT_CATEGORIES | 1 | 8 | This table defines the categories of reports displayed in the Forms and Reports module in the application | |
| REPORT_IMAGES_REPO | 1 | 6 | Reporting table to store images | |
| REPORT_JAVA_TYPES | 4 | 7 | Administration table used for reporting | |
| REPORT_OUTPUT_TYPE_CODES | 1 | 11 | This table defines the valid output types for printing a report within Forms and Reports module in the application (e.g. PDF) | |
| REPORT_OUTPUT_TYPES | 3 | 9 | This table stores the selected output type for a report printed from the application | |
| REPORT_PARAMETER_GROUPS | 1 | 1 | 11 | Administration table used for reporting |
| REPORT_PARAMETER_INSTANCES | 2 | 7 | 23 | Administration table used for reporting |
| REPORT_PARAMETER_J_SCREENS | 2 | 7 | Administration table used for reporting | |
| REPORT_PARAMETER_LISTS | 2 | 9 | Administration table used for reporting | |
| REPORT_PARAMETER_VALUES | 1 | 8 | Administration table used for reporting | |
| REPORT_ROLE_SECURITY | 2 | 7 | Administration table used for reporting | |
| REPORT_SCREEN_PARAMETERS | 1 | 4 | 12 | Administration table used for reporting |
| REPORT_SCREEN_REPORTS | 2 | 8 | Administration table used for reporting | |
| REPORT_SCREENS | 2 | 10 | Administration table used for reporting | |
| REPORT_SECTION_CODES | 1 | 5 | Administration table used for reporting | |
| REPORT_SP_PARAMETERS | 1 | 12 | Administration table used for reporting | |
| REPORT_STORED_PROCEDURES | 2 | 10 | Administration table used for reporting | |
| REPORT_UNIT_IMAGES | 2 | 6 | Administration table used for reporting | |
| REPORT_UNIT_RELATIONS | 2 | 6 | Administration table used for reporting | |
| REPORT_UNITS | 4 | 11 | Administration table used for reporting | |
| REPORT_USER_PARAMETERS | 3 | 12 | Administration table used for reporting | |
| RESTRICTION_LISTS | 4 | 10 | A TABLE THAT REPRESENTS A LIST OF USERS LINKED TO ORGANIZAITONAL OBJECTS THAT SPECIFIES THAT THEY ARE EITHER INCLUDED AS THE USER WHO CAN GAIN VIEW OR UPDATE ACCESS TO THAT OBJECT OR THEY ARE INCLUDED AS USER WHO ARE DENIED ACCESS TO THE OBJECT FOR ANY REASON | |
| RESULT_ACTIVITY_CODES | 2 | 8 | Legacy table. This table is not currently used | |
| RMS_ALERTS | 6 | Administration table used for database alerting and configuration | ||
| ROAD_CONDITION_CODES | 1 | 5 | This table is not currently used | |
| ROLE_CODES | 3 | 2 | 8 | This table defines the valid roles codes to be used for people and organizations on an INCIDENT in the application |
| ROLE_SECUR_PERMISSIONS | 2 | 7 | This table defines the application permissions associated with a role that is then assigned to a user created by administrators of the application | |
| ROLE_SECURITIES | 21 | 2 | 8 | This table defines the valid roles that can be assigned to a user created by administrators of the application |
| ROUTE_ACT_INST_USR_ROLES | 2 | 6 | This table stores an instance of the notification routing information for a custom form | |
| ROUTE_ACTION_AGENCIES | 2 | 6 | This table defines the valid routing actions for an agency for routing custom form notifications | |
| ROUTE_ACTION_INST_AGENCIES | 2 | 7 | This table stores roles assigned to a route action instance | |
| ROUTE_ACTION_INST_ROLES | 2 | 7 | This table stores roles assigned to a route action instance | |
| ROUTE_ACTION_INST_USERS | 2 | 5 | 10 | this table stores the user and notification instance information for a custom form |
| ROUTE_ACTION_INSTANCES | 4 | 5 | 10 | This table stores the instances of a notification routing for a custom form |
| ROUTE_ACTION_ROLES | 2 | 6 | This table defines the roles allowed to use a routing action when routing a custom form notification | |
| ROUTE_ACTION_USERS | 2 | 6 | This table defines the users allowed to use a routing action when routing a custom form notification | |
| ROUTE_ACTIONS | 5 | 2 | 15 | This table defines routing actions for routing custom form notifications |
| ROUTE_INSTANCE_AGENCIES | 2 | 7 | Stores Agencies selected by the user when Sending a forms out for review | |
| ROUTE_INSTANCE_ROLES | 2 | 7 | Stores Agencies selected by the user when Sending a forms out for review | |
| ROUTE_INSTANCES | 5 | 3 | 8 | This table stores the instances of notification routes for a custom form |
| ROUTE_TEMPLATES | 4 | 2 | 7 | This table defines the routing templates for a custom form notification |
| RV_ACCESS_CHAIN_NODES | 2 | 7 | This table stores individual chain identifiers in an access chain | |
| RV_ACCESS_CHAINS | 2 | 5 | This table stores chains of accessors so objects can be accessed by rules and validations | |
| RV_ACCESSOR_FIELD_TYPES | 3 | 7 | This table associates custom field types with accessors so they may be validated against | |
| RV_ACCESSOR_OBJECTS | 1 | 6 | This table stores root accessor objects. It exists simple to cross reference values in RV_ACCESSORS with their corresponding object | |
| RV_ACCESSORS | 9 | 9 | 21 | This table stores a hierarchical structure which defines objects that can be validated by the Rules & Validations Engine |
| RV_AGENCY_CONDITIONS | 2 | 6 | Associates Conditions with Agencies | |
| RV_AGENCY_OVERRIDES | 2 | 6 | Disables conditions for child agencies | |
| RV_ATTRIBUTES | 2 | 11 | Attributes For Rules | |
| RV_COND_PROP_ATTRIBUTES | 3 | 10 | Associates Attributes with Condition Properties | |
| RV_COND_PROP_OBJ_VAR_VALUES | 2 | 7 | This table associates variable values with custom validations | |
| RV_COND_PROP_VAR_VALUES | 3 | 8 | Stores variable values for a specific condition property | |
| RV_CONDITION_FACTORS | 1 | 7 | 13 | Associates Conditions With Factors |
| RV_CONDITION_PROPERTIES | 3 | 5 | 11 | Associates properties with conditions |
| RV_CONDITIONS | 5 | 4 | 12 | Stores Conditions for Rules and Validations |
| RV_CUSTOM_OBJECT_VARIABLES | 2 | 6 | This table stores custom object variables | |
| RV_CUSTOM_OBJECTS | 2 | 3 | 14 | This table stores data about custom validations implemented in the Java code for RMS |
| RV_DATA_SOURCE_CODES | 3 | 7 | Data Sources | |
| RV_FACTORS | 5 | 13 | Condition Factors | |
| RV_MODULE_CODES | 7 | 2 | 8 | Stores modules using field validations |
| RV_MODULE_SCREEN_TYPES | 2 | 7 | This table associates modules with custom from types | |
| RV_NATURE_ATTRIBUTES | 2 | 6 | Associates Attributes with certain natures | |
| RV_NATURE_CODES | 7 | 6 | Nature Codes | |
| RV_NATURE_OPERATORS | 2 | 6 | Joins Natures with Operators | |
| RV_OPERATOR_CODES | 3 | 7 | Factor Operators | |
| RV_PROPERTIES | 1 | 2 | 12 | Properties |
| RV_PROPERTY_VARIABLES | 2 | 1 | 6 | Joins Properties to Variables |
| RV_VARIABLES | 2 | 1 | 7 | Rule Variables |
| SAFETY_INSPECTIONS | 1 | 11 | Legacy table. This table is not currently used | |
| SALARY | 3 | 17 | Legacy table. This table is not currently used | |
| SCHEDULES | 1 | 4 | 33 | This table stores schedules created in the scheduling module in the application |
| SCREEN_ITEM_PARAMETERS | 1 | 1 | 9 | Legacy table. This table is not currently used |
| SCREEN_ITEMS | 2 | 3 | 13 | Legacy table. This table is not currently used |
| SCREEN_TYPE_RPT_INCLUDES | 2 | 6 | This table is used for custom reports | |
| SCREEN_TYPE_SCREEN_PDF_FIELDS | 2 | 9 | Fields for fillable PDFS | |
| SCREEN_TYPE_SCREEN_PDFS | 1 | 3 | 10 | Associates Fillable PDFs with Custom Forms |
| SCREEN_TYPE_SCREEN_RPTS | 3 | 7 | This table is used for custom reports | |
| SCREEN_TYPE_SCREENS | 6 | 5 | 9 | This table maps custom forms from USER_SCREENS to a SCREEN_TYPE (e.g. Incident, Field Arrest) in order for the application to know where to associate the custom form |
| SEARCH_AGENCIES | 2 | 7 | Legacy table. This table is not currently used | |
| SEARCH_BOOSTS | 9 | This table is used to boost master index search results | ||
| SEARCH_INT_FORM_TYPES | 4 | 11 | This table defines the different types of search types for external searches | |
| SEARCH_INT_RESULTS_ACCESS | 9 | This table tracks who accessed cached results of external system searches | ||
| SEARCH_INTERFACE_FIELD_MAPS | 6 | 12 | This table defines which fields are needed for given search interfaces | |
| SEARCH_INTERFACE_GROUPS | 3 | 7 | This table groups multiple external search interfaces into categories | |
| SEARCH_INTERFACE_RESULTS | 3 | 11 | This table stores raw results of external system searches for the purpose of caching these results | |
| SEARCH_INTERFACE_VALIDATORS | 1 | 3 | 10 | This table defines the the search interface validations |
| SEARCH_INTERFACES | 5 | 8 | 22 | This table defines the different types of searches available |
| SERIALIZED_OBJECTS | 8 | Legacy table. This table is not currently used | ||
| SMTS | 5 | 14 | This table stores the Scars, Marks, and Tatoos for a MASTER PERSON created in the application | |
| SOLR_ASYNC_SETTINGS | 6 | Stores configuration settings for SOLR Updates. Each column value can be Y, N, or D | ||
| SOLR_LOG | 12 | Administrative table for logging solr searches | ||
| SOLR_UPDATE_ID_TMP | 7 | Temporary table for queueing SOLR updates. | ||
| SOLR_XSLT_FUNCTIONS | 2 | SOLR style sheet. Application table | ||
| SPEED_LIMIT_FINES | 3 | This table defines the fine association with speed limit values | ||
| STAGING_OFFENSES | 20 | This table serves as a staging area for the offense management/mass update functions | ||
| STATE_DISTRICT_CODES | 1 | 10 | This table defines state district codes used for citations | |
| STATE_LICENSE_FORMATS | 4 | 5 | This table defines the license plate formats for each state | |
| SUB_AGENCIES | 4 | 6 | This table defines sub agencies for an agency | |
| SUB_BEAT_CODES | 1 | 1 | 6 | This table defines sub beat codes within an agency |
| SUB_BEAT_POINTS | 1 | 4 | Legacy table. This table is not currently used | |
| SUBSCRIPTION_ACTIONS | 3 | 8 | This table stores the actions selected for a user subscription to a master indices | |
| SUBSCRIPTION_NOTIFY_METHODS | 3 | 10 | This table stores the notify methods selected for a user subscription to a master indices | |
| SUBSCRIPTION_TYPE_CODES | 1 | 1 | 10 | This table defines a subscription type for each master indices type |
| SUBSCRIPTIONS | 3 | 2 | 11 | This table stores user subscriptions to master indices |
| SUBSCRIPTIONS_QUEUE | 1 | 9 | This table stores notification queue entries for user subscriptions to a master indices | |
| SUSPECT_QUERY_VW | 4 | |||
| TABLE_ADMIN_AUDIT | 1 | 6 | This table audits all actions taken via the table administration module including inserts, updates, and deletes | |
| TAG_CASES | 2 | 7 | Stores Tagged Cases | |
| TAGS | 1 | 1 | 7 | Table to Hold Generic Tags for Tagging Records |
| TDEX_RMS_ARREST_VW | 30 | |||
| TDEX_RMS_ARRESTEE_VW | 72 | |||
| TDEX_RMS_CITATION_VW | 93 | |||
| TDEX_RMS_COMPLAINANT_VW | 47 | |||
| TDEX_RMS_DRUG_VW | 15 | |||
| TDEX_RMS_INCIDENT_VW | 35 | |||
| TDEX_RMS_NARRATIVE_VW | 16 | |||
| TDEX_RMS_OFFENSE_VW | 39 | |||
| TDEX_RMS_PROPERTY_VW | 21 | |||
| TDEX_RMS_SUSPECT_VW | 73 | |||
| TDEX_RMS_VEHICLE_VW | 25 | |||
| TDEX_RMS_VICTIM_VW | 56 | |||
| TDEX_RMS_WARRANT_CHARGES_VW | 19 | |||
| TDEX_RMS_WARRANT_VW | 82 | |||
| TDEX_RMS_WITNESS_VW | 41 | |||
| TEST_OUTCOME_CODES | 1 | 3 | Legacy table. This table is not currently used | |
| TOAD_PLAN_TABLE | 36 | |||
| TOW_COMPANY_CODES | 3 | 4 | 18 | This table stores the tow company information for a tow added to a vehicle in the application |
| TOW_REASONS | 4 | 9 | This table stores the reason for the tow added to a vehicle in the application | |
| TOWS | 4 | 7 | 25 | This table stores tow information added to a vehicle in the application |
| TRACE_ENTRIES | 1 | 12 | This table records every user request made and tracks user application screen requests | |
| TRACE_IGNORES | 6 | This table is used for Trace | ||
| TRACE_REQUEST_PARAMS | 1 | 4 | This table is used for Trace | |
| TRAINING_EXPIRED_CERT_VW | 10 | |||
| TRAINING_EXPIRED_COURSES_VW | 11 | |||
| TRAINING_TYPE_CODES | 1 | 7 | Legacy table. This table is not currently used | |
| TRAINING_UPCOMING_COURSES_VW | 7 | |||
| TRAININGS | 2 | 3 | 17 | Legacy table. This table is not currently used |
| TRANSACTION_CONTROL | 1 | TRANSACTION_CONTROL | ||
| UCR_ARRESTEES_GTT | 18 | This table is used for UCR Reporting | ||
| UCR_COL_TBL_GTT | 31 | This table is used for UCR Reporting | ||
| UCR_DISP_GTT | 5 | This table is used for UCR Reporting | ||
| UCR_HEADERS_GTT | 11 | This table is used for UCR Reporting | ||
| UCR_I_RANK_GTT | 9 | This table is used for UCR Reporting | ||
| UCR_LEOKA_BASE_GTT | 16 | This table is used for UCR Reporting | ||
| UCR_LEOKA_DISP_GTT | 3 | This table is used for UCR Reporting | ||
| UCR_LEOKA_DS_WEP_HIER_GTT | 15 | This table is used for UCR Reporting | ||
| UCR_LEOKA_ROOT_GTT | 4 | This table is used for UCR Reporting | ||
| UCR_LEOKA_VICTIM_GTT | 9 | This table is used for UCR Reporting | ||
| UCR_LEOKA_WEP_HIRE_GTT | 4 | This table is used for UCR Reporting | ||
| UCR_MOTO_GTT | 9 | This table is used for UCR Reporting | ||
| UCR_O_RANK_GTT | 10 | Temporary table of highest priority offenses for UCR Reporting | ||
| UCR_OFFENSES_GTT | 16 | Temporary table of offense data for UCR reporting | ||
| UCR_PIVOT_GTT | 64 | This table temporarily holds data from the NIBRS_PIVOT_VW for UCR reporting | ||
| UCR_PLOSS_GTT | 3 | This table is used for UCR Reporting | ||
| UCR_PROPERTY_GTT | 19 | Temporary table of property data for UCR Reporting | ||
| UCR_ROOT_DS_GTT | 20 | This table is used for UCR Reporting | ||
| UCR_ROOT_RANK_COL_2_GTT | 26 | This table is used for UCR Reporting | ||
| UCR_ROOT_RANK_COL_3_GTT | 1 | This table is used for UCR Reporting | ||
| UCR_ROOT_RANK_COL_4_GTT | 1 | This table is used for UCR Reporting | ||
| UCR_ROOT_RANK_COL_5_GTT | 1 | This table is used for UCR Reporting | ||
| UCR_ROOT_RANK_COL_6_GTT | 1 | This table is used for UCR Reporting | ||
| UCR_VICTIMS_GTT | 11 | This table is used for UCR Reporting | ||
| UF_QUERY_CHARGE_VW | 7 | |||
| UF_QUERY_DATE_VW | 5 | |||
| UF_QUERY_LOCATION_VW | 6 | |||
| UF_QUERY_NUMBER_VW | 5 | |||
| UF_QUERY_OFFENSE_VW | 6 | |||
| UF_QUERY_OFFICER_VW | 11 | |||
| UF_QUERY_ORGANIZATION_VW | 5 | |||
| UF_QUERY_PERSON_VW | 9 | |||
| UF_QUERY_PROPERTY_VW | 10 | |||
| UF_QUERY_TEXT_VW | 5 | |||
| UF_QUERY_VEHICLE_VW | 9 | |||
| UF_SUB_FORM_VW | 4 | |||
| UFI_FIELDARRESTS_ADDRESS_VW | 11 | |||
| UFI_FIELDARRESTS_CHARGE_VW | 11 | |||
| UFI_FIELDARRESTS_PERSON_VW | 11 | |||
| UFI_FIELDARRESTS_VEHICLE_VW | 11 | |||
| UFI_INCIDENTS_ADDRESS_VW | 11 | |||
| UFI_INCIDENTS_OFFENSE_VW | 11 | |||
| UFI_INCIDENTS_ORGANIZATION_VW | 11 | |||
| UFI_INCIDENTS_PERSON_VW | 11 | |||
| UFI_INCIDENTS_PROPERTY_VW | 11 | |||
| UFI_INCIDENTS_VEHICLE_VW | 11 | |||
| USER_AGENCIES | 2 | 8 | This table is not currently used | |
| USER_AGENCY_ACCESS_VW | 3 | |||
| USER_ASSIGNMENT_AGENCIES | 2 | 6 | This table defines the user's agencies that they are available for assignment. This is accessible from the user profile page as options for an assignment | |
| USER_DATA_FIELDS | 4 | 3 | 21 | This table is not currently used |
| USER_DEFINED_DATA | 2 | 14 | This table is not currently used | |
| USER_DEFINED_MODULES | 1 | 16 | This table is not currently used | |
| USER_FIELD_ADDR_VALUES | 2 | 7 | This table stores the values entered in the application for custom address type fields | |
| USER_FIELD_BUS_VALUES | 2 | 7 | This table stores the values entered in the application for custom business (referred to as an organization) type fields | |
| USER_FIELD_CHARGE_VALUES | 2 | 7 | This table stores the values entered in the application for custom charge code fields | |
| USER_FIELD_CODE_VALUES | 3 | 8 | This table stores the values entered in the application for custom code type fields | |
| USER_FIELD_DATE_VALUES | 1 | 7 | This table stores the values entered in the application for custom date type fields | |
| USER_FIELD_GROUPS | 1 | 1 | 9 | This table defines groups of fields on a custom form |
| USER_FIELD_INSTANCES | 14 | 2 | 8 | This table stores an instance of a custom field within the application |
| USER_FIELD_NUM_VALUES | 1 | 7 | This table stores the values entered in the application for custom number type fields | |
| USER_FIELD_OFF_VALUES | 3 | 8 | This table stores the values entered in the application for custom officer type fields | |
| USER_FIELD_OFFENSE_VALUES | 2 | 7 | This table stores the values entered in the application for custom offense code fields | |
| USER_FIELD_PER_VALUES | 4 | 8 | This table stores the values entered in the application for custom person type fields | |
| USER_FIELD_PROP_VALUES | 2 | 7 | This tables stores the values entered in the application for custom property type fields | |
| USER_FIELD_ROWS | 1 | 1 | 7 | This table defines rows of custom fields within groups on a screen in the application |
| USER_FIELD_SIG_VALUES | 2 | 7 | This table stores the values entered in the application for user field sig values. | |
| USER_FIELD_STR_VALUES | 1 | 7 | This table stores the values entered in the application for custom string type fields | |
| USER_FIELD_SUB_INST_VALUES | 2 | 8 | This table stores the values entered in the application for sub-instances of the custom fields | |
| USER_FIELD_VEH_VALUES | 2 | 7 | This table stores the values entered in the application for custom vehicle type fields | |
| USER_FIELDS | 11 | 13 | 33 | This table defines custom fields for an agency used throughout the application |
| USER_GROUP_USERS | 2 | 7 | Joins a user group to a user | |
| USER_GROUPS | 1 | 2 | 8 | Describes a generic group of users |
| USER_LOV_CODES | 2 | 11 | This table is not currently used | |
| USER_PINNED_RECORDS | 3 | 9 | Lookup table associating users to their pinned records | |
| USER_PROFILES_VW | 22 | |||
| USER_SCREEN_ADMINS | 2 | 6 | Defines who can edit a form other than the creator and others with certain privelages within the system | |
| USER_SCREEN_AGENCIES | 2 | 6 | This table determines what agencies have access to what forms. End User access, not administrative | |
| USER_SCREEN_AUDIT_LOG | 5 | 10 | This table stores log entries for a custom form added it the application | |
| USER_SCREEN_COMMENTS | 2 | 7 | 13 | This table stores the comment text added in a custom form comment-type field |
| USER_SCREEN_DELETE_AUDIT | 9 | Holds Audit Information on deleted custom forms, custom fields, and sub forms | ||
| USER_SCREEN_HEADER_FIELDS | 2 | 9 | This table defines the fields from the associated module (e.g. Incident, Field Arrest) to include when printing a custom form | |
| USER_SCREEN_HEADER_ROWS | 1 | 1 | 7 | This table defines header information from the associated module (e.g. Incident Field Arrest) to be included when printing a custom form |
| USER_SCREEN_HEADERS | 3 | 2 | 9 | This table defines header information from the associated module (e.g. Incident, Field Arrest) to be included when printing a custom form |
| USER_SCREEN_INST_ROUTES | 2 | 6 | This table stores routing information for notifications sent for comments added to an instance of a custom form in the application | |
| USER_SCREEN_INSTANCE_DELETE | 12 | This table stores custom from instance delete records. | ||
| USER_SCREEN_INSTANCES | 35 | 9 | 15 | This table stores instances of a custom form created by a user in the application |
| USER_SCREEN_MISC_NOTES | 5 | 10 | This table stores additional notes added on a custom form in the application | |
| USER_SCREEN_ROLES | 2 | 6 | This table defines the user roles that can access a custom form | |
| USER_SCREEN_TYPE_VIEWS | 2 | 6 | This table is used for custom form searches in the application | |
| USER_SCREEN_TYPES | 6 | 5 | 21 | This table defines the module type within the application that a custom form can be associated with (e.g. Incident, field ARREST) |
| USER_SCREEN_USER_PRIVS | 2 | 6 | This table stores users who have access to search/view/print instances of this form | |
| USER_SCREEN_VIEW_COLUMNS | 1 | 8 | This table is used for custom form searches in the application | |
| USER_SCREEN_VIEWS | 4 | 12 | This table is used for custom form searches in the application | |
| USER_SCREENS | 10 | 9 | 31 | This table defines custom forms to be used in the application |
| USER_SEARCH_INTERFACES | 2 | 9 | This table stores search interfaces available for a user. This is configured under agency admin | |
| USER_SEARCH_OPTIONS | 3 | 8 | Stores The search options the user can set to overide the agency default | |
| USI_ATTACHMENTS | 2 | 10 | This table stores attachments added to a custom form | |
| USI_CASE_ACTIVITIES | 2 | 6 | This table maps an instance of a case activity to the instance of the associated custom form | |
| USI_CASE_ACTIVITY_FIELDS | 2 | 6 | This table maps an instance of a case activity to the instance of the associated custom fields | |
| USI_CASE_FIELDS | 2 | 6 | This table maps an instance of a case to the instance of the associated custom fields | |
| USI_CASES | 2 | 6 | This table maps an instance of a case to the instance of the associated custom form | |
| USI_CITATION_FIELDS | 1 | 6 | This table maps an instance of a citation to the instance of the associated custom fields | |
| USI_CITATIONS | 2 | 6 | This table maps an instance of a citation to the instance of the associated custom form | |
| USI_COURT_PAPER_FIELDS | 2 | 6 | This table maps an instance of a court paper (referred to as Civil Process in the application) to the instance of the associated custom fields | |
| USI_COURT_PAPERS | 2 | 6 | This table maps an instance of a court paper (referred to as Civil Process in the application) to the instance of the associated custom form | |
| USI_CRIMINAL_COMPLAINT_FIELDS | 2 | 6 | This table maps an instance of a Criminal Complaint to the instance of the associated custom fields | |
| USI_CRIMINAL_COMPLAINT_FORMS | 2 | 6 | This table maps an instance of a Criminal Complaint to the instance of the associated custom form | |
| USI_DISPATCH_FIELDS | 2 | 6 | This table maps an instance of a field DISPATCH field to the instance of the associated custom fields | |
| USI_DV_ASSIGNMENTS | 2 | 6 | This table maps an instance of a Fleet Vehicle Assignment to the instance of the associated custom form | |
| USI_FI_FIELDS | 2 | 6 | This table maps an instance of a field interview (referred to as FIELD CONTACTS in the application) to the instance of the associated custom fields | |
| USI_FIELD_ARREST_FIELDS | 2 | 6 | This table maps an instance of a field ARREST field to the instance of the associated custom fields | |
| USI_FIELD_ARREST_VEH_FIELDS | 2 | 6 | This table maps an instance of a field ARREST vehicle to the instance of the associated custom fields | |
| USI_FIELD_ARRESTS | 2 | 6 | This table maps an instance of a field ARREST to the instance of the associated custom form | |
| USI_FIELD_INTERVIEWS | 2 | 6 | This table maps an instance of a field interview (referred to as FIELD CONTACTS in the application) to the instance of the associated custom form | |
| USI_FLEET_VEHICLE_FORMS | 2 | 6 | This table maps an instance of a fleet vehicle to the instance of the associated custom form | |
| USI_FLEET_VEHICLES | 2 | 6 | This table maps an instance of a fleet vehicle to the instance of the associated custom form | |
| USI_IMAGES | 2 | 9 | This table stores image attachments added to custom forms | |
| USI_IMPOUND_FIELDS | 2 | 6 | This table maps vehicle impounds to custom fields | |
| USI_INCIDENT_FIELDS | 2 | 6 | This table maps an instance of an INCIDENT to the instance of the associated custom fields | |
| USI_INCIDENT_PEOPLE | 2 | 6 | This table maps an instance of an INCIDENT person to the instance of the associated custom form | |
| USI_INCIDENT_PROPERTIES | 2 | 6 | This table maps an instance of an INCIDENT property to the instance of the associated custom form | |
| USI_INCIDENTS | 3 | 7 | This table maps an instance of an INCIDENT to the instance of the associated custom form | |
| USI_OFFENSES | 4 | 8 | This table maps an instance of an offense to the instance of the associated custom form | |
| USI_PEOPLE | 2 | 6 | This table maps an instance of a MASTER PERSON to the instance of the associated custom form | |
| USI_SEARCH_VW | 11 | |||
| USI_VEHICLES | 2 | 6 | This table maps an instance of a MASTER VEHICLE to the instance of the associated custom form | |
| USI_WARRANT_FIELDS | 2 | 6 | This table maps an instance of a warrant to the instance of the associated custom fields | |
| USI_WARRANTS | 2 | 6 | This table maps an instance of a warrant to the instance of the associated custom form | |
| USRSCRN_CASE_ACTIVITY_VW | 20 | |||
| USRSCRN_CASE_VW | 2 | |||
| USRSCRN_CITATION_VW | 5 | |||
| USRSCRN_CP_VW | 7 | |||
| USRSCRN_CRIMINAL_COMPLAINT_VW | 9 | |||
| USRSCRN_DV_ASSIGNMENT_VW | 8 | |||
| USRSCRN_FIELDARREST_VW | 2 | |||
| USRSCRN_FIELDINTERVIEW_VW | 3 | |||
| USRSCRN_FLEET_VEHICLE_VW | 6 | |||
| USRSCRN_INCIDENT_VW | 6 | |||
| USRSCRN_VEHICLE_VW | 5 | |||
| USRSCRN_WARRANT_VW | 6 | |||
| VALIDATION_ELEMENTS | 3 | 12 | Used for search interface fields | |
| VEHICLE_ASSOC_CNT_VW | 3 | |||
| VEHICLE_ATTACHMENTS | 2 | 10 | This table stores attachments added to a MASTER VEHICLE in the application | |
| VEHICLE_CITATION_TYPE_CODES | 1 | 5 | This table defines the citation types for vehicle citation | |
| VEHICLE_DESC_NAME_VW | 26 | |||
| VEHICLE_DESC_VW | 17 | |||
| VEHICLE_DESCRIPTIONS | 4 | 13 | 28 | This table stores the description entered in the application for a MASTER VEHICLE |
| VEHICLE_DUP_SEARCH_VW | 10 | |||
| VEHICLE_IMAGES | 4 | 10 | This table stores an association to images added to a MASTER VEHICLE in the application. The image is stored in IMAGES | |
| VEHICLE_IMPOUND_VW | 12 | |||
| VEHICLE_INCIDENT_SUMMARY_VW | 19 | |||
| VEHICLE_INCIDENT_VW | 8 | |||
| VEHICLE_INSURANCE | 1 | 1 | 10 | This table stores the insurance information added to a vehicle in the application |
| VEHICLE_INV_ROLE_CNT_VW | 3 | |||
| VEHICLE_MAKES | 2 | 1 | 4 | This table defines the valid make codes that can be added to a vehicle in the application |
| VEHICLE_MAKES_AT_TK_VW | 2 | |||
| VEHICLE_MODELS | 2 | 2 | 6 | This table defines the valid model codes that can be added to a vehicle in the application |
| VEHICLE_MODELS_AT_TK_VW | 2 | |||
| VEHICLE_PERSON_VW | 19 | |||
| VEHICLE_RMS_SEARCH_VW | 53 | |||
| VEHICLE_SEARCH_TEST_VW | 26 | |||
| VEHICLE_SEARCH_VW | 38 | |||
| VEHICLE_STYLES | 2 | 1 | 4 | This table defines the valid style codes that can be added to a vehicle in the application |
| VEHICLE_SUMMARY_VW | 16 | |||
| VEHICLE_TOW_VW | 11 | |||
| VEHICLE_TYPE_CODES | 4 | 2 | 7 | This table defines the valid type codes that can be added to a vehicle in the application |
| VEHICLES | 24 | 7 | 20 | This table stores the vehicle information added in the application |
| VEHICLES_NOT_DUPLICATES | 2 | 8 | This table stores vehicles that are similar but have been flagged as not duplicates so they don't accidentally get collapsed into one | |
| VICTIM_ARRESTEES | 7 | 13 | This table stores the relationship between a victim and an offense on an INCIDENT in the application | |
| VICTIM_INJURY_CODES_VW | 7 | |||
| VICTIM_RELATION_CODES_VW | 6 | |||
| VICTIM_REQQUES_VW | 3 | |||
| VICTIM_TYPE_CODES_VW | 3 | |||
| VICTIMS | 3 | 11 | 21 | This table stores victim information for a MASTER PERSON added to an INCIDENT as a victim in the application |
| VINE_CURRENTPHYDESC_VW | 2 | |||
| VISIBILITY_CODES | 1 | 5 | This table is not currently used | |
| VS_OFFENSE_COUNT_VW | 10 | |||
| VS_TIME_CATEGORY_VW | 11 | |||
| WARRANT_ADDR_SEARCH_VW | 52 | |||
| WARRANT_ARREST_CHARGES | 3 | 11 | This table stores the association of a warrant to a charge on an ARREST in the application | |
| WARRANT_ATTACHMENTS | 2 | 9 | This table stores attachments added to a WARRANT in the application | |
| WARRANT_CFS | 1 | 7 | This table stores the association between a warrant and an Calls for Service | |
| WARRANT_CHARGE_NARRATIVES | 4 | 10 | This table stores charging language narratives for charges on warrants. | |
| WARRANT_CHARGES | 1 | 5 | 16 | This table stores the charges added to a warrant in the application |
| WARRANT_CHG_DISPO_CODES | 1 | 4 | This table stores the disposition code added to a warrant in the application | |
| WARRANT_DELETE | 17 | This tables stores the WARRANT information when a WARRANT is deleted from the application | ||
| WARRANT_FREETEXT_CHARGES | 2 | 11 | This table stores free text charges (i.e. one-off charges) added to a warrant in the application | |
| WARRANT_IMAGES | 2 | 8 | This table stores associations to images added to a WARRANT in the application | |
| WARRANT_LOG | 3 | 13 | This table stores log entries for actions taken on a warrant in the application | |
| WARRANT_OFFENSE_CHARGE_VW | 23 | |||
| WARRANT_OFFICER_SEARCH_VW | 41 | |||
| WARRANT_OFFICER_VW | 9 | |||
| WARRANT_OFFICERS | 4 | 12 | Associates Assigned Officers to Warrantss | |
| WARRANT_PERSON_ADDR_VW | 37 | |||
| WARRANT_REFERENCES | 3 | 10 | This table stores reference numbers and types added to a warrant in the application | |
| WARRANT_REFERENCES_AUDIT | 11 | A Shadow table created to track changes on WARRANT_REFERENCES | ||
| WARRANT_REFERENCES_DELETE | 2 | 10 | This table stores reference numbers and types added to a warrant in the application | |
| WARRANT_SEARCH_VW | 34 | |||
| WARRANT_SERVICE_ADDRESSES | 2 | 10 | Associates Service Addresses to a Warrant. Joins to Master Index ADDRESSES | |
| WARRANT_SERVING_OFFICERS | 2 | 9 | This tables stores the Serving Officers of Warrants | |
| WARRANT_SRVOFF_SEARCH_VW | 38 | |||
| WARRANTS_VW | 32 | |||
| WEAPON_MAKE_CODES | 1 | 5 | This table defines the valid make codes that can be added to a weapon in the application | |
| WEAPON_MODEL_CODES | 1 | 5 | This table defines the valid model codes that can be added to a weapon in the application | |
| WEAPON_TYPE_CODES | 1 | 5 | This table defines the valid type codes that can be added to a weapon in the application | |
| WEAPONS | 5 | 11 | This table stores weapons associated with an INCIDENT created in the application | |
| WEAPONS_TRAININGS | 5 | 18 | Legacy table. This table is not currently used | |
| XML_AUTOMATCH_CRITERIA | 3 | 3 | This table is an administration table that is used for processing XML documents being loaded into the database | |
| XML_AUTOMATCH_FIELDS | 1 | 4 | This table is an administration table that is used for processing XML documents being loaded into the database | |
| XML_DOC_APP_TABLES | 2 | 6 | This table is an administration table that is used for processing XML documents being loaded into the database | |
| XML_DOC_CAT_CRITERIA | 2 | 2 | 3 | This table is an administration table that is used for processing XML documents being loaded into the database |
| XML_DOC_DESTINATIONS | 2 | 7 | This table is an administration table that is used for processing XML documents being loaded into the database | |
| XML_DOCUMENT_CATEGORY_CODES | 12 | 6 | 19 | This table is an administration table that is used for processing XML documents being loaded into the database |
| XML_DOCUMENT_OPTIONS | 4 | 11 | This table is an administration table that is used for processing XML documents being loaded into the database | |
| XML_MULTIMATCH_CRITERIA | 3 | 4 | This table is an administration table that is used for processing XML documents being loaded into the database | |
| ZZ_AGENCY_CODES | 58 | |||
| ZZ_ARREST_CHARGE_CODES | 13 | This table stores audit information for ARREST charges | ||
| ZZ_CHARGE_CODES | 43 | This table stores audit information for charge codes | ||
| ZZ_DS_ICR_FILE_REFERENCES | 17 | |||
| ZZ_EJS_CODE_NIBRS_MAPPINGS | 14 | This table stores audit information for EJS Code to NIBRS mappings | ||
| ZZ_EJS_CODES | 20 | This table stores audit information for EJS Codes | ||
| ZZ_EJS_SUB_MAINT | 21 | |||
| ZZ_GUN_MAKE_CODES | 14 | |||
| ZZ_NIBRS_CODE_EJS_MAPPINGS | 12 | This table stores audit information for NIBRS to EJS Code mappings | ||
| ZZ_NIBRS_CRIME_TARGETS | 7 | This table stores audit information for NIBRS crime targets | ||
| ZZ_NIBRS_LESSER_OFFENSES | 11 | This table stores audit information for NIBRS lesser offenses | ||
| ZZ_NIBRS_OFFENSES | 11 | This table stores audit information for NIBRS offenses | ||
| ZZ_NIBRS_PROP_MAPPINGS | 15 | This table stores audit information for NIBRS property mappings | ||
| ZZ_OFFENSE_CODES | 16 | This table stores audit information for offense codes | ||
| ZZ_TOW_COMPANY_CODES | 21 | This table stores audit information for tow companies | ||
| ZZC1_AGENCY_CODES | 57 | |||
| ZZC1_ARREST_CHARGE_CODES | 12 | |||
| ZZC1_CHARGE_CODES | 42 | |||
| ZZC1_DS_ICR_FILE_REFERENCES | 16 | |||
| ZZC1_EJS_CODE_NIBRS_MAPPINGS | 13 | |||
| ZZC1_EJS_CODES | 19 | |||
| ZZC1_EJS_SUB_MAINT | 20 | |||
| ZZC1_GUN_MAKE_CODES | 13 | |||
| ZZC1_NIBRS_CODE_EJS_MAPPINGS | 11 | |||
| ZZC1_NIBRS_CRIME_TARGETS | 6 | |||
| ZZC1_NIBRS_LESSER_OFFENSES | 10 | |||
| ZZC1_NIBRS_OFFENSES | 10 | |||
| ZZC1_NIBRS_PROP_MAPPINGS | 14 | |||
| ZZC1_OFFENSE_CODES | 15 | |||
| ZZC1_TOW_COMPANY_CODES | 20 | |||
| ZZV1_AGENCY_CODES | 58 | |||
| ZZV1_ARREST_CHARGE_CODES | 13 | |||
| ZZV1_CHARGE_CODES | 43 | |||
| ZZV1_DS_ICR_FILE_REFERENCES | 17 | |||
| ZZV1_EJS_CODE_NIBRS_MAPPINGS | 14 | |||
| ZZV1_EJS_CODES | 20 | |||
| ZZV1_EJS_SUB_MAINT | 21 | |||
| ZZV1_GUN_MAKE_CODES | 14 | |||
| ZZV1_NIBRS_CODE_EJS_MAPPINGS | 12 | |||
| ZZV1_NIBRS_CRIME_TARGETS | 7 | |||
| ZZV1_NIBRS_LESSER_OFFENSES | 11 | |||
| ZZV1_NIBRS_OFFENSES | 11 | |||
| ZZV1_NIBRS_PROP_MAPPINGS | 15 | |||
| ZZV1_OFFENSE_CODES | 16 | |||
| ZZV1_TOW_COMPANY_CODES | 21 | |||
| 1,074 Tables | 12,679 | |||
| 430 Views | 11,299 |