Enhancement in SAP BW

Topic Covered :

Overview : Userexit / Enhancement

Method of Enhancement

Common Enhancement

Troubleshooting



Download
Enhnacement in SAP BW

Click Here to Read More !!!!

SAP BW Certification Material (Versions 3.0b & 3.5)

To read these files(.rar ext. ) on your system you need to Download Free version of WinRAR Software .Download from http://www.rarlab.com/download.htm


(1)Title: BW310 - Data Warehousing
Pages: 497
Size: 44.9 MB



DOWNLOAD ( Megashare)
Password: sapdocs



(2)Title: BW305 - Reporting and Analysis
Pages:591
Size: 45.1 MB
DOWNLOAD (Megashare)
Password: sapdocs

Mirror Link: DOWNLOAD (Rapidshare)


(3) Title: BW330 - Modeling
Pages: 308
Size: 12.8 MB

SAP BW 330 : Data Modeling

Audience: Project team members with extensive BW Administrator Workbench knowledge

Objectives: Effectively apply various data modeling techniques in a BW environmentUnderstand the trade-offs between various data modeling techniques

Content:
Extended BW Star Schema
Using Navigation Attributes
Time dependent data
Tracking History
ODS Scenarios
Performance and Maintenance
MultiProvider
DataMarts
Additional Modeling Concepts
Data Modeling Tools

DOWNLOAD
Size: 12.8 MB Pages: 308 eSnips


(4) Title: BW340 - Data Staging
Pages: 237
Size: 11.7 MB

Course Content
- Basics of data extraction
-Data staging via flat file interface
-ETL process
-Extraction from non-SAP systems using various interfaces
-Delta update options in connection with external data extraction

DOWNLOAD

Size: 11.7MB Pages: 237 eSnips


(5) Title: BW350 - Data Extraction
Pages: 329
Size: 16.0 MB

Content:
-SAP BW in SAP NetWeaver
-Data Transfer with the Service API
-Delta Management
-Transfer of flat files
-Data Transfer with DB Connect
-Data Transfer with UDC
-XML-Based Extraction
-Data Transfer with Third-Party ETL Tools
-Data Mart Interface
-Open Hub Service

DOWNLOAD


(6) Title: BW365 - Authorizations

Pages: 241
Size: 20.3 MB

Course Content

• SAP BW architecture and strategies for an authorization concept
  
• Similarities and differences between security requirements in SAP R/3 and SAP BW
  
• Setting up authorizations for reporting users
  
• SAP BW administrators and authorizations for administrative tasks
  
• Standard roles and templates for supporting the creation of an authorization concept
  
• Authorizations necessary for linked source systems

DOWNLOAD





Source: mysapbi.blogspot.com

Click Here to Read More !!!!

Using Query Exit to restrict users output

Using Query Exit to restrict users output

Please note this article has been written from an ABAPers point of view and some knowledge of creating BW queries will be required. When using an authorisation object to restrict a query report it determines if the user can see everything in a range. If they cant see them all then an authorisation error will be displayed. You may have a requirement to still allow the user to see the report but to remove values they are not authorised to see.This would be done by having 2 variables on the report selection screen, one for the user to enter theirselection and a hidden one which will do the actual report restriction. The code for this will look somethinglike this, where 'ZGMGTNOI' is the hidden field and '0S_GRANT' is the visible user input field.



**** ZGMGTNOI variable derives input from variable OS_GRANT
WHEN 'ZGMGTNOI'. if i_step = 2.
* gets selection values entered by user (0S_GRANT)
loop at I_T_VAR_RANGE into wa_range
where VNAMeq '0S_GRANT'
and IOBJNM eq '0GRANT_NBR'.
wa_grant-low = wa_range-low.
wa_grant-high = wa_range-high.
wa_grant-option = wa_range-opt.
wa_grant-sign = wa_range-sign.
append wa_grant to r_grant.
endloop.
* selects all grants user is authorised to see within entered
* selection values

select grant_nbr
from ZGMUSERGRANTS into corresponding fields of table it_ZGMUSERGRANTS where UNAME eq sy-uname
and grant_nbr in r_grant.

