Metadata
(Common)

QBI-3656

Additions were made to the common module's dim_item dimension to support the new SSM functionality; but all existing customers should know that dim_item changed, whether they are planning on adding SSM or not, as they get new columns.

 

QBI-3722

perm_work_order_routing, perm_work_order_master, and their supporting objects have been moved to the Common module so they can be shared between modules OM and SSM.

Users with OM installed will not notice any difference. These objects have been moved to Common scheduled jobs.

Users upgrading to BI 3.10 or higher without OM or SSM will now receive these objects. There are ways to disable them in the scheduled job runs if there are no plans to install OM or SSM.

Metadata
(Financials EE)

QBI-3777

The prior stage table delete in the procedure that updates the AR/AP snapshot tables has been modified so that it is only pulling the distinct source/domain/effective_date/snapshot frequency for deletion instead of matching up every single record in a Cartesian join that creates a lot of unnecessary processing overhead. This should improve performance on these tables during daily runs.

 

QBI-3942

Column added and upgrade script provided. Includes changes to the snap1,2,3 table to ensure that when weekly and monthly is chosen, that on days an end of week day is the same as an end of month day, records for both will be created. Until now, a monthly record would be created, but the weekly record would be skipped.

 

QBI-3943

Column added and upgrade script provided. Includes changes to the snap1,2,3 table to ensure that when weekly and monthly is chosen, that on days an end of week day is the same as an end of month day, records for both will be created. Until now, a monthly record would be created, but the weekly record would be skipped.

Metadata
(Financials EE and SE)

QBI-3628

Business key sequence has been reordered to take advantage of the business key during the deletion process. Key sequence for both AR/AP snapshots in both SE and EE environments is now source_system_code, domain_code, effective_date and snapshot_frequency, then the rest of the business key columns.

Metadata
(Financials SE)

QBI-3653

Changed the logic that was improperly flagging records with a zero amount_open. The old logic had been setting the dss_current_flag to N and leaving the dss_history_end_date with its future end date.

The new logic leaves the dss_current_flag as Y and sets the dss_history_end_date to the dss_history_begin_date for that row. This ensures that the record appears in the snapshot table for only one period and does not keep reappearing period after period.

 

QBI-3771

The prior stage table delete in the procedure that updates the AR/AP snapshot tables has been modified so that it is only pulling the distinct source/domain/effective_date/snapshot frequency for deletion instead of matching up every single record in a Cartesian join that creates a lot of unnecessary processing overhead. This should improve performance on these tables during daily runs.

Metadata
(Multimodule)

QBI-3679

perm_op_hist and all supporting tables have been moved to the Common module.

A new auto test has been written to ensure that this table is available in the SSM module.

 

QBI-720

 

The Daily load of tr_hist data will now pick up data from any domain, including new domains. Previously the load_tr_hist table included in its Where clause a list of previously loaded domains for each source, so it would only load new records that were from previously known domains. That clause has been removed, so new records from new domains will also be loaded in daily loads.

Metadata
(Order Management)

QBI-3407

Set+Cursor updates removed from Order Management staging. All fact tables will now use "Unknown" zero-key dimension record when the dimension cannot be identified in the ERP master data. For example, if an order contains an item that does not appear in item master, a dim_item record will not be created to simulate it. The order will instead reflect the generic unknown item. This is a minor loss in functionality that will create a major performance benefit during each DAILY scheduled job run.

Metadata
(Purchasing)

QBI-3980

A job named UPGRADE_39_TO_310_PO_SNAPSHOT_FOR_B_TO_M has been included in the BI 3.10 Operations Module Upgrade Application. If you have been running the Purchasing Snapshot for both weekly and monthly periods (that is, PO_SNAPSHOT_FREQUENCY is set to B for Both), and you want to change that to just Monthly (M), you can change your parameter value. Then, run the UPGRADE_39_TO_310_PO_SNAPSHOT_FOR_B_TO_M job to remove the unwanted Weekly records from the snapshot table and therefore reduce both the amount of space being taken up by the Purchase Order Snapshot table and the time it takes to process the snapshot table each day.

Portal

QBI-3341 & QBI-3344

Previous versions of the BI Portal did not correctly pass parameter values when drilling from a report to another report. This has been fixed and the correct parameter values will be passed.

 

QBI-3877

