How to calculate the total amount before and after aggregation?

Product name, quantity and amount
defining the formula at local level

Total amount= product quantity x amount

It will give out put like means total amount not yet aggregated it is giving product quantity x product price = total amount

Now report output but achievement total amount should be aggregated value.

Creating global level calculated key figure

Creating KF at Global level

Here not using exception aggregation

This Total amount KF defined at global level

global level calculated KF will appear the calculation after aggregation

Output should be below report

After un check the calculation after aggregation means before aggregation it will give total aggregated total amount value.

Output of the report now showing total amount was aggregated

Now report out put total amount is given aggregated value.

hope it will help beginners.

How to utilize Exception Aggregation using BEx Query Designer.

Exception  aggregation can be used to derive additional information out of a limited number of Key Figures provided in the InfoCube that is to be analyzed.
Thereby, you can create Calculated Key Figures by using a formula that uses exception aggregation itself (this is a nested exception aggregation). Furthermore, it is possible to use Calculated Key Figures created on cell level (using the cell editor) with the new functions of exception aggregation.

Example: If a sales manager wants to analyze the number of materials sold and the average number of different materials sold to different customers for each sales month. In the sales InfoCube, only a Key Figure of the Sales Volume in EUR for the different sold materials is provided.  Using the functions for exception aggregation,  he can derive the additionally required two Key Figures just from the sales volume in EUR for sold materials.

Procedure: To define an exception aggregation for the example above, the following steps are performed

1.  You create a Query that contains the Characteristics "Sold-to Party" (Customer) and "Material" in the free Characteristics, the characteristics

      "Cal. year/ month" in the rows and the Key Figure "Sales Volume EUR"

2. In the next step, you define a new formula ("Different materials"), which simply includes the Query Key Figure "Sales Volume in EUR" (no operator       required in this example).

Then you access the properties of this formula and choose the exception aggregation setting "count all values<> 0" for the reference Characteristic "Material".  In this way, you have defined a counter for your sold materials derived from the Key Figure "Sales Volume in EUR". You have simply counted

the number of occurrences of "Sales Volume in EUR" to give you the new Key Figure 'Different Materials'.

3. Now you will nest the exceptions: You are now able to count the number of materials sold in each month for all customers using the step above, but you want to know what the average number of materials the customers bought in each month. To achieve this, you must define another formula   ("Avg. sold materials/ customers"), which simply refers to the first formula. Again no other operators are required. You access the properties of the second formula and choose the exception aggregation "Average of all Values" for the reference Characteristic "Sold-to Party". The Key point here is that the results of the first aggregation are further processed by the second aggregation.

4. Check your query by performing a validity check to know if your query is correct or not.

5. Save your Query with a description and a technical name and then click on execute to see how exception aggregation works.

There are situations when there is a need to make a restriction on a characteristic with its compounding characteristic. I will try to explain the problem with an example, mention about the SAP Note related with this problem and propose a shortcut solution for this problem.

Problem Definition:

Suppose we have a characteristics ZDUMMY_PA (Personnel Area) and ZDUMMYPSA (Personel Sub Area). ZDUMMY_PA is the compounding characteristic of ZDUMMY_PSA. We have data such as:

We have an infoprovider using these two characteristics. We have a query where we make a restriction on ZDUMMY_PA. We want to restrict the Sub Areas: 100 from A area and 200 from C area. In the query when we drag A/100 for the restriction, only 100 is dragged and all personnel areas related with 100 are included in the restriction as seen below:

An overview on SAP Note related with this problem:

The SAP Note: 541253 describes this situation and proposes a solution. However, this solution is not suitable for the requirement described above. The note suggests restricting the compounded infoobject. When we do that in this case, we have to restrict A and C for personnel area and 100 and 200 for personnel subarea. Then in the report we will see all 100 and 200 subareas belonging to A and C. That is; even if we don’t want to show A/200, it will be shown in the report.

Solution approach for the problem:

The shortcut solution I suggest will be defining a new attribute to Personnel Subarea characteristic. For this aim, we define a new characteristic with data type char 8 (8 comes from the total number of characters defined in personnel area and personnel subarea. In our example, personnel area is defined as char 4 and personnel subarea is also defined as char 4).

We add this new characteristic as the attribute of personnel sub area: ZDUMMYPSA.

In the transformation for master data we add personnel area and subarea to source fields list and select rule type as routine:

We write a small routine to update ZDUMMYCH:

  CONCATENATE SOURCE_FIELDS_RULE-/BIC/ZDUMMY_PA
  SOURCE_FIELDS_RULE-/BIC/ZDUMMYPSA   INTO RESULT.

In this part, we may give any other character in between the personnel and subarea. I generally use '/' sign in between.

This kind of approach may become a must in some situations. For example if we had personnel_areas such as A and A1 and subarea

such as 100 and 00, when we concatenate there will be one concatenated value for two different personnel area - subareas: A100.

Then it will mislead the report when filtered. For sake of simplicity in this blog I go with direct assignment without any character in between.

After we load and activate master data we see the master data as:

Now we need to add ZDUMMYCH to the navigation attributes of the infoprovider. Then in the query designer we can add ZDUMMYCH to the characteristic restrictions pane and we can easily select ZDUMMYCH to filter with our desired restrictions:

As a result, with some modeling changes in both characteristic and the infoprovider, we can achieve to see the desired results. I hope it gives an idea.

Yasemin Uluturk

Hi Friends,

Here is the blog which drives to write this blog Restricting a Characteristic With Its Compounding Characteristic.. Thanks Yasemin ULUTURK

Above blog has greatly explained an approach how to overcome issue which arise while restricting characteristic which is compounded with another characteristic.

To do above approach we need to do modelling changes by writing routine at Transformation level and enable navigational attribute at Infocube level. Then transporting whole flow to production system. It may difficult some times to transports in big clients.

Here I am providing another additional approach to get same results.

Let’s see the approach

Here I am considering Storage location and Plant as Scenario to explain method.

Find the data for our scenario:

Here user wants to exclude Storage location of 0088 of plant 1000. If I simply exclude storage location 0088, then I will lose data of storage location 0088 belongs to  plant 1001 also. This shouldn't happen.

To overcome this issue , I am providing another approach which can achieve directly at BEx level  without  doing modelling changes. All we need do some workaround at BEx level by creating Selections and formulas logically.

I restricted Closing stock with  Storage location 0088 of plant 1000. (KF2)

Then created another KF with restricting Closing Stock KF with only Plant 1000.(KF1)

Then create formula by subtracting KF2 from KF1.

Finally we got closing stock of plant 1000, after deducting stock belongs to  Storage location 0088 of plant 1000.

Here find stock of plant 1001 and user doesn't want to exclude any storage location. So simply restricted Stock with plant 1001.

Thanks for reading this article and hope it helps you.

Best Wishes,

Vijay

Purpose: Find unused InfoObjects which are available in any Infoprovider (Multiprovider,InfoCube and DSO),

                 and NOT used in any report which are built on provided infoprovider.

Step 1 : Run Given ABAP program and provide Infoprovider name as shown in below screenshot.

Note: Unused  infoobjects  means,  which are available in infoprovider but not used in any report which are built on given infoprovider.

Step 2 : ABAP program finds the unused InfoObjects and list in ALV output , as shown in below screenshot.

ABAP Code.

Dear Followers,

