SAS Enterprise Case Management 3.1. Data Dictionary

Transcription

1 SAS Enterprise Case Management 3.1 Data Dictionary

2 The correct bibliographic citation for this manual is as follows: SAS Institute Inc SAS Enterprise Case Management 3.1: Data Dictionary. Cary, NC: SAS Institute Inc. SAS Enterprise Case Management 3.1: Data Dictionary Copyright 2012, SAS Institute Inc., Cary, NC, USA All rights reserved. Produced in the United States of America. For a hard-copy book: No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, or otherwise, without the prior written permission of the publisher, SAS Institute Inc. For a Web download or e-book: Your use of this publication shall be governed by the terms established by the vendor at the time you acquire this publication. The scanning, uploading, and distribution of this book via the Internet or any other means without the permission of the publisher is illegal and punishable by law. Please purchase only authorized electronic editions and do not participate in or encourage electronic piracy of copyrighted materials. Your support of others rights is appreciated. U.S. Government Restricted Rights Notice: Use, duplication, or disclosure of this software and related documentation by the U.S. government is subject to the Agreement with SAS Institute and the restrictions set forth in FAR , Commercial Computer Software-Restricted Rights (June 1987). SAS Institute Inc., SAS Campus Drive, Cary, North Carolina st electronic book, February 2012 SAS Publishing provides a complete selection of books and electronic products to help customers use SAS software to its fullest potential. For more information about our e-books, e-learning products, CDs, and hard-copy books, visit the SAS Publishing Web site at support.sas.com/publishing or call SAS and all other SAS Institute Inc. product or service names are registered trademarks or trademarks of SAS Institute Inc. in the USA and other countries. indicates USA registration. Other brand and product names are registered trademarks or trademarks of their respective companies.

3 iii Contents Chapter 1 Introduction 1 About the Data Dictionary 1 What Is the SAS Enterprise Case Management Data Model? 1 Chapter 2 Descriptions of the Tables 3 Chapter 3 Descriptions of Table Columns 9

4 iv

5 CHAPTER 1 Introduction 1 About the Data Dictionary... 1 What Is the SAS Enterprise Case Management Data Model?... 1 About the Data Dictionary This data dictionary is a list of the tables and their columns that are contained in the SAS Enterprise Case Management 3.1 data model. The first table lists all of the tables that are in the data model. The remaining tables list the columns and their descriptions for each table in the data model. Use the data dictionary as a reference as you perform tasks such as these: Review the detailed descriptions of various fields to prepare reports that are based on the SAS Enterprise Case Management 3.1 data model. Build database views to combine fields that are used for reports. What Is the SAS Enterprise Case Management Data Model? The SAS Enterprise Case Management 3.1 data model is a common data repository for SAS Enterprise Case Management. The model provides the reporting data. See SAS Enterprise Case Management 3.1: Data Model for a diagram of the data model.

6 2

7 CHAPTER 2 Descriptions of the Tables 3 The following table contains descriptions of all of the tables in the SAS Enterprise Case Management 3.1 data model. The tables are listed in alphabetic order, and the columns are listed in the order found in the data model. Table CASE_CONFIG CASE_CONFIG_X_USER_GROUP CASE_EVENT CASE_LIVE CASE_SEARCH_CRITERIA_FIELD CASE_SEARCH_FILTER_FIELD CASE_SEARCH_RESULT_FIELD CASE_UDF_CHAR_VALUE CASE_UDF_DATE_VALUE CASE_UDF_DEF CASE_UDF_LGCHR_VALUE CASE_UDF_NUM_VALUE CASE_VERSION CASE_X_PARTY CASE_X_USER_GROUP ECM_COLUMN_LABEL ECM_ENTITY_LOCK ECM_LOCALE ECM_TABLE_LABEL Definition Defines the rules which determine the UI definition to display for a given case, based on the case s type, category and subcategory values. If a record includes null for category or subcategory, that is treated as a wildcard and that rule would apply for any value in that column. In situations where multiple rules apply, the sequence number is treated as the priority; the matching rule with the smallest sequence number will be selected. Intersection table linking the initial groups of users who can access a case to a case configuration. Details of all actions taken on a case. Details of a case involving one or more suspicious incidents. This table contains the current version of the case. Contains search criteria field configurations for the case search panel. Contains search filter field configurations for the case search panel. Contains search result field configurations for the case search panel. Contains character data typed user-defined field values for cases. Contains date data typed user-defined field values for cases. Details of user-defined field definitions for cases. Contains CLOB data types for user-defined field values for cases. Contains number data typed user-defined field values for cases. Details of a case involving one or more suspicious incidents. Intersection table linking parties to cases. Intersection table linking cases to groups of users who can access the case. Contains column label translation information. Allows any user-editable ECM object to be locked before editing. Contains localization data supported by the application. Contains table label translation information.

8 4 Chapter 2 Table Definition EFILE_CONFIG Defines the rules which determine the UI definition to display for a given e-file, based on the e-file s type, category and subcategory values. If a record includes null for category or subcategory, that is treated as a wildcard and that rule would apply for any value in that column. In situations where multiple rules apply, the sequence number is treated as the priority; the matching rule with the smallest sequence number will be selected. EFILE_CONFIG_X_USER_GROUP Intersection table linking the initial groups of users who can access an e-file to an e-file configuration. EFILE_EVENT Details of all actions taken on an e-file. EFILE_LIVE Details of an e-file. This table contains the current version of the e-file. EFILE_SEARCH_CRITERIA_FIELD Contains search criteria field configurations for the case search panel. EFILE_SEARCH_FILTER_FIELD Contains search filter field configurations for the case search panel. EFILE_SEARCH_RESULT_FIELD Contains search result field configurations for the case search panel. EFILE_UDF_CHAR_VALUE Contains character data typed user-defined field values for cases. EFILE_UDF_DATE_VALUE Contains date data typed user-defined field values for cases. EFILE_UDF_DEF Details of user-defined field definitions for cases. EFILE_UDF_LGCHR_VALUE Contains CLOB data types for user-defined field values for cases. EFILE_UDF_NUM_VALUE Contains number data typed user-defined field values for cases. EFILE_VERSION Details of an e-file. This table contains all versions of the e- file. EFILE_X_USER_GROUP Intersection table linking e-files to groups of users who can access the e-file. FINANCIAL_ITEM_CONFIG The FINANCIAL_ITEM CONFIG table maps which UI definition to use for each FINANCIAL_ITEM type. The FINANCIAL_ITEM_CONFIG table differs from the other CONFIG tables. Financial items are configured solely on the FINANCIAL_ITEM type code. Case, incident and party are configured based on type, category and sub-category. FINANCIAL_ITEM_LIVE A financial item is associated with a case or an incident and stores the monetary value associated with a suspicious transaction or exposure. This table contains the current version of the financial item. FINANCIAL_ITEM_UDF_CHAR_VALUE Contains character data typed user-defined field values for cases. FINANCIAL_ITEM_UDF_DATE_VALUE Contains date data typed user-defined field values for financial items. FINANCIAL_ITEM_UDF_DEF Details of user-defined field definitions for financial items. FINANCIAL_ITEM_UDF_LGCHR_VALUE Contains CLOB data types for financial items. FINANCIAL_ITEM_UDF_NUM_VALUE Contains number data typed user-defined field values for financial items. FINANCIAL_ITEM_VERSION A financial item is associated with a case or an incident and stores the monetary value associated with a suspicious transaction or exposure.

