Oracle® Business Intelligence Applications Installation and Configuration Guide > Installing and Configuring Oracle BI Applications on Windows > Configuring the DAC Server >

Process of Setting DAC Source System Parameters


You set Source System Parameters (also known as DAC ETL Preferences) in the DAC to specify how the ETL routines process data for a container. For example, if operating in the United States, you might set the $$DLFT_COUNTRY to 'USA' to identify your data.

NOTE:  The following preferences are applied to all tasks within a container. If extracting data from more than one source, these preferences will need to be re-applied to each associated container. They can be overridden at the task level by adding the parameter to the specific task and assigning a value there.

To set DAC source system parameters

  1. Log into the DAC.
  2. Display the Design view.
  3. Maker sure that you have selected the correct container from the containers drop down list.
  4. Select the Source System Parameters tab.
    Click for full size image
  5. Use the Edit tab below the list of Source System Parameters to change the value of parameters in the list.
  6. Click Save.

The following table describes commonly available Source System Parameters.

Table 30. Commonly Available Source System Parameters
Parameter
Description
Parameter Name
Default

Analysis Start Date

The start date used to build the day dimension and to flatten exchange rates and costs lists.

$$ANALYSIS_START, $$ANALYSIS_START_WID

Jan 1, 1980

Analysis End Date

The end date used to build the day dimension and to flatten exchange rates and costs lists.

$$ANALYSIS_END, $$ANALYSIS_END_WID

Dec 31, 2010

Max Days in a SalesStage

Applicable to opportunities only. The maximum number of days an opportunity can spend in a sales stage.

$$MAX_DAYS_IN_STG

30

Default Language

Siebel Specific. The language into which columns' display strings are translated.NOTE: Language-independent strings are stored in the _l columns. If you do not know the default language setting, issue the following query against the transactional database: select VAL from S_SYS_PREF where SYS_PREF_CD='ETL Default Language'; 12-MAL12D

$$DFLT_LANG

ENU

Alignment Version

Applicable to Siebel vertical applications only. Seed data needs to be updated in certain lists of values to make sure that the ETL process correctly populates the alignment type and product category relationships in the Oracle Business Analytics Warehouse.This setting is used by Siebel Life Sciences to control loading of changes in assignment rules in Siebel Assignment Manager.

$$ALIGNMENT_VER

Y

Maximum LOV Size

Siebel specific parameter. Numeric LOVs must have a maximum value for proper analysis and consistent data in the data warehouse. This value determines what the maximum value will be

$$LOV_MAX_VAL

9999999999

Minimum LOV Size

Siebel specific parameter. Numeric LOVs must have a minimum value for proper analysis and consistent data in the data warehouse. This value determines what the minimum value will be

$$LOV_MIN_VAL

0

Type 2 Flag

Slow changing dimension (Type-2) specific parameter. If this dimension is "capable" of storing history, you can choose to set the flag value to be 'Y' or 'N'. If set to 'Y' and you have already identified columns that your history tracking mechanism will be based upon, then this will trigger insertion of new records with new surrogate keys whenever anything history tracking event happens. If set to 'N', it just updates the existing record.

$$TYPE2_FLG

Y (This is just an out of box setting. The value of this parameter should be overridden at a task level, because not all dimensions will have the same setting.)

Update All History Flag

Applicable for slowly changing dimensions (Type-2). With a Type-2 change happening along with some other changes in a non-history tracking column, you can choose to update values of that non-Type2 column for all historical records. If so, set this flag to 'Y'. If you want to preserve the old values for non-Type2 columns for older records, set this to 'N'.

$$UDATE_ALL_HISTORY

Y (Recommended approach and out of box setting).

Language Code

Datawarehouse language that is used to resolve NAMES for the CODES in your system.

$$LANGUAGE_CODE

E (out of box setting)

Global1 Currency Code

Generic parameter identifying the global (Data Warehouse) currency code. Three distinct global currencies are supported; this is the first of the three.

$$GLOBAL1_CURR_CODE

USD

Global2 Currency Code

Generic parameter identifying the global (Data Warehouse) currency code. Three distinct global currencies are supported; this is the second of the three.