Over the past weeks we are seeing many incidents being opened by BI Java customers which upgraded their portal systems to Netweaver 7.30 SPS 09, 10 and 11, NW 7.31 SPS 09, 10 and 11 and NW 7.40 SPS 04, 05 and 06.

The cause for the issue is a missing .jar file (urbrowser) on EP-BASIS SCA, because of a regression caused by SAP Note 1972506.

Our development team has already delivered two notes with the corrections for this:

1995970 - Missing urbrowser.jar caused an exception com.sapportals.portal.useragent.UserAgentSetException
2000082 - Runtime Exception when trying to add new user agent string

Please refer to these notes on which patch contains the corrections for the relevant NW Portal version you are using.

We hope with these new patches the issue is completely solved now.

Kind Regards,
Marcio

Creating Authorization in BW System

Steps for creating authorization

RSD1-To maintain info object authorization relevant.

PFCG – To maintain roles

RSECADMIN – To maintain analysis authorization and role assignment to user

1. Make a variable authorization relevant.

2. Create roles.

3. Create BI Analysis Authorization.

1. Make a variable authorization relevant

Go to RSA1 select info object target and go to business Explorer and check the box for authorization relevant 

2. Create BI Analysis Authorization

Use transaction RSECADMIN

Select AUTHORIZATION Tab

Select MAINTENANCE

Give the name for the authorization and click create

Give the short text

Below characteristics are mandatory while creating authorization object.

1. 0TCAACTVT: This characteristic handles the general activity like create, change, display etc.

2. 0TCAVALID: This characteristic handles the authorization for Info Provider by default it gives access to all the Info Providers i.e. full access. We can restrict authorizations for particular Info Providers using this characteristic.

3. 0TCAVALID:  This characteristic handles the validity of an authorization. Always valid (*) is set as the default for validity. You can restrict this validity. You can also specify a single value or an interval.

Insert new row and add the dimension and give a value

1. For giving values double click the intervals cell

Add a row and give the value depending upon the requirement

Save the authorization

3. Creating the role

Select user tab

Select Role maintenance

Give the role name and select either single role or composite role (in my case I selected single role)

Select menu tab

Select transaction

Give the transaction to be allowed

Ex- RSRT – Query monitor

Select Authorization Tab

Add the authorization created to S_RS_AUTH

Generate then Save

Select the user tab

Add the users which has the role

Then do user comparison

Creating Authorization variable

Open query designer

Creating authorizing variable

In Query Designer Put the authorization variable under filter panel.

Checking the authorization

Go to the analysis tab -> select execute as -> give the user (EX – RETUSER1) -> select with log

Select start transaction -> select the authorization query -> execute

Then run as the user to which role was assign then run the query

Query display as HTML

Now check the below out only for the RUKSHAYA

Thanks,

Phani.

To find the KPI's (CKF, RKF,Formula) where used in Bex queries.

Access required to SE11/SE16, SE37.

Views - V_COMPDIR_COMPIC

Steps to Follow

1. Go to SE11/SE16
2. Enter the View Name - V_COMPDIR_COMPIC

3.Select a Definition type of an Element with A version, I am selecting  RKF here.

4. Execute and get the COMPUID .

5. Go to SE37 , use the FM RSZ_DB_COMP_WHERE_USED

6.Input the COMPUID  got from STEP 4 into I_COMPUID

7.After Execution you will get the where used list entries as highlighted

8. 9 Entries shown below. Since i have chose RKF, the list shows the RKF's used in CKF's and the query names

PS : You can get the COMPUID  from the table  RSZELTDIR .By choosing the needed element definitions , input the COMPUID in the FM.

Hope this helps....

Summary:

  The purpose of this document is to illustrate how exceptions can be set for Date key figures in BEx queries. The way BEx handles exceptions creates a challenge when trying to set them for date key figures. This document explains how to overcome these challenges.

Report Requirements:

HR Training Compliance reports generally include the business need of highlighting employee’s training gaps. Training gaps could come in the form of expired qualifications; the skill has to be renewed or updated. Proactively business would like to be aware of these cases before they occur, therefore the need to identify soon-to-expire qualifications too.

A way to identify either expired or expiring soon qualifications is to highlight them with different colors in a qualifications / employee matrix. Comparing qualifications expiry date versus a key date (evaluated date) it is possible to determine their compliance status. In order to fulfill business requirement BEx Query Designer exception feature can be leveraged.

BEx Query Designer Exceptions feature:

Two types of exceptions can be defined in BEx Query Designer: status exceptions or trend exceptions. Status exceptions evaluate the current value of a key figure (KF > $5000), while trend exceptions evaluate key figure changes, such as deviation (σKF > 5%).

For highlighting qualifications’ compliance, status exceptions type are sufficient. These can be defined in the exception editor.

In this business case the evaluated key figure (expiry date) has data type date (DATS). A date key figure can be either defined directly in the cube or created via a replacement path formula variable referencing a characteristic:

BEx query designer interprets threshold values defined in exceptions as numbers. This means that is not possible to enter a date directly as a threshold value.

However, system can be tricked by entering it in SAP date number format: 20,130,731 instead of 31.07.2013

This trick will do the work for those scenarios where the evaluation date (Value) is static, which is not a very common one.

Exceptions with Formula Variables:

It is possible to specify dynamic values as thresholds by using formula variables with processing type Customer Exit. The formula variable must have the dimension ‘date’. Standard formula variables provided by SAP as business content can also be used, i.e. 0F_ADAY – Formula Variable for Current Calendar Day.

Specify your desired Alert Level and Operator, Click on the Entry Variable icon to select the required formula variable. Then click on Transfer button.

SAP standard variable 0F_ADAY will be sufficient for scenarios where qualification’s expiry date is evaluated against the current calendar day. Not always the case as some time it is necessary to see how things were in a past date. This past date is usually provided in the form of a Ready for Input Variable, either as a specific calendar day or as a calendar month/year. The later requires the last day of the month to be derived from specified month.

The following steps show how to tackle the scenario where qualification’s expiry date is compared to a calendar date derived from a calendar month/year Ready for input variable. For this purpose standard variable 0CMLMON2 is used.

Step 1: Create a Formula Variable with processing type ‘Customer Exit’ and dimension ‘date’.

A second formula variable could be required when identifying soon-to-expire qualifications. Like qualifications expiring in the next 90 days.

Step 2: Maintain formula variables ABAP code

In transaction SE38 maintain the following code in ABAP program ZXRSRU01. This code generates the values for both formula variables based on Ready for Input variable 0CMLMON2:

when 'ZHR_FVCE_KEYDATE00'.

    if i_step = 2.

      READ TABLE i_t_var_range INTO l_s_var_range

      WITH KEY vnam = '0CMLMON2'.

      if sy-subrc = 0.

         lv_date =  sy-datum.

         if lv_date(6) EQ l_s_var_range-low(6).

           l_s_range-low    = lv_date.

           l_s_range-sign   = 'I'.

           l_s_range-opt    = 'EQ'.

           APPEND l_s_range TO e_t_range.

         else.

           concatenate l_s_var_range-low '01' into lv_datum.

           call function 'SLS_MISC_GET_LAST_DAY_OF_MONTH'

             EXPORTING

               DAY_IN            = lv_datum

             IMPORTING

               LAST_DAY_OF_MONTH = lv_date

             EXCEPTIONS

               DAY_IN_NOT_VALID  = 1

               others            = 2.

           IF SY-SUBRC = 0.

             l_s_range-low    = lv_date.

             l_s_range-sign   = 'I'.

             l_s_range-opt    = 'EQ'.

             APPEND l_s_range TO e_t_range.

           ENDIF.

         endif.

       endif.

    endif.

