Skip to Content
Author's profile photo Former Member

BW & BI Comprehension

Following are the angles that we commonly encounter in SAP system, at the time of maintenance in particular…


1. Table space full… table level analysis

Issue Example – Several table spaces are over 80% full.
It’d be better to check whether it’s possible to do tablespace clean-up, before extending it.
   For table EDIDS:
      IDocs should be archived then delete.
      The program RSEXARCD cannot delete IDocs if they are not archived.
      IDocs can be archived using the program RSEXARCA.
   In addition,
      delete IDoc links,
      delete entries in table BDSER- (Serialization Time: Last Date at Sender for Each Object),
      delete table entries in audit database (t-code BDM9)
   Extra Hints –
      BALDAT – application log data table. 
      BALHDR – is header table.
      RSDDSTATAGGRDEF table – Statistics data OLAP: Navigation step / aggregate definition

2. Message Type X dump – InfoPackage
Issue Example – Message Type X dump when trying to open the info package with a dump in RSM1_CHECK_FOR_DELTAUPD
Hint –
OSS note: 852443
   In BW system the init condition values are stored in tables RSSDLINIT and RSSDLINITSEL.
   In SAP R/3, the init condition values are stored in tables ROOSPRMSF and ROOSPRMSC.
Upon deletion of these entries from the aforementioned tables will release the infopackage for edit – step. We can then set a new init / use the same IP for data load.

3. ACR Termination in BW 3.x

Issue Example – Terminated change run affects other ACR / Roll-up jobs
When any attribute change run (ACR) job gets failed / disturbed, the flag in the table – RSDDAGGRMODSTATE (field name = CLOSEDFL), will not be cleared. This flag is generated in this table for the yet to / currently running ACRs.
In such cases in BW 3.x systems, upon termination, any further ACRs or roll-up jobs will not run and will fail, as the lock entry set is not released for new jobs.
To avoid such situation we got to clear this flag in the above said table. To do so, just execute the below function module.
rsdds_ aggr_ mod _close
This function module will clear the locked flag entries and will allow further ACR / Roll-up jobs to complete.
Hint –
   Use func. Mod. – rsdds_ aggr_ mod _open, if in case a manual (explicit) flag set is necessary.
   Use func. Mod. – RSDDS_AGGR_MOD_STATE_GET, which The function module determines whether a Changerun runs and provides the result upon indicating which characteristics and hierarchies are concerned.
4. Alternate TCODE for Selective Deletion

It’d be better to use the TCODE – delete_facts, rather than getting into the manage screen of each DSO / Info cube for the below reasons –
      a. No need to navigate more screens
      b. One place stop for selection condition / job schedule
      c. Option to take source code selection and edit the selective deletion
      d. Option to generate a selective deletion program for background schedule
(in process chain for example)
 Hint –
      Alternate SE38 program for this TCODE is – RSDRD_DELETE_FACTS, in case of authorization restrict.

5. Removing ‘#’ in BEx Analyzer (Report)

The macro code –
  Sub SAPBEXonRefresh(queryID As String, resultArea As Range)
  If queryID = “SAPBEXq0001” Then
   ‘Remove ‘#’
   Selection.Cells.Replace What:=”#”, Replacement:=””, LookAt:=xlWhole, _ SearchOrder:=xlByRows, MatchCase:=False, MatchByte:=True
   ‘Remove ‘Not assigned’
   Selection.Cells.Replace What:=”Not assigned”, Replacement:=””, LookAt:=xlWhole, _ SearchOrder:=xlByRows, MatchCase:=False, MatchByte:=True
   End If
   ‘ Set focus back to top of results
   resultArea(1, 1).Select
   End Sub

Assigned Tags

      1 Comment
      You must be Logged on to comment or reply to a post.
      Author's profile photo Gajesh Nagesh
      Gajesh Nagesh
      Thanks, this blog was realy helpful