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 Glossary

  • Upgrade to 3.5.1 from 3.5
    Plan for a couple of hours of down time.
    Ensure that there are no loads currently in progress. All jobs must be completed.
    Put all scheduled jobs On Hold until the upgrade is complete. Shut down the scheduler.
    Take a backup of the current warehouse database.
    Before you begin, make note of the following:
    Note any custom DAILY_LOAD_JOBxxx jobs that appear after the final ROLLUP jobs; for example, DAILY_PO_ROLLUP or DAILY_SALES_ROLLUP if you do not have the Purchase Orders module installed. If you have neither Sales nor Purchase Order processing, note any custom jobs that might be after the final SNAPSHOT jobs: ____________________________________ _____________________________________________________________________________
    Note any custom HIST_LOAD_JOBxxx jobs that appear after the standard ROLLUP or SNAPSHOT jobs: ______________________________________________________________
    Important: This upgrade will replace some load and stage tables. If there are any customizations to these tables, ensure that they are ready to be made again.
    Upgrade Steps for QAD BI Metadata
    Unzip the metadata for the BI 3.5.1 Upgrade.
    Log in to Setup Administrator.
    Choose Tools|Start Logging. Select a name and location for your log file, then save.
    Load the BI 3.5.1 Upgrade Application as follows:
    Set the application directory to the new metadata folder.
    Load application upgradeBI by right-clicking on the file and choosing Install Application.
    From the drop-down list, select the ODBC DSN for your DWD instance.
    The system prompts you to proceed. Click OK.
    Note: You can always cancel 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.
    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 on the box next to Existing Dimension objects will be and select Altered.
    On the left, select Dimension View. On the right, click on the box next to Existing Dimension View objects will be and select Recreated.
    On the left, select Stage Table. On the right, click on the box next to Existing Stage table objects will be and select Recreated.
    On the left, select Permanent Stage Table. On the right, click on the box next to Existing Permanent Stage table objects will be and select Altered.
    On the left, select Fact Table. On the right, click on the box next to Existing Fact table objects will be and select Altered.
    Click OK.
    Note: The upgrade application installations will take some time as the load process alters and re-creates various objects.
    If the upgrade affected any customized tables, reapply your customizations. For a list of new and modified tables, see Data Warehouse Tables Changed.
    Start the Scheduler. Make sure all jobs are still suspended.
    If any customizations were previously added to HIST_INV_PROCESS_XXXXXXXX and DAILY_INV_PROCESS_XXXXXXX, update the job to reinclude those extra parts. You can double check what was in the job by looking at the newly renamed HIST_INV_PROCESS_XXXXXXXX_1 or DAILY_INV_PROCESS_XXXXXXXX_1. Then, rename any existing DAILY_INV_PROCESS_<source> job to DAILY_INV_PROCESS_<source>_1. Insert a copy of the new DAILY_INV_PROCESS_XXXXXXXX and rename it to DAILY_INV_PROCESS_<source>. Repeat this to copy the new HIST_INV_PROCESS_XXXXXXX for each source.
    If any customizations were previously added to HIST_PERM_XXXXXXXX and DAILY_PERM_XXXXXXX, update the job to reinclude those extra parts. You can double check what was in the job by looking at the newly renamed HIST_PERM_XXXXXXXX_1 or DAILY_PERM_XXXXXXXX_1. Then, rename any existing DAILY_PERM_<source> job to DAILY_PERM_<source>_1. Insert a copy of the new DAILY_PERM_XXXXXXXX and rename it to DAILY_PERM_<source>. Repeat this to copy the new HIST_PERM_XXXXXXX for each source.
    Run the UPGRADE_35_to_351_QBIS_25 job to update the permsup_transaction_hist, fact_om_booking, and fact_op_transaction tables to include the transaction date and to seed the TR_HIST_DATE_MAX values for each source.
    Run the Upgrade job for the inventory valuation issues:
    Set the JOB_CHAINING_ENABLED parameter to N.
    Important: Ensure that the INV_PROCESS_DAYS parameter is set to be large enough to load records from the ERP system since the last Daily run.
    Run SET_CONNECTION_<connection_name> for your first source system. If you have only one source system, you do not need to perform this step.
    Run DAILY_COMMON_PROCESS_<connection_name>.
    Run DAILY_PERM_<connection_name>.
    Run DAILY_INV_PROCESS_<connection_name>.
    Replace the prefix of the word DAILY with HIST for the INV_PROCESS_RUNNING_JOB_NAME parameter.
    Run the UPGRADE_35_to_351_QBI_1773 job.
    Note: This job may take a long time because it is recalculating the entire fact_inv_mth_balances table.
    Repeat steps b through g for each connection name.
    Set the INV_PROCESS_DAYS parameter back to an appropriate value such as 5-10 days.
    Set the JOB_CHAINING_ENABLED parameter back to Y.
    Reset the DAILY_START job so that it will run again normally.
    Check the values of the TR_HIST_DATE_MAX_Sxx parameters for each source. If necessary, increase TR_HIST_PROCESS_DAYS from the default value of 3 days. The number of Process Days must be such that the TODAY - earliest TR_HIST_DATE_MAX_Sxx is less than the TR_HIST_PROCESS_DAYS. There are also several new parameters to control how the BI system handles the rollover of the tr_trnbr:
    TR_HIST_PROCESS_DAYS. This is the number of look-back days when extracting data from tr_hist. The records being extracted are records where tr_trnbr is greater than the highest transaction_number records already extracted for that source, except after tr_trnbr rollover, when newer transactions may have smaller trnbrs than older transactions. The BI DW must also take into account the transaction date in order to find the lower-numbered transactions that are actually new. This parameter says to extract from the ERP transactions entered within the last X days. If the number of days since the TR_HIST_DATE_MAX_Sxx is greater than the TR_HIST_PROCESS_DAYS parameter, a task that checks this during the run will fail and indicate that this number needs to be increased. The default value is 3.
    TR_HIST_MAX_VALUE. This is the maximum number allowed for the tr_hist.tr_trnbr field, or in other words, the number after which the tr_trnbr will roll over and start at the first available low number. The default value is 99999999. If the tr_sq01 sequence is set to a different maximum value, enter that here.
    TR_HIST_PRE_ROLLOVER_COUNT. This is the number of records that would typically be in three days worth of data to ensure readiness for tr_hist.tr_trnbr rollover. Once the tr_trnbr for a source is detected to be within TR_HIST_PRE_ROLLOVER_COUNT of TR_HIST_MAX_VALUE, the BI system sets the TR_HIST_TRAN_MAX_Sxx value for the source to 0. This will force the tr_hist extraction to scan the whole table for records that have been processed within the last TR_HIST_PROCESS_DAYS. The default value is 5000.
    TR_HIST_PCT_OF_MAX_REF. This is the percent of the TR_HIST_MAX_VALUE to use as a reference point to look for new low-numbered transactions when dealing with the rollover. The default value is 50. When this value is 50, you search the transactions with numbers less than 50% of the TR_HIST_MAX_VALUE for the highest number with a transaction date within the processing window.
    Resume normal processing.