How to Add site map of your Blog

Enter your blog  URL details in ctrl.org/blogger/

In the setting tab , Copy the generated site map form the above website and save

SAP BW -Implementing Authorizations for a Charecterictics

Open the Infoobject and navigate to :Business Explorer” Tab

Mark the InfoObject Authorization Relevant & Activate it.

Create Authorisation Variable in Query Designer

Right CLick and select Restrict

Select “Variables” option in Show list-box (As shown in below figure)

Click Create button (As shown in below figure)

Create an Authorization Variable - Variable with Processing by Authorization in Query Designer as Below for”Test Char for Autho”.Restrict the ”Test Char for Autho” with the Authorization Variable and execute the query.

BW Training 3-Types of Applications and Details , R/3 Database Design

TYPES OF APPLICATION

Applications are generally categorized into 2 categories , Online transaction processing (OLTP) & Online analytical processing (OLAP).

OLTP

You are going to process your transaction online. As soon as the business takes place , This data has to be updated immediately into the database. In this case we will be using OLTP type of applications.

Example :

Why data has to update immediately , Suppose you went to an ATM and with drawn some money and system updating this after 15 minutes . Meanwhile you can withdraw some more  money . Even sap r/3 is a business driven application and is OLTP database . Suppose am developing a PO , Sales order , etc ..

Primary operation here is to update the data into the database Immediately .

OLAP

 Primary operation in OLAP is to analyse the data . You are extracting your data from OLTP to OLAP . When it comes to your BW , it is OLAP type of application .

DIFFERENCE BETWEEN OLTP AND OLAP

Relevance of data Example :

Any point of time , What the relevance of data in database . In OLTP always you will have present data . OLAP you will have historical data .

At 8 AM , In a  table 1000 records are there .

OLTP --- 1000 records                

After extraction ,

OLAP ---- 1000 records

At 8:05 AM

Lets say 5 transaction happened at this time . , Immediately OLTP gets updated .

OLTP --1005

OLAP--1000

EXTRACTION PROCESS:

Update Mode : It is a parameter setting which has to be set before extracting the data to BW, which defines what amount of data has to be extracted from the source.

Types of Update modes :

Full Update :

Whenever we use this update mode and extract the data ,it extracts entire data from source to target . If we are extracting from a file , Its always full update

Initial Update

Same as full update , But it will maintain a pointer / timestamp.

Delta update

Compares to the pointer and extracts only the updations.It extracts only LUWs

• Logical Unit of Works (LUWs) : These are modified and newly added records compared to previous load .

Example :

If we are extracting from a store or other system , first time we will be extracting using Initial update and there on delta update

If we want to see pointers / time stamps  of last extracts can be find using transaction RSA7  in R/3

DATABASE DESIGNS

First we are going to understand how exactly data gets saved in SAP R/3 , Next we will see how it gets stored in BW

R/3 DB Design :

R/3 called a 2 dimensional model . Data is stored in the form of table.a table consists of rows and columns .Every table will have fields / Entities  .Field defines physical existence of an object .Every column is a field and each row is a record. Every table will have primary key . The column which has primary are called as KEY COLUMN and the rest are called NON KEY COLUMNS.

Combination of two columns can  be  used to create primary key .maximum we can use 16 columns to form a primary key . Thats why we will call CUBE is 16 dimensional .

Example for primary key defined based on (BILLNO+ITEMNO).Maximum we can have 16 fields as a part of primary key.

If we use primary key of one table used in another table called as foreign key .

R/3 Database is designed based on ER model , which stands for Entity Relationship model .

Any transaction takes place in R/3 , This data will not be updated in single table . The transaction has been splitted (based on relationship between the entities.)and updated in multiple tables , in order to avoid data redundancy.

Below example illustrates how data stored

  R/3 is a ready made database, ready made tables are there , Ready-made fields are there .Everything is pre-designed, We just analysed how it was designed. We are not going to design any database of R/3.

Normal data storage in single table.

Data storage after  Entity relationship split

R/3 is optimized for storage not for analysis . This is one reason why we won't develop musch reports in R/3.When we develop report from R/3 it has to combine data from multiple tables and create a report . Can top level management wait that much of time to generate report.

So while extracting data from R3 to BW , I will put relevant tables data in one cube of BW.Even Though it start degrading DB performance , For us important is Analysis. BW is optimal for analysis , BW is denormalized.

BW Training General -how to find in which Queries an infoobject is used

Go to  transaction“SE 37” and enter the below function module name and press F8

RSZ_I_BASIC_CHA_WHERE_USED

RSZ_I_BASIC_KEYFIG_WHERE_USED

First one for characteristics, second one for keyfigures.

Enter below details in screen

In I_IOBJNM, give ur info object name,

In I_OBJVERS, give A (for Active version)

In I_QUERIES_ONLY put X

Press F8 (will take some time if ur info object has been used in more queries)

Now E_T_COMPLIST shows the number of queries ur info object has been used. Click on

contents box next to it.

You will find the queries in the COMPID field.

You can use following table for all details.This will give you information about key figure ,characteristic formula etc that we use in a query and other details like  last changed by info ,last changed date and query for which key figure exist  :

RSZCOMPDIR

Other useful table will be :

RSRREPDIR	Number of queries available in BW system
RSZELTDIR	Directory of the reporting component elements
RSZELTTXT	Texts of reporting component elements
RSZELTXREF	Directory of query element references
RSRREPDIR	Directory of all reports (Query GENUNIID)
RSZCOMPDIR	Directory of reporting com

BW Training 2 - Basics of Net weaver & SAP Workbench

SAP NETWEAVER :