9 Descriptions of the Tables 5 Table FORM_CONFIG FORM_EFILE_FIELD_CONFIG FORM_EFILE_RECORD_CONFIG FORM_PREVIEW_FIELD_CONFIG FORM_PREVIEW_SECTION_CONFIG GENERIC_DATA_UDF_CHAR_VALUE GENERIC_DATA_UDF_DATE_VALUE GENERIC_DATA_UDF_DEF GENERIC_DATA_UDF_LGCHR_VALUE GENERIC_DATA_UDF_NUM_VALUE INCIDENT_CONFIG INCIDENT_CONFIG_X_USER_GROUP INCIDENT_EVENT INCIDENT_LIVE INCIDENT_SEARCH_CRITERIA_FIELD INCIDENT_SEARCH_FILTER_FIELD INCIDENT_SEARCH_RESULT_FIELD INCIDENT_UDF_CHAR_VALUE INCIDENT_UDF_DATE_VALUE INCIDENT_UDF_DEF INCIDENT_UDF_LGCHR_VALUE INCIDENT_UDF_NUM_VALUE INCIDENT_VERSION INCIDENT_X_PARTY INCIDENT_X_USER_GROUP Definition Form configuration table to link report and e-file configuration. Defines the mapping of the source data fields to the target fields in EFILE. Controls the records of the output e-file. Defines the mapping of the source data fields to the form fields. Controls the sections of the output e-file. Contains character data types for generic user-defined values. Contains date data types for generic user-defined values. Details of user-defined field definitions for a generic item. Contains CLOB data types for generic user-defined values. Contains number data types for generic user-defined values. Defines the rules which determine the UI definition to display for a given incident, based on the incident s type, category and subcategory values. If a record includes null for category or subcategory, that is treated as a wildcard and that rule would apply for any value in that column. In situations where multiple rules apply, the sequence number is treated as the priority; the matching rule with the smallest sequence number will be selected. Intersection table linking the initial groups of users who can access an incident to an incident configuration. Details of all actions taken on an incident. Details of a suspicious incident. This table contains the current version of the incident. Contains search criteria field configurations for the incident search panel. Contains search filter field configurations for the incident search panel. Contains search result field configurations for the incident search panel. Contains character data typed user-defined field values for incidents. Contains date data typed user-defined field values for incidents. Details of user-defined field definitions for incidents. Contains CLOB or long character data typed user-defined field values for incidents. Contains number data typed user-defined field values for incidents. Details of a suspicious incident. Intersection table linking parties to incidents. Intersection table linking incidents to groups of users who can access the incident.

10 6 Chapter 2 Table PARTY_CONFIG PARTY_CONFIG_X_USER_GROUP PARTY_EVENT PARTY_LIVE PARTY_SEARCH_CRITERIA_FIELD PARTY_SEARCH_FILTER_FIELD PARTY_SEARCH_RESULT_FIELD PARTY_UDF_CHAR_VALUE PARTY_UDF_DATE_VALUE PARTY_UDF_DEF PARTY_UDF_LGCHR_VALUE PARTY_UDF_NUM_VALUE PARTY_VERSION PARTY_X_PARTY PARTY_X_USER_GROUP REF_TABLE_TRANS REF_TABLE_VALUE RELATED_ITEM_CONFIG RR_CONFIG RR_CONFIG_X_USER_GROUP RR_EVENT Definition Defines the rules which determine the UI definition to display for a given party, based on the party s type, category and subcategory values. If a record includes null for category or subcategory, that is treated as a wildcard and that rule would apply for any value in that column. In situations where multiple rules apply, the sequence number is treated as the priority; the matching rule with the smallest sequence number will be selected. Intersection table linking the initial groups of users who can access a party to a party configuration. Details of all actions taken on a party. Details of an individual or organization that plays a role in a case or a suspicious incident. This table contains the current version of the party. Contains search criteria field configurations for the party search panel. Contains search filter field configurations for the party search panel. Contains search result field configurations for the party search panel. Contains character data typed user-defined field values for parties. Contains date data typed user-defined field values for parties. Details of user-defined field definitions for parties. Contains CLOB or long character data typed user-defined field values for parties. Contains number data typed user-defined field values for parties. Details of an individual or organization that plays a role in a case or a suspicious incident. Intersection table linking parties to other parties. Intersection table linking parties to groups of users who can access the party. A record in the translation table corresponds to a single translation of a single entry in the REF_TABLE_VALUE table. The locale column should be to a Java-compliant locale-specifier. Contains code value definitions for reference tables. This table is used to define different scenarios to find related incidents, cases and parties. Defines the rules which determine the UI definition to display for a given report, based on the report s type, category and subcategory values. If a record includes null for category or subcategory, that is treated as a wildcard and that rule would apply for any value in that column. In situations where multiple rules apply, the sequence number is treated as the priority; the matching rule with the smallest sequence number will be selected. Intersection table linking the initial groups of users who can access a report to a report configuration. Details of all actions taken on a report.

11 Descriptions of the Tables 7 Table RR_LIVE RR_SEARCH_CRITERIA_FIELD RR_SEARCH_FILTER_FIELD RR_SEARCH_RESULT_FIELD RR_UDF_CHAR_VALUE RR_UDF_DATE_VALUE RR_UDF_DEF RR_UDF_LGCHR_VALUE RR_UDF_NUM_VALUE RR_VERSION RR_X_USER_GROUP SCHEMA_VERSION SNA_CONFIG_DETAIL SNA_CONFIG_MASTER SUBJSRCH_CONFIG_DETAIL SUBJSRCH_CONFIG_MASTER TASK_LIST TEMP_TABLE Definition Details of a report. This table contains the current version of the report. Contains search criteria field configurations for the case search panel. Contains search filter field configurations for the case search panel. Contains search result field configurations for the case search panel. Contains character data typed user-defined field values for cases. Contains date data typed user-defined field values for cases. Details of user-defined field definitions for cases. Contains CLOB data types for user-defined field values for cases. Contains number data typed user-defined field values for cases. Details of a report. This table contains all versions of the report. Intersection table linking reports to groups of users who can access the report. Contains the schema version. This table stores the detail definition of SNA_CONFIG_MASTER. It contains one or many records of each SNA_CONFIG_MASTER record. A SNA_CONFIG_MASTER match criterion is considered as met when all of its associated SNA_CONFIG_DETAIL match criteria are met. This table is used to configure the match criteria for Case Network Analysis. Subjects are considered as Networked when one or many of these match criteria are met. This table stores the detail definition of SUBJSRCH_CONFIG_MASTER. It contains one or many records of each SUBJSRCH_CONFIG_MASTER record. A SUBJSRCH_CONFIG_MASTER match criterion is considered as met when all of its associated SUBJSRCH_CONFIG_DETAIL match criteria are met. This table is used to configure the match criteria for subject search. Subjects are considered as matched when one or many of these match criteria are met. Stores task list information related to a case or an incident with automatic reminders. Temporary table for building complicated search queries. For example, when ECM needs to integrate workflow search results with ECM search results, the workflow results are inserted into the temp table for a more efficient query.

