10/22/08

Process Chain Creation using SAP BW 3.5

Process chains are used extensively in SAP Business Warehousing for executing loads, running reports
etc. sequentially or parallel.
There can be number of steps with in a process chain. You can also decide what has to be done incase
a particular step fails. In case of failure you can decide to sent notification email to concern person
who can correct the issue.

In this section we will see how to create a process chain using SAP BW 3.5. Using this process chain we
will load data in Infocube.

1) Execute transaction RSPC

2) Press 'Create', enter 'Name' and 'Description' of the process chain, press 'Continue'

3) First step in the process chain will be a 'Start'

step,
press 'Create' to create a process variants

4) Enter 'Name' and 'Description' of the process

variant

5) 'Save' process variant and go back, 'Change

selections' is used to schedule the process chain, we will revisit this again later

6) Press 'Continue'
 7) Select the InfoPackage which is used to load
data in
Infocube, drag InfoPackage to right panel

8) Select the process variants as InfoPackage using

fucntion key F4

9) Select the InfoPackage ZAAA and press

'Continue'

10) Following steps will be added in the process

chain

11) Join 'Start' step with step 'Indexes' by selecting

'Start' step and
dragging the line to 'Indexes'

12) Go back to 'Start' step and right click to

'Maintain Variant'

13) Select 'Immediate' to schedule the process

chain immediately
 14) 'Check' the process chain and 'Activate' the
process chain

15) Execute the process chain, enter the server

name in the following screen

16) Process chain will start executing, to check

the status, Press
 17) Select 'Yesterday and Today' to check the
status of the process chain

18) Following screen shows that load is still not completed

19) Once completed, the status will appear as follows,

incase there is any failure, the status will appear as cancelled
Posted by prasheel Reddy at 9:55 PM 

1 comments:

manoj said...

excellent prasheel.....its very useful

January 6, 2010 12:53 AM

Post a Comment

Page break by AutoPager.  Page(    2    ).              LoadPages

10/22/08
Open Hub Service using SAP BI 7.0
Open Hub Destination functionality is used to distribute data from SAP BI to other non-SAP data
systems. In earlier version, it was part of InfoSpoke but in SAP BI 7.0 this can be used independently.

In this section, we will see, how data is extracted from SAP BI InfoCube to a .csv file on a desktop.

1) Execute transaction RSA1, Press 'Open Hub Destination'

 2) Select InfoArea and right click to 'Create Open Hub Destination

3) Enter Name and Description

4) Go to 'Destination' tab, enter Destination Type

as 'File type'. In this example, we will be exporting data in a .csv file, select Directory to 'Desktop'

5) Go to 'Fields Def.' tab, select the InfoObjects

you would like to have in your exported file
 6) Activate the Open Hub Destination by pressing
'Activate' button

7) Select the Open Hub Destination and right click

to 'Create Transformation'

8) Enter source of transformation as InfoCube

9) Accept the proposed mapping and activate

10) Create Data Transfer Process for transfering

data from InfoCube to Desktop as .csv file
 11) Enter source of DTP as InfoCube

12) Activate DTP and Execute, Data will be

exported to .csv file which will be stored at desktop

13) Press 'Yes' to check the status of request

monitor

14) Data is exported as the monitor status is green

 15) Check the exported file at desktop

Posted by prasheel Reddy at 1:15 AM 

Labels: Reporting, SAP BW Frequently Asked Question

0 comments:

Post a Comment

Page break by AutoPager.  Page(    3    ).              LoadPages

10/22/08
Open Hub Service using SAP BW 3.5
Open Hub Service functionality in SAP BW is mainly used with InfoSpoke.
InfoSpoke is an object for exporting data. InfoSpoke is defined using a data source (from which data is
extracted), extraction mode and destination (where data will be stored).In this section, we will see,
how data is extracted from SAP BW InfoCube to a .csv file on a desktop.
1) Execute transaction RSA1, 'Tools' -> Open Hub Service -> Edit InfoSpoke
 2) Enter name of InfoSpoke and press 'Create'

3) Enter short description and select the Data

Source as 'InfoCube'

4) Select Extraction Mode as 'Full'

 5) Go to 'Destination' tab, enter short description. In
this example, we will be exporting data in a .csv file, select the 'File' and chose 'Directory'

6) Go to 'InfoObjects' tab, select the InfoObjects you

would like to have in your exported file
 7) Go to 'Selection' tab, enter if you want a
particular selection criteria, in this example there is no selection used.

8) Activate the InfoSpoke by pressing 'Activate'

button
 9) After activation, source structure will appear
as follows

10) Go back and display the InfoSpoke, press

'Dialog' button
 11) Data will be exported to .csv file which will be
stored at desktop

12) Go to InfoSpoke Monitor to check status of

export

13) Data is exported as the monitor status is green

14) Check the exported file at desktop

Posted by prasheel Reddy at 1:07 AM 

Major Difference between SAP BI 7.0 and SAP BW 3.5

1) Administrator Workbench is renamed as Data Warehousing Workbench.

2) There are additional modeling options available at left hand side panel in
transaction RSA1 as shown below. The additions are 'DataSources' and 'Open Hub
Destination'.

3) The functions of the InfoPackage tree are fully covered by process chains.

4) Process Chains are used instead of Event Collector.

5) The 'Remodelling' transaction help you add Key Figures and Characteristics
in a Infocube while handling historical data effectively.

6) Infocubes can be included in Infosets.

7) Transformation is used instead of update and transfer rules.

8) ODS objects have been renamed as DataStore Objects.

9) You can access objects till InfoPackage directly from InfoCube as shown
below.

Common SAP BW Transactions

Following are most commonly used SAP BW Transactions

1) SBIW: Data Transfer to SAP BW