Unicode values in reports will now export properly to PDF and to Excel. Note that this requires the existence of Arial Unicode MS fonts on the BI Portal server. If this font is not available on the Tomcat server, a different Unicode font will need to be provided. In this case, the font-extensions file (in the Portal web application's WEB-INF\classes directory) should be modified to reference the preferred Unicode font.

Cubes

QBI-2449

When viewing the OLAP cubes in Analysis Services, the correct dates should be seen when using moving_fin_year ot moving_cal_year within a date dimension. This correction has been made to all OLAP date dimensions, and the three OLAP cubes—Inventory, Purchasing, and Sales—have all been refreshed with the corrected dimensions. Note that if you have customized any of these cubes in your own environment you will need to save a copy of your own cubes, as they will be overwritten when you install the BI 3.10 upgrade.

Previously when using moving_fin_year or moving_cal_year some incorrect dates would be included in the "Current" or "Previous" year. This was due to dimension relationships that the BI DWD tools sets up automatically when OLAP date dimensions are created. Moving_fin_year and moving_cal_year were getting dimension relationships set up automatically that should not be there. These unwanted dimension attribute relationships have been removed for all OLAP date dimensions.

Metadata
(Capacity Plan)

QBI-3849

Added a new stage and perm table to manage the site_working_calendar used for determining performance dates in the PO process. This should improve the processing time of the Purchasing Performance job. Previously, this determination of whether PO receipt was within the threshold for 'on-time' used a view, which was less efficient. The jobs HIST_COMMON_PERM_CHAINED and DAILY_COMMON_PERM_CHAINED have been modified to process the new stage and perm tables (this processing must happen after perm_shop_cal is processed).

Metadata
(EAM Maint)

QBI-3526

EAM History loads no longer check history date for "last time ran".

 

QBI-3670

When an EAM work order is in (C)losed status, fact_eam_wo_history.dss_history_end_date now reflects the last changed date of the work order instead of the default '2999-12-31'. The 3.9 to 3.10 upgrade script will update all the records in this fact table with the correct dss_history_end_date.

Since the snapshot table and other related tables do not depend on the dss_history_end_date field, no other changes have to be applied for this fix.

 

QBI-3706

Cross traffic between ERP and EAM calendar sources has been eliminated by adding truncates to these tables in these jobs:

Truncate tables:

stage_date_qad3

stage_eam_date_qad3

dim_date_qad processes in:

DAILY_COMMON_PROCESS_CHAINED

DAILY_EAM_PROCESS_CHAINED

HIST_COMMON_PROCESS_CHAINED (twice process, once custom)

HIST_EAM_PROCESS_CHAINED

 

QBI-3873

The load_eam_domain task will now work properly for EAM applications running on Progress Open Edge v 11.

One key change with Progress Open Edge v11 is that the word "domain" is now a Progress SQL Reserved Word; since "domain" is also the name of a table in EAM, whenever this table is referenced in a SQL query it now must be enclosed in double-quotes.

Prior to this fix the load_eam_domain task would fail with SQL error 10713 Syntax error in SQL statement at or about ".domain".

Metadata
(Financials EE)

QBI-3118

Starting in BI 3.10, all customers will be in the dim_customer_ship_to dimension view. This will ensure the best reporting data possible for Financials EE tables showing customers.

Prior to this fix, some ship to customers were set to 'Unknown'. This change will prevent this from happening in the future when the customer record is anywhere in the table.

For customers who historically loaded financials in BI 3.9 or earlier, unknown customers can only be corrected in the table by truncating the fact table and reloading from the perm.

Metadata
(Financials SE)

QBI-3905

Have addressed a myriad of issues with the history tables and their subsequent snapshot tables.

In the History table, records with a zero balance that are the last version of the record are now flagged as current and have their end date set to the begin date.

As a result of this the snapshot tables picks up the closed order in only one period and not in subsequent periods (which previously had been appearing month after month and year after year, creating an ever growing number of records to process daily).

Metadata
(Inventory)

QBI-2859

The fact_inv_mth_balance will now be populated with proper data in the total_unit_cost_base field when there is no tr_hist record available for a particular item.

 

QBI-3898

This code was reworked to work more efficiently. Customers with large data sets that are finding slowness populating this table may benefit from implementing this changed code.

 

QBI-3899

This logic was finding the appropriate transaction costs for all periods back to the beginning of the Inventory month balance start time on all daily runs even if it only needed to do so for one or two prior months. This code was re-written so that it would only go as far back as is appropriate for the periods necessary for the daily run. This ensures faster run time and less required space and processing power, especially if there is a large number of items in the system.

Metadata
(Multimodule)

QBI-3775

Truncate of stage_date_qad3 added to DAILY/HIST_COMMON_PROCESS.

Truncate of stage_eam_date_qad3 added to DAILY/HIST_EAM_PROCESS.

 

QBI-3871

Changes made to any function that had a varchar or char data type instead of nvarchar. This ensures that Unicode characters can pass through functions and implicit data conversions that cause index usage to fail is avoided.

Metadata
(Order Management)

QBI-3673

In BI 3.9, a few new fields in fact_om_order_history—the scheduled_order_flag, consignment_flag, and ssm_flag fields—are set as Attributes but the EUL flag is N so these are not visible in the Portal.

In BI 3.10, this has been corrected; the EUL flag is Y for these three fields so that they will be visible in the BI Portal.

Metadata
(Purchasing)

QBI-3328

Upgraded date processing logic now includes fact_po_order snapshot records from the current day as well as better managing crossovers between Weekly and Monthly snapshots when (B)oth is selected.

Users upgrading to BI 3.10 can run the OP Upgrade script to wipe out the snapshot table and rebuild it from the history table to see changes.

 

QBI-3576

Corrected the Divide by Zero error in stage_op_transaction1.material_cost_scrap by applying CAST(x AS FLOAT) to operands.

 

QBI-3945

The default value for PO_SNAPSHOT_FREQUENCY is now "M" (for "Monthly"). In previous versions, the default value was "B" for "Both Monthly and Weekly" - if left as "B" when the customer did not really need weekly snapshots the customer could find their snapshot table (a) getting large rapidly and (b) taking longer to process due to the excess weekly snapshots. The default for new installations will now be Monthly so that a customer must make the explicit choice if they want both Weekly and Monthly snapshots (understanding that this will result in a larger table that takes longer to process).

Portal

QBI-3879

Prior versions of the BI Portal did not correctly handle numeric parameters on BI Reports. This has been resolved in BI 3.10.