12 8 Chapter 2

13 CHAPTER 3 Descriptions of Table Columns 9 The following tables contain descriptions of all of the table columns in the SAS Enterprise Case Management 3.1 data model. The tables are listed in alphabetic order. Table 3.1 CASE_CONFIG Table CASE_CONFIG Table CASE_CONFIG_SEQ_NO NUMBER(10) The CASE_CONFIG table defines the rules which determine the UI definition to display for a given case, based on the case s type, category and subcategory values. If a record includes null for category or subcategory, that is treated as a wildcard and that rule would apply for any value in that column. In situations where multiple rules apply, the sequence number is treated as the priority; the matching rule with the smallest sequence number will be selected. CASE_TYPE_CD VARCHAR2(10) Case type code. CASE_CATEGORY_CD VARCHAR2(10) Case category code. CASE_SUBCATEGORY_CD VARCHAR2(10) Case subcategory code. UI_DEF_FILE_NM VARCHAR2(100) User interface definition file name. INVESTIGATE_WORKFLOW_DEF_NM VARCHAR2(100) Investigate case workflow definition name. REOPEN_WORKFLOW_DEF_NM VARCHAR2(100) Reopen case workflow definition name. INVESTIGATOR_USER_ID VARCHAR2(60) Investigator who initially owns the case. Table 3.2 CASE_CONFIG_X_USER_GROUP Table CASE_CONFIG_X_USER_GROUP Table CASE_CONFIG_SEQ_NO NUMBER(10) Case configuration sequence number. USER_GROUP_NM VARCHAR2(60) User group name. Table 3.3 CASE_EVENT Table CASE_EVENT Table CASE_EVENT_RK NUMBER(10) System-generated case event surrogate key.

14 10 Chapter 3 CASE_EVENT Table CASE_RK NUMBER(10) System-generated case surrogate key. EVENT_TYPE_CD VARCHAR2(10) Event type code. EVENT_DESC VARCHAR2(256) Event description. CREATE_USER_ID VARCHAR2(60) User who created the case event. CREATE_DTTM TIMESTAMP Date/time when the case event was created. LINKED_OBJECT_NM VARCHAR2(100) Linked object name. LINKED_OBJECT_RK NUMBER(10) Linked object surrogate key. Table 3.4 CASE_LIVE Table CASE_LIVE Table CASE_RK NUMBER(10) System-generated case surrogate key. VALID_TO_DTTM TIMESTAMP Standard dates used for versioning. CASE_ID VARCHAR2(32) Case identifier. SOURCE_SYSTEM_CD VARCHAR2(10) Source system code. CASE_TYPE_CD VARCHAR2(10) Case type code. CASE_CATEGORY_CD VARCHAR2(10) Case category code. CASE_SUBCATEGORY_CD VARCHAR2(10) Case sub-category code. CASE_STATUS_CD VARCHAR2(10) Case status code. CASE_DISPOSITION_CD VARCHAR2(10) Case disposition code. CASE_DESC VARCHAR2(100) Case description. CASE_LINK_SK NUMBER(10) System-generated surrogate key for linking related cases. PRIORITY_CD VARCHAR2(10) The priority code of a case, used for sorting (that is, High, Medium, Low). REGULATORY_RPT_RQD_FLG CHAR(1) Regulatory Report Required Flag. INVESTIGATOR_USER_ID VARCHAR2(60) Investigator who owns the case. OPEN_DTTM TIMESTAMP Date/time when the case was opened. REOPEN_DTTM TIMESTAMP Date/time when the case was last reopened. CLOSE_DTTM TIMESTAMP Date/time when the case was closed. UI_DEF_FILE_NM VARCHAR2(100) Custom Page Builder user interface file name. CREATE_USER_ID VARCHAR2(60) User who created the case. CREATE_DTTM TIMESTAMP Date/time when the case was created. UPDATE_USER_ID VARCHAR2(60) User who last updated the case.

15 Descriptions of Table Columns 11 CASE_LIVE Table VERSION_NO NUMBER(10) Version number used to implement optimistic locking. DELETE_FLG CHAR(1) This flag indicates whether or not the case has been logically deleted and is now obsolete. Table 3.5 CASE_SEARCH_CRITERIA_FIELD Table CASE_SEARCH_CRITERIA_FIELD Table USER_ID VARCHAR2(60) User who this configuration applies to. Equals '*' for the default configuration for all users. TABLE_NM VARCHAR2(30) Field table name. FIELD_NM VARCHAR2(30) Field name. DISPLAY_ORDER_NO NUMBER(6) Display order number. REF_TABLE_NM VARCHAR2(30) Reference table name to render a selection list criteria filter for the field. FORMAT_TXT VARCHAR2(40) Name of the resource bundle key that contains the display format for numeric fields. Table 3.6 CASE_SEARCH_FILTER_FIELD Table CASE_SEARCH_FILTER_FIELD Table USER_ID VARCHAR2(60) User who this configuration applies to. Equals '*' for the default configuration for all users. TABLE_NM VARCHAR2(30) Field table name. FIELD_NM VARCHAR2(30) Field name. DISPLAY_ORDER_NO NUMBER(6) Display order number. REF_TABLE_NM VARCHAR2(30) Reference table name to render a selection list filter for the field. Table 3.7 CASE_SEARCH_RESULT_FIELD Table CASE_SEARCH_RESULT_FIELD Table USER_ID VARCHAR2(60) User who this configuration applies to. Equals '*' for the default configuration for all users. TABLE_NM VARCHAR2(30) Field table name. FIELD_NM VARCHAR2(30) Field name. DISPLAY_ORDER_NO NUMBER(6) Display order number. REF_TABLE_NM VARCHAR2(30) Reference table name to render coded values as displayable values. FORMAT_TXT VARCHAR2(40) Name of the resource bundle key that contains the display format for numeric and date fields.

