www.ibm.com/docs/en/filenet-p8-platform/5.5.x?topic=analyzer-as-analysis-tool
IBM Case Analyzer services can use OLAP (online analytical processing). This is configured as an optional OLAP integration; the IBM Case Analyzer CASTORE must then be hosted on a Microsoft SQL Server database.
Enabling OLAP Integration
If OLAP integration is enabled, the IBM FileNet Content Platform Engine calls the IBM Case Analyzer SSAS Connector to perform cube processing. The IBM Case Analyzer SSAS Connector communicates with the Microsoft SQL Server Analysis Services (SSAS) cube processing system and then builds the OLAP cubes, which are stored in the Case Analyzer OLAP database and used for Cognos Business Intelligence reports or Microsoft Excel charts.
The following Microsoft URLs describe the installation of Microsoft SQL Server Analysis Services:
In SqlServer Query Analyzer, a new table view can be created in the cube database, VMAEDM, to utilize an existing date dimension as the basis of the calculation:
CREATE VIEW dbo.DMDaysIn_Workflow AS
SELECT
TOP 100 PERCENT DATEDIFF([day], ReceivedDate, { fn NOW() }) AS DaysIn,
ReceivedDate_key
FROM dbo.D_DMDataField_ReceivedDate
WHERE (ReceivedDate <> ”)
ORDER BY DaysIn
This uses the DateDiff function to calculate the number of days from the current date (from the { fn NOW() } function) that the case data has been received (from the ReceivedDate Dimension field).
This can then be used to display the counts of cases in each of the calculated day “slots.”
Dynamic Dimensions for Aging Bands
The procedure used to create the simple calculated Dimension earlier can be extended to create a “range” Dimension to allow the display of counts for ranges of dates, for example, in bands, for example, Today, ‘+ 1 Day’, ‘+ 2 Days’, ‘+ 3 Days’, ‘+ 4 Days’, ‘+ 5 Days’, ‘+ 6 Days’, ‘1 – 2 Weeks’, ‘2 – 3 Weeks’, ‘3 – 4 Weeks’, ‘4 – 5 Weeks’, ‘>= 5 Weeks’.
CREATE VIEW dbo.DMAgeing_Workflow AS
SELECT [AgeBand] = CASE
WHEN DATEDIFF([hour], ReceivedDate, { fn NOW() }) < 24 THEN ‘Today’
WHEN DATEDIFF([hour], ReceivedDate, { fn NOW() }) Between 24 and 47 THEN ‘+ 1 Day’
WHEN DATEDIFF([hour], ReceivedDate, { fn NOW() }) Between 48 and 71 THEN ‘+ 2 Days’
WHEN DATEDIFF([hour], ReceivedDate, { fn NOW() }) Between 72 and 95 THEN ‘+ 3 Days’
WHEN DATEDIFF([hour], ReceivedDate, { fn NOW() }) Between 96 and 119 THEN ‘+ 4 Days’
WHEN DATEDIFF([hour], ReceivedDate, { fn NOW() }) Between 120 and 143 THEN ‘+ 5 Days’
WHEN DATEDIFF([hour], ReceivedDate, { fn NOW() }) Between 144 and 167 THEN ‘+ 6 Days’
WHEN DATEDIFF([hour], ReceivedDate, { fn NOW() }) Between 168 and 335 THEN ‘1 – 2 Weeks’
WHEN DATEDIFF([hour], ReceivedDate, { fn NOW() }) Between 336 and 503 THEN ‘2 – 3 Weeks’
WHEN DATEDIFF([hour], ReceivedDate, { fn NOW() }) Between 504 and 671 THEN ‘3 – 4 Weeks’
WHEN DATEDIFF([hour], ReceivedDate, { fn NOW() }) Between 672 and 839 THEN ‘4 – 5 Weeks’
ELSE ‘>= 5 Weeks’
, ReceivedDate_key
FROM dbo.D_DMDataField_ReceivedDate
WHERE (ReceivedDate <> ”)
This can then be used to display the counts of cases in each of the calculated aging bands.
Leave a Reply