2) RSA1: Admin Workbench Modelling
3) RSZV: Maintain Variable for BEx Analyser
4) RSSM: BW Authorization
5) RSO2: Maintain Generic Data Sources
6) RSA7: BW Delta Queue Maintenance
7) RSA3: Data Extractor Check
8) RSA5: Installation of Data Sources from Business Content
9) LISTCUBE: To display content of Info Providers
10) RSCUSTA: Set User ID for Source System Communication
11) RSKC: Permitted Characters
12) SNUM: Number ranges for Transfer Structure
13) SM62: Define Event
14) RSMO: Evaluation of Requests

General SAP Transactions:

1) SE11: ABAP Dictionary (Create, Change, Display Table, View, Data Elements,
etc.)
2) SE16: Data Browser for Table and View
3) SU01: User Maintenance
4) PFCG: Role Maintenance
5) SPRO: Customizing
6) SE80: Object Navigator
7) SE93: To check transaction codes available
8) STMS: Transport Management
9) SE09: Transport Organiser
Naming Convention in SAP BW
SAP BW has a naming convention related to its objects.

SAP BW prefixes /BIO/ to the names of Business Content database objects. It prefixes /BIC/ to the
database objects created by users.

If a user creates characteristics type info object ZPRODUCT and activates it, information will be stored
in following:

Data element: /BIC/IOZPRODUCT
SID table: /BIC/SZPRODUCT
Master data table: /BIC/PZPRODUCT
Text table: /BIC/TZPRODUCT
View: /BIC/MZPRODUCT

When an info cube ZSALES is created and activated, information will be stored in following:

View Fact table: /BIC/VZSALESF

Transparent Fact table: /BIC/FZSALES
Dimension tables: /BIC/DZSALES1 to /BIC/DZSALESN where N being no. of dimensions
/BIC/DZSALESP, /BIC/DZSALEST, /BICDZALESU for Data Packet, Unit & Time (maximum 16 dimensions
possible, 3 reserved for P, T & U)

If a hierarchy is used in an info object ZDATE, following tables will be created:

Hierarchy table: /BI0/HZDATE
Hierarchy SID table: /BI0/KZDATE
SID hierarchy structure: /BI0/IZDATE
HierInterval table: /BI0/JZDATE

Questions Answers on SAP BW

Questions Answers on SAP BW

What is the purpose of setup tables?

Setup tables are kind of interface between the extractor and application tables. LO extractor takes data
from set up table while initalization and full upload and hitting the application table for selection is
avoided. As these tables are required only for full and init load, you can delete the data after loading in
order to avoid duplicate data. Setup tables are filled with data from application tables.The setup tables sit
on top of the actual applcation tables (i.e the OLTP tables storing transaction records). During the Setup
run, these setup tables are filled. Normally it's a good practice to delete the existing setup tables before
executing the setup runs so as to avoid duplicate records for the same selections

We are having Cube. what is the need to use ODS. what is the necessary to use ODS though we are having
cube?

1) Remember cube has aggregated data and ods has granular data.
2) In update rules of a infocube you do not have option for over write whereas for a ods the default is
overwrite.

What is the importance of transaction RSKC? How it is useful in resolving the issues with speial
characters.

How to handle double data loading in SAP BW?

What do you mean by SAP exit, User exit, Customer exit?

What are some of the production support isues-trouble shooting guide?

When we go for Business content extraction and when go for LO/COPA extraction?

What are some of the few infocube name in SD and MM that we use for extraction and load them to BW?

How to create indexes on ODS and fact tables?

What are data load monitor (RSMO or RSMON)?

1A. RSKC.

Using this T-code, you can allow BW system to accept special char's in the data coming from source
systems. This list of chars can be obtained after analyzing source system's data OR can be confirmed with
client during design specs stage.

2A. Exit.s

These exits are customized for handling data transfer in various scenarios.
(Ex. Replacement Path in Reports- > Way to pass variable to BW Report)
Some can be developed by BW/ABAP developer and inserted wherever its required.

Some of these programs are already available and part of SAP Business Content. These are called SAP
Exits. Depends on the requirement, we need to extend some exits and customize.

3A.

Production issues are different for each BW project and most common issues can be obtained from some
of the previous mails. (data load issues).
4A.

LIS Extraction is kind of old school type and not preferred with big BW systems. Here you can expect
issues related to performance and data duplication in set up tables.

LO extraction came up with most of the advantages and using this, you can extend exiting extract
structures and use customized data sources.

If you can fetch all required data elements using SAP provided extract structures, you don't need to write
custom extractions... You can get clear idea on this after analyzing source system's data fields and
required fields in target system's data target's structure.

5A.

MM - 0PUR_C01(Purchasing data) , OPUR_C03 (Vendor Evaluation)

SD - 0SD_CO1(Customer),0SD_C03( Sales Overview) ETC..

6A.

You can do this by choosing "Manage Data Target" option and click on few buttons available in
"performance" tab.

7A.

RSMO is used to monitor data flow to target system from source system. You can see data by request,
source system, time request id etc.... just play with this..

What is KPI?

A KPI are Key Performance Indicators.

These are values companies use to manage their business. E.g. net profit.

In detail:

Stands for Key Performance Indicators. A KPI is used to measure how well an organization or individual
is accomplishing its goals and objectives. Organizations and businesses typically outline a number of KPIs
to evaluate progress made in areas where performance is harder to measure.

For example, job performance, consumer satisfaction and public reputation can be determined using a set
of defined KPIs. Additionally, KPI can be used to specify objective organizational and individual goals
such as sales, earnings, profits, market share and similar objectives.

KPIs selected must reflect the organization's goals, they must be key to its success, and they must be
measurable. Key performance indicators usually are long-term considerations for an organization