Saturday, February 13, 2016

Parameters of RSADMINC table

One of important customizing tables in BW is table RSADMINC. The customizing of this table takes place when the BW system is setup for first time. But also during time when the system is operational some parameters need to be maintained. Also entries need to be adjusted in case of BW upgrade.

The table stores basic customizing parameters of the BW system. Depending on installation scenario of the BW system values of parameters are either populated automatically (so called Wizard-Based Basic Configuration for BW ABAP) or if it is not the case than then it is possible to perform all steps manually.

In general you can find a documentation of the table params here. On that page all params that are really needed for BW to function properly are listed. Also there on the page are listed corresponding t-codes where respective params are maintained.


General parameter

CUSTOMIZID                ID for Customizing in BW. For the BW system a value of this param is always BW. Note: 1576461 - Unable to open any Web Application from BI Launchpad


Data Warehousing Workbench related parameters

RSAWBN_HIDE_FUNC     Hide obsolete Functions of the Data Warehousing Workbench
PROTAWBSTART                        Write Log to Application Log when DWB Starts
COL_WARNING              Traffic Light Color in Monitor if Warnings Occurred


Query processing related parameters

SPLT_QRY_TAB_THR      Threshold Value for Query Split, Note: 514907 - Processing complex queries (data mart, and so on)
SPLT_DM_TAB_THR        Threshold for Splitting Data Mart Requests


Analysis Process related parameters

ANPR_SERV                   Application Server for Batch Execution of Analysis Processes
ANPR_SERVTYPE                        Type of Server


Any DB specific related parameters

DB_STATISTICS                        Let BW Generate Database Statistics


Oracle specific related parameters

ORA_LOGGING              Deactivates NOLOGGING while Building Index
ORA_PARALLEL_DEG      Degree of Parallelization during Aggregate and Index Building, Note: 544521 - Controlling the PARALLEL degree


Upload related parameters

INFOIDOCFRQ                Frequency with which status IDocs are sent
IDOCPACKSIZE              Number of Data Records per Package
MONITIMEOUT               Waiting time until traffic light status is changed in the monitor
MDMTBOOKMODE           Update method in master data maintenance


DB Connect source system upload related parameters

DBC_BWSERVER          BW Application Server (as of 6.10) settings for DB Connect customizing settings, Note: 930353 - DB Connect customizing settings
DBC_PACKSIZE             Number of Data Records per Package for DB Connect
DBC_SHOWSIZE                        Number of Data Records with Display Mode


SID generation related parameters

AUTOSID                      Automatic MD ID entry when loading transaction data
RRSITHRESHOLD         Threshold Value: Select Single -> Select for All Entries, Note: 1522691 - Performance Optimization: SID Flag Updates


Flat file format related parameters

EXCEL_ESC                    Field Delimiter for CSV Files
EXCEL_FIELDSEP                        Field separator for csv files


Authorization related parameters

USE_NEW_REPAUTH       Analysis Authorization System, Value NEW means current procedure with analysis authorizations. Note: 1369820 - Analysis authorizations: Select concept
MPRO_CHECK                Use MultiProvider Authorization Object (S_RS_MPRO)
MPRO_CHECK_QUERY     Use MultiProvider Authorization Object in Query
CUBE_CHECK_QUERY     Use Authorization Object InfoCube (Query)


“Display of Numeric Values in the Business Explorer” related parameters

RRXDATADIFF0              Display value for dividing by zero
RRXDATANOTEXIST       Display value for cells with error
RRXDATALARGE             Display value for numeric overflow
RRXDATANOAUTHOR      Display value for cells without authorization


Currency display/conversion related parameters

CURR_CONV                  Currency Conversion for External Systems
RRXDATAMIXCUR                       Display value from various currencies/units or mixed values
RRXSHOWMIXCURVAL    Display value of a cell with mixed currency
TCURF_FAKT                  Indicator: Consider TCURF Ratios in Currency Conversion, Note 531983 - TCURF factors ignored during currency translation


Quantity conversion related parameters

UOM_BUFF_SIZE                        Quantity Conversion: Setting Buffer Size Internal Tables


Hierarchies related parameters

