Upgrade Steps for QAD BI Metadata
Preparation
1 Plan for a couple of hours of down time.
2 Ensure that there are no loads currently in progress. All jobs must be completed.
3 Put all scheduled jobs On Hold until the upgrade is complete. Shut down the scheduler.
Important: Take a backup of the current warehouse database and the current portal database.
Upgrade Steps
1 Unzip the metadata for the Common module and any other modules you have installed. Because the metadata files are now segregated by module, it is only necessary to install the modules that are needed.
2 Perform the Common upgrade first. The other upgrades can be done in any order.
Warning If you use EE Financials, this upgrade deletes all EE Financials tables and installs an entirely new set.
3 Run the Common metadata upgrade application.
a If you process any of the Order Management (Sales) fact_om_* tables, install the Order Management (OM) upgrade application.
b If you process Inventory and/or Purchase Order tables, install the Operations module upgrade application.
c If you process any Financial tables, install the Financials module upgrade application.
4 Log in to Setup Administrator.
5 Choose Tools|Start Logging. Select a name and location for your log file and save.
6 Load the Common Module Upgrade Application as follows:
a Set your application directory to the new metadata/common folder.
b Load application upgradeCom by right-clicking on the file and choosing Install Application.
c From the drop-down list, select the ODBC DSN for your DWD instance.
d The system prompts you to proceed. Click OK.
e You can cancel the installation here to review the list of new and modified objects. To continue with the load, right-click in the window and choose Proceed with Load Application.
f The next dialog box is Application Load Properties. Verify that the default values are correct. Make any changes if necessary:
• On the left, select Dimension. On the right, click the box next to Existing Dimension objects will be and select Altered.
• On the left, select Dimension View. On the right, click the box next to Existing Dimension View objects will be and select Recreated.
• On the left, select Stage Table. On the right, click the box next to Existing Stage table objects will be and select Recreated.
• On the left, select Permanent Stage Table. On the right, click the box next to Existing Permanent Stage table objects will be and select Altered.
• On the left, select Fact Table. On the right, click the box next to Existing Fact table objects will be and select Altered.
g Click OK.
7 Repeat for any other modules that must be upgraded.
a Order Management. Change the Application Directory to the metadata/order_management subdirectory and install application upgradeOM.
Note: Watch for errors here when trying to create an index on fact_om_order. If you see this, create the index manually in the next step.
b Operations. Change the Application Directory to the metadata/operations subdirectory and install application upgradeOps.
c Financials. Change the Application Directory to the metadata/financials subdirectory and install application upgradeFin. The upgrade application installations take some time as the load process alters and re-creates various objects.
8 If you have errors during the Order Management module upgrade that a unique index on fact_om_order could not be created, create it manually as non-unique so that the upgrade jobs run properly. Without the index, the OM Postprocess job may take much longer than usual.
a Go to fact_om_order in the BI DWD. Right-click on the table and choose Display Indexes.
b Double-click on fact_om_order_idx_A and clear the Unique check box. Click OK.
c Right-click on fact_om_order_idx_A and choose Create Index.
d If you also have an error on upgrade while attempting to create a fact_om_order_history index, you do not need to address it at this time because the upgrade job drops and re-creates the indexes.
9 In SQL Server Management Studio, run the misc.sql script in your Data Warehouse database:
<Location of unpacked Common module>\sqlserver\misc.sql
This enables an extra Tech Notes tab in your Data Warehouse Designer.
10 Start the Scheduler. Make sure that all jobs are still suspended.
11 If the upgrade affects any customized tables, reapply your customizations. For a list of new and modified tables, see
Data Warehouse Tables Changed.
12 If there were any customizations previously added to any of the modified jobs, update the job to include those extra parts. You can double check what was in the job by looking at the newly renamed <jobname>_1. The jobs that changed in this release are:
|
• CLEANUP_COMMON_TABLES
|
• CLEANUP_FIN_TABLES
|
|
• CLEANUP_OPERATIONS_TABLES
|
• CUSTOMER_PROCESS
|
|
• DAILY_COMMON_PERM_CHAINED
|
• DAILY_COMMON_PROCESS_CHAINED
|
|
• DAILY_FIN_EE_AP_PROCESS_CHAINED
|
• DAILY_FIN_EE_AR_PROCESS_CHAINED
|
|
• DAILY_FIN_EE_GL_PROCESS_CHAINED
|
• DAILY_FIN_EE_PERM_CHAINED
|
|
• DAILY_FIN_EE_PERM_EXTRACT
|
• DAILY_FIN_SE_AP_PROCESS_CHAINED
|
|
• DAILY_LOAD_TR_HIST
|
• DAILY_OM_PERM_CHAINED
|
|
• DAILY_OM_PROCESS_CHAINED
|
• DAILY_OP_INV_PROCESS_CHAINED
|
|
• DAILY_OP_PERM_CHAINED
|
• DAILY_OP_PO_PROCESS_CHAINED
|
|
• HIST_COMMON_PERM_CHAINED
|
• HIST_COMMON_PROCESS_CHAINED
|
|
• HIST_EAM_PROCESS_CHAINED
|
• HIST_FIN_EE_AP_PROCESS_CHAINED
|
|
• HIST_FIN_EE_AR_PROCESS_CHAINED
|
• HIST_FIN_EE_GL_PROCESS_CHAINED
|
|
• HIST_FIN_EE_PERM_CHAINED
|
• HIST_FIN_EE_PERM_EXTRACT
|
|
• HIST_FIN_SE_AP_PROCESS_CHAINED
|
• HIST_LOAD_TR_HIST
|
|
• HIST_MODULES_LOAD_FINISH
|
• HIST_OM_PROCESS_CHAINED
|
|
• HIST_OP_INV_PROCESS_CHAINED
|
• HIST_OP_PERM_CHAINED
|
|
• HIST_OP_PO_PROCESS_CHAINED
|
• INITIAL_JOB_SETUP
|
|
• ITEM_PROCESS
|
• POSTPROCESS_FIN_EE_AP_SUMMARY
|
|
• POSTPROCESS_FIN_EE_AR_SUMMARY
|
• POSTPROCESS_OP_PO_DAILYONLY_SUMMARY
|
|
• POSTPROCESS_OP_PO_HISTONLY_SUMMARY
|
• PREPROCESS_COMMON_DAILYONLY_LOADS
|
|
• PREPROCESS_COMMON_EE2010UP_LOADS
|
• PREPROCESS_COMMON_EEONLY_LOADS
|
|
• PREPROCESS_COMMON_LOADS
|
• PREPROCESS_COMMON_TRUNCATE
|
|
• PREPROCESS_FIN_EE_LOADS
|
• PREPROCESS_FIN_TRUNCATE
|
|
• PREPROCESS_OM_DAILYONLY_LOADS
|
• PREPROCESS_OM_LOADS
|
|
• PREPROCESS_OM_TRUNCATE
|
• PREPROCESS_OP_LOADS
|
|
• PREPROCESS_OP_TRUNCATE
|
|
13 Set a new parameter for each Source Connection:
INITIAL_JOB_SETUP_CONNECTION_xx_VERSION
Set this to the ERP version number for each source. Use only the whole number and do not add any point values. For example, if you have SE 2010, enter 2010. If you have EE 2011.1, enter 2011. Do NOT enter 2011.1. If you have more than two sources, add parameters for each source.
14 Set INITIAL_JOB_SETUP_ENABLED to Y and run INITIAL_JOB_SETUP to rebuild the daily and historical job chains.
15 Run the upgrade jobs for BI 3.8:
a Common Module. Edit your INITIAL_JOB_SETUP_CONNECTION_xx_DAILY_MODULES parameter values to ensure there are no spaces in the comma-separated list. For example, if your DAILY_MODULES parameter currently lists "COM, OM, OP" change it to "COM,OM,OP". Then, run the UPGRADE_37_to_381_QBI_1233 job to populate several new fields in the dim_item table.
b Order Management Module. Run the UPGRADE_37_to_381_ OM job.
c Operations module. Run the UPGRADE_37_to_381_QBI_2171 job to create the dim_po_buyer dimension. Also, if desired, set the new parameter INV_FUTURE_DEMAND_MONTHS from the default value (12) to your desired horizon.
d Financials SE Module. Run the UPGRADE_37_to_381_ FINSE job.
16 Run the Daily load.
17 If you had set the index on fact_om_order to non-unique earlier, re-create the index as a Unique index now:
a Go to fact_om_order in the BI DWD and right-click the table and choose Display Indexes.
b Double-click on fact_om_order_idx_A and check the Unique box. Click OK.
c Right-click on fact_om_order_idx_A and choose Drop Index.
d Right-click on fact_om_order_idx_A and choose Create Index.