In order to bring you the best possible user experience, this site uses Javascript. If you are seeing this message, it is likely that the Javascript option in your browser is disabled. For optimal viewing of this site, please ensure that Javascript is enabled for your browser.
Login  |   On Demand  |   Home  |   qad.com




Install BI Analytical Modules
1
The QAD Business Intelligence analytical modules are packaged as zip files. The zip files contain metadata files for the Common module and all necessary analytical modules. Unzip the contents of the .zip files into a directory that you reference for installation.
Note: Install the Common module before installing any of the analytical modules except TMS. The Common module contains core components used by all modules except TMS.
Note: For users installing TMS only, you do not need to install the Common module application files into the DWD. If you want to install the technical module documentation or any translation files, you must obtain these items from the Common module media.
2
In Setup Administrator, confirm that the job scheduler has started. If the job scheduler has not started, start the service and confirm that it does not stop.
Note: The job scheduler is created when the data warehouse is created.
3
In the directory where you extracted the Common module, there is a subdirectory named sqlserver. In this directory, there is a SQL script named misc.sql. In the SQL Server Management Studio, open misc.sql, change the database to your Data Warehouse, and execute the misc.sql script. This step adds a tab called Technical Info for the following types of objects:
Dimension Column
Dimension View Column
Fact Table Column
Kpi Fact Table Column
Datastore Table Column
View Column
4
These objects can be seen from the DWD under Tools|Options|Documentation.
Install BI Common Module
5
If you are installing any of these analytical modules, the Common module is required:
 
Order Management (OM)
Financials (both SE and EE) (FIN)
Operations (OP)
EAM
Note: Skip this section and see “Install BI Analytical Module” if the analytical module you are installing does not require the Common module.
6
Go to the Application option in Setup Administrator. Change Application Directory to the directory into which you extracted the QAD Business Intelligence Common Module metadata. The contents consist of a series of .wst files.
7
Go to Tools and Start Logging.

Start Logging
8
Choose a file name for your log and a directory for it to write to.
9
Install the application through Application Load. Right-click on the Common module and choose Install.

Application Load
10
If a message appears saying that files may be overwritten, choose Cancel and confirm that the files are OK to be overwritten. If the files can be overwritten, go back to step 6 and repeat.

Confirm File Overwrite
Install BI Analytical Module
11
Next, go back to the Application option in Setup Administrator. Change the Application Directory to the directory into which you extracted the first Analytical Module you want to install.
12
Select Start Logging from the Tools drop-down menu.

Start Logging
13
Choose a file name for your log and a directory for it to write to.
14
Install the application through Application Load. Right-click on the desired module and choose Install.

Application Load
15
If a message appears about files being overwritten, choose Cancel and confirm that the files are OK to be overwritten. If the files can be overwritten, go back to step 11 and repeat.

