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

  • Fixes
    Issue ID
    Two or more dashboards can now have the same name as long as they are in different folders. Previously the portal could display the wrong dashboard when there were dashboards in different folders with the same name.
    Query results are now ordered by column properly when locale-specific numbers are in use.
    In a Portal data security model, two constraints within the same dimension are now ORed rather than ANDed. This means that a user with a security model with two constraints on the same dimension now sees the Superset of values that meet either constraint (rather than the subset of values that meet both constraints only). For example, if the Customer Bill-To dimension has one constraint that Customer Country = UK, and another that the Customer Salesperson 1 Name = John Doe, then the user with this model can now see all records where the Customer Country is UK (no matter what the Customer Salesperson1 Name is), plus all the records where the Customer Salesperson 1 Name is John Doe (no matter what the Customer Country is). Previously the user would only see those records where Customer Country = UK and the Customer Salesperson 1 = John Doe.
    If a chart is viewed via drill-in from another chart, and then collaborated on, the collaboration icon only appears on the proper chart, and not on its parent. Previously the portal would display the icon on the top-level chart of the drill-in hierarchy.
    The Test Run button in the Query Designer now creates the proper Comparative query. Previously the Test Run button would not generate the proper comparative measures.
    Sales (Order Management) snapshots were previously only weekly; you can now choose to have them done Weekly, Monthly, or Both like other snapshot tables. Default is Monthly.
    Closed orders are no longer excluded from fact_om_order_history.
    fact_om_order_history should no longer create records with overlapping dss_history_start and end dates
    dim_credit_term slowly changing column changed from credit_term_percent_due to credit_term_percent_due_orig to prevent keys from changing daily. New keys should now be generated only when the percent due changes in the record in ERP; previously certain customized versions of the code would generate new keys daily even though the percent due had not changed.
    Blanket Release Purchase Orders are now included in fact_po_order_history.
    Some work tables for OM and PO processing were not filtering for source system code, and therefore processing more records than necessary. These tables now filter by source code, which should improve performance.
    Historic loads of Purchase Order History sometimes failed due to null purchase order dates. The DATE_EARLIEST_POSSIBLE parameter value is now used to set the purchase_order_history_date if the value in the ERP records is null.
    Standard Edition (SE) Accounts Receivable and Accounts Payable currency conversion have been corrected to use override exchange rates where applicable. Also corrected in the SE AR and AP tables was the proper use of the ROUNDNUMBERAP and ROUNDNUMBERAR functions (in some places AR processes had been using the AP function and vice versa); AP Voucher processing now uses credit_term_split_sequence as part of the primary key; and voucher processing uses the proper amount for partially paid vouchers.
    Since the concept of 'bookings' was not really applicable to Purchase Orders, the fact_po_booking table and its associated stage tables have been removed. Also, the po_growth_rate measure has been removed from fact_po_order.
    The fact_ap_invoice_snapshot table has been renamed to the AP Voucher Snapshot table in its Business Display name (end user label), since the concept in AP is better known as Voucher, not Invoice. Also, the primary key has been set to Source_system, domain, invoice_number (from ap_mstr.ap_ref), credit_term_split_sequence (ctd_det.ctd_seq), effective_date.
    The aging measures have been hidden from end user display for fact_ar_invoice_history and fact_ap_voucher_history tables, since they really only make sense in the corresponding snapshot tables (where there will be only one row per invoice) and not in the history tables (where there might be many records per invoice as the records change over time).
    work_po_change_list4 has been corrected to consider changes based upon the perm_update_time rather than the dss_update_time (which was causing it to process records that had not really changed).
    fact_po_order_history insertion has been corrected to ensure the discount_percentage is in the appropriate column order. The incorrect order of columns was causing unnecessary creation of extra rows in the table.
    The primary key for the fact_po_order_history table has been modified to include the dss_version_number, and a second unique index has been added on source_system_code, domain_code, po_number, po_line_number, dss_history_start_date, dss_history_end_date.
    Purchase Order performance changes: Supplier performance tracks order lines received On Time or not On Time (early or late) based on any receipts against the line being early or late factoring in a tolerance days. It also tracks In Full or not In Full, based on the PO line, factoring in a quantity tolerance. Determining the In Full portion of OTIF requires the line to be past due or closed.
    Purchase Receipt changes: In measuring On Time-ness for Supplier Performance KPIs, we need to look at the actual receipts since every receipt needs to be On Time for its own due date. When the Supplier Performance module is used, On Time-ness including built in days tolerances is accurately found via the vepd_det table (one vepd_det record created for every receipt for tracked Suppliers). For End-Users who do not use Supplier Performance and also for End Users who do use Supplier Performance but for PO lines for Suppliers not tracked there, the receipts have a due date associated with that receipt. We indicate the receipt is On Time, early, or late. We now do all this in fact_po_receipt. This accounts for multiple receipts with multiple due dates. If any of the receipts against a line are flagged as early or late, the whole line is NOT OTIF.
    Purchase Order Performance: In Full flag added. In order for a PO Line to be considered In Full, the line must be closed or past due (we are looking at all receipts for a PO Line cumulatively).
    If Actual Net Qty Received = Qty Ordered in Ordered UM, then In Full Flag = 1
    If (Actual Net Qty Received/ Qty Ordered in Ordered UM) > 1 and <= 1 + % PO_PERCENT_QTY_OVER, then In Full Flag = 1
    If (Actual Net Qty Received/Qty Ordered in Ordered UM) < 1 and >= 1 - % PO_PERCENT_QTY_UNDER, In Full Flag = 1
    Else In Full Flag = 0
    PO_PERCENT_QTY_OVER and PO_PERCENT_QTY_UNDER are new BI parameters
    Purchase Order Performance: On Time In Full flag added. If On Time Flag = 1 AND In Full Flag = 1 then 1 else 0.
    Purchase Order Performance: po_line_quality is now called Returns Flag and is calculated thus: If pod_qty_rtnd > PO_RET_QTY_TOLERANCE * order quantity then 1, else 0. PO_RET_QTY_TOLERANCE is a new BI parameter - note this is a different % quantity tolerance than that used to determine In Full (see QBI-740 above)
    The sourcing and calculation of Quantity Open measures have been corrected in fact_po_order_history, fact_po_order, and fact_po_order_performance. The business name (end user label) for Quantity Open has been changed to Quantity Open in Ordered UM. The business names for the open_amount measures have been changed to Actual Open Value.
    The primary key for the fact_om_order_history table has been modified to include the dss_version_number, and a second unique index has been added on source_system_code, domain_code, order_number, order_line_number, dss_history_start_date, dss_history_end_date.
    Two load tables have been modified to collect information required to determine if a sales order is consignment, FSM, or scheduled. The table load_sod_det now includes columns sod_sched, sod_fsm_type, sod_consigment, and sod_compl_stat (this last column is EE-only). The table load_idh_hist now includes columns idh_fsm_type and idh_sched.
    Some Standard Edition AR and AP columns that are no longer used have been removed from end user display - sort and entity_exchange_rate.
    fact_om_order_history now populates the order status properly for open and closed orders.
    A new dimension has been added named dim_order_line_order_type that is linked to fact_om_order_history and contains flags for whether an order is consigned, scheduled, or has an FSM type (SSM Flag).
    fact_om_order_history will populate order_complete_state properly for EE orders that are closed but still in the system (sod_compl_stat = 01). (Since the sod_compl_stat column does not exist in SE, the order_complete_state for SE records are set to N/A.)
    If the base and transaction currency are the same, but are different from the corporate currency, the currency conversion is now calculated properly. Previously the corporate value would be set to the same as the base & transaction value in this case.