bw_2

1

Business Information Warehouse

Agenda

Section 1 MOR Process

Section 2 SAP BW Architecture: Overview

Section 3 SAP BW Terminology

Section 4 Executing Pre-MOR Report

Section 5 Using Extractor Checker

Section 6 BEx Analyzer: Overview

Section 7 Executing WWMOR Queries

2


ObjectivesAt the Completion of the Course, you will:

Understand the MOR generation process in Concord

“Understand” relevant concepts of SAP BW

Be able to describe the architecture of SAP BW

Be able to use the SAP R/3 Extractor Checker to review data replicated from R/3 to BW

Be able to execute Pre MOR report / SAP R/3 Reports

Be able to execute WWMOR report / BW queries

3


Section 1 MOR Process

4


5


MOR Data Integration in SAP R/3

COPA

SD

MM

BW

Sales Order/Billing Sales Forecast (SIS) Customer Price

Material Master Data

Sales Transaction Data Characteristics Key Figures

COPC

Product Costing

SD/MM/COPC -> COPA is a real time system interface (except SIS sales forecast data)

COPA to BW is a customized interface

BW Interface

COPA Interface

6


Section 2 SAP BW Architecture: OverviewIn principle, SAP BW architecture can be divided into three layers:

SAP R/3Transaction

System

System extract R/3 data by executing the extraction Program

Staging Area(For data cleansing)

BW Load data into a data model, called

(eg:ODS,InfoCube)

Users Workstation

User runs BW query to perform data analysis and ad hoc reporting

From the end user’s point of view. InfoCube and Query are the core of BW, operations performed in layer 1 and 2 are transparent to the end users.Store Master Data &

Transaction Data

7


MOR Conversion ODS

MOR Production ODS

Flat File (Converted MOR/

Budget e.g. WWMOR FY2004, WWMOR

Budget 2005)

SAP R/3(Transaction System)

Source System

SAP BW Server

BEx Analyzer

Regular Data ReplicationOne Time/Regular Data Upload

User run BW queries to perform data analysis and ad hoc reporting.

User may develop same set of BW queries from both BW objects and embedded them in the same workbook.

BW/MOR Design in Concord

8


Chapter 3 SAP BW Terminology

InfoCubes Operational Data Store InfoObject Characteristics Key Figures Query Workbook

9


What is an InfoCube ? InfoCube is a set of table linked together to store the consolidated / analytical

information

Enable user to perform multi dimensional analysis

It is made up of two elements:

Key figures : The quantitative data value, and

Characteristics : The dimension to describe the key figures

Example : A Sales InfoCube will enable user to access

Actual Sales amount,

COGS,

Sales Quantity

from the following perspective :

Material,

Sales Region,

Time

56

98

2834

56

13 8

6 53

Material 2

Material 1

Material 3

Reg 1 Reg 2 Reg 3

Q1Q2

Q3

10


What is an Operational Data Structure (ODS)?

Loading DateRecord No Year Date Material No. Customer No. Packaging Code Silk Screen Code Sales QuantitySales Amt2004.02.10 1 2004 1-Oct MM01 CU001 xxx ttt 10 4002004.02.10 2 2004 1-Oct MM02 CU002 xxx fff 3 4502004.02.10 3 2004 2-Oct MM01 CU003 yyy ttt 4 5002004.02.10 4 2004 2-Oct MM02 CU003 yyy rrr 1 700

Material No. Material Code Marketing Model Code Film Type File Speed Falsh TypeMM01 MG0001 Kaban 35mm 40 65FMM02 MG0001 Polariod 54mm 70 76F

Material Master Data

Customer No. Customer Name LocationCU001 Fuji File JapanCU002 Leica ItalyCU003 Sony Entertainment Japan

Customer Master Data

Transaction AttributeCaptured from COPAinterface

Key Figures Captured from COPA interface

Graphical Illustration of BW MOR ODS Data ObjectsGraphical Illustration of BW MOR ODS Data Objects

Unique Key to Differentiate eachData records

An ODS is used to stored consolidated and cleansed data (transaction data or master data for example) on a document level. ODS stores data in transparent, flat database tables.

11