when 'ZHR_FVCE_KEYDATE90'.

    if i_step = 2.

      READ TABLE i_t_var_range INTO l_s_var_range

      WITH KEY vnam = '0CMLMON2'.

      if sy-subrc = 0.

         lv_date =  sy-datum.

         if lv_date(6) EQ l_s_var_range-low(6).

           lv_date = sy-datum + 90.

           l_s_range-low    = lv_date.

           l_s_range-sign   = 'I'.

           l_s_range-opt    = 'EQ'.

           APPEND l_s_range TO e_t_range.

         else.

           concatenate l_s_var_range-low '01' into lv_datum.

           call function 'SLS_MISC_GET_LAST_DAY_OF_MONTH'

             EXPORTING

               DAY_IN            = lv_datum

             IMPORTING

               LAST_DAY_OF_MONTH = lv_date

             EXCEPTIONS

               DAY_IN_NOT_VALID  = 1

               others            = 2.

           IF SY-SUBRC = 0.

             add 90 to lv_date.

             l_s_range-low    = lv_date.

             l_s_range-sign   = 'I'.

             l_s_range-opt    = 'EQ'.

             APPEND l_s_range TO e_t_range.

           ENDIF.

         endif.

       endif.

    endif.

Extra Note: Numbers of days to evaluate soon-to-expire qualifications (90 days) can also be made dynamic by implementing an extra Ready for Input variable to capture the number of days. Not showed in this post.

Step 3: Define exception’s required alert levels.

The system processes alert levels and associated threshold sequentially. When multiple alert levels and thresholds are defined for a single key figure, the system displays the lowest alert level.

Indicate the Key Figure the exception is defined on and what data cells will be affected by the alert.

Make sure the exception is active then run the query to see the result.

Additional Considerations:

BEx Query exceptions can only take effect if the key figure the exception is defined on is included in the query output. When the key figure is hidden by either ‘Always Hide’ or ‘Hide (Can be shown)’ display options, the exception won’t take place. It is this tool behavior that rules out the alternative of having the exception defined on other key figure than the expiry date itself, unless additional key figures are allowed in the query result. When additional key figures are allowed in the output a different approach can be followed by choosing to display the exception on an key figure (expiry date) different from the one (compliance status) the exception is defined on.

Business Objects tools like Web Intelligence or Analysis, when available, could save the effort of defining query exceptions by using conditional formatting rules directly in the reporting tool.

Useful Links:

https://help.sap.com/saphelp_nw70ehp1/helpdata/en/43/21b4cd14cd06f4e10000000a422035/content.htm

This blog has beentranslatedwithGoogleTranslate.theoriginalblogcan be found here: ekessler.de

In the blog BAdI RSROA_VARIABLES_EXIT_BADI I have shown how exit variables using the BAdI RSROA_VARIABLES_EXIT_BADI can be processed.

Now In this blog I want to deal with the coexistence of BAdI and customer exit. First, you should always consider I need the new technical way the SAP me here provides or can I also use the (customer exit) life?

The customer exit for BEx variables has always been a good candidate for unstructured, extensive and historically (often hysterical) grown Coding. This is due to the fact that the exit (Include ZXRSRU01) usually from many different developers (often short-term purchased external consultants) will be processed with different programming views (functional or Objektorientier). Not infrequently, bring this their procedures and approaches to structuring the customer exit (call dynamic function blocks / methods, nesting Includes, ...) from other projects with a.

Another reason that makes a structuring of the customer exits so complicated is the interleaving of two case distinctions. Firstly, it must be distinguished according to the current process step, the I_STEP, and secondly, by the variable to be processed. This nested branching nearly impossible to exit structuring. For this reason, a lot of different methods have been developed for customers all over how to tackle the problem. The following methods can be found in practice (partly slightly modified):

• Nested Includes
  The implementations of the individual departments are hereby outsourced to include and the include ZXRSRU01 only contains the individual department-specific includes.
• Dynamic call of function modules
  For each variable, a function block is created. By means of a fixed naming convention can be derived from the name of the variable and thus dynamically invoked the name of the function block.
• Dynamic invocation of methods of ABAP OO classes
  A method is created for each variable. By means of a fixed naming convention can be derived from the name of the variable and thus dynamically invoked the name of the method. Following the procedure for the function module. In this method the professional belonging together variables / methods are often summarized in a class. This makes the link between the variables with the appropriate method somewhat expensive but has the advantage that helper methods in the class can be reused easily.

Often customers have invested a lot of work into the development of such a concept and a migration towards the BAdI RSROA_VARIABLES_EXIT_BADI is made difficult by this method. It is therefore important that is initially clarified whether the use of the new BAdI also brings much added value that the migration effort worthwhile. To understand where the added value of using the BAdI's against the customer exit is I want to describe the use and the internal processing of exit variables and the interaction of the BAdI RSROA_VARIABLES_EXIT_BADI and the customer exit briefly here.

1.1 Internal processing of exit variables

To understand the internal processing process, it is first necessary to understand how the BAdI RSROA_VARIABLES_EXIT_BADI works. In the BAdI RSROA_VARIABLES_EXIT_BADI is a "new" BAdI. New BAdI are organized in enhancement spot. As known in the rule of the BAdI name, not the enhancement spots I always climb in through the BAdI Builder (transaction SE18) to edit the BAdI implementations. Furthermore, the BAdI RSROA_VARIABLES_EXIT_BADI is a filter-based BADI. As filter the BAdI uses the info object that forms the basis for the BEx variable. Figure 1.1 shows on the left the SAP code to handle variables. If it is in the current variables to be processed by an exit variable by means

      GET BADI variable_exit
        FILTERS
          iobjnm = i_iobjnm.

tested whether an active BAdI implementation exists in the filter settings to the info object names match. That is the calling process within the SAP standard variable processing, checks whether the BAdI Framework is an active BAdI implementation for a filter value.
If an active BAdI implementation found PROCESS method of the class of the BAdI implementation is called:

      CALL BADI variable_exit->process
        EXPORTING
          i_vnam        = i_vnam
          i_vartyp      = i_vartyp
          i_iobjnm      = i_iobjnm
          i_s_cob_pro  = i_s_cob_pro
          i_s_rkb1d    = i_s_rkb1d
          i_periv      = i_periv
          i_t_var_range = i_t_var_range
          i_step        = i_step
        CHANGING
          c_t_range    = e_t_range
          c_no_screen  = e_no_screen
          c_check_again = e_check_again
          c_s_customer  = c_s_customer.

The definition of the BAdIs RSROA_VARIABLES_EXIT_BADI allows more than one active implementation (Multible use) to form a filter value. Find the BAdI framework for a filter value several active implementations are all performed sequentially. Here, the order is indeterminate.

Figure 1.1: Processing of exit variables

1.2 Default implementation

In addition to the BAdI definition RSROA_VARIABLES_EXIT_BADI were running SAP in the standard of an active BAdI implementation (SMOD_EXIT_CALL). (= IOBJNM <>'' or IOBJNM'') of the filter value of this implementation is defined so that this implementation will always be used as BAdI active implementation.