Netweaver is a combination of various applications. This is developed based on concept called Enterprise Service Architecture [ESA] (earlier SOA).An application which provides end 2 end solution of business is called as ESA application . Its is a combination of PI, BI & EP together called as NETWEAVER suite.

APPLICATION PLATFORM:

As we got data from various applications, it will have different business processes and different formats (XML,IDOC,) all these will be in application layer

PROCESS INTEGRATION LAYER

Imagine You need to integrate data from web based and SAP , We can't combine /convert XML and IDOC .As data is from different formats /business process ,We need to integrate all the in process integration layer . In one world PI brings data from any where and any format and sends data to any where and any format . In the above example as we are sending data from web to sap , so we are converting XML to IDOC.

INFORMATION INTEGRATION LAYER (BI in old versions )(BW from latest versions)

This is what your BW layer . All our data stores in BW Layer .Suppose imagine if we are processing data from sap R/3 , no need to load to PI , We can directly load in BW.

In BW layer , we will be doing Modelling ,extraction and generating reports

PEOPLE INTEGRATION LAYER (Enterprise Portal)[EP]

This is one of the building blocks in the SAP NetWeaver architecture. With a Web Browser, users can begin work once they have been authenticated in the portal which offers a single point of access to information, enterprise applications, and services both inside and outside an organization. The portal provides access to business processes and information, social collaboration and content management across various consumption channels.

Terminology of basic SAP Screen

Data Warehousing WorkBench (DWWB)

This application we are going to in BW .This can be triggered by using transaction “RSA1”.

It has got 2 frames, one is left frame and right frame.

Left frame has got various tabs.each tab has different levels

In the right frame , it will display all objects according to what we select in left frame

Functions of DWWB :

1. Modelling-

whenever we want to create any object in BW, we use Modelling tab .

2. Administration -

To schedule load in the background and to monitor them

4. Transport connection

To transport objects from one system to another , All objects are created in development system will be unit testing whether the new objects working fine or not and moving these new objects to User Acceptance Test(UAT) and finally to live systems / production systems.

4. Documents-

To do the documentation .

5. BI Content

The readymade objects given in BI are called as BI Content objects .When ever you want to use these objects , we can go to BI Content tab . All Bi Content objects start with Zero.

6. Translation -

To translate the object from one language to another . Every object has got 2 names , technical name and description . Technical name cannot be changed .

7. MetaData Repository

Data about data is called Meta data . We can get information about all objects .

BW Training Basics 2

2 .ETL :

Developing a link between source to target

• Data Source :

This is a structure, which is created in the source system and replicated to the BW system. Maintaining a data source in a source system is doing any changes related to the data source. It could be adding/deleting fields or checking the flags in the data source like the hide and selection flag. Also, if the datasource is provided in the LO Cockpit, changes can be made there too depending on how the extraction of data is made for that data source. Extraction could be of flat file extraction or of multiple flat structures ie., hierarchies.

What data has to be extracted from source

• Persistant Staging Area (PSA) [2DM table]:

PSA is a automatically generated by system itself when we create data source.In generally we will be cleaning these PSA tables on regular intervals of time .

• Transformations :

This is to transform data from staging tables and moved to targets.Some times we will write some ABAP code to transform the data , This is called routines.

3. Reporting

Reporting tool may be different from client to client , default tool provided by SAP is Business Explorer (Bex) . Sap has recently acquired BO ( Business objects) , Soon this will replace Bex.

Combination of 4 applications :

1. Analizer :

         Using analyser we can report in the form of excel sheet

 Input for Analyser is Query & info Provider

2. Query designer

        Using this we can design the query according to requirements of end user and we can    execute this in browser

 Input for Query designer is  Info Providers

3. Report designer

         We can format the query output using report designer .

        Input for report designer is Query

4. Web Application Designer (WAD):

        

        

Using this we can see query output in our own designed webpage

Step 1 ) We can design webpage .If you know HTML you can design your own webpage ,else we would be having drag and drop options available to create webpage .

Step 2 )  Data Binding --Assign input for the web page

        Query

        Info Provider

                Query View (When we design small reports using analyser , that will be called as Query view)

Suppose if we want to see two table output , This can't be done using query designer .We need to use WAD to design such requirements.

4) Performance Tuning

1. AGGREGATION : This is hard to understand in the beginning , Aggregates are like a smaller cubes on the main cube to improve query performance
2. COMPRESSION:
3. PARTITIONS
4. INDEX
5. LINE ITEM DIMENSIONS
6. OLAP CACHE MEMORY
7. BI ACCELERATOR INDEX

5)Broad Casting

 Sending the reports to concerned end users

1. When to Send ?(Time)
2. How to Send ? (Format)
3. Where to Send ?(Location)

BW Training Basics 1

A)     Info Object : This is like a column / field in general DB table . basic modelling starts with Info Object creation

B)      Info Cube : This is a multi dimensional model An object that can function as both a data target and an InfoProvider. An InfoCube is a quantity of relational tables arranged according to the star schema: A large fact table in the middle surrounded by several dimension tables.

C)      Data Store Objects (DSO’s)[2 Dimensional]: This is like a flat table in normal DB terms .

D)     Multi providers: This is like view’s in normal data base terms. If you want to create data from two cubes, we will be using Multi Providers  . There is no physical data storage of data in Multi provider (Virtual)

E)      Info Sets : These are like JOINS in normal DB terms , Like Multi providers there is no physical data storage of data in Info sets (Virtual) .This brings intersection data from tables .

 Info providers :

An InfoProvider is an object which sends data for reporting .The below objects will be called as Info providers

·          InfoCubes

·          Data Storage Objects

·          Multi Providers

·         InfoSets