What is an InfoObject ? InfoObjects are the “smallest available information modules” (= fields) in SAP

BW. They are business evaluation objects such as customers or sales revenue.

InfoObject can be uniquely identified with their technical name.

An InfoObject is divided into characteristics, key figures, units and time characteristics.

InfoObjects are used in InfoCubes & ODS objects.

12


What is Characteristic ? An evaluation group such as company code, product, customer type, fiscal

year, period or region.

Characteristics are dimensions to describe the key figures.

In Concord’s MOR ODS, the characteristics are mainly the non-quantitative data fields in our MOR report. (E.g. region, sales office, marketing model code, model type, material etc.)

What is Key Figure ? Values or quantities, such as sales revenue, fixed costs, sales quantity or

number of employees.

In Concord’s BW/MOR design, key figures correspond to the value fields in COPA.

13


What is a Query ? A query is a data evaluation based on the selection of characteristics and key

figures. This combination of characteristic selection and key figures is used to analyze InfoCube/ODS data for SAP BW.

Queries can be configured according to the way user wants to view and navigate through data.

Queries are defined in the BEx Analyzer and stored in the SAP BW server.

In Concord, we have created 8 WWMOR queries based on the format of the existing WWMOR reports.

What is a Workbook ? In BEx Analyzer, user can insert one or more SAP BW queries into a workbook.

A query can be inserted more than once into a workbook to display different views of the of data.

To facilitate the WWMOR generation, we could combine the 8 WWMOR queries into 1 workbook to avoid executing the 8 queries separately. All the data in the workbook will be refreshed automatically.

14


Section 4 Executing Pre-MOR Report

Pre MOR Selection Screen

Currency Type

Sales Office

Fiscal Year

Quarter

Period to

Sales Order Type

Additional Display Option Display Sales Order Number

ZSTD

2004

COPA Pre MOR Report

B0

4

4100

In SAP R/3: Transaction Code - ZCO01

Branch Supply chain will run Pre-MOR report daily, review with sales daily, and revise plan daily.

15


Field name Definition Possible Values (MOR related)

Currency Type (Mandatory Field)

Currency to be displayed on the report Note: Sale forecast data from SIS could only be displayed in B0 because it is the only currency type that the data is captured in COPA

10 (Company Code Currency)B0 (Operating Concern Currency)

Sales Office

(Mandatory Field)

Responsible branch in Concord 3100, 3300, 3400, 4100, 4200, 4300, 5100, 5300

Fiscal Year

(Mandatory Field)

Fiscal year 2004, 2005 etc.

Quarter

(Optional Field)

Quarter, user may choose to enter this field instead of Period

1, 2, 3, 4

Period

(Optional Field)

Fiscal Period, user may choose to enter this field instead of Quarter

1, 2, 3…12

Sales Order Type

(Mandatory Field)

Sales Document Types that support the predefined concord scenarios

ZSTD (Standard Sales Order)ZECS (End Customer Sample Sales)

Display Sales Order Number

(Optional Field)

Check this box if user want to display the SO# in the report

Note: Choosing this option would cause segregation of transactions sharing same price,

customer, product & period. It is recommended to click this box when reviewing

data for a particular order only

-

Definition of Report Selection Fields

16


Pre-MOR Report Demo

17


Section 5 Using Extractor Checker

In SAP R/3: Transaction Code – RSA3

Before data is replicated to SAP BW, user could preview the data to be replicated in SAP R/3 via Extractor Checker.

This step will be performed by US Finance as one of the main data quality assurance

procedure for the WWMOR!!

18


In SAP R/3: Transaction Code – RSA3

STEP 1: Enter DataSource (1_CO_PACCGP)

STEP 3: Press Extraction

STEP 2: Enter Data Selection Criteria

19


After Extraction is completed, a dialogue box will pop up showing the number of data records that matches with your data selection criteria:

STEP 4: Press Enter

STEP 5: Press Display List

20


The next screen will list the record that were extracted :

STEP 6: Double click each “Records” for each DataPacket to view the detail of record to be replicated to BW

21


The next screen will list the detail characteristic & key figures to be replicated to BW from the specified DataSource:

STEP 7 (Optional): User may select “Set Filter” or “Current…” to reformat the report to facilitate the data checking process

22


Field name (Short Text) Definition Possible values relating to MOR

Sales Document Type Sales Document Types that support the predefined concord scenarios

ZSTD (Standard Sales Order)ZECS (Sample Sales Customer)

Fiscal Year Fiscal year 2004, 2005 etc.

Period/year Fiscal period and year 2004010, 2004011, 2004012 etc.

Plan version (CO-PA) Allows the business to have multiple versions of data for operation and planning.

050 – SIS Sales Forecast Version0 – Operational

Record Type Indicates the source of posting and can be used to make reconciling easier and a split in reporting

A – Order (Actual & Plan depending on version chosen)F – Billing (Invoice)B – FI Direct Posting

Definition of the fields available in the Data Selection Criteria:Definition of the fields available in the Data Selection Criteria:

The Extractor Checker transaction consumes a vast amount of system resources, only use that when necessary (only for checking BW extraction data).

To facilitate the data checking process and minimize the system resource consumption, it is very important to enter relevant data selection parameter in “STEP 2: Enter Data Selection Criteria”. Refer to the table below for the definition of each field.

IMPORTANT !!!

23


Extractor Checker Demo

24


Section 6 BEx Analyzer: Overview

The top layer in the SAP BW architecture.

Serves as the reporting environment for end users.

BEx Analyzer is a Microsoft Excel-based interactive environment where analyses and queries are defined by selected characteristics and key figures.

The selected data can be analyzed by navigating through multi-dimensional data.

Presentation in Microsoft Excel allows users to take a report view and manipulate it as a document. We can perform further calculations, add charts or graphics using the Excel functionality.

What’s the FY2004 Total Gross Sales

for

?

25


Start BEx Analyzer BEx Analyzer can be launched from the Windows Start Start button.

Choose StartStart > Programs > Business Explorer > Analyzer

A dialog box informs you that C:\Program Files\SAP\FrontEnd\Bw\sapbex.xlaC:\Program Files\SAP\FrontEnd\Bw\sapbex.xla contains macros.

Choose Enable Macros

BEx Analyzer starts and displays Microsoft Excel with the SAP Business Explorer toolbar. BEx functionality is now active in Microsoft Excel.

26


How to execute a query from BEx Analyzer? To run a query , go to OpenOpen > QueriesQueries

Fill in the client number, user name and password, then press [OK].

Press “System” to choose the desired system environment. E.g. QAS, PRD, DEV

27


You are now connected to the BW system and ready to execute any query.

Click on the InfoAreasInfoAreas icon, and breakdown the MOR BW ProductionMOR BW Production node till the bottom level. All available queries will be displayed.

Press this button to view the technical names of the queries

Highlight the desired query and click OK OK. System will then execute the query.

28


Define, Check and Save a New Query Step 1: in the BEx toolbar, choose Open > QueriesOpen > Queries

Step 2: To create a new query, select the desired ODS (e.g.MOR Production ODS). Choose NewNew.

29


Step 3: To define the rows, drag and drop the desired characteristics into the RowsRows frame.

30


Step 4: To define the columns, drag and drop the desired key figure into the ColumnsColumns frame.

User may also choose Calculated Key Figure or Restricted Key Figures

Calculate Key Figure are formulas that consist of basic key figure for the InfoCube/ODS

Restricted Key Figures are basic key figures for the InfoCube that are restricted or filtered by one or more characteristic selections

31


Step 5: To define the free characteristics, drag and drop the desired characteristics to the Free characteristicsFree characteristics frame.

Select the characteristics into the “Free Characteristics” frame so that you can add them to the drilldown when you navigate in the query

These 6 “Data Fields” must be exist in each query in order to obtained a correct WWMOR

data

32


Step 6: Check the new query, choose Check QueryCheck Query.

If the query definition is correct, a message with “Query is Correct” will be displayed here.

33


Step 7: Save the new query

On Query Designer, choose Save QuerySave Query.

On Save QuerySave Query dialog box, enter “Description”

On Save QuerySave Query dialog box, enter a “Technical Name” begins with the naming convention ZUSR_XXX. E.g. ZUSR_SALES.