The BAdI implementation SMOD_EXIT_CALL is characterized in Release 7:30 as the default implementation. As a result, this implementation is called only if no other active implementation is found. It must be noted that the filter value is taken into account when determining the active implementations.
I will illustrate this with a small example. As part of a migration project, we want to change the processing of the exit variables of the processing in the customer exit to the BAdI based variant. The migration project can not be implemented in a Big Bang but due to the scope. So that some variables in the customer exit and some in the BAdI be processed.
Variables and basic information items:

• ZTKE_TODAY (0CALDAY)
• ZTKE_YESTERDAY (0CALDAY)
• ZTKE_CURWEEK (0CALWEEK)

BAdI implementations for variables and the filter

• SMOD_EXIT_CALL [default implementation]
  • BAdI Impl. SMOD_EXIT_CALL
  • Filter:  IOBJNM <>'' OR'' = IOBJNM
• TKE_TODAY
  • BAdI Impl. ZTKE_IMPL_CALDAY
  • Filter: IOBJNM = '0 CALDAY 'OR IOBJNM =''
• ZTKE_YESTERDAY
  • Processing takes place in the customer exit!

Query and variable

• ZTKE_Q_DAY (ZTKE_TODAY)
• ZTKE_Q_WEEK (ZTKE_CURWEEK)
• ZTKE_Q_YDAY (ZTKE_YESTERDAY)

Query processing ZTKE_Q_DAY

First, we consider the processing in I_STEP = 1
When you call the query ZTKE_Q_DAY the standard SAP processing determines all active Implementation to the filter 0CALDAY that are not marked as a default implementation.

GET BADI variable_exit
  FILTERS
    iobjnm = i_iobjnm.

Here the BAdI Framework will only find the BAdI implementation ZTKE_IMPL_CALDAY (filter  IOBJNM = '0 CALDAY ').
In I_STEP = 3 BAdI BAdI Implementation Framework only ZTKE_IMPL_CALDAY place again (filter  IOBJNM =''). In I_STEP = 3 all variables for validation (i_t_var_range) are available. I_vnam The parameters and i_iobjnm are I_STEP = 3 initial.

Query processing ZTKE_Q_YESTERDAY

Again, we first consider the processing in I_STEP = 1
When you call the query ZTKE_Q_YESTERDAY the standard SAP processing determines all active implementation to the filter 0CALDAY that are not marked as a default implementation.

GET BADI variable_exit
  FILTERS
    iobjnm = i_iobjnm.

Here the BAdI Framework will only find the BAdI implementation ZTKE_IMPL_CALDAY (filter  IOBJNM = '0 CALDAY ')! But we want to take advantage of the processing in the customer exit. This can be the case if, as have, the processing for this variable is not yet migrated in our example. Below I show how this can be implemented.
In I_STEP = 3 BAdI BAdI Implementation Framework only ZTKE_IMPL_CALDAY place again (filter  IOBJNM =''). Here the same applies as I_STEP = 1

Query processing ZTKE_Q_WEEK

Again, we first consider the processing in I_STEP = 1 When you call the query ZTKE_Q_WEEK the standard SAP processing determines all active implementation to the filter 0CALWEEK that are not marked as a default implementation.

GET BADI variable_exit
  FILTERS
    iobjnm = i_iobjnm.

Here you will find the BAdI Framework no active implementation that is not marked as a default implementation!
The default implementation SMOD_EXIT_CALL is used as the active implementation.
In I_STEP = 3 BAdI BAdI Implementation Framework finds the ZTKE_IMPL_CALDAY (filter  IOBJNM ='').

1.3 Results

The following points should be noted:

• In the various implementations of the I_STEP must be checked and the current variable (Relocated CASE)
  In the example above, the implementation ZTKE_IMPL_CALDAY used as the active implementation for all variables based on the info object 0CALDAY. That within the implementation must be distinguished according to the currently processed variable analogous to the customer exit a case distinction. The case distinction is here implemented instruction usually with the help of CASE.

• I_STEP 0,1,2 and the special case I_STEP = 3
  Similar to the variable name must be distinguished within the implementations of the I_STEP. The I_STEP = 3 provides as a special case here. In I_STEP = 3 all variables are testing and validation, and the parameters I_VNAM and I_IOBJNM are initial. That a case distinction according to the variable name is not possible here. When processing the I_STEP = 3 all BAdI implementations are called as active implementations in the filter IOBJNM = contain''. That it must be here a distinction according to the current query to be processed. The current query can be determined from the component COMPID the structure I_S_RKB1D.

• With Release 7:30 it is not possible without further a BAdI implementation and parallel to use the customer exit.

• From Release 7:40 SPS09 and BAdI customer exit can be used in parallel without further notice. For 7.40er systems from SPS09 the Note 2036773 needs to be implemented

2 Coexistence with Release 7:30

In a SAP BW / .3 system of BAdI RSROA_VARIABLES_EXIT_BADI and the customer exit EXIT_SAPLRRS0_001 can not be operated in parallel without further ado, see example above. To ensure that the customer exit is always run, it is necessary to set up your own BAdI implementation to this. For the BAdI implementation, the filter values are defined analogously to the SAP standard implementation.

Figure 2.1 shows a BAdI implementation to call the customer exits.

Figure 2.1: BAdI definition for Customer Exit

Figure 2.2 shows the filter values of the BAdI implementation.

Figure 2.2: Filter values of the BAdI implementation

Listing 2.1 shows the implementation of the PROCESS method of BAdI implementation. Within the implementation of the call to the customer exit is passed. It should be noted that it must be ensured not be deleted that may have already been determined value. The parameter E_T_RANGE of the function block is a pure export parameters, ie if the parameter C_T_RANGE was already filled in another BAdI implementation, this value must be saved before calling the exit.

METHOD if_rsroa_variables_exit_badi~process.

  DATA: lt_range_tmp TYPE rsr_t_rangesid.

  IF c_t_range IS NOT INITIAL.
    APPEND LINES OF c_t_range TO lt_range_tmp.
  ENDIF.

  CALL FUNCTION 'EXIT_SAPLRRS0_001'
    EXPORTING
      i_vnam        = i_vnam
      i_vartyp      = i_vartyp
      i_iobjnm      = i_iobjnm
      i_s_cob_pro  = i_s_cob_pro
      i_s_rkb1d    = i_s_rkb1d
      i_periv      = i_periv
      i_t_var_range = i_t_var_range
      i_step        = i_step
    IMPORTING
      e_t_range    = c_t_range
*    E_MEEHT      =
*    E_MEFAC      =
*    E_WAERS      =
*    E_WHFAC      =
      e_no_screen  = c_no_screen
      e_check_again = c_check_again
    CHANGING
      c_s_customer  = c_s_customer.

  IF lt_range_tmp IS NOT INITIAL.
    APPEND LINES OF lt_range_tmp TO c_t_range.
  ENDIF.

ENDMETHOD.

Listing 2.1: Implementation of the PROCESS method

This blog has been translated with Google Translate. the original blog can be found here: ekessler.de

As part of the authorization check for Reporting's permission relevant values​​, among other things with the help of exit variables can be determined. It happens that the requirements of the business require that to be included in the determination of the values ​​within the exit implementation of the report in which the data should be displayed. That if user A, he should look at the data on the X report be eligible for other values ​​than when he looks at the data on Z report.