16 12 Chapter 3 Table 3.8 CASE_UDF_CHAR_VALUE Table CASE_UDF_CHAR_VALUE Table CASE_RK NUMBER(10) System-generated case surrogate key. ROW_NO NUMBER(10) Row number. UDF_VALUE VARCHAR2(4000) User-defined field value. Table 3.9 CASE_UDF_DATE_VALUE Table CASE_UDF_DATE_VALUE Table CASE_RK NUMBER(10) System-generated case surrogate key. ROW_NO NUMBER(10) Row number. UDF_VALUE TIMESTAMP User-defined field value. Table 3.10 CASE_UDF_DEF Table CASE_UDF_DEF UDF_TYPE_NM VARCHAR2(10) User-defined field data type (VARCHAR, BIGINT, DOUBLE, BOOLEAN, DATE, TIMESTAMP). UDF_DESC VARCHAR2(100) User-defined field description. MAX_CHAR_CNT NUMBER(6) Maximum number of characters for a CHAR data typed user-defined field. Table 3.11 CASE_UDF_ LGCHR_VALUE Table CASE_UDF_LGCHR_VALUE CASE_RK NUMBER(10) System-generated case surrogate key.

17 Descriptions of Table Columns 13 CASE_UDF_LGCHR_VALUE ROW_NO NUMBER(10) Row number UDF_VALUE CLOB User-defined field value. Table 3.12 CASE_UDF_NUM_VALUE Table CASE_UDF_NUM_VALUE Table CASE_RK NUMBER(10) System-generated case surrogate key. ROW_NO NUMBER(10) Row number. UDF_VALUE DOUBLE PRECISION User-defined field value. Table 3.13 CASE_VERSION Table CASE_VERSION Table CASE_RK NUMBER(10) System-generated case surrogate key. VALID_TO_DTTM TIMESTAMP Standard dates used for versioning. CASE_ID VARCHAR2(32) Case identifier. SOURCE_SYSTEM_CD VARCHAR2(10) Source system code. CASE_TYPE_CD VARCHAR2(10) Case type code. CASE_CATEGORY_CD VARCHAR2(10) Case category code.

18 14 Chapter 3 CASE_VERSION Table CASE_SUBCATEGORY_CD VARCHAR2(10) Case sub-category code. CASE_STATUS_CD VARCHAR2(10) Case status code. CASE_DISPOSITION_CD VARCHAR2(10) Case disposition code. CASE_DESC VARCHAR2(100) Case description. CASE_LINK_SK NUMBER(10) System-generated surrogate key for linking related cases. PRIORITY_CD VARCHAR2(10) The priority code of a case, used for sorting (that is, High, Medium, Low). REGULATORY_RPT_RQD_FLG CHAR(1) Regulatory Report Required Flag INVESTIGATOR_USER_ID VARCHAR2(60) Investigator who owns the case. OPEN_DTTM TIMESTAMP Date/time when the case was opened. REOPEN_DTTM TIMESTAMP Date/time when the case was last reopened. CLOSE_DTTM TIMESTAMP Date/time when the case was closed. UI_DEF_FILE_NM VARCHAR2(100) Custom Page Builder user interface file name. CREATE_USER_ID VARCHAR2(60) User who created the case. CREATE_DTTM TIMESTAMP Date/time when the case was created. UPDATE_USER_ID VARCHAR2(60) User who last updated the case. VERSION_NO NUMBER(10) Version number used to implement optimistic locking. DELETE_FLG CHAR(1) This flag indicates whether or not the case has been logically deleted and is now obsolete. Table 3.14 CASE_X_PARTY Table CASE_X_PARTY Table CASE_RK NUMBER(10) System-generated case surrogate key. PARTY_RK NUMBER(10) System-generated party retained surrogate key. RELATION_TYPE_CD VARCHAR2(10) Relationship type code. RELATION_DESC VARCHAR2(100) Relationship description. CREATE_DTTM TIMESTAMP Date/time when the case/party relationship was created. Table 3.15 CASE_X_USER_GROUP Table CASE_X_USER_GROUP Table CASE_RK NUMBER(10) System-generated case surrogate key. USER_GROUP_NM VARCHAR2(60) User group name. Equals '*' if any user may access the case.

19 Descriptions of Table Columns 15 Table 3.16 ECM_COLUMN_LABEL Table ECM_COLUMN_LABEL Table SOURCE_NM VARCHAR2(30) The source of the translation entry. Valid values are 'APPLICATION' if the label translation comes from the standard application translation files or 'CUSTOM' if it comes from one of the custom properties files. OBJECT_NM VARCHAR2(30) The name of the object that the label is associated with. Valid values include 'CASE', 'INCIDENT', 'PARTY', 'FINANCIAL_ITEM' or '*' if the label applies to all objects. TABLE_NM VARCHAR2(30) The name of the object or the name of the user-defined table that the column is associated with. COLUMN_NM VARCHAR2(30) The name of the column that the label is associated with. LOCALE VARCHAR2(5) A locale supported by the application. The locale should follow the Java locale naming convention: a valid 2- letter lowercase ISO 639 language code optionally appended with an underscore and a 2-letter uppercase ISO 3166 country code (for example, en, en_us, en_gb, fr_fr ). LABEL_TXT VARCHAR2(100) The translated label. Table 3.17 ECM_ENTITY_LOCK Table ECM_ENTITY_LOCK Table ENTITY_RK NUMBER(10) A sequential system-generated key. A surrogate key is added in the ETL process to ensure a unique identifier. May be used with validity date ranges in order to establish historical changes in the data. ENTITY_NM VARCHAR2(100) Entity name LOCK_USER_ID VARCHAR2(60) User ID that is locking the ECM object. LOCK_DTTM TIMESTAMP Date/time the lock on the object occurred.

20 16 Chapter 3 Table 3.18 ECM_ LOCALE Table ECM_LOCALE Table LOCALE VARCHAR2(5) A locale supported by the application. The locale should follow the Java locale naming convention: a valid 2- letter lowercase ISO 639 language code optionally appended with an underscore and a 2-letter uppercase ISO 3166 country code (for example, en, en_us, en_gb, fr_fr ). FALLBACK_LOCALE VARCHAR2(5) The locale to consult next if there is no translation available for the locale specified by the LOCALE column. For example, if en_gb is a supported locale, it s fallback would be en. If the supported locale is en, then the fallback would be the default locale/translation def. Table 3.19 ECM_ TABLE_LABEL Table ECM_TABLE_LABEL Table SOURCE_NM VARCHAR2(30) The source of the translation entry. Valid values are 'APPLICATION' if the label translation comes from the standard application translation files or 'CUSTOM' if it comes from one of the custom properties files. OBJECT_NM VARCHAR2(30) The name of the object that the label is associated with. Valid values include 'CASE', 'INCIDENT', 'PARTY', 'FINANCIAL_ITEM' or '*' if the label applies to all objects. TABLE_NM VARCHAR2(30) The name of the table that the label is associated with. LOCALE VARCHAR2(5) A locale supported by the application. The locale should follow the Java locale naming convention: a valid 2- letter lowercase ISO 639 language code optionally appended with an underscore and a 2-letter uppercase ISO 3166 country code (for example, en, en_us, en_gb, fr_fr ). LABEL_TXT VARCHAR2(100) The translated label.

