1 / 51

Agenda

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

leonora
Download Presentation

Agenda

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 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. Objectives At 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. MOR Data Integration in SAP R/3 • SD/MM/COPC -> COPA is a real time system interface (except SIS sales forecast data) • COPA to BW is a customized interface COPC SD • Product Costing Historical WW MOR • Sales Order/Billing • Sales Forecast (SIS) • Customer • Price • Sales Transaction Data • Characteristics • Key Figures COPA BW Pre MOR Report • Material Master Data MM BW Interface COPA Interface

  5. Section 2 SAP BW Architecture: Overview In principle, SAP BW architecture can be divided into three layers: 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. 2. SAP BW Server SAP R/3 Transaction System System extract R/3 data by executing the extraction Program Store Master Data & Transaction Data 3. BEx Analyzer (MS Excel) Staging Area (For data cleansing) 1. Source System Users Workstation BW Load data into a data model, called (eg:ODS,InfoCube) User runs BW query to perform data analysis and ad hoc reporting InfoProvider

  6. BW/MOR Design in Concord Flat File (Converted MOR/ Budget e.g. WWMOR FY2004, WWMOR Budget 2005) SAP R/3 (Transaction System) Source System One Time/Regular Data Upload Regular Data Replication SAP BW Server MOR Conversion ODS MOR Production ODS • 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. BEx Analyzer

  7. Chapter 3 SAP BW Terminology • InfoCubes • Operational Data Store • InfoObject • Characteristics • Key Figures • Query • Workbook

  8. Q3 Q2 Q1 56 34 28 Material 1 Material 2 13 8 98 Material 3 56 6 53 Reg 1 Reg 2 Reg 3 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 fromthe following perspective : • Material, • Sales Region, • Time

  9. What is an Operational Data Structure (ODS)? • 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. Graphical Illustration of BW MOR ODS Data Objects Material Master Data Unique Key to Differentiate each Data records Transaction Attribute Captured from COPA interface Key Figures Captured from COPA interface Customer Master Data

  10. 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.

  11. 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.

  12. 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.

  13. Branch Supply chain will run Pre-MOR report daily, review with sales daily, and revise plan daily. In SAP R/3: Transaction Code - ZCO01 Section 4 Executing Pre-MOR Report COPA 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 B0 4100 2004 4 ZSTD

  14. Definition of Report Selection Fields

  15. Pre-MOR Report Demo

  16. Section 5 Using Extractor Checker Before data is replicated to SAP BW, user could preview the data to be replicated in SAP R/3 via Extractor Checker. In SAP R/3: Transaction Code – RSA3 This step will be performed by US Finance as one of the main data quality assurance procedure for the WWMOR!!

  17. In SAP R/3: Transaction Code – RSA3 STEP 1: Enter DataSource (1_CO_PACCGP) STEP 2: Enter Data Selection Criteria STEP 3: Press Extraction

  18. 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

  19. 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

  20. 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

  21. IMPORTANT !!! • 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. Definition of the fields available in the Data Selection Criteria:

  22. Extractor Checker Demo

  23. What’s the FY2004 Total Gross Sales for ? 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.

  24. Choose Enable Macros Start BEx Analyzer • BEx Analyzer can be launched from the Windows Start button. • Choose Start > Programs > Business Explorer > Analyzer • A dialog box informs you that C:\Program Files\SAP\FrontEnd\Bw\sapbex.xla contains macros. • BEx Analyzer starts and displays Microsoft Excel with the SAP Business Explorer toolbar. BEx functionality is now active in Microsoft Excel.

  25. How to execute a query from BEx Analyzer? • To run a query , go to Open > Queries • 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

  26. Press this button to view the technical names of the queries You are now connected to the BW system and ready to execute any query. • Click on the InfoAreas icon, and breakdown the MOR BW Production node till the bottom level. All available queries will be displayed. • Highlight the desired query and click OK. System will then execute the query.

  27. Define, Check and Save a New Query • Step 1: in the BEx toolbar, choose Open > Queries • Step 2: To create a new query, select the desired ODS (e.g.MOR Production ODS). Choose New.

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

  29. 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 • Step 4: To define the columns, drag and drop the desired key figure into the Columns frame. User may also choose Calculated Key Figure or Restricted Key Figures

  30. These 6 “Data Fields” must be exist in each query in order to obtained a correct WWMOR data • Step 5: To define the free characteristics, drag and drop the desired characteristics to the Free 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

  31. Step 6: Check the new query, choose Check Query. If the query definition is correct, a message with “Query is Correct” will be displayed here.

  32. Step 7: Save the new query • On Query Designer, choose Save Query. • On Save Query dialog box, enter “Description” • On Save Query dialog box, enter a “Technical Name” begins with the naming convention ZUSR_XXX. E.g. ZUSR_SALES. • Press Save

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

  34. Step 2: Choose the modification as needed • Step 3: After changes completed, choose Quit and Use Query • Step 4: On Save dialog box, press Yes to save the changes You can drag & drop the desired characteristics & key figure and see the changes in preview area

  35. Copy Query • You may save (copy) queries under a different name by using Save query as function available on the query definition toolbar. • Step 1: Choose Open > Queries, highlight the “source” query, press Change

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

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

  38. BEx Analyzer Demo

  39. 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.

  40. Currency Type 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: Consequence if not filtered or entered Field Name Possible Values COPA record each transaction in 2 different currencies, we need to choose only 1 currency type to avoid data duplication B0 (Group Currency USD) or 10 (Company Code Currency MOR report run date e.g. 20040628, 20040705 Data will be lumped together across different MOR version If we did not filter Order and Invoice status transaction, data will be duplicated Order, Invoice, Projection, SD Adjustment, FI Adjustment MOR Record Status Data will be lumped together across different year Z1/2004 or Z1/2005 Fiscal Year Data will be lumped together across different quarter 1, 2, 3 or 4 Quarter Choose Period or Week as well If the analysis is by “Period” or “Week”

  41. WWMOR Queries Demo

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

  43. Step 2: Enter Currency Type Since WWMOR is reported in Group Currency “USD”, B0 (Operating concern currency) is set as a default entry.

  44. Press this button to view the available values of the MOR Version • Step 3: Enter MOR Version Select 2 versions for comparison Press this button after replication to display the new MOR version “values”

  45. 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

  46. 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

  47. Step 6: Set filter value for fiscal year Place 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 This is a mandatory step to restrict the data to be shown in the query belongs to the fiscal year that you are analyzing.

  48. The filtered result will be displayed on the Excel

More Related