The SAP BW authorization concept is the consideration of the report for the determination of the authorization-relevant data are available. For this reason, the name of the report is not handed over to the Cuxtomer exit interface. That is, the parameter is the report name usually provides the customer exit for exit variables in the processing of exit variables in the context of initial authorization.

In the following I want to show the behavior of an example. Furthermore, I would like to show an alternative way how to determine the name of the current report. The feature 0COUNTRY is filtered through an exit variable within the authorization check.

Figure 1.1 shows the definition of authorization ZTKE_AUTH01. To determine the appropriate values ​​the exit variable ZTKE_COUNTRY is used.

Figure 1.1: Definition of authorization

Figure 1.2 shows the use of the authorization in the role.

Figure 1.2: Definition of the role

In my example, I put the implementation not in the customer exit EXIT_SAPLRRS0_001 (Extension - RSR00001 BI: Enhancements for Global Variables in Reporting) to, but here I use the SAP BW 7.30 newly introduced BAdI RSROA_VARIABLES_EXIT_BADI.

For the new implementation of the BAdI RSROA_VARIABLES_EXIT_BADI I define as a filter IODBJNM = 0COUNTRY. The filter combination IOBJNM = '' we do not need here because of us I_STEP 3 = not interested. Only in I_STEP = 3, the parameter IOBJNM is not maintained. Exit variables that will come as part of the authorization to use = 0 processed in I_STEP and the parameter IOBJNM is maintained. Figure 1.3 shows the upper part of the filter combination used.

Figure 1.3: BAdI implementation

The lower panel in Figure 1.3 shows how the name of the report can be found. When processing in I_STEP 1, 2 and 3, the name of the report is on the COMPID field of the structure I_S_RKB1D. But in I_STEP = 0 the field is empty. With the help of the instruction:

IMPORT compid = l_compid FROM MEMORY ID 'COMPID'.

may the name of the report but are determined at runtime.

I found very interesting report. It has no ABAP code at all. But it has a lot of text in there instead. Name of the report mentioned in here is RSR_BEXANALYZER_TEXT. The texts which it carries are related to BW’s BEx Analyzer. So basically all the texts used within this Windows based tool are stored with the report.

The texts are downloaded to user’s folder (%temp%\BW\COMMON\texts\ into the file e.g. BExTexts_EN.xml as per language used for login) when first logon to BEx Analyzer is performed. There are many SAP Notes which deal with the report. Mostly they deliver new or changed texts. So once you are not able to see new/changed text delivered by Note you may want to delete this folder or file to get refreshed texts to your workstation. See SAP Note “1732598 - Text Elements do not appear correctly in BEx Analyzer” for details.

I was curious to know how many texts the report has. So I prepared short ABAP report to count that. Here it is:

DATA: lt_tpool TYPE TABLE OF textpool,
            lv_lin   TYPE i.

CALL FUNCTION 'RS_TEXTPOOL_READ'
       EXPORTING  OBJECTNAME = 'RSR_BEXANALYZER_TEXT'
                             ACTION            = 'DISPLAY'
                            LANGUAGE      = 'E'
      TABLES         TPOOL             = lt_tpool
      EXCEPTIONS  others          = 0.

DESCRIBE TABLE lt_tpool LINES lv_lin.
WRITE: / lv_lin.

BTW: in my system based on SAP_BW 731 SP 0002 it has 827 texts.

So basically this is how I was playing tonight

The blog is cross posted on my personal blog.

This blog explains the use of BI commands to pass variable parameters to a BEx query.

Scenario:

It is quite usual scenario that we will have to open a BEx query from another Web Application Designer report or from any other portal. This will generally be implemented by having a button / URL pointing to the target query.

At times, it is also required that we have to pass the selections made in the landing page to the query so that the output will be filtered according to the values passed.

Solution:

In order to achieve this, we can make use of the standard BI commands. One such command is SET_VARIABLES_STATE. This command is used to set the value of a variable which is used in BEx query.

Consider the following example, where in a query has a single value variable ZVAR_DATE created on InfoObject ZDATE. From the landing page, when the user clicks on the URL of the target query, it should pass the date value selected in the landing page to the above said query.

Below is the BI command which we need to append it to the actual query URL with required <variable name> and <variable value>.

<Generated_URL>&BI_COMMAND_1-BI_COMMAND_TYPE=SET_VARIABLES_STATE&BI_COMMAND_1-VARIABLE_VALUES-VARIABLE_VALUE_1-VARIABLE=<variable_name>&BI_COMMAND_1-VARIABLE_VALUES-VARIABLE_VALUE_1-VARIABLE_TYPE=VARIABLE_INPUT_STRING&BI_COMMAND_1-VARIABLE_VALUES-VARIABLE_VALUE_1-VARIABLE_TYPE-VARIABLE_INPUT_STRING=<variable_value>

In our case, we should replace <variable_name> with ZVAR_DATE and <variable_value> with 01.01.2014(or any other required date).

Similarly, it is possible to pass values for multiple variables by appending the query URL with the above command with ‘N’ number of times, where N= number of variable values that needs to be passed.

Thanks for reading this blog

Appreciate any suggestions/feedbacks!

In this blog I am going to demonstrate on how the fields can be populated during run time in BEx query.

Scenario:

A firm has confidential data such as the price of a material which is yet to be released to market, which the firm does not want to store it in a data store object or an InfoCube straightaway. Instead they will store it in an encrypted format in a database table. But certain users such as Product Managers or Board Members should be able to view the decrypted prices in the final BEx query. In this case, it is required to populate the decrypted values during run time of a BEx query.

Solution:

We can make use of classic BADI implementation on RSR_OLAP_BADI. This BADI basically gets executed for the specified characteristics / KeyFigures and populate the values during run time based on the code written for the implementation.

To do this, we need to have virtual charactristics/KeyFigures present in the underlying InfoProvider i.e. say we already have the decrypted value stored in the InfoObject ZDEC_VALUE of an InfoProvider, then we need to create a dummy Key Figure say ZENC_VALUE on the same InfoProvider.

Once the above step is complete, then create a custom implementation on RSR_OLAP_BADI which will have three pre-defined methods i.e. INITIALIZE, DEFINE and COMPUTE. It is mandatory to define and initialize the fields in INITIALIZE and DEFINE methods in order to use them in COMPUTE method. In the COMPUTE method we can have the logic to decrypt the values and assign it to the dummy virtual characteristic/KeyFigure created.

By doing this, everytime when the queries having the InfObjects specified in the BADI will undergo the business logic and the fields are populated accordingly.

It is possible to create new custom methods other than the pre-defined methods.

Note:

It is also possible to restrict the BADI to run it only for the queries built over a particular InfoProvider or a particular query alone. This can be handled by using a TVARVC variable by having list of queries stored in it and having a lookup to this before going to the actual logic in COMPUTE method. The InfoProvider restriction can be added straightaway in FILTERS area of BADI implementation.

Where as sample piece of code for INITIALIZE method can be copied from the example class CL_EXM_IM_RSR_OLAP_BAPI and this can be changed based on the requirement.

Thanks for reading this blog.

Appreciate any comments/feedbacks!

