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



  •     QAD Glossary

  • Release Notes for Releases 3.6.1 and 3.5.1
    QAD Business Intelligence Version: 3.6.1 and 3.5.1
    Date: June 2012
    QAD BI 3.6.1 and 3.5.1 address the tr_hist.trnbr roll-over issue and the inventory issues involving correct determination of unit cost and end quantity on hand. Customers who are not experiencing these issues are not required to install this maintenance release.
    Fixes
     
    Component
    QAD Issue
    Releases
    Description
    Metadata
    QBIS-25
    BI 3.5.1, 3.6.1
    tr_hist.trnbr archive and rollover are now handled in BI.
    Metadata
    QBI-1363
    BI 3.5.1, 3.6.1
    Inventory - fact_inv_mth_balance will now properly capture the unit_cost of items.
    Metadata
    QBI-33,
    QBI-1773
    BI 3.5.1, 3.6.1
    Corrects calculation of Inventory End Quantity on Hand.
    Metadata
    QBI-1556
    BI 3.6.1
    Added sales_person_code to perm_transaction_hist.
    Metadata
    QBI-1698
    BI 3.6.1
    Truncation and load of inventory transaction type tables moved earlier as required by Inventory processing.
    Metadata
    QBI-1768
    BI 3.6.1
    stage_om_order3 join to dim_account corrected.
    Metadata
    QBI-703
    BI 3.5.1
    Index added to stage_inv_mth_balance to improve performance of fact_inv_mth_balance custom processing.
    Data Warehouse Tables Changed
    The following section lists the Data Warehouse tables that have been changed, added, or deleted.
    Note: The tables on the Modified list may have been changed structurally. For example:
    Columns added or deleted
    Indexes added or deleted
    Changes made to business display names
    Changes to visibility of particular columns in the BI Portal
    Any combination of these modifications
    List of Tables Modified for BI 3.6.1
    Common Module
     
    load_tr_hist
    perm_transaction_hist
    stage_tr_hist_list
    permsup_transaction_hist
    Operations Module
     
    extract_inv_trans_hist_cons
    stage_inv_bal_mth_list
    stage_op_transaction_merge
    extract_inv_transaction_hist
    stage_inv_bal_mth_trans
    stage_op_transaction_merge
    extract_po_transaction_hist
    stage_inv_bal_mth_trans1
    stage_op_transaction_merge
    extract_op_transaction_hist
    stage_inv_bal_mth_trans2
    stage_op_transaction0
    fact_inv_mth_balance
    stage_inv_mth_balance
    stage_op_transaction1
    fact_inv_transaction
    stage_inv_mth_balance_hist_calc
    stage_op_transaction2
    fact_op_transaction
    stage_inv_mth_balance1
    stage_po_order_hist_initial4
    perm_op_hist
    stage_inv_transaction_con_cus3
    stage_po_order_hist_initial5
    stage_inv_bal_mth_current
    stage_inv_transaction_con_cus4
    stage_po_order_hist_initial6
    stage_inv_bal_mth_current4
    stage_op_tr_hist_rjct_wo
    work_inv_change_hist_list
    stage_inv_bal_mth_date
    stage_op_trans_scrapi
    work_inv_change_list
    stage_inv_bal_mth_date1
    stage_op_transaction
    work_inv_change_list1
    stage_inv_bal_mth_date2
     
     
    Order Management Module
     
    :
    extract_om_transaction_hist
    stage_om_booking_previous
    stage_om_order
    stage_om_booking
    stage_om_booking_transaction
    stage_om_order1
    fact_om_booking
    stage_om_booking_transaction1
    stage_om_order2
    fact_om_shipment
    stage_om_invoice_transaction
    stage_om_order3
    stage_om_booking_max_tran
    stage_om_invoice_transaction1
     
    List of Tables Added for BI 3.6.1
     
    stage_inv_mth_end_cst
    stage_inv_mth_end_cst1
    stage_inv_trx_chg_mths
    stage_inv_trx_chg_mths1
    List of Tables Deleted for BI 3.6.1
    No tables deleted for BI 3.6.1 upgrade.
    List of Tables Modified for BI 3.5.1
     
    extract_inv_trans_hist_cons
    stage_inv_bal_mth_date2
    stage_om_invoice_transaction
    extract_inv_transaction_hist
    stage_inv_bal_mth_list
    stage_om_invoice_transaction1
    extract_om_transaction_hist
    stage_inv_bal_mth_trans
    stage_om_order
    extract_po_transaction_hist
    stage_inv_bal_mth_trans1
    stage_om_order1
    fact_inv_mth_balance
    stage_inv_bal_mth_trans2
    stage_om_order2
    fact_inv_transaction
    stage_inv_bal_revalue1
    stage_om_order3
    fact_om_booking
    stage_inv_mth_balance
    stage_po_order_hist_initial4
    fact_om_shipment
    stage_inv_mth_balance_hist_calc
    stage_po_order_hist_initial5
    load_tr_hist
    stage_inv_mth_balance1
    stage_po_order_hist_initial6
    perm_transaction_hist
    stage_inv_transaction_con_cus3
    stage_tr_hist_list
    permsup_transaction_hist
    stage_inv_transaction_con_cus4
    stage_tr_hist_list
    stage_inv_bal_item_list
    stage_om_booking
    stage_unit_of_measure3
    stage_inv_bal_mth_current
    stage_om_booking_max_tran
    work_inv_change_hist_list
    stage_inv_bal_mth_current4
    stage_om_booking_previous
    work_inv_change_list
    stage_inv_bal_mth_date
    stage_om_booking_transaction
    work_inv_change_list1
    stage_inv_bal_mth_date1
    stage_om_booking_transaction1
     
    List of Tables Added for BI 3.5.1
     
    stage_inv_mth_end_cst
    stage_inv_mth_end_cst1
    stage_inv_trx_chg_mths
    stage_inv_trx_chg_mths1
    List of Tables Deleted for BI 3.5.1
    No tables deleted for BI 3.5.1 upgrade.
    Upgrade to 3.6.1 from 3.6
    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.
    4
    Take a backup of the current warehouse database.
    5
    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
    1
    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.
    2
    Log in to Setup Administrator.
    3
    Choose Tools|Start Logging. Select a name and location for your log file and Save.
    4
    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.
    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.
    e
    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.
    5
    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.
    6
    After the upgrade applications have been installed, reapply the customizations to the upgraded tables. Verify that all other customizations are not affected.
    7
    Start the Scheduler. Make sure all jobs are still suspended.
    8
    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.
    9
    Run the Upgrade job for the inventory valuation issues:
    a
    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.
    b
    Run the UPGRADE_36_to_361_QBI_1773 job.
    c
    Set the JOB_CHAINING_ENABLED parameter back to Y.
    10
    If the upgrade affected any customized tables, reapply your customizations. For a list of new and modified tables, see Data Warehouse Tables Changed.
    11
    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:
    PREPROCESS_COMMON_LOADS
    PREPROCESS_COMMON_TRUNCATE
    PREPROCESS_OP_LOAD
    PREPROCESS_OP_TRUNCATE
    DAILY_OP_PERM_EXTRACT
    HIST_OP_PERM_EXTRACT
    DAILY_OP_INV_PROCESS_CHAINED
    HIST_OP_INV_PROCESS_CHAINED
    12
    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.
    13
    Resume normal processing.
    Upgrade to 3.5.1 from 3.5
    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.
    4
    Take a backup of the current warehouse database.
    5
    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
    1
    Unzip the metadata for the BI 3.5.1 Upgrade.
    2
    Log in to Setup Administrator.
    3
    Choose Tools|Start Logging. Select a name and location for your log file, then save.
    4
    Load the BI 3.5.1 Upgrade Application as follows:
    a
    Set the application directory to the new metadata folder.
    b
    Load application upgradeBI 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.
    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.
    e
    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.
    5
    If the upgrade affected any customized tables, reapply your customizations. For a list of new and modified tables, see Data Warehouse Tables Changed.
    6
    Start the Scheduler. Make sure all jobs are still suspended.
    7
    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.
    8
    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.
    9
    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.
    10
    Run the Upgrade job for the inventory valuation issues:
    a
    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.
    b
    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.
    c
    Run DAILY_COMMON_PROCESS_<connection_name>.
    d
    Run DAILY_PERM_<connection_name>.
    e
    Run DAILY_INV_PROCESS_<connection_name>.
    f
    Replace the prefix of the word DAILY with HIST for the INV_PROCESS_RUNNING_JOB_NAME parameter.
    g
    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.
    h
    Repeat steps b through g for each connection name.
    i
    Set the INV_PROCESS_DAYS parameter back to an appropriate value such as 5-10 days.
    j
    Set the JOB_CHAINING_ENABLED parameter back to Y.
    k
    Reset the DAILY_START job so that it will run again normally.
    11
    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.
    12
    Resume normal processing.