The first step consists of setting the parameters that control the behavior of the accelerator.
Go to the System Parameters menu.

The parameters are divided into categories. The first category is Important parameters, which contain parameters such as case sensitivity, time zones, name length restrictions for Oracle targets, etc.

Every parameter has a Parameter Level. This determines the lowest level at which the parameter can be changed. For example, the level “SOURCE” means that this parameter can be set differently for the system, each project and each source. Changing parameters at a certain level will

propagate this change to all the lower levels, e.g. changing “INSERT_ONLY_LOGIC” to “Y” in this screen will change it for all projects and sources. The level hierarchy looks as follows:

  • SYSTEM – system level
  • PROJECT – project level
  • SOURCE – source level
  • TAB_SRC – object level (tables, views, etc.)
  • DV – data vault level

As will be seen later, you can find a

button at each level to adjust the parameters for this level. Parameters at lower levels have Level Specific flags, e.g.

Turning this flag on will make sure that the parameter will not be overwritten if it is changed at a higher level. On a similar note, the Overwrite lock flag will make sure that when a parameter is adjusted at higher levels, it will not propagate to the lower levels.
There are also certain dependencies between parameters. For example, in the figure above, the “CDC_TIMESTAMP_WITH_TZ” and “LOAD_TIMESTAMP_WITH_TZ” parameters are grayed out, because the overarching parameter “TIME_ZONE_LOCAL” is “Y”. The parameter values can also be restricted to certain values based on other parameters. For instance, if “ORACLE_12_2_OR_HIGHER” is “Y”, then the only possible value for “ORACLE_12_1_OR_HIGHER” is “Y”, so you first have to change the former parameter to alter the latter.

If a parameter has an invalid value, it will be highlighted in red. For example, if you change the prefix of the SAT tables to “hub” or if you remove both prefix and suffix. This change will cause naming conflicts in your data vault, so the parameter will become highlighted red, indicating that its value is invalid, and a pop-up message will appear.
The Schema names category is important as well. These are the schemas you need to have/make in your target database as the Foundation Accelerator does not generate DDL for creating schemas. Note, that some schema names have to be adjusted at a lower level, such as SRC, EXT and MTD schemas, because these need to be unique for each source, else naming conflicts will occur. Also, some layers cannot share the same schema such as EXT, STG, DFV, DTV, FL and BV.