21 Descriptions of Table Columns 17 Table 3.20 EFILE_CONFIG Table EFILE_CONFIG Table EFILE_CONFIG_SEQ_NO NUMBER(10) E-file configuration record sequence number. EFILE_TYPE_CD VARCHAR2(10) First code to classify an e-file. EFILE_CATEGORY_CD VARCHAR2(10) Second code to classify an e-file. EFILE_SUBCATEGORY_CD VARCHAR2(10) Third code to classify an e-file. UI_DEF_FILE_NM VARCHAR2(100) File name of the user interface definition to be used for the type of e- file. FORM_AGENCY_CD VARCHAR2(32) Unique code to define the government agency who published the form. FORM_TYPE_CD VARCHAR2(32) Unique code to define the government form published by the agency defined in FORM_AGENCY_CD. Table 3.21 EFILE_CONFIG_X_USER_GROUP Table EFILE_CONFIG_X_USER_GROUP Table EFILE_CONFIG_SEQ_NO NUMBER(10) Key to link e-file configuration record to a user group. USER_GROUP_NM VARCHAR2(60) Unique key to link the user group with an e-file configuration record. Table 3.23 EFILE_EVENT Table EFILE_EVENT Table EFILE_EVENT_RK NUMBER(10) System-generated case event surrogate key. EFILE_RK NUMBER(10) Since source data for EFILE_EVENT may come from multiple systems, the business supplied keys may not be unique. A surrogate key is added in the ETL process to ensure a unique identifier for EFILE_EVENT. EVENT_TYPE_CD VARCHAR2(10) Internal code to identify an event (for example, LOCKOB, ULOCK for locking and unlocking a record). EVENT_DESC VARCHAR2(256) Description of an event that will be displayed in the e-file history. CREATE_USER_ID VARCHAR2(60) User who created the case event. CREATE_DTTM TIMESTAMP Date/time when the case event was created. LINKED_OBJECT_NM VARCHAR2(100) Linked object name. LINKED_OBJECT_RK NUMBER(10) Linked object surrogate key.

22 18 Chapter 3 Table 3.24 EFILE_LIVE Table EFILE_LIVE Table EFILE_RK NUMBER(10) Since source data for EFILE_LIVE may come from multiple systems, the business supplied keys may not be unique. A surrogate key is added in the ETL process to ensure a unique identifier for EFILE_LIVE. VALID_TO_DTTM TIMESTAMP Standard dates used for versioning. EFILE_ID VARCHAR2(32) E-file identifier within the source system. SOURCE_SYSTEM_CD VARCHAR2(10) Source system code.efile_id and SOURCE_SYSTEM_CD unique identity an e-file record. FORM_CONFIG_RK NUMBER(10) Since source data for EFILE_LIVE may come from multiple systems, the business supplied keys may not be unique. A surrogate key is added in the ETL process to ensure a unique identifier for EFILE_LIVE. EFILE_TYPE_CD VARCHAR2(10) E-file type code. First code to classify an e-file. First code to classify an e- file. EFILE_CATEGORY_CD VARCHAR2(10) E-file category code. Second code to classify an e-file. EFILE_SUBCATEGORY_CD VARCHAR2(10) E-file subcategory code. Third code to classify an e-file. EFILE_STATUS_CD VARCHAR2(10) E-file status code, such as A for accepted and R for Rejected. EFILE_DESC VARCHAR2(100) Description of the e-file entered by the user or set by the batch program. OUTPUT_PATH_NM VARCHAR2(100) Subdirectory where the output e-file is stored. OUTPUT_NM VARCHAR2(100) Name of the output e-file. OUTPUT_RR_CNT NUMBER(10) Number of reports in the output e-file. OUTPUT_LINE_CNT NUMBER(10) Number of lines in the output e-file.

23 Descriptions of Table Columns 19 EFILE_LIVE Table OUTPUT_FILE_SIZE NUMBER(10) Size of the output e-file. OUTPUT_CREATE_DTTM TIMESTAMP Date/time when the output is created. TRANSMISSION_ID VARCHAR2(100) Transmission ID provided by the agency after an e-file is submitted. TRANSMISSION_DTTM TIMESTAMP Date/time when the e-file was transmitted. EFILE_AGENCY_REF_ID VARCHAR2(100) The reference ID provided by the agency to identify an accepted e-file. It is equivalent to Document Control Number from FINCEN. EFILE_AGENCY_STATUS_CD VARCHAR2(10) The e-file status provided by the agency (for example, Accepted, Accepted with Warnings, Rejected). COVERAGE_START_DT DATE Date of the earliest report activity in the e-file COVERAGE_END_DT DATE Date of the latest report activity in the e-file CORRECTION_FLG CHAR(1) Flag that indicates a correction report. OWNER_USER_ID VARCHAR2(60) User who initially owns the report.. UI_DEF_FILE_NM VARCHAR2(100) User interface definition file name. CREATE_USER_ID VARCHAR2(60) The ID of the user that added the record. CREATE_DTTM TIMESTAMP The date/time when the record was added. UPDATE_USER_ID VARCHAR2(60) The ID of the user who updated the record. VERSION_NO NUMBER(10) The date/time when the record was updated. DELETE_FLG CHAR(1) A flag indicating whether the record is active. Table 3.25 EFILE_SEARCH_CRITERIA_FIELD Table EFILE_SEARCH_CRITERIA_FIELD Table USER_ID VARCHAR2(60) User who this configuration applies to. Equals '*' for the default configuration for all users. TABLE_NM VARCHAR2(30) Table name of the field that is use for searching e-files. FIELD_NM VARCHAR2(30) Field name of the field that is used for searching e-files. DISPLAY_ORDER_NO NUMBER(6) Order number for displaying the search fields in the e-file search UI. REF_TABLE_NM VARCHAR2(30) Reference table name to render a selection list criteria filter for the field. FORMAT_TXT VARCHAR2(40) Name of the resource bundle key that contains the display format for numeric fields.

24 20 Chapter 3 Table 3.26 EFILE_SEARCH_FILTER_FIELD Table EFILE_SEARCH_FILTER_FIELD Table USER_ID VARCHAR2(60) User who this configuration applies to. Equals '*' for the default configuration for all users. TABLE_NM VARCHAR2(30) Table name of field that can be used for filtering e-files. FIELD_NM VARCHAR2(30) Field name of the field that can be used for filtering e-files. DISPLAY_ORDER_NO NUMBER(6) Order number for displaying the search fields in the e-file filter UI. REF_TABLE_NM VARCHAR2(30) Reference table name to render a selection list filter for the field. Table 3.27 EFILE_SEARCH_RESULT_FIELD Table EFILE_SEARCH_RESULT_FIELD Table USER_ID VARCHAR2(60) User who this configuration applies to. Equals '*' for the default configuration for all users. TABLE_NM VARCHAR2(30) Table name of the field that will be displayed in the search result list. FIELD_NM VARCHAR2(30) Field name of the field that will be displayed in the search result list. DISPLAY_ORDER_NO NUMBER(6) Order number for displaying the fields for filtering e-files. REF_TABLE_NM VARCHAR2(30) Reference table name to render coded values as displayable values. FORMAT_TXT VARCHAR2(40) Name of the resource bundle key that contains the display format for numeric and date fields. Table 3.28 EFILE_UDF_CHAR_VALUE Table EFILE_UDF_CHAR_VALUE Table EFILE_RK NUMBER(10) Since source data for EFILE_UDF_CHAR_VALUE may come from multiple systems, the business supplied keys may not be unique. A surrogate key is added in the ETL process to ensure a unique identifier for EFILE_UDF_CHAR_VALUE.