MERGE_APPL                 Hierarchies: Merge with applications, yes/no
MERGE_AREA                 Hierarchies: Merge with InfoArea, yes/no
MERGE_IPG                   Hierarchies: Merge with IPG, yes/no
HIER_ISRCMD                Hierarchies: Use Authorization Object S_RS_ISRCM


PSA related parameters

PSAPARTSIZE                Size of PSA Partition. In case if the highest existing partition has more records than this param specifies new partition is created. Note 771191 - Copying BW objects to new tablespaces
PSA_REQUDEL               Check for Activity 06 during PSA Request Deletion


Attribute Change Run (ATR) related parameters

DELTALIMIT                 Threshold Value (0-99): Delta -> Reconstruct Aggregates, Value 0 means that all the aggregates are always reconstructed (this normally has a negative impact on performance). It is recommended that you start with a value of approximately 20%. Note: 903886 - Hierarchy and attribute change run
BLOCKSIZE                  Block Size for Building Aggregate. Size of block for ATR. If E or F table of aggregate is larger than this parameter, system does not read the source in one go, rather it divides it into blocks. The division into blocks is based on a characteristic, the value range of which is divided into intervals. The system only reads the data from such an interval from the source and writes it to the aggregate. If there is no value of the param default value is 100,000,000 valid for ORACLE. Notes: 903886 - Hierarchy and attribute change run; 646402 - Programs for checking aggregates (as of BW 3.0B SP15)
CR_MAXWAIT                Wait Time for Change Run Lock (in Minutes), Note: 825927 - The BW Changerun: CR_MAXWAIT
LOCKCR                                    Reporting Lock on Change Run. I case of huge volume of data while master data IO activation a DB commit is executed between DELETE and UPDATE operation on data if this param is set to X. This ensures that it doesn’t dump. Note: 1694993 - Consulting: Transactional logs filled during MD activation


BW Web environment related parameters

STYLE_SHEET                Style Sheet for Html Page Generation
TMPLID                         Name of the Web Template for Ad Hoc Analysis (SAP BW 3.x)
PROPERTIESID              Name of Standard Template Properties (SAP BW 3.x)
ITS                               ITS Name for URLs Created by Server for BW Web Reporting; Obsolete in 3.x and 7.x.
WEBSERVICE                 ITS Service for BW Web Reporting URLs created by the server; Obsolete in 3.x and 7.x.
WBID                            Workbook ID for the Standard Web Page; Obsolete in 3.x and 7.x.
PAGEID                         Page Name of the Standard BW Web Template; Obsolete in 3.x and 7.x.
For an overview of web reporting related params see Note: 589947 - Relevant Customizing entries in RSADMINC in Web environment


Web templates related parameters

RSER_TMPL_ID              Standard Template for Enterprise Reporting, Note: 1576461 - Unable to open any Web Application from BI Launchpad
TMPLID_BROADCAST     Standard Web Template for Broadcasting (BW 3.5), Note: 666214 - Enhancement RSADMINC - 'Standard Web Template'
TMPLID_QUERY_BR        Standard Web Template for Query Precalculation (BW 3.5)
TMPLID_DOCUMENTS     Standard Web Template for Document Browser (SAP BW 3.x)
TMPLID_BCAST              Standard Web Template for Broadcasting
TMPLID_BCAST_QUE      Standard Web Template for Query Precalculation
TMPLID_ANALYZER         Name of the Template for Ad Hoc Analysis
TMPLID_BCAST70          Standard Web Template for Broadcaster
TMPLID_BCAST_Q70      Standard Web Template for Query Precalculation
TMPLID_BCAST_REP       Standard Web Template for Report Precalculation
TEMPL_PARAM               Name of Standard Template Settings


Broadcasts related parameters

BCAST_SUPP_FOOT        Broadcasting: Suppress Footer in E-mail
BCAST_MAIL_EXP          Number of Days Until Send Requests Are Deleted


OLAP: Cache related parameters

INACTIVE                      Cross-transactional cache is deactivated
MAX_LCS_MB                 Local Cache Size
MAX_GCS_MB                Global Cache Size
PERSISTMODE               Cache Persistence Mode
FILENAME                      Flat File Name
FILENAME_SPAN             Comprehensive Flat File Name for AppServer
LIMIT                            Database Cache Limit
CLUSTER_LIMIT             Size Limit for Clustering


