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.6.1 from 3.6
    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 Common module and any other modules you have installed.
    Note: Because the metadata files are now segregated by module, it is only necessary to install the modules that are needed.
    Perform the Common upgrade first. The other upgrades can be done in any order.
    All users need to run the Common metadata upgrade application.
    If you process any of the Order Management (Sales) fact_om_* tables, install the Order Management (OM) upgrade application.
    If you process Inventory and/or Purchase Order tables, install the Operations module upgrade application.
    There is no upgrade to the Financials module in this maintenance release.
    Log in to Setup Administrator.
    Choose Tools|Start Logging. Select a name and location for your log file and Save.
    Load the Common Module Upgrade Application as follows:
    Set your application directory to the new metadata/common folder.
    Load application upgradeCom 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 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.
    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.
    Repeat for any other modules that must be upgraded.
    Order Management. Change the Application Directory to the metadata/order_management subdirectory and install application upgradeOM .
    Operations. Change the Application Directory to the metadata/operations subdirectory and install application upgradeOps .
    Note: The upgrade application installations will take some time as the load process alters and re-creates various objects.
    After the upgrade applications have been installed, reapply the customizations to the upgraded tables. Verify that all other customizations are not affected.
    Start the Scheduler. Make sure all jobs are still suspended.
    Run the Upgrade jobs for the tr_hist.tr_trnbr roll-over issue for each module you have installed:
    Common Module. Run the UPGRADE_36_to_361_QBIS_25_COMMON job to update the permsup_transaction_hist table to include the transaction date and to seed the TR_HIST_DATE_MAX values for each source.
    Order Management. Run the UPGRADE_36_to_361_QBIS_25_OM job to update the fact_om_booking table to include the transaction date.
    Operations. Run the UPGRADE_36_to_361_QBIS_25_OP job to update the fact_op_transaction table to include the transaction date.
    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 the UPGRADE_36_to_361_QBI_1773 job.
    Set the JOB_CHAINING_ENABLED parameter back to Y.
    If the upgrade affected any customized tables, reapply your customizations. For a list of new and modified tables, see Data Warehouse Tables Changed.
    If there were any customizations previously added to any of the modified jobs, update the job to reinclude 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:
    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 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 will 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.