I am sure most of you have come across multiple issues during BEX workbook upgrade from 3.x to 7.x. Most of the customers use BEX workbooks pretty heavily. Some of the workbooks might have huge number of tabs. I have seen workbooks with 50+ tabs. Do you believe it? I am not kidding…

The BEX 7.x is based on .NET framework. A process can allocate a maximum of approximately 1.2 gigabytes (GB) in the .NET framework, regardless of the memory capacity in the front-end. This corresponds to approximately 750,000 data cells.

Following are some of the potential solutions, if you get the error “Client out of memory” in the upgraded workbook.

1. Avoid refreshing the whole workbook. Refresh the queries that you require by enabling the following features. The following features are available only from a certain support package level.
   1. Allow refresh of single queries as a global setting in BEX
   2. Single data provider refresh functionality
2. Split the workbook into multiple. It’s time to re-engineer and remove unwanted tabs.
3. Covert BEX workbook into to a new tool called SAP BO Analysis for Office. It's a bigger decision. If you have plans to move to this tool in future , this a good time to move forward. One of the main prerequisites is that you have to be on SAP BW 7.01 SP11 or higher.

(1)  Net..Net…Plan to upgrade the back-end and front-end patches to leverage the above-mentioned features so that you can avoid memory related errors in the upgraded workbook.

In the next part, I am going to talk about the missing features in BEX 7.x workbook compared to BEX 3.x workbook and provide alternate options to overcome the same.

This blog has been translated with Google Translate. the original blog can be found here: ekessler.de

In the blockUse the reporting name in Exit-variables for authorizationI have shownas the nameof a reportin the processing ofexit variablesin the contextof theauthorizationmaybeused. In thisblock, I show what restrictionsaretaken into account.

Thecustomer exitis traversed twicein the context ofauthorization. In the first passtheCOMPIDfieldisnot yet availablein thememory, and the call

IMPORTFROMMEMORYIDl_compidcompid='COMPID'.

returnsforl_compidnothing. With the followingcodetoensure that allusersof the report'ZTKE_EXIT_VAR_AUTH' onlytheinformation on the countryGermany(DE) is obtained.

METHODif_rsroa_variables_exit_badi~process.

   DATA: TYPEl_compidrszcompid,

         ls_rangeTYPErrrangesid.

 

   IMPORTFROMMEMORYIDl_compidcompid='COMPID'.

 

   CASEl_compid.

     WHEN 'ZTKE_EXIT_VAR_AUTH'.

          ls_range-sign = 'I'.

          ls_range-opt = 'EQ'.

          ls_range-low = 'EN'.

          APPENDTOls_rangec_t_range.

      ...

   ENDCASE.

ENDMETHOD.

The first callinI_STEP=0stilldeterminednotCOMPIDandthusno valueforthe processedhereexit variablecomesbackas part of theauthorization. In the secondcall, theCOMPIDcanbedeterminedandthe permission isrestricted toDE.

The first callhasthe consequence thatwein the executionof thereport, thewarning

You do nothaveanalysisauthorizationforanychar. values​​of char. 0COUNTRY

get, seeFigure2.1. theauthorization

By default, the variables are determinedbufferedvalues​​in the contextof the authorization check. To ensurethat the values​​can be evaluatedin thesecond pass, thebuffering intheRSECADMIN(seeFigure2.1) can be switched off.This is onlypossiblesystem-wide!

Figure 2.1: Variablen Pufferung deaktivieren

After thebufferwasswitched off, we getno warningsregarding. The lack ofanalysisauthorizationmore.

Unfortunately, there isnoalternative toturning off thebuffer. Theanalysisauthorization conceptclearly statesthat an analysis ofauthorizationshouldbemade​​to the dataandnotthereportingobject.

The original blog can be found here: ekessler.de

Inthis blog Iwould like to trysome clarityintheprocessingofexit variables(EXIT_SAPLRRS0_001) to bring.TheemergedwithBW7.30BAdIRSROA_VARIABLES_EXIT_BADIhasto dealwithExitvariablenot exactlysimplified.In addition,theBAdIisunfortunatelynotdocumentedintheSAPHelp. Furthermore,it has nowalsochanged60withthe7.4domainRSCHAVLofCHARtoSSTRING.

Allexit variablesdescribedhereare used tothe range of valuesof a reportlimit orexpandthescopeofpermissions. In addition,thepropertiesdescribedhereby ExitvariablesforExitvariables areto beusedas part of thestaginginDTP's orInfoPackages.

First, however,let usfirst of alldealwith the differenttypesofexitvariables and theirprocessing order.

1.1      Variablentypen

If I talk about exit variablesIdistinguish the followingtypes of use:

• Ready for input
• Not ready for input
• Use for authorization or staging

Ready for inputvariablescomethentouseiftheuser shouldbe given the opportunityto influence theoutcomereportindividually. The basic concept ofan input-readyvariablesprovidestheuserdetermines the valueforthe variable, and the value could not be changed by internalprocessingprocesses(customer exit). Insection 1.3,"Overriding inputvalues", I describe how this conceptcanbebypassedandtheuser-enteredvalue of aninput-readyvariablesin the customer exitcanbeoverwritten.

Reday for inputvariables would be processed in I_STEP=1andI_STEP=3, seeSection 1.2"processing steps(I_STEP)".

Notready for inputvariablescomethentouseifthe value is tobedetermined byrules. Hererulesare often defined(implemented) in whichthe variable valuesforinput-readyvariablesnotdepending on ready for input variables aredetermined.

Notready for inputvariables would be processed inI_STEP=1andI_STEP=2, seeSection 1.2"processing steps(I_STEP)".

Exitvariablescan also be usedas partofauthorization or tostaging. At exitvariablesthat must be consideredare used here, that there is nointeraction with a userisusuallyheld. This meanshereisthe processing orderanother.

Therefore,it must be ensuredherethatcombinationsasready for input, mandatoryandnodefault value(Default value)thatcauseavariable dialogis needed. Processofstaging(DTP, InfoPackage) are usuallyscheduledprocessesinplacethat are executed bybackground-users.

Variablesof usageauthorization andstagingareprocessedonlyinI_STEP = 0, seeSection 1.2"processing steps(I_STEP)".

1.2 Processingsteps(I_STEP)

Exitvariablesdepending on theusageandpurposeinone or more steps, theI_STEP's processed. In the section "Dependencies for Variables ofTypeCustomer Exit" theSAPHelptheI_STEP's are briefly explained.The descriptioninthe online help is unfortunately incomplete and omitted entirely on examples. Therefore, I willbrieflyexplain eachstep again using examples.

1.2.1AuthorizationandStaging(I_STEP =0)

InI_STEP=0exit variablesare processedin theauthorization andare usedinstaging. Figure1.1shows the useof an exitvariableswithintheauthorization. FortheprocessingofexitvariableswithintheentitlementonlytheI_STEP=0is traversed.

Figure1.1: Exitvariableswithintheauthorization

Figure1.2showsthe use of anexit variablesinstagingthe example ofselectionwithin anInfoPackage.

Figure1.2: Exitvariables within theStaging

1.2.2Initialization(I_STEP =1)

TheI_STEP=1 is used forinitializationofvariablesandexitis runseparatelyfor eachexit variable. In the first stagetheinput-readyvariablesandthennotready for inputvariables are processed, seeFigure1.7. (The order could be differ, depends on the release (here BW 7.31 SP06)!)

