Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

On this page:

Summary: CAST AIP 8.3.16 introduces a number of features and changes as listed below. To view the impacts of these changes on analysis results, see: Changes in results post upgrade.

CAST Database Extractor

The CAST Database Extractor now supports:

  • (by reference) the extraction of schemas on Oracle 18c and above in line with Oracle's updated release cycle, however the extractor will handle the schemas as Oracle 12c schemas and no new syntax or features introduced in these newer releases is supported. 
  • Case sensitive passwords (introduced in Oracle 12c R2).

SAP / ABAP rules

"CX_ROOT" should not be used in TRY .. CATCH.. ENDTRY block (8412) 

The parent technical criterion for this rule was incorrectly set to "61020: Programming Practices - Modularity and OO Encapsulation Conformity", but it has been changed to "61014: Programming Practices - Error and Exception Handling". See also Changes in results post upgrade - 8.3.16.

Dynamic Links rule files

Dynamic Links rule files now function with SAP BusinessObjects and SAP PowerBuilder analysis results.

Changes to the structure of the Dashboard and Analysis Services schemas

Some changes have been made to the structure of the Dashboard and Analysis Service schemas to reduce the potential size of the Dashboard Service schema tables DSS_LINKS and DSS_LINK_INFO:

Data (links with IDs from 11000 to 110006) related to CAST Transaction Configuration Center datafunctions and transactions that was previously stored in these two tables will now be stored in a new table called FP_LINK_INFO. This table now contains all object details of transactions/datafunctions. It has exactly the same structure as DSS_LINK_INFO:

SNAPSHOT_IDthe snapshot id
PREVIOUS_OBJECT_IDdatafunction or transaction
LINK_TYPE_IDbetween 11000 and 11006
NEXT_OBJECT_IDdetail object of a transaction/datafunction

Impact on Analysis Services schema

Details of transactions and data functions are now sent to a new table called DSS_FPLINKS instead of previously DSS_LINKS.

Transfer from Analysis to Dashboard Service schema

The links from local database from DSS_FPLINKS are sent to central Database via DSS_IN_FPLINKS instead of previously DSS_IN_LINKS

CENTRAL DATABASE

finally the information related to details of transactions and data function are stored in FP_LINK_INFO instead of previously DSS_LINK_INFO.

MIGRATION

when migrating to this version, all occurrence of link_type_id between 11000 and 11006 will be

  • Moved from DSS_LINK_INFO to FP_LINK_INFO
  • Removed from both DSS_LINK_INFO and DSS_LINKS
  • No labels