25 Descriptions of Table Columns 21 EFILE_UDF_CHAR_VALUE Table ROW_NO NUMBER(10) Row number of the UDF table UDF_VALUE VARCHAR2(4000) Value of the user-defined field (CHAR). Table 3.29 EFILE_UDF_DATE_VALUE Table EFILE_UDF_DATE_VALUE Table EFILE_RK NUMBER(10) Since source data for EFILE_UDF_DATE_VALUE may come from multiple systems, the business supplied keys may not be unique. A surrogate key is added in the ETL process to ensure a unique identifier for EFILE_UDF_DATE_VALUE. ROW_NO NUMBER(10) Row number of the UDF table UDF_VALUE TIMESTAMP User-defined field value (date). Table 3.30 EFILE_UDF_DEF Table EFILE_UDF_DEF Table UDF_TYPE_NM VARCHAR2(10) User-defined field data type (VARCHAR, BIGINT, DOUBLE, BOOLEAN, DATE, TIMESTAMP). UDF_DESC VARCHAR2(100) User-defined field description. MAX_CHAR_CNT NUMBER(6) Maximum number of characters for a CHAR data typed user-defined field.

26 22 Chapter 3 Table 3.31 EFILE_UDF_LGCHR_VALUE Table EFILE_UDF_LGCHR_VALUE Table EFILE_RK NUMBER(10) Since source data for EFILE_UDF_LGCHR_VALUE may come from multiple systems, the business supplied keys may not be unique. A surrogate key is added in the ETL process to ensure a unique identifier for EFILE_UDF_LGCHR_VALUE. ROW_NO NUMBER(10) Row number UDF_VALUE CLOB User-defined field value. Table 3.32 EFILE_UDF_NUM_VALUE Table EFILE_UDF_NUM_VALUE Table EFILE_RK NUMBER(10) Since source data for EFILE_UDF_NUM_VALUE may come from multiple systems, the business supplied keys may not be unique. A surrogate key is added in the ETL process to ensure a unique identifier for EFILE_UDF_NUM_VALUE. ROW_NO NUMBER(10) Row number. UDF_VALUE DOUBLE PRECISION User-defined field value.

27 Descriptions of Table Columns 23 Table 3.33 EFILE_VERSION Table EFILE_VERSION Table EFILE_RK NUMBER(10) Since source data for EFILE_VERSION may come from multiple systems, the business supplied keys may not be unique. A surrogate key is added in the ETL process to ensure a unique identifier for EFILE_VERSION. VALID_TO_DTTM TIMESTAMP Standard dates used for versioning. EFILE_ID VARCHAR2(32) The e-file identifier within the source system. SOURCE_SYSTEM_CD VARCHAR2(10) The EFILE_ID and SOURCE_SYSTEM_CD uniquely identify an e-file record. FORM_CONFIG_RK NUMBER(10) Since source data for EFILE_VERSION may come from multiple systems, the business supplied keys may not be unique. A surrogate key is added in the ETL process to ensure a unique identifier for EFILE_VERSION. EFILE_TYPE_CD VARCHAR2(10) E-file type code. EFILE_CATEGORY_CD VARCHAR2(10) E-file category code. EFILE_SUBCATEGORY_CD VARCHAR2(10) E-file subcategory code. EFILE_STATUS_CD VARCHAR2(10) E-file status code. EFILE_DESC VARCHAR2(100) E-file description OUTPUT_PATH_NM VARCHAR2(100) Subdirectory where the output e-file is stored. OUTPUT_NM VARCHAR2(100) Name of the output e-file. OUTPUT_RR_CNT NUMBER(10) Number of reports in the output e-file. OUTPUT_LINE_CNT NUMBER(10) Number of lines in the output e-file. OUTPUT_FILE_SIZE NUMBER(10) Size of the output e-file. OUTPUT_CREATE_DTTM TIMESTAMP Date/time when the output is created.

28 24 Chapter 3 EFILE_VERSION Table TRANSMISSION_ID VARCHAR2(100) Transmission ID provided by the agency after an e-file is submitted. TRANSMISSION_DTTM TIMESTAMP Date/time when the e-file was transmitted. EFILE_AGENCY_REF_ID VARCHAR2(100) The reference ID provided by the agency to identify an accepted e-file. It is equivalent to Document Control Number from FINCEN. EFILE_AGENCY_STATUS_CD VARCHAR2(10) The e-file status provided by the agency (for example, Accepted, Accepted with Warnings, Rejected). COVERAGE_START_DT DATE Date of the earliest report activity in the e-file. COVERAGE_END_DT DATE Date of the latest report activity in the e-file. CORRECTION_FLG CHAR(1) Flag that indicates a correction report. OWNER_USER_ID VARCHAR2(60) User who initially owns the report. UI_DEF_FILE_NM VARCHAR2(100) User interface definition file name. CREATE_USER_ID VARCHAR2(60) The ID of the user that added the record. CREATE_DTTM TIMESTAMP The date/time when the record was added. UPDATE_USER_ID VARCHAR2(60) The ID of the user who updated the record. VERSION_NO NUMBER(10) The date/time when the record was updated. DELETE_FLG CHAR(1) A flag indicating whether the record is active. Table 3.34 EFILE_VERSION Table EFILE_X_USER_GROUP Table EFILE_RK NUMBER(10) Since source data for EFILE_X_USER_GROUP may come from multiple systems, the business supplied keys may not be unique. A surrogate key is added in the ETL process to ensure a unique identifier for EFILE_X_USER_GROUP. USER_GROUP_NM VARCHAR2(60) User group name.

