Support Specifics

Contents

• Introduction
• Support Specifics
  • LCS Support Queue
  • Single Patches
  • Single Patch Handling - LCS Bug Example

Introduction

This section called 'Analysis Models - Support and Upgrade Process' gives information and guidelines related to the support and upgrade process of the Analysis Models.

Note: The Analysis Models were formerly known as IFS BI Analysis Package.

Note: Related example content in the Analysis Models and IFS BI Analysis Package, such as SSRS and Power BI reports, are not supported.

Support Specifics

An Analysis models bug is handling in the following way in LCS.

LCS Support Queue

Cases should be entered in LCS in the Business Intelligence with Business Analytics queue.

Single Patches

Single patches are distributed as bug corrections that will be documented by the BI team and made available in LCS together with modified files. The attached bug documentation will describe changes that have been made to affected files.

Single Patch Handling - LCS Bug Example

Bug Description
Symptom: Activity descriptions are truncated in the Procurement cube.

Correction Description: The Activity_Description of the dimension DIM_ACTIVITY, in the Procurement cube, is too short. It needs to be increased from 200 to 300 characters.

Components: PCSUPC, PROJDI

Actions

In PROJDI do the following:

Table changes

• Increase the length of ACTIVITY_DESCRIPTION to 300 in dbo.Dm_DIM_ACTIVITY.sql
• Increase the length of ACTIVITY_DESCRIPTION to 300 in dbo.IFSAppl_DIM_ACTIVITY.sql
  
• Increase the length of ACTIVITY_DESCRIPTION to 300 in dbo.Dw_DIM_ACTIVITY.sql
  
• Increase the length of ACTIVITY_DESCRIPTION to 300 in dbo.Dm_DIM_ACTIVITY_TEMP.sql

SSIS changes

• Make sure that the meta data for ACTIVITY_DESCRIPTION is defined with the length of 300 characters in:
  • 1.1.002 Load IFSAppl_DIM_ACTIVITY_BI.dtsx
  • 2.1.002 Load Dw_DIM_ACTIVITY.dtsx
  • 3.1.002 Load Dm_DIM_ACTIVITY.dtsx
• Cube changes (SSAS)
• In PCSUPC do the following:
  • Increase the length of Activity_Descr to 300 in ACTIVITY.dim
• Process the cube to see that the modification has taken effect.

Note: These corrections must handled according to the circumstances in the customer environments with manual deployment if necessary.