Bjarne Berg March 22 th, 2006 A billing analysis Data Warehouse University of North Carolina at Charlotte

2 What We will cover Requirement analysis Logical design Physical design Clean and integrating data Analysis Security design

3 This is a sales and billing data warehouse to meet the following requirements: Analyze sales by customer groups (key, value, preferred and quality)  What items are sold to what customer group by Universal Product Codes (UPC) and what payment term are used by the various sales organizations. Analyze plant utilization by shipment point and customer location  Are we using the right plants for sales to the customers, or are we cross shipping items (potential cost savings) Pricing analysis  Are different profit centers using substantial different pricing procedures and what are the impacts on Net sales, excluding allocated costs (aka “subtotal A”). Returns analysis  What material groups are most likely to be returned (see credit reason code), and are there differences between the plants, customer groups or material groups. Scope and Purpose

4 Functional specifications are real and given by International Paper

5 Hardware and Network The hardware and BW system is located in Houston Texas and owned by the mid-sized consulting firm MyITgroup Ltd. The source system is an SAP R/3 demo system located in India (Bangalore), owned by MyITgroup Ltd and loaded with sample demo data as provided by SAP. The Network access is through Citrix and VPN. The web-server located in Houston is doing the rendering of the web reports

6 What We will cover Requirement analysis Logical design Physical design Clean and integrating data Analysis Security design

7 Logical data model & enhancements Colored fields indicate enhanced fields to standard content

8 What We will cover Requirement analysis Logical design Physical design Clean and integrating data Analysis Security design

9 Data Mapping The data was mapped from the source to the transfer structure which was created using Application Link Enabler through Active Data Objects (ALE-ADO) The data was again mapped from the transfer structure (as stored in the persistent storage area- PSA) to the InfoObject in the InfoCube. A list of this mapping is enclosed below Similar mapping tables was completed for key figures, unit of measures and time characteristics

10 Navigational Attributes and Hierarchies The following navigational attributes and external hierarchies are available to the InfoCube as part of the standard content InfoObjectDescriptionNavigation attributes available? External hierarchy available? 0D_CO_CODECompany code Yes No 0D_COUNTRYCountry Yes No 0D_DIS_CHANDistribution channelNo 0D_DIVDivisionNo 0D_INDUSTRYIndustry code Yes No 0D_MATERIALMaterial Yes 0D_MTLGROUPMaterial group Yes No 0D_PROD_HIEProduct hierarchyNo Yes 0D_SALE_EMPSales employeeNo 0D_SALE_ORGSales organizationNo 0D_SOLD_TOSold-to party Yes No 0D_VERSIONVersionNo

11 What We will cover Requirement analysis Logical design Physical design Clean and integrating data Analysis Security design

12 ETL Processing Source: SAP, Sdn BW 2005 Masterdata extract programs - Customer - Material - Profit center Transactional extract programs - Billing document header - Billing document line items - Credit memos - Debit memos Dimensions data extracts - logistics - document details - accounting - organization (+ personnel) Other dimensions are derived from document data

13 What We will cover Requirement analysis Logical design Physical design Clean and integrating data Analysis Security design

14 Query, web template, exceptions, calculated key figure and MDX cache The BW queries was created using the Business Explorer (BEx) query designer tool from SAP, and published into a standard web template. Exception rules were written to identify orders where 25% of more of the items were returned by the customer. “Returned items’ is a calculated Key Figure (CKF) and is not physically stored in the infocube (structure). Through the use of the reporting agent tool, the global query is published to the MDX cache and the data set is therefore controlled by the OLAP engine for maximized speed when subsets of the query is executed

15 What We will cover Requirement analysis Logical design Physical design Clean and integrating data Analysis Security design

16 Pre-Delivered SAP BW Workbooks by Security Roles. Security is LDAP implemented Role based security that is shared with the transactional system and enforced through a web portal Pre-delivered queries to the Infocube use this security and the pre- delivered roles. The new queries has to associated to a base- role or a composit- role to assure that SSO is maintained. No new roles will be created as part of this project

17 Your Turn!!!