Confirm File Overwrite
16
Repeat for any other modules that are required.
17
Review the message log. The files that are replaced are identified at the top of the log. To proceed, right-click within the log and choose Proceed to Load. Once the main application load is running, the operation can take as long as 5-10 minutes.
Note: If the top of the DWD screen displays Not Responding, wait up to 30 minutes for the job to finish. If it takes any longer, close the screen and start over.
18
After loading all the module components, you can refresh the DWD by clicking All Objects in the Browser pane and pressing F5. If this does not work, you can log off and log back in to the DWD.
Initial Parameter Setup
Note: In QAD BI DWD, choose Parameters from the Tools menu to display the current Parameter definitions. Customize the parameter definitions for your specific installation.
19
Set runtime parameters to the proper settings based on the customer feedback to the parameters (Parameter Values that Need to Be Set Before History Load). Also refer to Jobs and Parameters for the Common Module for additional assistance. In particular, change the HIST_LOAD_SOURCE_Sxx, DAILY_LOAD_SOURCE_Sxx and INITIAL_JOB_SETUP_CONNECTION_xx parameters to point at the source databases.
Note: Parameters that MUST be set before running INITIAL_JOB_SETUP must have an initial value of <some value between these symbols >. See Reference for more details.
Initial Job Setup
Note: The INITIAL_JOB_SETUP job creates the proper chained job flow for all the source connections. This is not used for the Transportation Management (TM) module. For more information, see TM Module Setup.
20
Set the INITIAL_JOB_SETUP_CONNECTION_01 parameter to your first QAD ERP source.
21
Populate the INITIAL_JOB_SETUP_CONNECTION_01_TYPE parameter with the type of source system (EE, SE) in order for the chained job flow to be set up with correct jobs for the source type.
Note: If you are using the EAM analytical module, the EAM system cannot be your first source. A QAD ERP source must precede the EAM source.
22
Populate the INITIAL_JOB_SETUP_CONNECTION_01_DAILY_MODULES with the list of analytical modules you want to include in your first source’s processing. Typically the list includes all your analytical modules for an ERP source. If you have more than one module installed, list them in the order in which you want them processed, separated by commas. List the Common module first for ERP sources.
The valid module identifiers for this list are:
COM. For the Common module, ERP sources
OP. For the Operations module, ERP sources
FIN. For the Financials module, ERP sources
OM. For the Order Management (Sales) module, ERP sources
EAM. For the Enterprise Application Module – EAM sources only
23
Populate the INITIAL_JOB_SETUP_CONNECTION_01_HIST_MODULES with the list of analytical modules you want to include in your first source’s historical loads. Typically the list includes all analytic modules the first time you install.
Note: If you install an additional analytical module later, you can list just that module and rerun INITIAL_JOB_SETUP. This method creates a Historical job flow that loads just the new module, so it is not necessary to repeat any historical loads for other modules.
24
Set INITIAL_JOB_SETUP_CONNECTION_01_VERSION to the version of your source system. This should be just the major release year. For example, if your source is SE 2010 set the version parameter to 2010; if your source is EE 2011.1, set the version parameter to 2011. Do not include the .1.
25
Finally, set INITIAL_JOB_SETUP_CONNECTION_01_RUN to N. This indicates you have not run a historic load for this source yet.
26
If you have more than one source system, set INITIAL_JOB_SETUP_CONNECTION_02 to your second connection (EE, SE, or EAM) and set INITIAL_JOB_SETUP_CONNECTION_02_TYPE appropriately.
Note: If you are loading an EAM source, a valid QAD ERP source must come before the EAM source in the source list.
27
You can continue adding as many INITIAL_JOB_SETUP_CONNECTION_XX* and parameters as necessary. Make sure that you add all the required parameters for each connection:
INITIAL_JOB_SETUP_CONNECTION_XX
INITIAL_JOB_SETUP_CONNECTION_XX_TYPE
INITIAL_JOB_SETUP_CONNECTION_XX_RUN
INITIAL_JOB_SETUP_CONNECTION_XX_DAILY_MODULES
INITIAL_JOB_SETUP_CONNECTION_XX_HIST_MODULES
INITIAL_JOB_SETUP_CONNECTION_XX_VERSION
28
Eliminate the values for the connections that are not being used.
29
Set the INITIAL_JOB_SETUP_ENABLED parameter to Y, and in the Scheduler, execute the INITIAL_JOB_SETUP job.
Setup Steps:
a
In QAD BI DWD, choose the Scheduler menu option.
b
Change the view to All Jobs.
c
Locate the job named INITIAL_JOB_SETUP (status On Hold).
d
Right-click the job name and start the job.
e
The status changes to Waiting.
f
Refresh the screen until the job completes.
g
If the job fails to start, check the scheduler status.
30
After INITIAL_JOB_SETUP has run, check Scheduled jobs to confirm that you now have SET_CONNECTION jobs with names that end with all connections you have created. If they have not been created, check the Parameters. Make sure that the INITIAL_JOB_SETUP_ENABLED parameter is set to Y and run INITIAL_JOB_SETUP again.
31
Verify that your parameters are all set properly for your installed modules. See Parameter Values that Need to Be Set Before History Load.
32
Confirm that your DEFAULT_* parameters are set properly. In particular, the DEFAULT_ACCOUNT and DEFAULT_SUB_ACCOUNT values must not be actual account values in any or your ERP sources.
Important: Failure to confirm that these parameter values are not duplicates of actual account values can result in errors in the history load, requiring reloading of GL history.
33
You are now ready to populate the Data Warehouse with your ERP history. In the scheduler, find the HIST_START job, right-click on it, and select Start the Job. Depending on the size of the source tables, this can take quite some time. It does not hurt to check in throughout this load process to make sure that the jobs are all running successfully.
Install Metadata Language Translation Files
Install the metadata language translations files, if any are required.
34
In the BI DWD tool, choose Tools|Options.
35
Click the Languages tab and add the following codes for the language files you want to install:
 
Language
Code
Czech
cs
German
de
Spanish
es
Spanish (Mexico)
es_MX
French
fr
Italian
it
Japanese
ja
Korean
ko
Dutch
nl
Polish
pl
Portuguese (Brazilian)
pt
Chinese (Simplified)
zh
Chinese (Traditional)
zh_TW
36
The complete set of files is in the metadata package, under metadata/translations. The file names are in the format lang_<code>.wst. For example, the file for traditional Chinese is lang_zh_TW.wst.
Note: The UI can be a little misleading here because you must click Add Language and then type in a language or abbreviation in the Language drop-down menu. The code you enter helps you find language options in the Analysis Services Languages drop-down list, but the language that displays in the drop-down list may not be the language you want. The code you enter for the Language is used for reference purposes in later steps. For example, if you enter es, the language code for Spanish, the Analysis Services Language drop-down list displays Estonian, because that starts with es. If this happens, click the Analysis Services Language drop-down list, scroll down, and select the Spanish option.

Language Install
37
After adding the language codes, launch the QAD BI Data Warehouse Setup Administrator.
38
Select Languages|Change Languages Directory. Navigate to the directory metadata/translations directory of your package.

Language Install 2
39
Choose Languages|Load Languages. Right-click on the language file you want to install and choose Install Language.
40
Select the Data Warehouse’s ODBC DSN. Then choose the language to which you want to map this language file. You are allowed to choose one of the language codes you entered in the QAD BI DWD in step 35.

Language Install 3
41
Repeat these steps for each language you want to install.
Creating and Processing Cubes
BI DWD allows you to create cubes in SQL Server Analytical Services (SSAS) from any of the fact tables.
42
Some of your analytical modules come with cube metadata already created. To use these cubes, first create them in SSAS.
43
Make sure that the DataWarehouse connection in the DWD has the Cube Data Source section of its Properties tab filled out correctly:
The Provider Type is set to SQLOLEDB.
The Server and Database fields contains the name of the SQL Server instance and the name of the DWD SQL Server Database.
The QAD_BI_Cube connection is set to the correct instance of SSAS.
44
Locate the cube in the Metadata Browser. Right-click on the cube and choose Properties.
45
Ensure the following:
The Cube Database Connection is set to your QAD_BI_Cube connection object.
The Data Source Connection is set to your DataWarehouse connection object.
46
Use the default Cube Database name or optionally create a different name for the SSAS database. Click OK to save.
47
Right-click on the cube and choose Create (Alter) Cube.
Note: For the older, non-OLAP cubes, the option is Create Cube. Verify that this completes successfully.
48
The final step is to process the cube, which populates the cube with data from the fact tables. For the analytical modules that come with cubes, there are standard jobs that process cubes; for instance, the job POSTPROCESS_<module>_CUBES.
Schedule this job to run at specific intervals, or add it to the end of the DAILY job chain to run it automatically after the daily jobs update the fact tables.
Note: The QAD Data Warehouse Designer User Guide contains additional information on creating and modifying OLAP cubes, including the following:
A table that describes the types of modifications to an OLAP cube’s metadata that can be processed using the Create (Alter) Cube action in the Data Warehouse without changing SSAS first.
Which modifications require the user to delete the SSAS cube database before re-creating the cube from the Data Warehouse.