Press SaveSave

34


Change Query Step 1: Choose Open > Queries, Open > Queries, highlight the query to be modified, press

ChangeChange

35


Step 2: Choose the modification as needed

Step 3: After changes completed, choose Quit and Use QueryQuit and Use Query

Step 4: On Save Save dialog box, press YesYes to save the changes

You can drag & drop the desired characteristics & key figure and see the changes in preview area

36


Copy Query You may save (copy) queries under a different name by using Save query asSave query as

function available on the query definition toolbar.

Step 1: Choose Open > Queries, Open > Queries, highlight the “source” query, press ChangeChange

37


Step 2: Press Save query asSave query as to copy the existing query to a new query

38


Step 3: On Save query asSave query as dialog box, enter “Description”and a “Technical Name” begins with the naming convention ZUSR_XXX. E.g. ZUSR_SALES.

Press Save Save and modify the new query as needed.

39


BEx Analyzer Demo

40


Section 7 Executing WWMOR Queries

We have created 8 sets of WWMOR Queries in the “MOR Production ODS”.

The “MOR Production ODS” data will be replicated weekly on every Sunday 9am HKT.

After each replication, a new “MOR Version” will be created to capture that particular ‘picture’ of MOR data. E.g. 20040628, 20040705 (this is equivalent to our As Is MOR “Report Run” field)

User may compare data across different “MOR Version” using the predefined WWMOR queries or create their own queries for analysis.

There are some data fields that MUST be exist in each query in order to obtained a correct MOR data due to the way that COPA and BW records data.

41


MOR Record Status

Order, Invoice, Projection, SD Adjustment, FI Adjustment

Currency Type

Fiscal Year

MOR Version

Field Name Possible ValuesConsequence if not filtered or entered

If we did not filter Order and Invoice status transaction, data will be duplicated

B0 (Group Currency USD) or 10 (Company Code Currency

COPA record each transaction in 2 different currencies, we need to choose only 1 currency type to avoid data duplication

Z1/2004 or Z1/2005Data will be lumped together across different year

MOR report run date e.g. 20040628, 20040705

Data will be lumped together across different MOR version

Following are the list of “Data Fields” that must be entered or filtered in each query in order to obtained correct WWMOR data:

Choose Period or Week as well If the analysis is by “Period” or “Week”Choose Period or Week as well If the analysis is by “Period” or “Week”

Quarter 1, 2, 3 or 4Data will be lumped together across different quarter

42


WWMOR Queries Demo

43


How to execute WWMOR “#1 Net Sales Variance Summary by Region & Branch”? Step 1: Highlight the desired query and Press OK

44


Step 2: Enter Currency Type

Since WWMOR is reported in Group Currency “USD”, B0 (Operating concern currency) is set as a default entry.

45


Step 3: Enter MOR Version

Press this button to view the available values of the MOR Version

Select 2 versions for comparison

Press this button after replication to display the new MOR version “values”

46


Step 4: Enter Quarter

Press this button to view the available values of the Quarter or the Multiple Selection button on the right

Select 2 versions for comparison

Press Execute

47


Step 5: Execute the query

Microsoft Excel displays the query.

A query consists of the filter cells and the result area.

Filter cells

Result area

48


Step 6: Set filter value for fiscal year

This is a mandatory step to restrict the data to be shown This is a mandatory step to restrict the data to be shown in the query belongs to the fiscal year that you are in the query belongs to the fiscal year that you are analyzing.analyzing.

Place cursor on the field “Fiscal Year” > Right click > Select filter valuePlace cursor on the field “Fiscal Year” > Right click > Select filter value

On the “Selection for Fiscal Year” dialog box:

Pull the fiscal year for analysis to the “Selection” on the right, press OK

49


The filtered result will be displayed on the Excel

50


51


SummaryYou are now able to:

Describe the architecture of SAP BW

“Understand” relevant concepts of SAP BW

Use the Extractor Checker to review data to be replicated to BW from R/3

Execute the Pre MOR report

Execute the WWMOR queries

Write a new query, copy or change an existing query

bw_2

Documents