Figure1.3shows a typical exampleof initializingan input-readyvariables. The variable isinitialized withthecurrent monthof last year.

Figure1.3: Initialization

1.2.3Derivationof variable values(I_STEP =2)

TheI_STEP=2is used toderive thevaluesfor the non-input-ready variablesExit. Again, thevariables areprocessedseparatelyanalogous toI_STEP=1. To derive thevalues for non-input-ready variablesExitall previouslydetectedvariable valuesin the parameterI_T_VAR_RANGEavailable. Insection 1.3,"Overriding values entered" I describeas well asinput-readyvariables can beprocessedhere.

Figure1.4 showshowthe currentvariable(examination of thevariable nameisnot shown here), the value is derived basedon thevalue of the variableZTKE_MONTH.

Figure1.4: Derivation ofvariables

1.2.4validation(I_STEP = 3)

TheI_STEP=3is used to validateall recordedvariables.InI_STEP=3all previouslyrecorded valuesin the parameterI_T_VAR_RANGEaretesting and validation.

TheI_T_VAR_RANGEparameter containsonlythevariablesthat contain a value. That isherearetheonlyvariablesincluded:

• value set by default value or
• value set byan implementation(I_STEP =1orI_STEP=3) or
• user entereda value in thevariable dialog

InI_STEP=3cannotbechanged, the values of the individualvariables. It is possibleto generate messages which would be displaywith thereport-result or the variable dialog. In the eventthatthevalidation of thevariablesmeans thatit makes no sensetorun the reportby throwingan exception(RAISE EXCEPTION) to preventthe report is run. The exceptionmeans thattheuserre-enters the values in the variablesdialog.

Figure1.5 showsthevaluesfor the two variablesZYEARFROMandZYEARTOdetermined andthen comparedas inI_STEP=3. Ifthe FROMvaluegreater thanTOvalueofamessage is issued andusing the RAISEstatementwrong_valueprevents thereport is run. The userhasthe opportunityto correct the valuein the variabledialog.

Figure1.5: Validation -CustomerExit

Figure1.6 showssimilar tothe exampleinFigure1.5, as in the object-orientedcontextto run thereportcan be prevented. The exceptionmustbethrownherein theobject-orientedcontext.

Figure1.6: Validation -BAdI

1.3Execution OrderofI_STEP

Figure1.7 showsthesequence in which theindividual's I_STEPunder aBExreports.I distinguishthe twophases:

• Präparation(preparation phase) and
• Validierung(Validation Phase)

TheI_STEP's thepreparationphaseare runbefore the variabledialogue andI_STEP's validationphasewill onlygo throughifthe values of theinput-readyvariableschangein thevariablesdialog.