29 Descriptions of Table Columns 25 Table 3.35 FINANCIAL_ITEM_CONFIG Table FINANCIAL_ITEM_CONFIG Table FINANCIAL_ITEM_CONFIG_SEQ_NO NUMBER(10) The primary key for the FINANCIAL_ITEM_CONFIG table. FINANCIAL_ITEM_TYPE_CD VARCHAR2(10) The financial item type being configured. This value should reference an entry in the financial item type reference table (stored in the REF_TABLE_VALUE table with REF_TABLE_NM = RT_FINANCIAL_ITEM_TYPE ). UI_DEF_FILE_NM VARCHAR2(100) The UI definition file to use for financial items of the given financial item type. Table 3.36 FINANCIAL_ITEM_LIVE Table FINANCIAL_ITEM_LIVE Table FINANCIAL_ITEM_RK NUMBER(10) Since source data for FINANCIAL_ITEM_LIVE may come from multiple systems, the business supplied keys may not be unique. A surrogate key is added in the ETL process to ensure a unique identifier for FINANCIAL_ITEM_LIVE. FINANCIAL_ITEM_ID VARCHAR2(32) Financial item ID. SOURCE_SYSTEM_CD VARCHAR2(10) The source system from which this financial item originated. This value should reference an entry in the source system reference table (stored in the REF_TABLE_VALUE table with REF_TABLE_NM = RT_SOURCE_SYSTEM ). FINANCIAL_ITEM_TYPE_CD VARCHAR2(10) Financial item type code. LOCAL_AMT REAL Local amount. LOCAL_CURRENCY_CD VARCHAR2(10) Local currency code. BASE_AMT REAL Base amount. CURRENCY_CONVERSION_DT DATE Currency conversion date. PARENT_OBJECT_NM VARCHAR2(100) The parent object name links a financial item to a case or an incident along with the surrogate key of that parent object.

30 26 Chapter 3 FINANCIAL_ITEM_LIVE Table PARENT_OBJECT_RK NUMBER(10) This key links the financial item to a case or an incident. SOURCE_FINANCIAL_ITEM_RK NUMBER(10) This contains the key to link multiple financial items together. UI_DEF_FILE_NM VARCHAR2(100) Custom Page Builder user interface file name. INCLUDE_IN_SUMMARY_FLG CHAR(1) Include in summary flag. CREATE_USER_ID VARCHAR2(60) User who created the financial item. CREATE_DTTM TIMESTAMP Date/time of the financial item. UPDATE_USER_ID VARCHAR2(60) User who last updated the financial item. VALID_TO_DTTM TIMESTAMP Standard dates used for versioning. VERSION_NO NUMBER(10) Version number. DELETE_FLG CHAR(1) Has the financial item been logically deleted? Table 3.37 FINANCIAL_ITEM_UDF_CHAR_VALUE Table FINANCIAL_ITEM_UDF_CHAR_VALUE Table FINANCIAL_ITEM_RK NUMBER(10) Since source data for FINANCIAL_ITEM_UDF_CHAR_VALUE may come from multiple systems, the business supplied keys may not be unique. A surrogate key is added in the ETL process to ensure a unique identifier for FINANCIAL_ITEM_UDF_CHAR_VALUE. The row content is valid within the time range specified by FROM and TO dates. For a given identifier, versions of its rows are distinguished by different nonoverlapping FROM and ROW_NO NUMBER(10) Row number. UDF_VALUE VARCHAR2(4000) User-defined field value.

31 Descriptions of Table Columns 27 Table 3.38 FINANCIAL_ITEM_UDF_DATE_VALUE Table FINANCIAL_ITEM_UDF_DATE_VALUE Table FINANCIAL_ITEM_RK NUMBER(10) Since source data for FINANCIAL_ITEM_UDF_DATE_VALUE may come from multiple systems, the business supplied keys may not be unique. A surrogate key is added in the ETL process to ensure a unique identifier for FINANCIAL_ITEM_UDF_DATE_VALUE. The row content is valid within the time range specified by FROM and TO dates. For a given identifier, versions of its rows are distinguished by different nonoverlapping FROM and ROW_NO NUMBER(10) Row number. UDF_VALUE TIMESTAMP User-defined field value. Table 3.39 FINANCIAL_ITEM_UDF_DEF Table FINANCIAL_ITEM_UDF_DEF Table UDF_TYPE_NM VARCHAR2(10) User-defined field data type (VARCHAR, BIGINT, DOUBLE, BOOLEAN, DATE, TIMESTAMP). UDF_DESC VARCHAR2(100) User-defined field description. MAX_CHAR_CNT NUMBER(6) Maximum number of characters for a CHAR data typed user-defined field. Table 3.40 FINANCIAL_ITEM_UDF_LGCHR_VALUE Table FINANCIAL_ITEM_UDF_LGCHR_VALUE Table FINANCIAL_ITEM_RK NUMBER(10) Since source data for FINANCIAL_ITEM_UDF_LGCHR_VALUE may come from multiple systems, the business supplied keys may not be unique. A surrogate key is added in the ETL process to ensure a unique identifier for FINANCIAL_ITEM_UDF_LGCHR_VALUE.

32 28 Chapter 3 FINANCIAL_ITEM_UDF_LGCHR_VALUE Table The row content is valid within the time range specified by FROM and TO dates. For a given identifier, versions of its rows are distinguished by different non-overlapping FROM and ROW_NO NUMBER(10) Row number UDF_VALUE CLOB User-defined field value. Table 3.41 FINANCIAL_ITEM_UDF_NUM_VALUE Table FINANCIAL_ITEM_UDF_NUM_VALUE Table FINANCIAL_ITEM_RK NUMBER(10) Since source data for FINANCIAL_ITEM_UDF_NUM_VALUE may come from multiple systems, the business supplied keys may not be unique. A surrogate key is added in the ETL process to ensure a unique identifier for FINANCIAL_ITEM_UDF_NUM_VALUE. The row content is valid within the time range specified by FROM and TO dates. For a given identifier, versions of its rows are distinguished by different non-overlapping FROM and ROW_NO NUMBER(10) Row number. UDF_VALUE DOUBLE PRECISION User-defined field value. Table 3.42 FINANCIAL_ITEM_VERSION Table FINANCIAL_ITEM_VERSION Table FINANCIAL_ITEM_RK NUMBER(10) Since source data for FINANCIAL_ITEM_VERSION may come from multiple systems, the business supplied keys may not be unique. A surrogate key is added in the ETL process to ensure a unique identifier for FINANCIAL_ITEM_VERSION.

33 Descriptions of Table Columns 29 FINANCIAL_ITEM_VERSION Table FINANCIAL_ITEM_ID VARCHAR2(32) Financial item ID. SOURCE_SYSTEM_CD VARCHAR2(10) Source system code. FINANCIAL_ITEM_TYPE_CD VARCHAR2(10) Financial item type code. LOCAL_AMT REAL Local amount. LOCAL_CURRENCY_CD VARCHAR2(10) Local currency code. BASE_AMT REAL Base amount. CURRENCY_CONVERSION_DT DATE Currency conversion date. PARENT_OBJECT_NM VARCHAR2(100) The parent object name links a financial item to a case or an incident along with the surrogate key of that parent object. PARENT_OBJECT_RK NUMBER(10) This key links the financial item to a case or an incident. SOURCE_FINANCIAL_ITEM_RK NUMBER(10) This contains the key to link multiple financial items together. UI_DEF_FILE_NM VARCHAR2(100) Custom Page Builder user interface file name. INCLUDE_IN_SUMMARY_FLG CHAR(1) Include in summary flag. CREATE_USER_ID VARCHAR2(60) User who created the financial item. CREATE_DTTM TIMESTAMP Date/time of the financial item. UPDATE_USER_ID VARCHAR2(60) User who last updated the financial item. VALID_TO_DTTM TIMESTAMP Standard dates used for versioning. VERSION_NO NUMBER(10) Version number DELETE_FLG CHAR(1) Has the financial item been logically deleted? Table 3.43 FORM_CONFIG Table FORM_CONFIG Table FORM_CONFIG_RK NUMBER(10) A sequential system-generated key. A surrogate key is added in the ETL process to ensure a unique identifier. May be used with validity date ranges in order to establish historical changes in the data.

34 30 Chapter 3 FORM_CONFIG Table FORM_AGENCY_CD VARCHAR2(32) A unique code to identify the government agency that published the form. FORM_TYPE_CD VARCHAR2(32) A unique code to identify the government form published by the agency defined in FORM_AGENCY_CD. FORM_COUNTRY_CD VARCHAR2(3) A three-character country code of the form. EFFECTIVE_FROM_DTTM TIMESTAMP Start date/time when the form is effective to use. This field is for documentation purpose only. It is not used to determine if the form is effective. EFFECTIVE_TO_DTTM TIMESTAMP End date/time when the form is effective. Null in this column is used to indicate that the form is currently effective. FORM_DESC VARCHAR2(100) The description of the form. PREVIEW_MIME_TYPE_CD VARCHAR2(255) The standard mimetype of the Preview report. PREVIEW_FILE_PREFIX VARCHAR2(60) The common prefix of all Preview templates. PREVIEW_DRIVER_PGM_NM VARCHAR2(60) The SAS macro to be called by the ECMRR_PREVIEW stored process. PREVIEW_PREPROCESS_PGM_NM VARCHAR2(60) The SAS macro to be called by the preview driver program for transforming the RR data into formready data. EFILE_FILE_PREFIX VARCHAR2(60) The name of the output folder that will be used to store the output files. EFILE_DRIVER_PGM_NM VARCHAR2(60) The SAS macro to be called by the e- file driver stored process. EFILE_PREPROCESS_PGM_NM VARCHAR2(60) The SAS macro to be called by the e- file driver program for transforming the RR data into e-file-ready data. EFILE_MAX_RR_CNT NUMBER(6) Indicates the maximum number of RR (reports) that can be included in an e- file for that particular form. CREATE_USER_ID VARCHAR2(60) The ID of the user that added the record. CREATE_DTTM TIMESTAMP The date/time when the record was added. UPDATE_USER_ID VARCHAR2(60) The ID of the user who updated the record. UPDATE_DTTM TIMESTAMP The date/time when the record was updated. DELETE_FLG CHAR(1) A flag indicating whether the record is active.

35 Descriptions of Table Columns 31 Table 3.44 FORM_EFILE_FIELD_CONFIG Table FORM_EFILE_FIELD_CONFIG Table FORM_CONFIG_RK NUMBER(10) A sequential system-generated key. A surrogate key is added in the ETL process to ensure a unique identifier. May be used with validity date ranges in order to establish historical changes in the data. FORM_EFILE_RECORD_SEQ_NO NUMBER(10) The sequence number used to uniquely identify the record type of an e-file. FORM_EFILE_FIELD_SEQ_NO NUMBER(10) The sequence number used to uniquely identify the data fields of an e- file. TARGET_FIELD_START_POS_NO NUMBER(10) The start position of the EFILE field published by the government agency. TARGET_FIELD_END_POS_NO NUMBER(10) The end position of the EFILE field published by the government agency. TARGET_FIELD_NM VARCHAR2(100) The name of the EFILE field published by the government agency. TARGET_FIELD_LENGTH_NO NUMBER(10) The length of the EFILE field published by the government agency. TARGET_FIELD_DESC VARCHAR2(1000) The description of the EFILE field published by the government agency. SOURCE_FIELD_NM VARCHAR2(30) The name of the field in the source table to be used for populating the form fields. SOURCE_FIELD_NUM_FLG CHAR(1) A flag that indicates if the source field or the result of the source field expression is numeric. SOURCE_FIELD_EXP VARCHAR2(4000) The expression used to transform the source field. SAS_FORMAT_NM VARCHAR2(40) The name of the SAS format used to output the source field or the result of the source field expression. If the field is missing, the default format will be used. Table 3.45 FORM_EFILE_RECORD_CONFIG Table FORM_EFILE_RECORD_CONFIG Table FORM_CONFIG_RK NUMBER(10) A sequential system-generated key. A surrogate key is added in the ETL process to ensure a unique identifier. May be used with validity date ranges in order to establish historical changes in the data. FORM_EFILE_RECORD_SEQ_NO NUMBER(10) The sequence number used to uniquely identify the record type of an e-file. FORM_EFILE_RECORD_ID VARCHAR2(30) The ID used to uniquely identify the record type of an e-file.

36 32 Chapter 3 FORM_EFILE_RECORD_CONFIG Table FORM_EFILE_RECORD_DESC VARCHAR2(1000) The description of the e-file record. RECORD_SORT_ORDER_NO NUMBER(10) The order number in which the records will be placed into the e-file. RECORD_LENGTH_NO NUMBER(10) The record length of the e-file. SOURCE_TABLE_NM VARCHAR2(30) The name of the source table that will be used to populate the e-file record. PAGE_BY_FIELD_NM VARCHAR2(30) The name of the field for grouping the depending records together. For example, for FINCEN, the page types are BATCH, INSTITUTION, BRANCH and RR. Table 3.46 FORM_PREVIEW_FIELD_CONFIG Table FORM_PREVIEW_FIELD_CONFIG Table FORM_CONFIG_RK NUMBER(10) A sequential system-generated key. A surrogate key is added in the ETL process to ensure a unique identifier. May be used with validity date ranges in order to establish historical changes in the data. FORM_PREVIEW_SECTION_SEQ_NO NUMBER(10) The sequence number used to uniquely identify the form templates of a form. FORM_PREVIEW_FIELD_SEQ_NO NUMBER(10,2) The sequence number used to uniquely identify the form fields in the form template. SOURCE_FIELD_NM VARCHAR2(30) The name of the source table field to be used for populating the form fields. SOURCE_FIELD_NUM_FLG CHAR(1) A flag that indicates if the source field or the result of the source field expression is numeric. SOURCE_FIELD_EXP VARCHAR2(4000) The expression used to transform the source field. TARGET_FIELD_NM VARCHAR2(30) The name of the form field defined in the form template. TARGET_FIELD_TYPE_CD VARCHAR2(10) The code for each type of form field (for example, P1, P2, P3 and other depending on the number of parameters defined in the list). TARGET_FIELD_TYPE_PARM_LIST VARCHAR2(1000) The list of ' ' separated parameters to be passed to the macros.