SAS Enterprise Case Management 3.2 Data Dictionary. Copyright 2013 SAS Institute Inc., Cary, NC, USA. All Rights Reserved.
|
|
- Beatrix Pitts
- 6 years ago
- Views:
Transcription
1 SAS Enterprise Case Management 3.2 Data Dictionary Copyright 2013 SAS Institute Inc., Cary, NC, USA. All Rights Reserved. 1
2 Table CASE_CONFIG CASE_CONFIG_X_USER_GROUP 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_EVENT ECM_LOCALE ECM_TABLE_LABEL FINANCIAL_ITEM_CONFIG Definition Defines the rules which determine the ui definition to display for a given case, based on the case 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 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 screen. Contains search filter field configurations for the case search screen. Contains search result field configurations for the case search screen. 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 datatypes 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. Consolidated audit trail table for all objects. Contains localization data supported by the application. Contains table label translation information. 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. 2
3 Table FINANCIAL_ITEM_LIVE FINANCIAL_ITEM_UDF_CHAR_VALUE FINANCIAL_ITEM_UDF_DATE_VALUE FINANCIAL_ITEM_UDF_DEF FINANCIAL_ITEM_UDF_LGCHR_VALUE FINANCIAL_ITEM_UDF_NUM_VALUE FINANCIAL_ITEM_VERSION 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_LIVE INCIDENT_SEARCH_CRITERIA_FIELD INCIDENT_SEARCH_FILTER_FIELD INCIDENT_SEARCH_RESULT_FIELD INCIDENT_UDF_CHAR_VALUE Definition 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. Contains character data typed user defined field values for cases. Contains date data typed user defined field values for financial items. Details of user defined field definitions for financial items. Contains CLOB datatypes for Financial Items. Contains number data typed user defined field values for financial items. A Financial Item is associated with a Case or an Incident and stores the monetary value associated with a suspicious transaction or exposure. 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 a suspicious incident. This table contains the current version of the Incident. Contains search criteria field configurations for the incident search screen. Contains search filter field configurations for the incident search screen. Contains search result field configurations for the incident search screen. Contains character data typed user defined field 3
4 Table INCIDENT_UDF_DATE_VALUE INCIDENT_UDF_DEF INCIDENT_UDF_LGCHR_VALUE INCIDENT_UDF_NUM_VALUE INCIDENT_VERSION INCIDENT_X_PARTY INCIDENT_X_USER_GROUP PARTY_CONFIG PARTY_CONFIG_X_USER_GROUP 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 Definition 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. 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 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 screen. Contains search filter field configurations for the party search screen. Contains search result field configurations for the party search screen. 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 4
5 Table REF_TABLE_VALUE RELATED_ITEM_CONFIG SCHEMA_VERSION SNA_CONFIG_DETAIL SNA_CONFIG_MASTER SUBJSRCH_CONFIG_DETAIL SUBJSRCH_CONFIG_MASTER TASK_LIST Definition 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. 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. SUBJSRCH_CONFIG_MASTER 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. CASE_CONFIG CASE_CONFIG_SEQ_NO NUMBER(10) Case sequence number. CASE_TYPE_CD VARCHAR2(32) Case type code. CASE_CATEGORY_CD VARCHAR2(32) Case category code. CASE_SUBCATEGORY_CD VARCHAR2(32) 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. 5
6 CASE_CONFIG_X_USER_GROUP CASE_CONFIG_SEQ_NO NUMBER(10) Case sequence number. USER_GROUP_NM VARCHAR2(60) User group name. CASE_LIVE CASE_RK NUMBER(10) System-generated case surrogate key. VALID_TO_DTTM TIMESTAMP Standard dates used for versioning. CASE_ID VARCHAR2(64) Case identifier. SOURCE_SYSTEM_CD VARCHAR2(10) Source system code. CASE_TYPE_CD VARCHAR2(32) Case type code. CASE_CATEGORY_CD VARCHAR2(32) Case category code. CASE_SUBCATEGORY_CD VARCHAR2(32) 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 is used for sorting (for example, High, Medium, and 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 and time when the case was opened. REOPEN_DTTM TIMESTAMP Date and time when the case was last re-opened. CLOSE_DTTM TIMESTAMP Date and 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. 6
7 CASE_LIVE CREATE_DTTM TIMESTAMP Date and 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. CASE_SEARCH_CRITERIA_FIELD 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. CASE_SEARCH_FILTER_FIELD 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. CASE_SEARCH_RESULT_FIELD 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. 7
8 CASE_SEARCH_RESULT_FIELD FORMAT_TXT VARCHAR2(40) Name of the resource bundle key that contains the display format for numeric and date fields. CASE_UDF_CHAR_VALUE CASE_RK NUMBER(10) System generated case surrogate key. ROW_NO NUMBER(10) Row number. UDF_VALUE VARCHAR2(4000) User-defined field value. CASE_UDF_DATE_VALUE CASE_RK NUMBER(10) System generated case surrogate key. ROW_NO NUMBER(10) Row number. UDF_VALUE TIMESTAMP User-defined field value. 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. 8
9 CASE_UDF_DEF MAX_CHAR_CNT NUMBER(6) Maximum number of characters for a CHAR data typed user-defined field. REF_TABLE_NM VARCHAR2(30) The name of the (optional) reference table used to display values for this field. CASE_UDF_LGCHR_VALUE CASE_RK NUMBER(10) System generated case surrogate key. ROW_NO NUMBER(10) Row number. UDF_VALUE CLOB User-defined field value. CASE_UDF_NUM_VALUE CASE_RK NUMBER(10) System generated case surrogate key. ROW_NO NUMBER(10) Row number. UDF_VALUE DOUBLE PRECISION User-defined field value. CASE_VERSION CASE_RK NUMBER(10) System generated case surrogate key. 9
10 CASE_VERSION VALID_TO_DTTM TIMESTAMP Standard dates used for versioning. CASE_ID VARCHAR2(64) Case identifier. SOURCE_SYSTEM_CD VARCHAR2(10) Source system code. CASE_TYPE_CD VARCHAR2(32) Case type code. CASE_CATEGORY_CD VARCHAR2(32) Case category code. CASE_SUBCATEGORY_CD VARCHAR2(32) 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 is used for sorting (for example, High, Medium, and 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 and time when the case was opened. REOPEN_DTTM TIMESTAMP Date and time when the case was last re-opened. CLOSE_DTTM TIMESTAMP Date and 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 and 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. 10
11 CASE_X_PARTY 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 and time when the case and party relationship was created. CASE_X_USER_GROUP 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. ECM_COLUMN_LABEL 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 they come 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 two-letter lowercase ISO 639 language code optionally appended with an underscore and a two-letter uppercase ISO 3166 country code. For example en 11
12 ECM_COLUMN_LABEL LABEL_TXT VARCHAR2(100) The translated label. ECM_EVENT EVENT_RK NUMBER(10) System generated event surrogate key. BUSINESS_OBJECT_NM VARCHAR2(100) Name of the type of object this event is associated with: CASE, INCIDENT, PARTY, RR, EFILE. BUSINESS_OBJECT_RK NUMBER(10) Key value of the event that is associated with this object. EVENT_TYPE_CD VARCHAR2(10) Event type code. EVENT_DESC VARCHAR2(256) Event description. CREATE_USER_ID VARCHAR2(60) User who created the event. CREATE_DTTM TIMESTAMP Date and time when the event was created. LINKED_OBJECT_NM VARCHAR2(100) Linked object name. LINKED_OBJECT_RK NUMBER(10) Linked object surrogate key. ECM_LOCALE LOCALE VARCHAR2(5) A locale supported by the application. The locale should follow the Java locale naming convention: a valid two-letter lowercase ISO 639 language code optionally appended with an underscore and a two-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. ECM_TABLE_LABEL SOURCE_NM VARCHAR2(30) The source of the translation entry. Valid values are 'application' if the label translation comes from the standard application translation 12
13 ECM_TABLE_LABEL files or 'custom' if they come 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 two-letter lowercase ISO 639 language code optionally appended with an underscore and a two-letter uppercase ISO 3166 country code. For example en, en_us, en_gb, fr_fr. LABEL_TXT VARCHAR2(100) The translated label. FINANCIAL_ITEM_CONFIG FINANCIAL_ITEM_CONFIG_SEQ_ NO NUMBER(10) The primary key for the FINANCIAL_ITEM_CONFIG table. FINANCIAL_ITEM_TYPE_CD VARCHAR2(32) 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. FINANCIAL_ITEM_LIVE 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 13
14 FINANCIAL_ITEM_LIVE identifier for FINANCIAL_ITEM_LIVE. Used with valid_from_dttm for versioning of rows. FINANCIAL_ITEM_ID VARCHAR2(64) 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(32) 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 and 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. 14
15 FINANCIAL_ITEM_LIVE VERSION_NO NUMBER(10) Version number. DELETE_FLG CHAR(1) Has the financial item been logically deleted? FINANCIAL_ITEM_UDF_CHAR_VALUE FINANCIAL_ITEM_RK NUMBER(10) Since source data for FINANCIAL_ITEM_UDF_CHAR_V ALUE 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_V ALUE. Used with valid_from_dttm for versioning of rows. ROW_NO NUMBER(10) Row number. UDF_VALUE VARCHAR2(4000) User-defined field value. FINANCIAL_ITEM_UDF_DATE_VALUE FINANCIAL_ITEM_RK NUMBER(10) Since source data for FINANCIAL_ITEM_UDF_DATE_V ALUE 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_V ALUE. Used with valid_from_dttm for versioning of rows. 15
16 FINANCIAL_ITEM_UDF_DATE_VALUE ROW_NO NUMBER(10) Row number. UDF_VALUE TIMESTAMP User-defined field value. FINANCIAL_ITEM_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. REF_TABLE_NM VARCHAR2(30) The name of the (optional) reference table used to display values for this field. FINANCIAL_ITEM_UDF_LGCHR_VALUE 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. Used with valid_from_dttm for versioning of rows. 16
17 FINANCIAL_ITEM_UDF_LGCHR_VALUE ROW_NO NUMBER(10) Row Number UDF_VALUE CLOB User-defined field value. FINANCIAL_ITEM_UDF_NUM_VALUE FINANCIAL_ITEM_RK NUMBER(10) Since source data for FINANCIAL_ITEM_UDF_NUM_VA LUE 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_VA LUE. Used with valid_from_dttm for versioning of rows. ROW_NO NUMBER(10) Row number. UDF_VALUE DOUBLE PRECISION User-defined field value. FINANCIAL_ITEM_VERSION 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. Used with valid_from_dttm for versioning of rows. 17
18 FINANCIAL_ITEM_VERSION FINANCIAL_ITEM_ID VARCHAR2(64) Financial item ID. SOURCE_SYSTEM_CD VARCHAR2(10) Source system code. FINANCIAL_ITEM_TYPE_CD VARCHAR2(32) 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 and 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? GENERIC_DATA_UDF_CHAR_VALUE GENERIC_DATA_RK NUMBER(10) Since source data for GENERIC_DATA_UDF_CHAR_VA LUE 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 18
19 GENERIC_DATA_UDF_CHAR_VALUE identifier for GENERIC_DATA_UDF_CHAR_VA LUE. Used with valid_from_dttm for versioning of rows. VALID_TO_DTTM TIMESTAMP Standard dates used for versioning. UDF_VALUE VARCHAR2(4000) User-defined field value. GENERIC_DATA_UDF_DATE_VALUE GENERIC_DATA_RK NUMBER(10) Since source data for GENERIC_DATA_UDF_DATE_VA LUE 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 GENERIC_DATA_UDF_DATE_VA LUE. Used with valid_from_dttm for versioning of rows. VALID_TO_DTTM TIMESTAMP Standard dates used for versioning. 19
20 GENERIC_DATA_UDF_DATE_VALUE UDF_VALUE TIMESTAMP User-defined field value. GENERIC_DATA_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. REF_TABLE_NM VARCHAR2(30) The name of the (optional) reference table used to display values for this field. GENERIC_DATA_UDF_LGCHR_VALUE GENERIC_DATA_RK NUMBER(10) Since source data for GENERIC_DATA_UDF_LGCHR_V ALUE 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 GENERIC_DATA_UDF_LGCHR_V ALUE. Used with valid_from_dttm for versioning of rows. 20
21 GENERIC_DATA_UDF_LGCHR_VALUE VALID_TO_DTTM TIMESTAMP Standard dates used for versioning. UDF_VALUE CLOB User-defined field value. GENERIC_DATA_UDF_NUM_VALUE GENERIC_DATA_RK NUMBER(10) Since source data for GENERIC_DATA_UDF_NUM_VAL UE 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 GENERIC_DATA_UDF_NUM_VAL UE. Used with valid_from_dttm for versioning of rows. VALID_TO_DTTM TIMESTAMP Standard dates used for versioning. UDF_VALUE DOUBLE PRECISION User-defined field value. INCIDENT_CONFIG INCIDENT_CONFIG_SEQ_NO NUMBER(10) Incident configuration sequence number. The sequence number is 21
22 INCIDENT_CONFIG also used as a priority when multiple configurations apply for a given incident. If multiple configurations apply, the one with the smaller sequence number will be chosen. INCIDENT_TYPE_CD VARCHAR2(32) Incident type code. INCIDENT_CATEGORY_CD VARCHAR2(32) Incident category code. INCIDENT_SUBCATEGORY_CD VARCHAR2(32) Incident subcategory code. UI_DEF_FILE_NM VARCHAR2(100) User interface definition file name. INCIDENT_CONFIG_X_USER_GROUP INCIDENT_CONFIG_SEQ_NO NUMBER(10) Incident configuration sequence number. USER_GROUP_NM VARCHAR2(60) User group name. INCIDENT_LIVE INCIDENT_RK NUMBER(10) System generated incident surrogate key. VALID_TO_DTTM TIMESTAMP Standard dates used for versioning. CASE_RK NUMBER(10) System generated case surrogate key. INCIDENT_ID VARCHAR2(64) Incident identifier. SOURCE_SYSTEM_CD VARCHAR2(10) Source system code. INCIDENT_TYPE_CD VARCHAR2(32) Incident type code. INCIDENT_CATEGORY_CD VARCHAR2(32) Incident category code. INCIDENT_SUBCATEGORY_CD VARCHAR2(32) Incident sub-category code. INCIDENT_DESC VARCHAR2(100) Incident description. INCIDENT_FROM_DT DATE Incident start date. INCIDENT_FROM_TM CHAR(8) Incident start time (format = 22
23 INCIDENT_LIVE HH:MM:SS). INCIDENT_TO_DT DATE Incident end date. INCIDENT_TO_TM CHAR(8) Incident end time (format = HH:MM:SS). DETECTION_DT DATE Incident detection date. DETECTION_TM CHAR(8) Incident detection time (format = HH:MM:SS). NOTIFICATION_DT DATE Incident notification date. NOTIFICATION_TM CHAR(8) Incident notification time (format = HH:MM:SS). UI_DEF_FILE_NM VARCHAR2(100) Custom Page Builder user interface file name. CREATE_USER_ID VARCHAR2(60) User who created the incident. CREATE_DTTM TIMESTAMP Date and time when the incident was created. UPDATE_USER_ID VARCHAR2(60) User who last updated the incident. VERSION_NO NUMBER(10) Version number used to implement optimistic locking. DELETE_FLG CHAR(1) Has the incident been logically deleted? INVESTIGATOR_USER_ID VARCHAR2(60) Investigator for the incident. INCIDENT_DISPOSITION_CD VARCHAR2(10) Incident disposition code. CLOSE_DTTM TIMESTAMP Date and time when the incident was closed. INCIDENT_STATUS_CD VARCHAR2(10) Incident status code. INCIDENT_SEARCH_CRITERIA_FIELD 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. INCIDENT_SEARCH_FILTER_FIELD USER_ID VARCHAR2(60) User who this configuration applies to. Equals '*' for the default configuration for all users. 23
24 INCIDENT_SEARCH_FILTER_FIELD 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. INCIDENT_SEARCH_RESULT_FIELD 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. INCIDENT_UDF_CHAR_VALUE INCIDENT_RK NUMBER(10) System generated incident surrogate key. ROW_NO NUMBER(10) Row number. UDF_VALUE VARCHAR2(4000) User-defined field value. INCIDENT_UDF_DATE_VALUE INCIDENT_RK NUMBER(10) System generated incident surrogate key. 24
25 INCIDENT_UDF_DATE_VALUE ROW_NO NUMBER(10) Row number. UDF_VALUE TIMESTAMP User-defined field value. INCIDENT_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. REF_TABLE_NM VARCHAR2(30) The name of the (optional) reference table used to display values for this field. INCIDENT_UDF_LGCHR_VALUE INCIDENT_RK NUMBER(10) System-generated incident surrogate key. ROW_NO NUMBER(10) Row number. UDF_VALUE CLOB User-defined field value. INCIDENT_UDF_NUM_VALUE INCIDENT_RK NUMBER(10) System-generated incident surrogate key. 25
26 INCIDENT_UDF_NUM_VALUE ROW_NO NUMBER(10) Row number. UDF_VALUE DOUBLE PRECISION User-defined field value. INCIDENT_VERSION INCIDENT_RK NUMBER(10) System generated incident surrogate key. VALID_TO_DTTM TIMESTAMP Standard dates used for versioning. CASE_RK NUMBER(10) System-generated case surrogate key. INCIDENT_ID VARCHAR2(64) Incident identifier. SOURCE_SYSTEM_CD VARCHAR2(10) Source system code. INCIDENT_TYPE_CD VARCHAR2(32) Incident type code. INCIDENT_CATEGORY_CD VARCHAR2(32) Incident category code. INCIDENT_SUBCATEGORY_CD VARCHAR2(32) Incident sub-category code. INCIDENT_DESC VARCHAR2(100) Incident description. INCIDENT_FROM_DT DATE Incident start date. INCIDENT_FROM_TM char(8) Incident start time (format = HH:MM:SS). INCIDENT_TO_DT DATE Incident end date. INCIDENT_TO_TM char(8) Incident end time (format = HH:MM:SS). DETECTION_DT DATE Incident detection date. 26
27 INCIDENT_VERSION DETECTION_TM char(8) Incident detection time (format = HH:MM:SS). NOTIFICATION_DT DATE Incident notification date. NOTIFICATION_TM char(8) Incident notification time (format = HH:MM:SS). UI_DEF_FILE_NM VARCHAR2(100) Custom Page Builder user interface file name. CREATE_USER_ID VARCHAR2(60) User who created the incident. CREATE_DTTM TIMESTAMP Date and time when the incident was created. UPDATE_USER_ID VARCHAR2(60) User who last updated the incident. VERSION_NO NUMBER(10) Version number used to implement optimistic locking. DELETE_FLG char(1) Has the incident been logically deleted? INVESTIGATOR_USER_ID VARCHAR2(60) Investigator for the incident. INCIDENT_DISPOSITION_CD VARCHAR2(10) Incident disposition code. CLOSE_DTTM TIMESTAMP Date and time when the incident was closed. INCIDENT_STATUS_CD VARCHAR2(10) Incident status code. INCIDENT_X_PARTY INCIDENT_RK NUMBER(10) System-generated incident 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 and time when the incident/party relationship was created. INCIDENT_X_USER_GROUP INCIDENT_RK NUMBER(10) System-generated incident surrogate key. USER_GROUP_NM VARCHAR2(60) User group name. Equals '*' if any user may access the incident. PARTY_CONFIG PARTY_CONFIG_SEQ_NO NUMBER(10) Party configuration sequence number. The sequence number is also used as a priority when multiple configurations apply for a 27
28 PARTY_CONFIG given party. If multiple configurations apply, the one with the smaller sequence number will be chosen. PARTY_TYPE_CD VARCHAR2(32) Party type code. PARTY_CATEGORY_CD VARCHAR2(32) Party category code. PARTY_SUBCATEGORY_CD VARCHAR2(32) Party sub-category code. UI_DEF_FILE_NM VARCHAR2(100) Custom Page Builder user interface definition file name. PARTY_CONFIG_X_USER_GROUP PARTY_CONFIG_SEQ_NO NUMBER(10) Party configuration sequence number. USER_GROUP_NM VARCHAR2(60) User group name. PARTY_LIVE PARTY_RK NUMBER(10) System-generated party retained surrogate key. VALID_TO_DTTM TIMESTAMP Standard dates used for versioning. PARTY_ID VARCHAR2(64) Party identifier. SOURCE_SYSTEM_CD VARCHAR2(10) Source system code. PARTY_TYPE_CD VARCHAR2(32) Party type code. PARTY_CATEGORY_CD VARCHAR2(32) Party category code. PARTY_SUBCATEGORY_CD VARCHAR2(32) Party sub-category code. IDENTICAL_PARTY_LINK_SK NUMBER(10) System generated surrogate key for linking identical parties. INDIVIDUAL_FLG CHAR(1) Is the party an individual? PARTY_FULL_NM VARCHAR2(200) Party full name. NATIONAL_ID VARCHAR2(32) National identification number. NATIONAL_ID_TYPE_CD VARCHAR2(10) National identification number type 28
29 PARTY_LIVE code. UI_DEF_FILE_NM VARCHAR2(100) Custom Page Builder user interface file name. CREATE_USER_ID VARCHAR2(60) User who created the party. CREATE_DTTM TIMESTAMP Date and time when the party was created. UPDATE_USER_ID VARCHAR2(60) User who last updated the party. VERSION_NO NUMBER(10) Version number used to implement optimistic locking. DELETE_FLG CHAR(1) This flag indicates whether or not the Party has been logically deleted and is now obsolete. PARTY_SEARCH_CRITERIA_FIELD 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. PARTY_SEARCH_FILTER_FIELD 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. PARTY_SEARCH_RESULT_FIELD 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. 29
30 PARTY_SEARCH_RESULT_FIELD 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. PARTY_UDF_CHAR_VALUE PARTY_RK NUMBER(10) System-generated party retained surrogate key. ROW_NO NUMBER(10) Row number. UDF_VALUE VARCHAR2(4000) User-defined field value. PARTY_UDF_DATE_VALUE PARTY_RK NUMBER(10) System-generated party retained surrogate key. ROW_NO NUMBER(10) Row number. UDF_VALUE TIMESTAMP User-defined field value. PARTY_UDF_DEF 30
31 PARTY_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. REF_TABLE_NM VARCHAR2(30) The name of the (optional) reference table used to display values for this field. PARTY_UDF_LGCHR_VALUE PARTY_RK NUMBER(10) System-generated party retained surrogate key. ROW_NO NUMBER(10) Row number. UDF_VALUE CLOB User-defined field value. PARTY_UDF_NUM_VALUE PARTY_RK NUMBER(10) System generated party retained surrogate key. ROW_NO NUMBER(10) Row number. UDF_VALUE DOUBLE PRECISION User defined field value. 31
32 PARTY_VERSION PARTY_RK NUMBER(10) System generated party retained surrogate key. VALID_TO_DTTM TIMESTAMP Standard dates used for versioning. PARTY_ID VARCHAR2(64) Party identifier. SOURCE_SYSTEM_CD VARCHAR2(10) Source system code. PARTY_TYPE_CD VARCHAR2(32) Party type code. PARTY_CATEGORY_CD VARCHAR2(32) Party category code. PARTY_SUBCATEGORY_CD VARCHAR2(32) Party sub-category code. IDENTICAL_PARTY_LINK_SK NUMBER(10) System generated surrogate key for linking identical parties. INDIVIDUAL_FLG CHAR(1) Is the party an individual? PARTY_FULL_NM VARCHAR2(200) Party full name. NATIONAL_ID VARCHAR2(32) National identification number. NATIONAL_ID_TYPE_CD VARCHAR2(10) National identification number type code. UI_DEF_FILE_NM VARCHAR2(100) Custom Page Builder user interface file name. CREATE_USER_ID VARCHAR2(60) User who created the party. CREATE_DTTM TIMESTAMP Date and time when the party was created. UPDATE_USER_ID VARCHAR2(60) User who last updated the party. VERSION_NO NUMBER(10) Version number used to implement optimistic locking. DELETE_FLG CHAR(1) This flag indicates whether or not the Party has been logically deleted and is now obsolete. PARTY_X_PARTY PARTY_RK NUMBER(10) System-generated party retained surrogate key. MEMBER_PARTY_RK NUMBER(10) Surrogate key of a party that is a 32
33 PARTY_X_PARTY member of another party. MEMBER_TYPE_CD VARCHAR2(10) Membership type code. MEMBER_DESC VARCHAR2(100) Membership description. PARTY_X_USER_GROUP PARTY_RK NUMBER(10) System-generated party retained surrogate key. USER_GROUP_NM VARCHAR2(60) User group name. Equals '*' if any user may access the party. REF_TABLE_TRANS REF_TABLE_NM VARCHAR2(30) Reference table name. VALUE_CD VARCHAR2(32) Coded value. LOCALE VARCHAR2(5) A locale supported by the application. The locale should follow the Java locale naming convention: a valid two-letter lowercase ISO 639 language code optionally appended with an underscore and a two-letter uppercase ISO 3166 country code. For example en, en_us, en_gb, fr_fr. VALUE_DESC VARCHAR2(100) The localized description for the given LOCALE of the reference table entry identified by the given REF_TABLE_NM and VALUE_CD. REF_TABLE_VALUE REF_TABLE_NM VARCHAR2(30) Reference table name. VALUE_CD VARCHAR2(32) Coded value. VALUE_DESC VARCHAR2(100) Displayable value. PARENT_REF_TABLE_NM VARCHAR2(30) Reference table name. PARENT_VALUE_CD VARCHAR2(32) Coded value. DISPLAY_ORDER_NO NUMBER(6) Display order number. ACTIVE_FLG CHAR(1) Flag indicates whether the reference table value is still active. RELATED_ITEM_CONFIG RELATED_ITEM_RK NUMBER(10) Since source data for RELATED_ITEM_CONFIG may come from multiple systems, the 33
34 RELATED_ITEM_CONFIG business supplied keys may not be unique. A surrogate key is added in the ETL process to ensure a unique identifier for RELATED_ITEM_CONFIG. Used with valid_from_dttm for versioning of rows. RELATED_ITEM_ID VARCHAR2(32) Related Item ID. RELATED_ITEM_DESC VARCHAR2(100) Description field. RELATED_PARTY_FIELD_NM VARCHAR2(30) Name of the subject field that will be used to match the subjects. RELATED_INCIDENT_FIELD_NM VARCHAR2(30) Name of the incident field that will be used to match incidents. RELATED_CASE_FIELD_NM VARCHAR2(30) Name of the case field that will be used to match the cases. CREATE_USER_ID VARCHAR2(60) ID of the user who created the Related Item Config record. CREATE_DTTM TIMESTAMP Date and time of when record was added. UPDATE_USER_ID VARCHAR2(60) ID of the user who updated this record. DELETE_FLG CHAR(1) Has the record been logically deleted? SCHEMA_VERSION VERSION_ID VARCHAR2(10) Schema version identifier (single row). SNA_CONFIG_DETAIL SNA_CONFIG_RK NUMBER(10) Since source data for SNA_CONFIG_DETAIL 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 SNA_CONFIG_DETAIL. Used with valid_from_dttm for versioning of rows. SNA_CONFIG_SEQ_NO NUMBER(10) System generated sequence. The combination of SNA_CONFIG_RK and SNA_CONFIG_SEQ_NO make the record unique. FROM_PARTY_TABLE_NM VARCHAR2(30) Name of the table where FROM_PARTY_FIELD_NM is 34
35 SNA_CONFIG_DETAIL found FROM_PARTY_FIELD_NM VARCHAR2(30) Name of the subject form matching subjects. This is the 'match from' field. FROM_PARTY_FIELD_EXP VARCHAR2(4000) Expression to be used to define FROM_PARTY_FIELD_NM. If blank, FROM_PARTY_FIELD_NM will be used for matching subjects. TO_PARTY_TABLE_NM VARCHAR2(30) Name of the table where TO_PARTY_FIELD_NM is found TO_PARTY_FIELD_NM VARCHAR2(30) Name of the subject field for matching subjects. This is the 'match to' field. TO_PARTY_FIELD_EXP VARCHAR2(4000) Expression to be used to define TO_PARTY_FIELD_NM. If blank, TO_PARTY_FIELD_NM will be used for matching subjects DELETE_FLG CHAR(1) Has the record been logically deleted? SNA_CONFIG_MASTER SNA_CONFIG_RK NUMBER(10) Since source data for SNA_CONFIG_MASTER 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 SNA_CONFIG_MASTER. Used with valid_from_dttm for versioning of rows. SNA_CONFIG_ID VARCHAR2(32) ID of the Case Network Analysis match criterion. SNA_CONFIG_DESC VARCHAR2(100) Description of the Case Network Analysis match criterion. DELETE_FLG CHAR(1) Has the record been logically deleted? CREATE_USER_ID VARCHAR2(60) Id of the user who created the Related Item Config record. CREATE_DTTM TIMESTAMP Date and time of when record was added. UPDATE_USER_ID VARCHAR2(60) Id of the user who updated this record. 35
36 SUBJSRCH_CONFIG_DETAIL SUBJSRCH_CONFIG_RK NUMBER(10) Since source data for SUBJSRCH_CONFIG_DETAIL 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 SUBJSRCH_CONFIG_DETAIL. Used with valid_from_dttm for versioning of rows. SUBJSRCH_CONFIG_SEQ_NO NUMBER(10) System generated sequence. The combination of SNA_CONFIG_RK and SNA_CONFIG_SEQ_NO make the record unique. FROM_PARTY_TABLE_NM VARCHAR2(30) Name of the table where FROM_PARTY_FIELD_NM is found. FROM_PARTY_FIELD_NM VARCHAR2(30) Name of the subject form matching subjects. This is the 'match from' field. FROM_PARTY_FIELD_EXP VARCHAR2(4000) Expression to be used to define FROM_PARTY_FIELD_NM. If blank, FROM_PARTY_FIELD_NM will be used for matching subjects. TO_PARTY_TABLE_NM VARCHAR2(30) Name of the table where TO_PARTY_FIELD_NM is found. TO_PARTY_FIELD_NM VARCHAR2(30) Name of the subject field for matching subjects. This is the 'match to' field. TO_PARTY_FIELD_EXP VARCHAR2(4000) Expression to be used to define TO_PARTY_FIELD_NM. If blank, TO_PARTY_FIELD_NM will be used for matching subjects. DELETE_FLG CHAR(1) Has the record been logically deleted? SUBJSRCH_CONFIG_MASTER SUBJSRCH_CONFIG_RK NUMBER(10) Since source data for SUBJSRCH_CONFIG_MASTER 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 SUBJSRCH_CONFIG_MASTER. Used with valid_from_dttm for versioning of rows. 36
37 SUBJSRCH_CONFIG_MASTER SUBJSRCH_CONFIG_ID VARCHAR2(32) ID of the Case Network Analysis match criterion. SUBJSRCH_CONFIG_DESC VARCHAR2(100) Description of the Case Network Analysis match criterion. DELETE_FLG CHAR(1) Has the record been logically deleted? CREATE_USER_ID VARCHAR2(60) Id of the user who created the Related Item Config record. CREATE_DTTM TIMESTAMP Date and time of when record was added. UPDATE_USER_ID VARCHAR2(60) ID of the user who updated this record. TASK_LIST TASK_LIST_RK NUMBER(10) Since source data for TASK_LIST 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 TASK_LIST. Used with valid_from_dttm for versioning of rows. BUSINESS_OBJECT_RK NUMBER(10) This key links the task to a case or an incident. BUSINESS_OBJECT_NM VARCHAR2(100) The business object name links a Task to a Case or an Incident along with the surrogate key of that business object. TASK_DESC VARCHAR2(1000) The description of the task. TASK_GOAL_DT DATE The expected completion date for this task. COMPLETE_FLG CHAR(1) Is this task complete? TIMEZONE_OFFSET NUMBER The time zone offset for the user who is to receive or who has received the reminder. REMINDER_DTTM TIMESTAMP Standard dates used for versioning. REMINDER_SENT_DTTM TIMESTAMP Standard dates used for versioning. 37
38 TASK_LIST OWNER_ID VARCHAR2(60) The user ID of the current task owner. REMINDER_USER_ID VARCHAR2(60) The user ID of the reminder receipient. ALERT_ID NUMBER(20) The alert ID for the reminder to be issued. 38
SAS Enterprise Case Management 6.3. Data Dictionary
SAS Enterprise Case Management 6.3 Data Dictionary The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2015. SAS Enterprise Case Management 6.3: Data Dictionary. Cary,
More informationSAS Enterprise Case Management 3.1. Data Dictionary
SAS Enterprise Case Management 3.1 Data Dictionary The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2012. SAS Enterprise Case Management 3.1: Data Dictionary. Cary,
More informationSAS Enterprise Case Management 2.1. Administrator s Guide
SAS Enterprise Case Management 2.1 Administrator s Guide The correct bibliographic citation for this manual is as follows: SAS Institute, Inc. 2010. SAS Enterprise Case Management 2.1: Administrator's
More informationWorkflow Templates in Compliance 360 Version 2018
Workflow Templates in Compliance 360 Version 2018 Workflow Templates 5 Workflow Elements 6 Workflow Teams 6 Workflow Template Changes 6 Create or Edit a Workflow Template 8 Import and Export Workflow Templates
More informationSAS Enterprise Case Management 2.2. Administrator s Guide
SAS Enterprise Case Management 2.2 Administrator s Guide The correct bibliographic citation for this manual is as follows: SAS Institute, Inc. 2010. SAS Enterprise Case Management 2.2: Administrator's
More informationOracle Financial Services Regulatory Reporting Rwanda Suspicious Transaction Report User Guide. Release October 2014
Oracle Financial Services Regulatory Reporting Rwanda Suspicious Transaction Report User Guide Release 2.5.2 October 2014 Oracle Financial Services Regulatory Reporting Rwanda Suspicious Transaction Report
More informationOracle Financial Services Currency Transaction Reporting User Guide. Release 1.2 December 2014
Oracle Financial Services Currency Transaction Reporting User Guide Release 1.2 December 2014 Oracle Financial Services Currency Transaction Reporting User Guide Release 1.2 December 2014 Document Control
More informationBanner General Release Guide. Release June 2017
Banner General Release Guide Release 8.9.2 June 2017 Notices Notices 2017 Ellucian. Contains confidential and proprietary information of Ellucian and its subsidiaries. Use of these materials is limited
More informationOracle Financial Services Currency Transaction Reporting User Guide. Release June 2015
Oracle Financial Services Currency Transaction Reporting User Guide Release 1.2.1 June 2015 Oracle Financial Services Currency Transaction Reporting User Guide Release 1.2.1 June 2015 Document Control
More informationOracle Financial Services Currency Transaction Reporting User Guide. Release January 2015
Oracle Financial Services Currency Transaction Reporting User Guide Release 8.0.0.0.0 January 2015 Oracle Financial Services Currency Transaction Reporting User Guide Release 8.0.0.0.0 January 2015 Part
More informationQuick-Start User Guide. Analytix Data Services Analytix: Mapping Manager. Quick-Start User Guide. Version 2.4
Analytix Data Services Analytix: Mapping Manager Quick-Start User Guide Version 2.4 Analytix Data Services LLC Page 1 of 62 Copyright Notice This manual is Analytix Data Services LLC 2007. All rights reserved.
More informationAccess Objects. Tables Queries Forms Reports Relationships
Access Review Access Objects Tables Queries Forms Reports Relationships How Access Saves a Database The Save button in Access differs from the Save button in other Windows programs such as Word and Excel.
More informationConfiguring Job Monitoring in SAP Solution Manager 7.2
How-To Guide SAP Solution Manager Document Version: 1.0 2017-05-31 Configuring Job Monitoring in SAP Solution Manager 7.2 Typographic Conventions Type Style Example Example EXAMPLE Example Example
More informationSQL Fundamentals. Chapter 3. Class 03: SQL Fundamentals 1
SQL Fundamentals Chapter 3 Class 03: SQL Fundamentals 1 Class 03: SQL Fundamentals 2 SQL SQL (Structured Query Language): A language that is used in relational databases to build and query tables. Earlier
More informationOracle Financial Services Compliance Regulatory Reporting India Suspicious Transaction Report User Guide. Release
Oracle Financial Services Compliance Regulatory Reporting India Suspicious Transaction Report User Guide Release 8.0.6.0.0 May 2018 Oracle Financial Services Compliance Regulatory Reporting India Suspicious
More informationOracle Financial Services Compliance Regulatory Reporting Indonesia Suspicious Transaction Report User Guide. Release 2.5.
Oracle Financial Services Compliance Regulatory Reporting Indonesia Suspicious Transaction Report User Guide Release 2.5.5 December 2015 Oracle Financial Services Compliance Regulatory Reporting Indonesia
More informationReading Sample. System Reports. Contents. Index. The Authors. First-hand knowledge.
First-hand knowledge. Reading Sample In this sample chapter, you ll learn how to use the out-of-the-box SAP BPC reports that come preloaded with your installation so that you can analyze both system administration
More informationOracle Financial Services Compliance Regulatory Reporting Canada Suspicious Transaction Report User Guide. Release May 2016
Oracle Financial Services Compliance Regulatory Reporting Canada Suspicious Transaction Report User Guide Release 2.5.6 May 2016 Oracle Financial Services Compliance Regulatory Reporting Canada Suspicious
More informationOracle Financial Services Compliance Regulatory Reporting Uganda Suspicious Transaction Report User Guide. Release 2.5.
Oracle Financial Services Compliance Regulatory Reporting Uganda Suspicious Transaction Report User Guide Release 2.5.4 November 2015 Oracle Financial Services Compliance Regulatory Reporting Uganda Suspicious
More informationOracle Financial Services Regulatory Reporting Uganda Suspicious Transaction Report User Guide. Release October 2014
Oracle Financial Services Regulatory Reporting Uganda Suspicious Transaction Report User Guide Release 2.5.2 October 2014 Oracle Financial Services Regulatory Reporting Uganda Suspicious Transaction Report
More informationThe MDM ETL Command Line Tool is named "Clarity MDM ETL.exe", and can be found in <Drive>: \Program Files\Clarity Systems\Clarity MDM\ folder.
MDM ETL Guide The MDM ETL Command Line Tool is named "Clarity MDM ETL.exe", and can be found in : \Program Files\Clarity Systems\Clarity MDM\ folder. There are 4 ETL modes available: ension Load
More informationFull file at
ch2 True/False Indicate whether the statement is true or false. 1. The SQL command to create a database table is an example of DML. 2. A user schema contains all database objects created by a user. 3.
More informationUser Group Configuration
CHAPTER 90 The role and user group menu options in the Cisco Unified Communications Manager Administration User Management menu allow users with full access to configure different levels of access for
More informationLecture 07. Spring 2018 Borough of Manhattan Community College
Lecture 07 Spring 2018 Borough of Manhattan Community College 1 SQL Identifiers SQL identifiers are used to identify objects in the database, such as table names, view names, and columns. The ISO standard
More informationDatabase Programming with PL/SQL
Database Programming with PL/SQL 2-3 Objectives This lesson covers the following objectives: Define data type and explain why it is needed List and describe categories of data types Give examples of scalar
More informationCommercial Bill Pay Administration Guide. January 2017
Commercial Bill Pay Administration Guide January 2017 1 Contents CheckFree Small Business Administration... 2 Administration... 2 Objectives... 2 Manage Authorized Users... 3 Changing Password... 4 Add
More informationUser Guide. Trade Finance Global. For customers using Guarantees. October nordea.com/cm OR tradefinance Name of document 5/8 2015/V1
User Guide Trade Finance Global For customers using Guarantees October 2015 nordea.com/cm OR tradefinance Name of document 2015/V1 5/8 Table of Contents 1 Trade Finance Global (TFG) - Introduction... 4
More informationMicrosoft Office Illustrated Introductory, Building and Using Queries
Microsoft Office 2007- Illustrated Introductory, Building and Using Queries Creating a Query A query allows you to ask for only the information you want vs. navigating through all the fields and records
More informationOracle Financial Services Regulatory Reporting User Guide MY STR. Release 2.4 October 2013
Oracle Financial Services Regulatory Reporting User Guide MY STR Release 2.4 October 2013 Oracle Financial Services Regulatory Reporting User Guide MY STR Release 2.4 October 2013 Document Control Number:
More informationOracle Financial Services Compliance Regulatory Reporting India Suspicious Transaction Report User Guide. Release
Oracle Financial Services Compliance Regulatory Reporting India Suspicious Transaction Report User Guide Release 8.0.5.0.0 October 2017 Oracle Financial Services Compliance Regulatory Reporting India
More informationA Practical Guide to Migrating from Oracle to MySQL. Robin Schumacher
A Practical Guide to Migrating from Oracle to MySQL Robin Schumacher Director of Product Management, MySQL AB 1 Agenda Quick look at MySQL AB Relationship between Oracle and MySQL n-technical reasons why
More informationOracle Financial Services Regulatory Reporting User Guide US SAR. Release June 2014
Oracle Financial Services Regulatory Reporting User Guide US SAR Release 2.5.1 June 2014 Oracle Financial Services Regulatory Reporting User Guide US SAR Release 2.5.1 June 2014 Document Control Number:
More informationOracle Financial Services Compliance Regulatory Reporting User Guide US SAR. Release April 2017
Oracle Financial Services Compliance Regulatory Reporting User Guide US SAR Release 8.0.4 April 2017 Oracle Financial Services Compliance Regulatory Reporting User Guide US SAR Release 8.0.4 April 2017
More informationMicrosoft Access Illustrated. Unit B: Building and Using Queries
Microsoft Access 2010- Illustrated Unit B: Building and Using Queries Objectives Use the Query Wizard Work with data in a query Use Query Design View Sort and find data (continued) Microsoft Office 2010-Illustrated
More informationReadme File. Purpose. Hyperion Financial Data Quality Management for Enterprise Release Readme
Hyperion Financial Data Quality Management for Enterprise Release 7.2.1 Readme Readme File This file contains the following sections: Purpose... 1 Restrictions... 2 New Features... 2 Multi-Language Support...
More informationOracle Financial Services Regulatory Reporting Bahamas Suspicious Transaction Report User Guide. Release 2.4 October 2013
Oracle Financial Services Regulatory Reporting Bahamas Suspicious Transaction Report User Guide Release 2.4 October 2013 Oracle Financial Services Regulatory Reporting Bahamas Suspicious Transaction Report
More informationAnalytics External Data Format Reference
Analytics External Data Format Reference Salesforce, Spring 18 @salesforcedocs Last updated: January 11, 2018 Copyright 2000 2018 salesforce.com, inc. All rights reserved. Salesforce is a registered trademark
More informationPega Foundation for Financial Services
Pega Foundation for Financial Services ACCOUNTING GUIDE 7.32 2017 Pegasystems Inc., Cambridge, MA All rights reserved. Trademarks For Pegasystems Inc. trademarks and registered trademarks, all rights reserved.
More informationOracle Financial Services Common Reporting Standard Singapore User Guide. Release May 2018
Oracle Financial Services Common Reporting Standard Singapore User Guide Release 8.0.6 May 2018 Oracle Financial Services Common Reporting Standard Singapore User Guide Release 8.0.6 May 2018 Part Number:
More informationOracle Financial Services Regulatory Reporting User Guide SG STR. Release 2.4 October 2013
Oracle Financial Services Regulatory Reporting User Guide SG STR Release 2.4 October 2013 Oracle Financial Services Regulatory Reporting User Guide SG STR Release 2.4 October 2013 Document Control Number:
More informationOracle Financial Services Common Reporting Standard Canada User Guide. Release May 2018
Oracle Financial Services Common Reporting Standard Canada User Guide Release 8.0.6 May 2018 Oracle Financial Services Common Reporting Standard Canada User Guide Release 8.0.6 May 2018 Part Number: E93132-01
More informationCLIQ Web Manager. User Manual. The global leader in door opening solutions V 6.1
CLIQ Web Manager User Manual V 6.1 The global leader in door opening solutions Program version: 6.1 Document number: ST-003478 Date published: 2016-03-31 Language: en-gb Table of contents 1 Overview...9
More informationGridDB Advanced Edition SQL reference
GMA022C1 GridDB Advanced Edition SQL reference Toshiba Solutions Corporation 2016 All Rights Reserved. Introduction This manual describes how to write a SQL command in the GridDB Advanced Edition. Please
More informationOracle Revenue Management and Billing for Financial Services Version
Oracle Revenue Management and Billing for Financial Services Version 2.2.4.0 Revision 1.0 E26807-01 November, 2011 Oracle Revenue Management and Billing E26807-01 Copyright 2010, Oracle and/or its affiliates.
More informationHyperion 4H Hyperion Financial Management v
Hyperion 4H0-435 Hyperion Financial Management v3.51 http://killexams.com/exam-detail/4h0-435 Answer: B QUESTION: 167 A client has a dynamic process of adding new accounts and products every month. They
More informationSAS Financial Management 5.5. Data Model Reference
SAS Financial Management 5.5 Data Model Reference The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2015. SAS Financial Management 5.5: Data Model Reference. Cary, NC:
More informationIntellicus Enterprise Reporting and BI Platform
Working with Query Objects Intellicus Enterprise Reporting and BI Platform ` Intellicus Technologies info@intellicus.com www.intellicus.com Working with Query Objects i Copyright 2012 Intellicus Technologies
More informationFundamentals, Design, and Implementation, 9/e Copyright 2004 Database Processing: Fundamentals, Design, and Implementation, 9/e by David M.
Chapter 5 Database Design Elements of Database Design Fundamentals, Design, and Implementation, 9/e Chapter 5/2 The Database Design Process Create tables and columns from entities and attributes Select
More informationFSEDIT Procedure Windows
25 CHAPTER 4 FSEDIT Procedure Windows Overview 26 Viewing and Editing Observations 26 How the Control Level Affects Editing 27 Scrolling 28 Adding Observations 28 Entering and Editing Variable Values 28
More informationQuickStart Guide 4 - Merge
QuickStart Guide 4 - Merge Document Version: v1.0 Product Version: v2.x Date: 13 th May 2017 This document provides an overview and Step-by-Step implementation instructions for the clearmdm Merge MDM operation.
More informationACTIVANT. Prophet 21 ACTIVANT PROPHET 21. New Features Guide Version 11.0 ADMINISTRATION NEW FEATURES GUIDE (SS, SA, PS) Pre-Release Documentation
I ACTIVANT ACTIVANT PROPHET 21 Prophet 21 ADMINISTRATION NEW FEATURES GUIDE (SS, SA, PS) New Features Guide Version 11.0 Version 11.5 Pre-Release Documentation This manual contains reference information
More informationOracle Financial Services Common Reporting Standard User Guide. Release March 2017
Oracle Financial Services Common Reporting Standard User Guide Release 8.0.4.0.0 March 2017 Oracle Financial Services Common Reporting Standard User Guide Release 8.0.4.0.0 March 2017 Part Number: E80239-01
More informationGEOFidelis SDSFIE Implementation Roles and Responsibilities Guide
GEOFidelis SDSFIE Implementation Roles and Responsibilities Guide Version: 1.4 Prepared for: USMC Installation Geospatial Information and Services Program (GEOFidelis) November 19th, 2012 TABLE OF CONTENTS
More informationCase Management System
Case Management System Administrator Instructions Your Lighthouse Services Case Management System (CMS) has been set up and is ready for your use. It is a powerful tool to oversee and manage all your Lighthouse
More informationProject and Portfolio Management Center
Project and Portfolio Management Center Software Version: 9.42 Getting Started Go to HELP CENTER ONLINE http://admhelp.microfocus.com/ppm/ Document Release Date: September 2017 Software Release Date: September
More informationSAS 9.3 LIBNAME Engine for DataFlux Federation Server
SAS 9.3 LIBNAME Engine for DataFlux Federation Server User s Guide SAS Documentation The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2012. SAS 9.3 LIBNAME Engine for
More informationCase Management System
Case Management System Investigator/non-Administrator Instructions Your Lighthouse Services Case Management System (CMS) has been set up and is ready for your use. It is a powerful tool to oversee and
More informationSearching Guide. November 17, Version 9.5
Searching Guide November 17, 2017 - Version 9.5 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
More informationThis document contains information on fixed and known limitations for Test Data Management.
Informatica Corporation Test Data Management Version 9.6.0 Release Notes August 2014 Copyright (c) 2003-2014 Informatica Corporation. All rights reserved. Contents Informatica Version 9.6.0... 1 Installation
More informationOracle Financial Services: Alert Management User Guide. Release 6.1 December 2013
Oracle Financial Services: Alert Management User Guide Release 6.1 December 2013 Oracle Financial Services: Alert Management User Guide Release 6.1 December 2013 Document Control Number: 9MN11-0020 Document
More informationIBM. Administration Guide. IBM Emptoris Contract Management SaaS
IBM Emptoris Contract Management IBM Administration Guide 10.1.2 SaaS IBM Emptoris Contract Management IBM Administration Guide 10.1.2 SaaS ii IBM Emptoris Contract Management: Administration Guide Copyright
More informationSolutions that Work The Comprehensive Data Dictionary. Antonio Amorin
Solutions that Work The Comprehensive Data Dictionary Antonio Amorin Agenda Introductions Case Study Overview Assessment Solution Implementation Deliverables Utilization Biography Antonio Amorin President,
More informationMetastorm BPM Release 7.6
Metastorm BPM Release 7.6 Administration Guide May 2008 Metastorm Inc. email: inquiries@metastorm.com http://www.metastorm.com Metastorm BPM Release 7.6 Copyrights and Trademarks 1996-2008 Metastorm Inc.
More informationComputational Expression
Computational Expression Variables, Primitive Data Types, Expressions Janyl Jumadinova 28-30 January, 2019 Janyl Jumadinova Computational Expression 28-30 January, 2019 1 / 17 Variables Variable is a name
More informationPrecise for BW. User Guide. Version x
Precise for BW User Guide Version 9.8.0.x 2 Precise for BW User Guide Copyright 2018 Precise Software Solutions, Inc. All rights reserved. Precise for BW User Guide version 9.8.0.x Document release version
More informationExpense: Process Reports
Expense: Process Reports User Guide for Standard Edition Applies to these SAP Concur solutions: Expense Professional/Premium edition Standard edition Travel Professional/Premium edition Standard edition
More informationIBM. Bulk Load Utilities Guide. IBM Emptoris Contract Management SaaS
IBM Emptoris Contract Management IBM Bulk Load Utilities Guide 10.1.2 SaaS IBM Emptoris Contract Management IBM Bulk Load Utilities Guide 10.1.2 SaaS ii IBM Emptoris Contract Management: Bulk Load Utilities
More informationFormulas, LookUp Tables and PivotTables Prepared for Aero Controlex
Basic Topics: Formulas, LookUp Tables and PivotTables Prepared for Aero Controlex Review ribbon terminology such as tabs, groups and commands Navigate a worksheet, workbook, and multiple workbooks Prepare
More informationMcAfee MVISION Mobile MobileIron Integration Guide
McAfee MVISION Mobile MobileIron Integration Guide Administrator's guide for providing Integration with MobileIron MDM September 2018 COPYRIGHT Copyright 2018 McAfee, LLC TRADEMARK ATTRIBUTIONS McAfee
More informationRouting EDIFACT Documents in Productions
Routing EDIFACT Documents in Productions Version 2018.1 2018-01-31 InterSystems Corporation 1 Memorial Drive Cambridge MA 02142 www.intersystems.com Routing EDIFACT Documents in Productions InterSystems
More informationHow to Use Full Pushdown Optimization in PowerCenter
How to Use Full Pushdown Optimization in PowerCenter 2014 Informatica Corporation. No part of this document may be reproduced or transmitted in any form, by any means (electronic, photocopying, recording
More informationTeamTrack Database Schema
TeamTrack Database Schema Database Version: 21 Last Modified: January 20, 2000 Copyright 1998, 1999, TeamShare, Inc. All Rights Reserved Dear Customer, This document describes TeamShare s database schema
More informationAdministration Guide
Administration Guide 04/11/2018 Blackbaud Altru 4.96 Administration US 2017 Blackbaud, Inc. This publication, or any part thereof, may not be reproduced or transmitted in any form or by any means, electronic,
More information29 Shades of Missing
SESUG 2015 ABSTRACT Paper CC106 29 Shades of Missing Darryl Putnam, Pinnacle Solutions, LLC Missing values can have many flavors of missingness in your data and understanding these flavors of missingness
More informationGovernance, Risk, and Compliance Controls Suite. Preventive Controls Governor Flow Rules User s Guide. Software Version
Governance, Risk, and Compliance Controls Suite Preventive Controls Governor Flow Rules User s Guide Software Version 7.2.2.1 Preventive Controls Governor: Flow Rules User s Guide Part No. AR007-7221A
More informationManaging and Monitoring Cloudbreak
2 Managing and Monitoring Cloudbreak Date of Publish: 2018-09-14 http://docs.hortonworks.com Contents User authorization... 3 Prerequisites... 4 Manage workspaces...4 Access a workspace...6 Operations
More informationAnalysis/Intelligence: Data Model - Configuration
Analysis/Intelligence: Data Model - Configuration User Guide Table of Contents Data Model - Configuration... 1 Section 1: Folder Expense Types & Categories, Payment Types... 1 Expense Types & Categories,
More informationNRS Logical Data Model to Physical Data Model Transformations
Corporate Services for the Natural Resource Sector Information Management Branch NRS Logical Data Model to Physical Data Model Transformations Last Updated: Dec 10 th, 2016 Version: 2.1 Document: NRS Logical
More informationPeopleSoft 9.1 PeopleBook: Events and Notifications Framework
PeopleSoft 9.1 PeopleBook: Events and Notifications Framework March 2012 PeopleSoft 9.1 PeopleBook: Events and Notifications Framework SKU hcm91fp2eewh-b0312 Copyright 1988, 2012, Oracle and/or its affiliates.
More informationDepartment of Computer Science University of Cyprus. EPL342 Databases. Lab 2
Department of Computer Science University of Cyprus EPL342 Databases Lab 2 ER Modeling (Entities) in DDS Lite & Conceptual Modeling in SQL Server 2008 Panayiotis Andreou http://www.cs.ucy.ac.cy/courses/epl342
More informationRCT Express. Administrator Training Manual. Version 4.3
RCT Express Administrator Training Manual Version 4.3 Copyright 2016 CoreLogic. All rights reserved. ii Contents Introduction 1 System Requirements... 1 Tools 2 Administration 3 Manage Agencies... 3 Manage
More informationItem: 1 (Ref:Cert-1Z )
Page 1 of 13 Item: 1 (Ref:Cert-1Z0-071.10.2.1) Evaluate this CREATE TABLE statement: CREATE TABLE customer ( customer_id NUMBER, company_id VARCHAR2(30), contact_name VARCHAR2(30), contact_title VARCHAR2(20),
More information618 Index. BIT data type, 108, 109 BIT_LENGTH, 595f BIT VARYING data type, 108 BLOB data type, 108 Boolean data type, 109
Index A abbreviations in field names, 22 in table names, 31 Access. See under Microsoft acronyms in field names, 22 in table names, 31 aggregate functions, 74, 375 377, 416 428. See also AVG; COUNT; COUNT(*);
More informationCreating and Managing Tables Schedule: Timing Topic
9 Creating and Managing Tables Schedule: Timing Topic 30 minutes Lecture 20 minutes Practice 50 minutes Total Objectives After completing this lesson, you should be able to do the following: Describe the
More informationDeep Dive: Pronto Transformations Reference
Deep Dive: Pronto Transformations Reference Available Transformations and Their Icons Transform Description Menu Icon Add Column on page 2 Important: Not available in Trial. Upgrade to Pro Edition! Add
More informationSQL OVERVIEW. CS121: Relational Databases Fall 2017 Lecture 4
SQL OVERVIEW CS121: Relational Databases Fall 2017 Lecture 4 SQL 2 SQL = Structured Query Language Original language was SEQUEL IBM s System R project (early 1970 s) Structured English Query Language Caught
More informationQuickStart Guide 6 - Data Quality
QuickStart Guide 6 - Data Quality Document Version: v1.2 Product Version: v2.9 Date: 9 th September 2017 This document provides an overview and Step-by-Step implementation instructions for the clearmdm
More informationCase Management System
Case Management System Investigator/non-Administrator Instructions Your Lighthouse Services Case Management System (CMS) has been set up and is ready for your use. It is a powerful tool to oversee and
More informationFull file at
SQL for SQL Server 1 True/False Questions Chapter 2 Creating Tables and Indexes 1. In order to create a table, three pieces of information must be determined: (1) the table name, (2) the column names,
More informationBaanBIS Decision Manager 2.0. Modeler User's Guide
BaanBIS Decision Manager 2.0 A publication of: Baan Development B.V. P.O.Box 143 3770 AC Barneveld The Netherlands Printed in the Netherlands Baan Development B.V. 2001. All rights reserved. The information
More informationAltia Hint Sheet Investigation Toolkit:
Altia Hint Sheet Investigation Toolkit: Processing Abbey Statements Scope This sheet provides information on how to deal with Abbey statements where the debit and credit values are printed in the same
More informationProcedures Oracle FLEXCUBE Universal Banking Release 12.0 [May] [2012] Oracle Part Number E
Procedures Oracle FLEXCUBE Universal Banking Release 12.0 [May] [2012] Oracle Part Number E51527-01 Table of Contents Procedures 1. ABOUT THIS MANUAL... 1-1 1.1 INTRODUCTION... 1-1 1.2 AUDIENCE... 1-1
More informationIBM Informix Change Data Capture API Programmer's Guide
Informix Product Family Informix Version 11.70 IBM Informix Change Data Capture API Programmer's Guide SC27-3527-02 Informix Product Family Informix Version 11.70 IBM Informix Change Data Capture API
More informationMicrosoft Access: Table Properites, Complex Forms. Start with a new, blank Access database,
: Table Properites, Complex Forms Start with a new, blank Access database, : Let s create the tblperson. We are going to use advanced properties for the table fields and create an advanced form. Add a
More informationCopyright...7. Overview of General Ledger Processes Configuration...11
Contents 2 Contents Copyright...7 Overview of General Ledger Processes... 8 Configuration...11 Preparation...11 Recommended Initial Configuration of the General Ledger Module... 11 Advanced Configuration...12
More informationTanium Asset User Guide. Version 1.3.1
Tanium Asset User Guide Version 1.3.1 June 12, 2018 The information in this document is subject to change without notice. Further, the information provided in this document is provided as is and is believed
More informationTechnical Overview. Access control lists define the users, groups, and roles that can access content as well as the operations that can be performed.
Technical Overview Technical Overview Standards based Architecture Scalable Secure Entirely Web Based Browser Independent Document Format independent LDAP integration Distributed Architecture Multiple
More informationTable of Contents ADMIN PAGES QUICK REFERENCE GUIDE
Admin Pages brings an all new look and feel to Banner. It delivers a fresh user experience, all new tools, and significantly improved capabilities. Admin Pages replaces underlying Banner 8 INB technology
More informationSearching Guide. September 16, Version 9.3
Searching Guide September 16, 2016 - Version 9.3 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
More informationDBLOAD Procedure Reference
131 CHAPTER 10 DBLOAD Procedure Reference Introduction 131 Naming Limits in the DBLOAD Procedure 131 Case Sensitivity in the DBLOAD Procedure 132 DBLOAD Procedure 132 133 PROC DBLOAD Statement Options
More information