$$GLOBAL2_CURR_CODE

USD

Global3 Currency Code

Generic parameter identifying the global (Data Warehouse) currency code. Three distinct global currencies are supported; this is the third of the three.

$$GLOBAL3_CURR_CODE

USD

Global1 Exchange Rate Type

Generic parameter identifying the default exchange type to be used against the Global1 (Data Warehouse) currency code.

$$GLOBAL1_RA TE_TYPE

Value of this parameter is source specific. For Siebel Sources, the default value is "Actual". In case of Oracle and Universal Adapters, the value is overridden with "Corporate".

Global2 Exchange Rate Type

Generic parameter identifying the default exchange type to be used against the Global2 (Data Warehouse) currency code.

$$GLOBAL2_RA TE_TYPE

Value of this parameter is source specific. For Siebel Sources, the default value is "Actual". In case of Oracle and Universal Adapters, the value is overridden with "Corporate".

Global3 Exchange Rate Type

Generic parameter identifying the default exchange type to be used against the Global3 (Data Warehouse) currency code.

$$GLOBAL3_RA TE_TYPE

Value of this parameter is source specific. For Siebel Sources, the default value is "Actual". In case of Oracle and Universal Adapters, the value is overridden with "Corporate".

Default Local Exchange Rate Type

Generic parameter identifying the default exchange rate type to be used against the local (OLTP) currency code, in case the same is not available from the source.

$$DEFAULT_LOC_RATE_TYPE

Value of this parameter is source specific. For Siebel Sources, the default value is "Actual". In case of Oracle and Universal Adapters, the value is overridden with "Corporate".

Current Date

These are runtime parameters that gets the value of the current date and the current quarter based on the date dimension, W_DAY_D, against the Fiscal or Gregorian calender, as the case may be.

$$CURRENT_DATE

Value obtained through firing SQL at the runtime.

Current Quarter

 

$$CURRENT_QUARTER

Value obtained through firing SQL at the runtime.

Data Source Number Identifier

This is a static parameter used to identify the source system type and its instance. For example, you could set '2' for the first instance of Oracle 11.5.8 source, and '3' for the second instance of Oracle 11.5.8, '4' for the only instance of Oracle 11.5.10 and '5' for Siebel OLTP source, and so on.This is a runtime parameter that increments by 1 (normally) for each ETL run. For instance, for the first full load, it might start with a 1. Then the first incremental ETL run gets a 2 and so on. This helps in identifying records that were affected during a given ETL run.

$$DATASOURCE_NUM_ID

Value is different for different containers, for example 3 for Oracle 11.5.8 and so on.

ETL process Identifier

 

$$ETL_PROC_WID

DAC generated. Normally starts with a 1 and then increments by 1.

Dates used for incremental extraction

This date is used to extract data for the full load.

$$INFA_LOAD_DT, $$INITIAL_EXTRACT_DATE

01/01/1970

Last Extract Date

This date is used to extract data during everyday incremental loads

$$LAST_EXTRACT_DATE$$JULIAN_LOAD_DT

Runtime, DAC generated. Based on when the last date/time extraction (ETL) happened.

ETL Load Date

The ETL load start Date

$$LOAD_DT

Runtime, DAC generated

Exception reporting for CODE-NAME pairs

This static parameter value is used to substitute the CODE part in (mostly) dimension tables when the master code (standardized code) was not found during code lookup against the supplied value of source side code.

$$MASTER_CODE_NOT_FOUND

 

Exception reporting for CODE-NAME pairs

This static parameter value is used to substitute the CODE part in (mostly) dimension tables when the code lookup failed to resolve to the standardized code in the event where the source-side code itself was not supplied in the staging area tables.

$$SOURCE_CODE_NOT_SUPPLIED

<null value> out of the box. But can be any string like "master code is not found" up to a limit of 30 characters.

Tenant Identifier

This is a static parameter used to identify the tenant id, in multi-tenancy situations.

$$TENANT_ID

 

Oracle® Business Intelligence Applications Installation and Configuration Guide Copyright © 2007, Oracle. All rights reserved.