HANA related parameters

RS2HANA_PACKAGE       SAP HANA Content Package for HANA Views
RS2HANA_ASSIGN_TYPE            Privileges assignment type
RS2HANA_DBMS_USER_MAPPING            SAP BW user to SAP HANA user mapping option


Other parameters

Most of these parameters is not used any more in modern BW systems (7.x + versions).
SRCSYST_USER             User in source system for ALE communication
COL_NODATA                Traffic-light color in monitor if no data in source system
CHAR1000                     Thousand separator
DECIMALCHAR               Character for decimal point
GANTT_MIN_LENGTH      Length of horizontal bar in Gantt chart
MSGPOPUP                    Message Long Text As Dialog Box
MONITORASSI               Indicator for standard default starting of the wizard
SRVNAME                      Data element for MD server name
RFCOLAPDEST               RSDP: data tp encapsulating RFC destination to work with
MSASEXIST                   RSDP: Data element for storing info if MS AS2000 can be used
TECHNAME                     RSDP: Data element for technical names
LOCALBORURL               Drag & Relate (D&R) Links for BW Unifier
WP3DEST                      Destination of URL Generation Server
WEBPROTOCOL              Web Protocol for BW Web Reporting URLs Created by Server, Note: 961142 - HTTP or HTTPS protocol when you jump to a 6.40 system
ISETHUGEWHERE                       InfoSet: Limit Value for Large Where Conditions, Note: 673575 - InfoSet: Long running program - SAPSQL_STMNT_TOO_LARGE
EP50_MENU                   Hide Menu 'Publish to Enterprise Portal 5.0'
MHTML_AS_ATTACH       Send MHTML Documents by E-Mail As Attachments
ER_STYLESHEET             Stylesheet for Exception Reporting (Path in MIME Repository)
SOBI_RFC_DEST                        RFC Destination for BW Model Generation
ASYNCHR_DELETION      Asynchronous Deletion from Write-Optimized DSOs


Related post:

Thursday, February 11, 2016

ABAP Tools Menu

I recently found one interesting transaction. It has very curious name thought. It is called AMEN - ABAP Tools Menu. It may be useful for ABAP programmers as it servers as central point to run few not very known ABAP tools. User interface of the code looks really prehistoric (created on 27.08.2002) however it is still intuitive. Whichever tool one would want to run it just needs to double click on respective line.

Following tools are available in the t-code AMEN:

General tools:
SYNT            Syntax Trace Analysis on Program Check
SAMT            ABAP Program Set Processing
SCI               SAP Code Inspector
SCOV            Coverage Analyzer

Verification tools:
UCCHECK       Unicode Check with Long Text
SLIN             ABAP Program Extended Syntax Check
SM31            Maintenance view for table T100 Message Maintenance
SE30             Runtime Analysis (replaced by tcode SAT)
RSHOWTIM    Runtime of ABAP Objects Statements
SE33             Context Builder

RABAX Texts:
RSNAPDOK    Maintenance view for table SNAPT – ABAP Runtime Errors
SM31            Maintain Syntax Error Messages

BSP Display Tools:
BSP_SHOW_SOURCE Display Page Source Display (Internal/External)

Syntax Diagrams:

RSXBNFDP     Display Syntax Diagrams for Keyword

Saturday, February 6, 2016

Law of Personal Data Protection in SAP BW

By default SAP BW provides logging capabilities of data access. Means all users access to data can be logged and evaluated from security and audit point of view. For regular usage of system usually this is enough. Some countries are requiring IT systems to fulfill their own rules while processing personal data. One of example is Spain which few years back introduced so call Ley Orgánica de Protección de Datos de Carácter Personal (LOPD) law.

As BW is one of systems that can store personal information; SAP had to provide capabilities within the SAP BW system to adhere the law. This resulted in introduction of LOPD Access Logging in Reporting and Planning Applications as feature of the SAP BW and/or SAP NetWeaver.

