2 Switches Configurable from Argus Safety

You need to configure the AM Common Profile Switches to have control over the data that you want to transfer from the Argus Safety database to the AM database. These Common Profile Switches are configured using the Argus Safety Console.

This chapter lists each of those Common Profile Switches along with other details such as Key, default value, and a brief description.

This chapter comprises the following sub-sections:

• Global Switches

• Enterprise-specific Switches

2.1 Global Switches

This section lists all the Global Common Profile Switches for Argus Mart that are configured using the Argus Safety Console. These switches are visible only if you are logged in from a default enterprise.

All these Profile Switches belong to the CMN_PROFILE_GLOBAL table that exists in Argus Safety.

This section comprises the following sub-sections:

• ENABLE SM PROCESSING

• REVISIONS TO PROCESS

• CUSTOM ROUTINE BEFORE STAGE TABLES POPULATION

• CUSTOM ROUTINE BEFORE REPORTING TABLES POPULATION

• CUSTOM ROUTINE AFTER REPORTING TABLES POPULATION

• CUSTOM ROUTINE BEFORE SIGNAL HELPER TABLES POPULATION

• CUSTOM ROUTINE AFTER SIGNAL HELPER TABLES POPULATION

• CUSTOM ROUTINE AFTER ETL

2.1.1 ENABLE SM PROCESSING

Section	Database
Key	ENABLE_SM_PROCESSING
Default Value	Yes
Description	This switch is used to enable or disable SM Processing for AM. Yes represents Enable SM Processing for Argus Mart. No represents Disable SM Processing for Argus Mart.The value for this switch must not be changed once Initial ETL has been executed.

2.1.2 REVISIONS TO PROCESS

Section	Database
Key	REVISIONS_TO_PROCESS
Default Value	0
Description	The value set for this switch refers to the maximum number of delta DLP revisions processed by an Incremental ETL run.Setting the value as 0 for this switch results in processing all the delta DLP revisions.

2.1.3 CUSTOM ROUTINE BEFORE STAGE TABLES POPULATION

Section	Database
Key	PRE_STAGE_TABLES_POPULATION
Default Value	Blank
Description	This switch refers to the custom routine to be executed before the population of the AM Staging Tables. If this routine is not executed or is not found, the ETL is not run and an error message is displayed.

2.1.4 CUSTOM ROUTINE BEFORE REPORTING TABLES POPULATION

Section	Database
Key	PRE_REPORTING_TABLES_POPULATION
Default Value	Blank
Description	This switch refers to the custom routine to be executed before population of Signal Reporting Tables. If this routine fails or is not found, the ETL is not run and an error message is displayed.

2.1.5 CUSTOM ROUTINE AFTER REPORTING TABLES POPULATION

Section	Database
Key	POST_REPORTING_TABLES_POPULATION
Default Value	Blank
Description	This switch refers to the custom routine to be executed after population of Signal Reporting Tables. If this routine fails or is not found, the ETL is not run and an error message is displayed.

2.1.6 CUSTOM ROUTINE BEFORE SIGNAL HELPER TABLES POPULATION

Section	Database
Key	PRE_HELPER_TABLES_POPULATION
Default Value	Blank
Description	This switch refers to the custom routine to be executed before population of Signal Helper Tables. If this routine fails or is not found, the ETL is not run and an error message is displayed.

2.1.7 CUSTOM ROUTINE AFTER SIGNAL HELPER TABLES POPULATION

Section	Database
Key	POST_HELPER_TABLES_POPULATION
Default Value	Blank
Description	This switch refers to the custom routine to be executed after population of Signal Helper Tables. If this routine fails or is not found, the ETL is not run and an error message is displayed.

2.1.8 CUSTOM ROUTINE AFTER ETL

Section	Database
Key	POST_ETL_POPULATION
Default Value	Blank
Description	This switch refers to the custom routine to be executed after Initial/Incremental ETL (post ETL commit). If this routine fails or is not found, the ETL is not run and an error message is displayed.

2.2 Enterprise-specific Switches

This section lists all the Enterprise-specific Common Profile Switches for Argus Mart.

To configure these switches, you need to login to each enterprise individually through Argus Safety Console. The value of these switches may differ across the enterprises.

All these Profile Switches belong to the CMN_PROFILE_ENTERPRISE table.

This section comprises the following sub-sections:

• FIRST HUMAN LANGUAGE

• SECOND HUMAN LANGUAGE

• CUSTOM DATASHEET FOR LISTEDNESS

• SMQ/CMQ FOR FATAL TERMS

2.2.1 FIRST HUMAN LANGUAGE

Section	Database
Key	FIRST_HUMAN_LANGUAGE
Default Value	en
Description	This switch refers to first human language for derived decoded items. This value should not be changed after data mart is initialized.

2.2.2 SECOND HUMAN LANGUAGE

Section	Database
Key	SECOND_HUMAN_LANGUAGE
Default Value	Blank
Description	This switch refers to second human language for derived decoded items. This value should not be changed after data mart is initialized.

2.2.3 CUSTOM DATASHEET FOR LISTEDNESS

Section	Database
Key	CUSTOM_DATASHEET_FOR_LISTEDNESS
Default Value	Blank
Description	This switch refers to the specific datasheet value to be used for the SM_EVENT_ PRODUCT.LISTEDNESS_CDS_VE column. This value should not be changed after data mart is initialized.

2.2.4 SMQ/CMQ FOR FATAL TERMS

Section	Database
Key	SMQ_CMQ_FOR_FATAL_TERMS
Default Value	Blank
Description	This switch refers to the specific SMQ/CMQ to be used for determining fatal terms for the FATAL_YN_DV column. This value should not be changed after data mart is initialized.