2164519 - RSHDB: SAP HANA Tools 07 for BW

Symptom

This note contains corrections and new developments for the classes and programs in package RSHDB, needed for integration issues of HANA DB into BW systems.

Other Terms

SAP HANA, inconsistency, partitioning, classification, landscape reorg, scale out, RSDU_TABLE_CONSISTENCY

Reason and Prerequisites

This note is applicable for SAP BW systems with the releases:

• SAP BW 7.50 Support Package 01
• SAP BW 7.40 Support Package 05 (SP 08 needed for ADSO functions)
• SAP BW 7.31 Support Package 06
• SAP BW 7.30 Support Package 08

Solution

IMPORTANT: You must implement SAP Note 2163258 before implementing this SAP Note
Important features and corrections delivered with this note are:

• FIX: Short dump in compression check scenario of RSDU_TABLE_CONSISTENCY due to a type mismatch
• NEW: BW specific implementations for future consistency checks
• NEW: Regard ADSO tables for consistency check
• FIX: Exclude tables from ODSO without infoobject from RSDU_TABLE_CONSISTENCY partition spec scenario
• NEW: interface IF_SHDB_APPL_INFO~DDSTORAGE() implemented
• FIX: avoid SQL error due to additional columns in P-dimension-tables
• NEW: full functionality of SelectionTables in table selection of the report RSDU_TABLE_CONSISTENCY
• NEW: unified interfaces for handling ADSO tables e.g. for SMIGR_CREATE_DDL
• FIX: Avoid processing non-BW-tables by RSDU_TABLE_CONSISTENCY
• FIX: detect needless E-fact-tables of flat infocubes and remove them (version 07)
• FIX: more reliable results for consistency checks on ADSO tables - relevant for 7.40 SP09-13 only (version 9)
• FIX: regard XXL-Attribute tables as InfoObjects with subtype "C" in table classification (version 10)
• FIX: usage of RSDU_TABLE_CONSISTENCY: TableLocation & Partition Number Check usable without EXPERT option (version 10)

Remarks:

1. For the usage of RSDU_TABLE_CONSISTENCY refer the PDF documentation delivered with note 1937062, please.
   
2. Before you start any note implementation, please refer note 1668882 concerning the transaction SNOTE, too.
   
3. In some cases an error occurs during activation of the note: "CL_LIB_ITER Method CONSTRUCTOR has already been declared". This error can be eliminated as follows:
   1. Cancel the activation 
   2. Open a new SAPGUI mode 
   3. Call transaction SE24 and enter the object name "CL_LIB_ITER". 
   4. Activate the object (CTRL-F3)
      Now, the error should not occur again.