The LOPD feature involves logging all access to sensitive personal data stored in SAP BW. Technically it is delivered via BADI RSEC_LEGAL_AUDIT_SAP. By implementing mentioned BADI the LOPD feature is enabled. As next steps particular InfoProviders which store personal data need to be customized as LOPD relevant via customizing table RSECLOPDIP. Once these things are setup system collects the LOPD relevant data.


Useful information:

933441 - Frequently asked questions on BW 7.0 and data protection

BW Workspace

Similarly as field based modeling BW Workspace aims to enable rapid modeling in SAP BW environment. It addresses gaps usually occurring during the BW implementation and application maintenance projects where conflicts between IT teams and power users from business departments are occurring. The IT department maintains and governs BW data models centrally. Every change requested goes under usually strictly defined change management process and in the end it is not delivered at speed the business department would want. The business is changed rapidly and to be able to react on market changes the business people need to have agile processes in place to address these changes in their IT systems.

The BW Workspace can help the business departments with its kind of a sandbox space where they can create data models for ad-hoc scenarios. Creation of these is supported by tools which allow combine centrally developed BW data objects (by IT) with locally created objects (InfoProviders) by business users. So called locally created objects are usually based on flat files data, data from existing BEx Queries or DataSources. The sandbox in these terms is called as Workspace and is managed by IT department however the Workspace can be used by business which means also then can create new objects within the workspace.  

Usually within the BW Workspace there are three types of users: Admin which defines workspace and data scope in it. Developer role has an access to use the workspace created by admin. The developer or let’s say designer can create a data model to support reporting as per needs. Finally End User has an access to providers created in workspace and the queries / dashboards based on them.

Prerequisites for using BW Workspace are as follows:
·         SAP NetWeaver BW 7.30 SP1 or higher
·         Workspace ABAP AddOn for BW7.30 (includes ABAP WebDynpro application)
·         SAP NetWeaver BWA 7.20 or SAP HANA 1.0 SP05 – the BW Workspace doesn’t work on system where neither HANA nor BWA is available.
·         For users (like developer and end user) who will work with BW Workspace object an Active Component Framework (ACF) needs to be installed on their machines (ACF712SP00_47-20006190)

Following ICF services are required to be activated for the BW Workspace Designer application (Web Dynpro application). They need to be enabled via t-code SICF:
·         RSL_UI_MY_WORKSPACE
·         RSL_UI_CREATE_COPR
·         RSL_UI_CREATE_PROVIDER
·         RSL_UI_CHANGE_WORKSPACE
·         RSL_UI_CHANGE_QUERIES

For more details on the BW Workspaces configuration see here.

Admin part: means creation of new workspaces objects takes place in SAP GUI in t-code RSWSP or RSWSPW. Here a central provider(s) can be assigned to the workspace. Also other options are available here like maintaining properties of the workspace, checking of data and status of Local (Composite) Providers, maintain users who are allowed with particular workspace, etc. Notice that technical names of tech name of e.g. CompositeProviders always starts with "@3".

Developer/designer part: activities here happen in web dynpro application that can be launched via t-code NWBC from SAP GUI. Users here can create or enhance new or existing models for data analysis. New InfoProviders (Local Provider / Local Composite Provider / Local Characteristics) can be created here. In case of the Composite Provider e.g. local data can be mashed up with data in BW’s classic InfoProviders using union or join.

User part:  here user is in usually reporting front end tool like BEx Query Analyzer or newer 
SAP Analysis Office for Excel (AO) where user just runs BW queries as usual.


Useful links:

SMP component: BW-BEX-OT-WSP BW Workspace

Active Component Framework

A SAP component which is responsible for integration of active components in web based user interfaces of SAP is called Active Component Framework (ACF). It enables usage of technologies like Adobe Forms or MS Office components in SAP technology like WebDynpro.

Implementation of the ACF contains ActiveX controls, JavaBeans, and applets that run in Web browsers or in SAP NetWeaver Business Client (NWBC). What the ACF does is to provide services to process mass data while fetching the data from the backend and reset modified data state), displaying data in-place or outside a browser or the NWBC, integrating components in the Web Dynpro programming model (data binding, event handling), keeping the status of a component when a new page is loaded.

Web Dynpro ABAP (WD4A) provides the following ACF based UI elements for developers of user interfaces: Gantt, Network, OfficeControl, InteractiveForm, AcfExecute, AcfUpDownload, FlashIsland, SilverlightIsland and ActiveX.

