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  |   Cloud ERP  |   Home  |   qad.com




Upgrade to QAD BI 3.5 from QAD BI 3.4.1
BI Portal Upgrade Procedure
Preparation
Shut down Tomcat.
Back up the BI Portal database.
Upgrade Steps for QAD BI Portal
1
Copy the TOMCAT_HOME\webapps\your_bi_appname directory to TOMCAT_HOME\your_bi_appname.save341 so that you have a backup of your BI 3.4.1 web application.
2
Unzip the new BI 3.5 Portal data.zip file into TOMCAT_HOME\webapps\ your_bi_appname, overwriting any existing files with the newer version from the data.zip file. Your configuration files are not overwritten.
3
Delete the file TOMCAT_HOME\webapps\ your_bi_appname \WEB-INF\lib\xstream-1.3.1.jar.
4
Start Tomcat.
Note: Users may need to clear their browser cache before reconnecting to the BI Portal to ensure that they are running the latest version of the application. Go to the Portal URL in the browser and click Refresh to make sure that the latest version of the application is loaded.
Verification
Connect to your BI Portal. Click the About link on the login screen and verify that the Version is 3.5 and the Build Number is BI3-TRUNK-JOB1-1086.
BI Metadata Upgrade Procedure
Refer to the release notes for what has changed in this release.
Preparation
1
Plan for a couple of hours of down time.
2
Ensure that none of the loads are currently in progress. All jobs must be completed.
3
Put all scheduled jobs On Hold until the upgrade is complete. Shut down scheduler.
4
Take a backup of the current warehouse database.
5
Before you begin, make note of the following:
a
Note any DAILY_LOAD_SOURCE_Sxx jobs that appear after the standard _SNAPSHOT tables.
b
Note any HIST_LOAD_SOURCE_Sxx jobs that appear after the standard _SNAPSHOT tables.
Important: This upgrade replaces some load and stage tables, so if there are any customizations to these tables, ensure that they are ready to be made again.
Upgrade Steps for QAD BI Metadata
1
Due to significant improvements in Purchase Order processing, completely reload the fact_po_receipt, fact_po_order_history, and fact_po_order_performance tables. Corrections made to the SE Financials module require the reprocessing of SE AP and AR data. Also reload the fact_om_order_history table. Truncate these tables now; after the upgrade application is loaded, jobs are run to reload these tables using the new processing. In SQL Server, truncate the tables as follows:
truncate table fact_po_receipt
truncate table fact_po_order_performance
truncate table fact_om_order_history
truncate table fact_ap_voucher_history
truncate table fact_po_order_history
2
Log in to Setup Administrator.
3
Set your application directory to the new metadata folder. Load Application 35-up (new/modified tables, procedures, parameters, and jobs) by right-clicking on it and choosing Install.
a
A dialog box prompts you to proceed; click OK.
b
The next dialog box is for Application Load Properties:
Select Dimension on the left; on the right, click the box next to Existing Dimension objects will be and select Altered.
Select Dimension View on the left; on the right, click the box next to Existing Dimension View objects will be and select Recreated.
Select Stage Table on the left; on the right, click the box next to Existing Stage table objects will be and select Recreated.
Select Permanent Stage Table on the left; on the right, click the box next to Existing Permanent Stage table objects will be and select Altered.
Select Fact Table on the left; on the right, click the box next to Existing Fact table objects will be and select Altered.
Click OK.
4
The upgrade application installation takes some time as the load process alters/recreates various objects. Once the process completes, make any necessary customizations to your load tables. Verify that all other customizations are not affected.
5
The upgrade application output may have errors that some indexes could not be dropped. This is OK as they are new indexes that do not yet exist in the database. The upgrade script tries to drop each index before recreating it; if the index is new, the drop fails. Note any other errors in the upgrade output other than those index errors listed above. Consult QAD Support before continuing.
6
Start the Scheduler, but make sure that all jobs are still suspended.
7
Populate some new parameters and possibly modify some existing values, as follows:
a
Modify PO_RET_QTY_TOLERANCE, PO_PERCENT_QTY_UNDER, PO_PERCENT_QTY_OVER from the default values if desired:
PO_PERCENT_QTY_OVER: Percentage of Receipt Quantity over Order Quantity for a Purchase Order to still be considered In Full. Default value is 10%. In other words, the actual quantity received can be up to 10% greater than the amount ordered and the order line is still considered In Full. If the quantity received is greater than the quantity ordered plus 10%, the order line is not considered In Full.
PO_PERCENT_QTY_UNDER: Percentage of Receipt Quantity under Order Quantity for a Purchase Order is still considered In Full. Default value is 10%. In other words, the actual quantity received can be up to 10% less than the amount ordered and the order line is still considered In Full. If the quantity received is less than the quantity ordered minus10%, the order line is not considered In Full.
PO_RET_QTY_TOLERANCE: This is the Percentage of Returns Quantity used for calculating the Defect Rate. Default value is 15%. In other words, if the return quantity is greater than 15% of the order quantity, the order line is considered a defect.
b
Modify SALES_SNAPSHOT_REPLACE_FLAG and SALES_SNAPSHOT_FREQUENCY from the default values if desired:
SALES_SNAPSHOT_REPLACE_FLAG: Y to replace the snapshot for recalculated periods when the SALES_ROLLUP job is run; N to add new records and not update previously calculated records. Default value is N.
SALES_SNAPSHOT_FREQUENCY: Set to M for monthly snapshots, W for weekly snapshots, or B for both monthly and weekly. Default value is M.
Important: Check the PO_ORDER_HISTORY_DATE and SALES_ORDER_HISTORY_DATE parameters. If the current date minus the PO_PROCESS_DAYS is newer than the PO_ORDER_HISTORY_DATE, or the current date minus the SALES_PROCESS_DAYS is newer than the SALES_ORDER_HISTORY_DATE, increase the process days value so that the current date minus that number of days produces a date that is before the related ORDER_HISTORY_DATE (PO or SALES).
8
Set INITIAL_JOB_SETUP_DATE to the current date.
9
Change INITIAL_JOB_SETUP_ENABLED to Y.
10
Check the following jobs for customizations. Note any custom changes that have been made; reapply them to the new job templates. Then delete the following jobs for each existing source (Note: do NOT delete the job name ending in _XXXXXXXX; that is the template from which the source-specific jobs are created):
DAILY_COMMON_PROCESS_sourcename
DAILY_PERM_sourcename (CAUTION: do NOT deleted the job named DAILY_PERM_EXTRACT)
DAILY_PO_PROCESS_sourcename
DAILY_SALES_PROCESS_sourcename
HIST_COMMON_PROCESS_sourcename
HIST_PERM_sourcename
HIST_PO_PROCESS_sourcename
HIST_SALES_PROCESS_sourcename
11
In the Scheduler, run the INITIAL_JOB_SETUP job.
12
The list of History and Daily jobs is rewritten by the INITIAL_JOB_SETUP job. Make sure any customizations that were made to the new job templates are now in the source-specific copies of those jobs (or reapply any customizations as necessary). Also add to the end of the DAILY_ and HIST_ load lists any jobs that occurred after the snapshot jobs (which you noted in the Preparation section).
13
This is a good time to review the Parameters and their definitions in the BI 3.5 Installation Guide. Check your parameter settings; you will want to consider changing some, such as various PROCESS_DAYS and SNAPSHOT_NUM_DAYS values, to make sure that you are not reloading extra data unnecessarily each day. The module PROCESS_DAYS are typically set to 10 by default; SNAPSHOT_NUM_DAYS are set to 31 by default.
Fixing Existing Fact Tables
Now run the jobs to reload the fact tables you had truncated earlier. Run these for each source. Depending on the amount of history data in your system, these jobs can take a while to run.
1
Set parameter JOB_CHAINING_ENABLED to N.
2
Run the job SET_CONNECTION_XXXXXX, where XXXXXX = the source connection name.
3
Run HIST_PERM_EXTRACT.
4
Run the job HISTORY_RELOAD_OM_35_UPGRADE.
5
Run the job HISTORY_RELOAD_PO_35_UPGRADE.
6
Run the job UPGRADE_FACT_PO_RECEIPT_341_TO_35.
7
(SE sources only) Run the job RELOAD_SE_AP_AR_FROM_PERM.
8
Repeat steps 2-7 for each source connection (if you have multiple sources).
9
Run the job HISTORY_SALES_ROLLUP.
10
Run the job HISTORY_PO_ROLLUP.
11
When upgrade jobs have been run for all sources, make sure to set the parameter JOB_CHAINING_ENABLED back to Y.
Re-create Purchasing Cube
If you use the Purchasing cube, delete the measure group that referenced the fact_po_booking table:
1
Delete the cube in the Analysis Server.
2
In the DWD, right-click on the OLAP Purchasing cube and select Display Measure Groups.
3
Right-click on the fact_po_booking measure group and choose Delete Measure Group. Click OK to answer the verification questions about deleting the associated measures.
4
Right-click on the OLAP Purchasing cube and choose Create (Alter) Cube.
5
Process the cube.
Upgrade is complete. Resume normal processing.
To Add a new Source
If you want to add a data source, do the following:
1
Add the new source name to DAILY_LOAD_SOURCE_Sxx (where xx represents the next number in the sequence).
2
Add the new source name to HIST_LOAD_SOURCE_Sxx (where xx represents the next number in the sequence).
3
Add the new source name to INITIAL_JOB_SETUP_CONNECTION_xx (where xx represents the next number in the sequence).
4
Add a INITIAL_JOB_SETUP_CONNECTION_xx_RUN (if it does not exist) and set its value to N.
5
Add a INITIAL_JOB_SETUP_CONNECTION_xx_TYPE (if it does not exist) and set its value to either EE or SE depending on which type your financials system for that source is.
6
Make sure INITIAL_JOB_SETUP_DATE is set to the current date.
7
Double-check the INITIAL_JOB_SETUP_CONNECTION_xx_RUN parameters to make sure that any sources that have been historically loaded have a Y next to their relative _xx_ number and that any new sources have an N.
8
Go to the Scheduler. Start the HIST_START job. Once it starts, double-check to make sure that it started running HIST_ jobs only for your new data source.
Update Portal Model
Log in to the Portal as an Administrator. Go to the Administration menu and choose Model Administration. Click Rebuild Model.
After the model has been rebuilt, if you have any custom data models, open each model and save it to ensure that it picks up changes in the Master model.
Update Portal Documentation and Standard Objects
Update the metadata documentation:
Delete the existing TOMCAT_HOME\webapps\ your_bi_appname \documentation\suite directory.
Unzip the latest qadbi-documentation.zip (found on the BI 3.5 Modules CD) into your TOMCAT_HOME\webapps\ your_bi_appname \documentation directory.
To install the latest BI Portal standard objects, copy these files from the BI 3.5 Modules CD into your TOMCAT_HOME\webapps\ your_bi_appname \export directory:
BI35_deprecated_items.zip
qad_standard_items.zip
Then, in the BI Portal:
1
Log in as an Administrator.
2
Go to the Administration -> Data Migration screen.
3
Click the Import tab.
4
Select the Update existing records box.
5
Click the radio button in front of File on server.
6
Enter in the box the file name BI35_deprecated_items.zip and click Import.
7
Repeat for the qad_standard_items.zip file.