Figure1.7: Processing ofexit variables(I_STEP's)

That isthe callingSAPstandardprocessing procedureinitially assumesthat the useraccepts thedefault values of thevariablesdialogwithout changing. In thiscase, the validationphaseis not runagain!

Theprocessstepsof thevalidationphasewill onlygo throughifthevaluesin thedialogvariableswerechanged by the user.

1.4ProcessingofprocessvariablesExit

WithBW7.3theBAdIRSROA_VARIABLES_EXIT_BADIwasintroducedandpresented to thecustomer exitEXIT_SAPLRRS0_001. The blog Coexistence of BAdI RSROA_VARIABLES_EXIT_BADI and Customer-Exit EXIT_SAPLRRS0_001showshowtheBAdIandthecustomer exitbehaveinaBW7.3system.

Figure1.8shows the individualprocessingblockswhich are executedas partof the variableprocessingofexitvariables.

Figure1.8: Variables processing

Thestandardprocessingprocessfirst checkswhether an activeBAdIimplementationbyTypeRSROA_VARIABLES_EXIT_BADIisavailable. As afiltervaluehere, the technical name of theInfoObjectis usedontheexit variablebasedcurrently being processed. From a technicalperspective, thistest is performedwithin the function blockRRS_VAR_EXITvia GETBADI.

The blogNew BAdIRSROA_VARIABLES_EXIT_BADIdescribesthemanufacturing processof theBAdI's in the details.

1.5Overridinginputvalues

The basic principleforinput-readyvariableswasinitiallythatuser enteredvalues can notbeoverwritten. An input-readyvariable isnotprocessedbydefaultafter the variabledialogas a singlevariable.

InI_STEP=3, the variablecanindeedbe validatedbutnot be changed. If it is determinedduring validationthattheuser enteredvalueisnot meaningful, in the I_STEP=3 is amessagethatthe usergeneratedinformed. In addition,an exceptionwill bethrown. The exceptionensures thatthevariablesdialogappearsagain.

With the introductionof the parameterE_CHECK_AGAIN(see Note1272242-RenewedVariablenverprobunginI_STEP=2), the concept was canceled. The parameterallows thedeveloperto theuser-enteredvalue of aninput-readyvariablesafter the variabledialoginI_STEP=2to overwriteas needed.

As describedinSection 1.2"processing steps(I_STEP)" input-readyvariablesonlyinI_TEP=1andI_STEP = 3 processed, the value onlyinI_STEP=1 changes(initialiesiert) canbe. To ensurethatan input-readyvariablesinI_STEP= 2 isagainprocessedmust be inI_STEP=1forthis variable is theexportparametersE_CHECK_AGAIN(E_CHECK_AGAIN ='X') are set. If the parameter issetE_CHECK_AGAINsothisis ready for inputvariable isprocessed into anotready for inputvariablesinI_STEP=2analogoustothevariablesdialog.

Issue:

I have ZGL_ACCNT with two compounding object 1 Chart of accounts 2 Logical Source System.

Created variable and using in BEx Report.

As per my requirement I need restrict F4 values for G/L Account variable specific to Chart of accounts.

Ex

P Table

GGL Account     Chart of Accounts          Source System

123                    A                                   ABC

123                    B                                   ABC

As per my requirement I need to show F4 values for chart of accounts 'A'.

So, implemented BADI using RSR_VARIABLE_F4_RESTRICT_BADI enhancement and written SELECT statement pull only where Char of accounts equal to 'A' and filling C_T_RANGE.

In C_T_RANGE I am able see only 123 and A record.(In Debug)

If I execute report and press F4 I am able see 123 A and 123 B also, I am wondering how 123 B is coming since i filled C_T_RANGE table with 123 A.

Finally I am not able to meet customer requirement ,

Here is the solution , you may found number of documents how to create(http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/4009b0a8-7adc-2e10-48b3-a111c8f407af?QuickLink=index&…) RSR_VARIABLE_F4_RESTRICT_BADI along with that we need add below piece of code to work as expected like 123 A as per above example, while working with compounding objects.

LOOP AT t_zgl_accnt INTO w_zgl_accnt.

           l_s_range-iobjnm = i_iobjnm. "ZGL_ACCNT

           l_s_range-sign = 'I'.

           l_s_range-option = 'EQ'.

           l_s_range-low = w_zgl_accnt-zgl_accnt.

           APPEND l_s_range TO c_t_range.

           l_s_range-iobjnm = 'ZCHRT_ACC' ." Char of accounts.

           l_s_range-sign = 'I'.

           l_s_range-option = 'EQ'.

           l_s_range-low = w_zgl_accnt-zchrt_acc.

           APPEND l_s_range TO c_t_range.

           l_s_range-iobjnm = 'ZSOSYS' ." Logical source system

           l_s_range-sign = 'I'.

           l_s_range-option = 'EQ'.

           l_s_range-low = w_zgl_accnt-ZSOSYS.

           APPEND l_s_range TO c_t_range.

          ENDLOOP.

Note: Need to add all compounding objects for C_T_RANGE, here chart of accounts and logical source system, adding to C_T_RANGE even though not required for user then only data will restrict and display when you press F4 as expected.

Thank you,

Nanda

Customer Exit OLAP Variables require ABAP coding which often can be found in a single INCLUDE program ZXRSRU01 as part of legacy Enhancement RSR00001 (a.k.a. Customer Exit EXIT_SAPLRRS0_001). Usually the INCLUDE program becomes bigger and bigger. Moreover, various people and/or project teams are working in the same place. You can imagine that it is dangerous because one programming or transport sequence mistake can destabilize the entire system. The solution is encapsulation of the coding of individual variables and you will need a framework to realize it.

In this blog I would like to discuss the latest enhancement technology to be used. Moreover, I will present an alternative approach for implementing a framework and the advantages it can offer you.

Please refer to my document Implementing Framework for Customer Exit OLAP Variables for a detailed step-by-step instruction for implementing the framework.

New Enhancement Spot

In SAP BW release 7.3 a new Enhancement Spot RSROA_VARIABLES_EXIT for Customer Exit OLAP Variables was introduced. It contains BAdI RSROA_VARIABLES_EXIT_BADI which can be impemented multiple times using an appropriate filter. It also contains a default implementation SMOD_EXIT_CALL to call program ZXRSRU01 as part of legacy Enhancement RSR00001.

I can recommend reading blog New BAdI RSROA_VARIABLES_EXIT_BADI (7.3) for more detailed information. Although it is a big improvement, I would like to suggest a more sophisticated approach to take the encapsulation to the next level.

Framework

My alternative approach indirectly uses standard SAP’s new BAdI RSROA_VARIABLES_EXIT_BADI. Instead of implementing this BAdI for every new variable, I introduce an intermediate layer: a new custom Enhancement Spot YBW_OLAP_VAR with 4 BAdIs (corresponding to the processing steps). The following 4 BAdI Definitions are available:

• YBW_OLAP_VAR_BEFORE_POPUP - OLAP Customer Exit Variables - Before Popup (i_step = 1);
• YBW_OLAP_VAR_AFTER_POPUP- OLAP Customer Exit Variables - After Popup (i_step = 2);
• YBW_OLAP_VAR_VALIDATION- OLAP Customer Exit Variables - Validation (i_step = 3);
• YBW_OLAP_VAR_AUTHORIZATION- OLAP Customer Exit Variables - Authorization (i_step = 0).

Only once BAdI RSROA_VARIABLES_EXIT_BADI will be implemented in a generic way. Here the respective BAdI implementation will be called dynamically according to the processing step and filter on variable name (except processing step 3 where I propose to filter on query name).

Rationale

The main reason for implementing such a framework is achieving a safer system that is much better/easier to manage and support. The main advantages are in my opinion:

• Every BAdI implementation is independent of all others, the encapsulated pieces of coding (residing in their own implementing class) can be maintained and transported independently and therefore eliminating risks which can destabilize the system;
• The BAdI implementation is filtered on variable name (except processing step 3 where I propose to filter on query name), only one BAdI implementation will be processed every time;
• The BAdI implementations are grouped by processing step (i.e. before pop-up, after pop-up, etc.) which increases transparency;
• There is no need anymore to program a filter on variable name (CASE I_VNAM. etc.) and the processing step (e.g. IF I_STEP = 1.) in a nested way, the framework is taking care of that and contains appropriate error handling;
• The Enhancement Spot technology is the latest and way forward technology for enhancing the system, it's using ABAP-OO programming technology and can optionally (not mandatory) be combined with the Switch Framework, you can find more information in the blog Simplify & structure your Enhancements by using Switchable Kernel BAdIs.

Migration

Most likely you are not working in an empty greenfield SAP BW system and you might find a considerable implemention effort in INCLUDE program ZXRSRU01 and/or any preceding framework (e.g. using Function Modules). If you decide to switch over to a new way-of-working, you will not be able to migrate all existing content in one go. Usually you will migrate gradually using a “phase in, phase out” approach. In other words, the legacy implementation and the new implementation have to live together in the same system for the time being.

This is possible but one “hidden” aspect will pop up as soon as you will create your first new implementation. The standard SAP BAdI implementation SMOD_EXIT_CALL will not be called anymore. This implementation is used to call INCLUDE program ZXRSRU01 as part of Enhancement RSR00001. Since this implementation is flagged as a “default implementation”, it will not be called as soon as any normal implementation is found.

The solution is creating another RSROA_VARIABLES_EXIT_BADI implementation which replaces the SMOD_EXIT_CALL implementation. It must be an exact copy of the standard SAP implementation so that it will call the legacy implementation in the same way.

You can find more information in blog Coexistence of BAdI RSROA_VARIABLES_EXIT_BADI and Customer-Exit EXIT_SAPLRRS0_001.

Conclusion

In this blog we discussed a new way of implementing Customer Exit OLAP Variables. The framework consists of an intermediate layer: a custom Enhancement Spot and 4 BAdIs which correspond to the processing step. The respective BAdI will be called dynamically using a single generic implementation of standard SAP BAdI RSROA_VARIABLES_EXIT_BADI. After an overview of the advantages of such an approach, we discussed the topic migration that is applicable in almost all cases.

If you are interested to know all about it, please refer to my document Implementing Framework for Customer Exit OLAP Variables. Here I will share with you detailed technical instructions how to implement such a framework.

In many BI projects it is necessary to create a custom hierarchy either by combining several logically linked characteristics, or by creating a subset hierarchy (diluted hierarchy according to business rules).

One of the ways to do it is to use an enhancement RSAP0001 with EXIT_SAPLRSAP_004 component in ZXRSAU04 include.

Here, after CASE/WHEN “8DATA_SOURCE_NAME”, we can place an ABAP coding which builds a hierarchy according to our logic (sure, important prerequisite is to generate export data source in RSA1 for the characteristic).

If our coding is OK and the hierarchy was created successfully - well done.

But if something was wrong (dump, errors, erroneous hierarchy structure) we would want to debug the coding.

Setting any breakpoint in ZXRSAU04 (hard-coded BREAK-POINT, using checkpoint, setting external breakpoint) doesn’t bring us to debugger session.

In this article I will explain one of the ways to debug ZXRSAU04 exit.

First, go to SE38 and show the report SAPLRSAP.

Then, go to include LRSAPF06 to the line 475.

In the line 475 we can see customer function ‘004’ is called – that is a call to EXIT_SAPLRSAP_004, so put an external breakpoint here.

It is possible that line number may vary depending on your system version, so, if there is no such call in the line 475, just try to search it around.

Then execute an info package which loads a custom hierarchy from "8DATA_SOURCE_NAME" (debugger still doesn’t called).

After the info package load was finished go to SM37, find your job (should have prefix BIREQU_*), check the line, write in transaction line JDBG and press enter.

Debugger will appear.

Press F8 and you will get to your breakpoint.

Finally, press F5 will get you into your ABAP coding.

Nice debugging