Technically the AFC is installed with SAP GUI. However it can be also download from SAP SMP via support.sap.com/patches -> "Browse our Download Catalog" -> "SAP Technology Components" -> "ACF" -> Download the latest available ACF patch. Also see following SAP Notes for the same.

766191 - Installation of Active Component Framework
891202 - Installing Active Component Framework for NW04S SP04

In closing words I need to say that as whole software world is moving to light wave option of HTML5 based UIs also SAP is shifting away from UIs based on such an active components. SAP is heavily investing in their Fiori based UI.

Useful links:
846952 - Erase ACF from client PC

1150277 - Prerequisites for using ACF

Friday, February 5, 2016

How to check whether HANA or BWA are available?

Some time back I wrote two posts regarding how to find whether SAP NetWeaver system is HANA DB based and how to find BWA version. Here I’m going bit further on same topic and I introduce another small ABAP code snippet. 
This time it is about how to check on both whether the HANA and/or BWA are available in the system.



REPORT ZMM_HANA_BWA_CHECK.

* via class's attr - this is preferable way
IF cl_rs_utilities=>n_is_hdb_system = rs_c_false.
  WRITE: / 'no hana'.
ELSE.
  WRITE: / 'hana in place'.
ENDIF.

* via class's method
IF cl_rs_utilities=>is_hdb_system( ) = rs_c_false.
  WRITE: / 'no HANA'.
ELSE.
  WRITE: / 'HANA in place'.
ENDIF.

* via class's method
IF cl_rsddtrex_core=>get_trex_rfc_dest( ) IS INITIAL.
  WRITE: / 'no BWA'.
ELSE.
  WRITE: / 'BWA in place'.
ENDIF.

Source code available at: github.com/softy12/ZMM_HANA_BWA_CHECK  

Related posts:


Tuesday, February 2, 2016

BEx Query where used program

An ABAP program I’m writing about originated in one requirement I had today. I needed to evaluate where a bunch of BEx queries are being used. Place where particular BEx query can be used comprises of: workbooks, web templates, query views, broadcast setting, BW transformation etc.


As I had bunch of the queries to evaluate I wrote simple ABAP report which extracted “where used” information for me. Here I’m posting a fragment of my program which does the thing. A list of where used objects are provided in internal table lt_where_used.



REPORT zmm_bex_query_where_used.
 
PARAMETERS: p_compid TYPE rszcompid,
            p_obv    TYPE rszhelp-objvers OBLIGATORY DEFAULT 'A'.
 
DATA:  lv_compuid         TYPE rsz_uid,
       lt_where_used_info TYPE rzd1_t_where_used_info.
 
SELECT SINGLE compuid FROM rsrrepdir INTO lv_compuid WHERE objvers = 'ACT' AND compid EQ p_compid.
 
CALL FUNCTION 'RSZ_DB_COMP_WHERE_USED'
  EXPORTING
    i_compuid           = lv_compuid
    i_objvers           = p_obv
  IMPORTING
    e_t_where_used_info = lt_where_used_info.

Source code available at: github.com/softy12/BEX_QUERY_WHERE_USED

Monday, February 1, 2016

Deletion of BEx workbooks

Sometimes during cleanup or maintenance activities there are many obsolete workbooks found in the BW systems. Even in case just one orphaned workbooks is found that was linked to query which was just test query such workbook needs to be deleted. In best case we ask user who created the workbook to delete. But in case when user left organization long time back someone else needs to step in and delete the workbook.

The question is how to perform it. We can do it in following ways:

1. Function module RRMX_WORKBOOKS_DELETE run it in tcode SE37 and provide following input parameters:

I_WORKBOOKID                 
I_OBJVERS                       A
I_PERSONALIZED_WORKBOOK         R

Notice that there are no any messages neither return code returned by the FM. In case deletion is successful there are no output parameters at all.



2. T-code RSZDELETE: In this case also query on which the workbook is originated is deleted. On selection screen provide report technical ID and thick off “Workbooks” check box.

On next screen select DELETE checkbox for corresponding query:

Once it is finished following confirmation popup is displayed: