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.
1 Set the INITIAL_JOB_SETUP_CONNECTION_01 parameter to your first QAD ERP source.
2 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.
3 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 Asset Management Module – EAM sources only
4 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.
5 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.
6 Finally, set INITIAL_JOB_SETUP_CONNECTION_01_RUN to N. This indicates you have not run a historic load for this source yet.
7 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.
8 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
9 Eliminate the values for the connections that are not being used.
10 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.
11 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.
13 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 of 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.
14 Ensure that your ERP sources all have their GL Calendars configured properly, both historically and into the future, for all domains. In addition to Financials, several of the BI modules, including Inventory and Order Management, use the GL Calendar to determine financial periods.
15 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.