* If no values are found! Populates hidden restriction variable with
* user input
if sy-subrc ne 0. l
oop at r_grant into wa_grant.
move-corresponding wa_grant to wa_ETRANGE.
wa_ETRANGE-opt = wa_grant-option.
append wa_ETRANGE to E_T_RANGE.
endloop.
* If values are found! Populates hidden restriction variable with
* all values user is authorised to see
else.
clear: wa_range.
loop at it_ZGMUSERGRANTS into wa_ZGMUSERGRANTS.
wa_ETRANGE-sign = 'I'.
wa_ETRANGE-opt = 'EQ'.
wa_ETRANGE-low = wa_ZGMUSERGRANTS-grant_nbr.
append wa_ETRANGE to E_T_RANGE.
endloop.
endif.
endif.

Click Here to Read More !!!!

Business Warehouse (BW) Development Info

BW Query User exit RSR00001:

Enhancement RSR00001 (user exit)

The enhancement RSR00001 (BW: Enhancements for Global Variables in Reporting) is called up several times
during execution of a report. Here, the parameter I_STEP specifies when the enhancement is called.


The following values are valid for I_STEP:
· I_STEP = 1
Call takes place directly before variable entry. Can be used to pre populate selection variables
· I_STEP = 2
Call takes place directly after variable entry. This step is only started up when the same variable
is not input ready and could not be filled at I_STEP=1.
· I_STEP = 3
In this call, you can check the values of the variables. Triggering an exception (RAISE) causes the
variable screen to appear once more. Afterwards, I_STEP=2 is also called again.
· I_STEP = 0
The enhancement is not called from the variable screen. The call can come from the authorization
check or from the Monitor. This is where you want to put the mod for populating the authorization
object. code for this is as follows:


Populate authorisation object dynamically :

Please note the article has been written from an ABAPers point of view and some knowledge of creating BW queries will be required. First you need to create an authorisation object which references a $Variable. In this example I am using$ZGMGRANT, which has been linked to the users authorisation profile via transaction PFCG.Now Within the BW query you have created via Bex Analyser you need to create and authorisation field with the processing type of 'customer exit'.

The next step is to active the customer exit 'EXIT_SAPLRRS0_001'. To do this create a project in the CMOD transaction, select the SAP enhancement RSR00001 and assign it to the enhancement project. Activate the project.

The enhancement RSR00001 (BW: Enhancements for Global Variables in Reporting) is called up several times during execution of the report. Here, the parameter I_STEP specifies when the enhancement is called.The following values are valid for I_STEP:

· I_STEP = 1Call takes place directly before variable entry. Can be used to pre populate selection variables·

I_STEP = 2Call takes place directly after variable entry. This step is only started up when the same variable is not input ready and could not be filled at I_STEP=1.·

I_STEP = 3In this call, you can check the values of the variables. Triggering an exception (RAISE) causes the variable screen to appear once more. Afterwards, I_STEP=2 is also called again.·

I_STEP = 0The enhancement is not called from the variable screen. The call can come from the authorization check or from the Monitor. This is where you want to put the mod for populating the authorizationobject. code for this is as follows:

case i_vnam.

WHEN 'ZGMGRANT'. "Query field name

if i_step = 0.

BREAK-POINT.

clear wa_ETRANGE.

* Gets all grants a user is able to see from ZTable,

* which is populated elsewhere

select grant_nbr

from ZGMUSERGRANTS

into corresponding fields of table it_ZGMUSERGRANTS

where UNAME eq sy-uname.

* Populate Authorisation Object.In i_step 0

* E_T_RANGE is used to populate the authorisation object

loop at it_ZGMUSERGRANTS into wa_ZGMUSERGRANTS.

wa_ETRANGE-sign = 'I'.

wa_ETRANGE-opt = 'EQ'.

CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'

EXPORTING INPUT = wa_ZGMUSERGRANTS-grant_nbr IMPORTING OUTPUT = wa_ZGMUSERGRANTS-grant_nbr.

wa_ETRANGE-low = wa_ZGMUSERGRANTS-grant_nbr.

append wa_ETRANGE to E_T_RANGE.

endloop.

endif.

ENDCASE.

Click Here to Read More !!!!