KX Session

For internal use only



Agenda SAP BW

• • • •

Introduction BW Architecture Data Extraction Presentation Layer

SAP BW - Introduction
• A Data Warehouse is a system which centrally provides data for analysis and controlling: – Extraction, transformation and load (ETL) of data – Analysis of the data – Presentation of the data – Data Warehouse Management

• Aims:
– Standardized structuring and presentation of all enterprise information – Highly developed reporting tool with self-service on all levels – Data provision from heterogeneous sources – Single point of entry

Agenda SAP BW • • • • Introduction BW Architecture Data Extraction Presentation Layer .

SAP BW architecture can be divided into three layers: • Source systems that provide the SAP BW system with data – Full integration with SAP components – Open architecture vis-à-vis external OLTP providers – SAP BW can be provided with target-oriented data from data providers (e. Dun & Bradstreet) – Data can be loaded from external relational database systems • The central administration area on the SAP BW server: – Staging engine – SAP BW databases • The Online Analytical Processing (OLAP) processor allows you to carry out multi-dimensional analyses of SAP BW data sets – BEx Analyzer – BEx Web Aplication – BEx Mobile Intelligence .SAP BW Architecture In principle.g.

Transformation. the process of loading data into the SAP BW is technically supported in different ways. .SAP BW – Architecture (II) Extraction. and Loading • Depending on the source systems and the type of data basis.

They contain two data types: – Characteristics – Key Figures • Master data is stored outside the InfoCubes in master data tables .SAP BW – Architecture (III) Star Schema and InfoCubes • The multi-dimensional model in SAP BW is based on the SAP BW star schema • InfoCubes serve as central data storage containers that form the basis for reports and analyses.

Agenda SAP BW • • • • Introduction BW Architecture Data Extraction Presentation Layer .

SAP BW – Data Extraction from SAP Source Systems ODS Object Master Data Texts InfoSource Communication structure Transfer structure Transfer structure DataSource Extract structure File SAP System .

Agenda SAP BW • • • • Introduction BW Architecture Data Extraction Presentation Layer .

whereas for each InfoCube. .SAP BW – Presentation Layer Business Explorer • The Business Explorer (BEx) is the reporting tool of SAP BW and consists of: – BEx Browser – BEx Analyzer (Excel-based) – BEx Query Designer • The Business Explorer allows the analysis of BW Data. • Queries always refer to exactly one InfoCube. as many queries as needed can be designed. • Individually designed queries highlight different views on the data and answer different business questions.

SAP BW – Presentation Layer BEx Query Designer • Ease-of use via drag & drop • Personalized access • Comfortable formula editor for calculations • access to any BW Data Provider • Windows-based component • Web interface for intuitive ad-hoc design & analysis .

SAP BW – Presentation Layer BEx Web Application Example Analysis of incoming orders Regions Monitoring Timetrends Budget Planning .


Agenda SAP APO  Main Functionalities  APO Architecture  APO Modules   Demand Planning Supply Network Planning .

interdependencies.) Optimization: Needed for solving of problems in decision-making:  Conflicting objectives. low inventory costs  high service levels  Huge number of decision alternatives  usage of heuristics and optimization models  Uncertainty about Future  Forecasting models . costs.Basics of Advanced Planning and Optimization APO  Advanced Planner and Optimizer Planning:  Huge number of decisions along a supply chain: which job? when? where? by whom?  Coordination of decisions necessary (interdependencies)  Planning = Preparation of decisions by collection and preparation of information (demand. e.g. capacities. etc.

relevant constraints and all alternatives) Forecasting Visibility of Planning Speed of Re-planning Basic Forecasting Low Visualisation Low Advanced Forecasting High visualization High .APO Main Functionality and Capabilities Key differences in planning capabilities between APS (APO) and ERP (R/3): CRITERIA Organizational Planning Type of Constraints Considered Optimization ERP Planning per Function (plant. warehouse…) Only some Constraints (capacities…) No Optimization APS Integrated Planning (for whole Supply Chain) Modelling of all relevant (bottleneck) Constraints Optimization (considering objective function.

Agenda SAP APO  Main Functionalities  APO Architecture  APO Modules   Demand Planning Supply Network Planning .

(Module 3) Available To Promise (Module 4) Transportation Planning (Module 5) Partner BW APO liveCache Customer Application Link Enabling OLTP Legacy OLTP Non R\3 OLTP Non R\3 OLTP . Planning+Schedul.APO Architecture SC Cockpit Infocubes Solvers Internet / EDI Demand Planning (Module 1) Supply Network Planning (Module 2) Product.

BOM .Integration of R/3 & APO R/3 Planned Order Sales Order    APO liveCache Planned Order Replenishment Order Time series & order network Update Production Order APO Material Master Location Production Model Production Order Material Master Client. Plant Routing.

Agenda SAP APO  Main Functionalities  APO Architecture  APO Modules   Demand Planning Supply Network Planning .

generates and aggregates data to create the most accurate forecast of customer demand.Overview Demand Planning Historical Data (from R/3 and BW) Market Intelligence APO Demand Planning Forecast APO Demand Planning collects. based on product historical sales pattern and future market intelligence. .Demand Planning .

How to clean history? Ja Fe Sp Ma Ap My Ju Jl Ag Events  Manual correction (events)  Promotion Planning (promotions) Ja Fe Sp Ma Ap My Ju Jl Ag Jan Sales History Events Corrected History 100 100 Feb 150 150 March April 100 100 160 160 May 140 140 June July August Sept 340 160 180 120 170 100 120 170 100 Corrected History Corrected History = baseline for forecast Ja Fe Sp Ma Ap My Ju Jl Ag . These non-representative values (outliers) can falsify the forecast results and must be corrected. values too high or too low can be found in the historical data. these picks and valleys will be reproduce in the future.Adjusting of Historical Data CLEAN HISTORY Sales History Due to situations ‘out of the norm’. Otherwise.

growth. PLC growth maturity discontinuation launch  Manual profile . especially in the launch and discontinuation phases. Demand planners need to take product lifecycle into account when forecasting.  Phase-out profile: Using a ‘phase-out profile’ it is possible to represent the discontinuation of a product.Consideration of Life Cycle Stage LIFECYCLE MANAGEMENT Different phases can be distinguish in a product lifecycle: launch. APO Demand Planning provides different tools to manage product life cycles: Phase-in profile: Using a ‘phase-in profile’ it is possible to represent the launch of a product. maturity and discontinuation.

Selection of Statistical Forecast Algorithem CHOOSE STATISTICAL ALGORITHM (forecast strategies) APO Demand Planning provides a wide range of statistical models that allows you to reproduce different time series patterns:  Trend demand  Seasonal demand  Seasonal trend demand  Intermittent demand  Automatic model selection How to select the best statistical model? 1st step) Gather historical and market intelligence data in order to identify demand behaviour (forecaster & product manager)  2nd step) Test which model better fits the expected demand pattern (forecast errors) .

APO Demand Planning Forecast APO Supply Network Planning Supply Network Planning . The supply chain planner can then use the demand plan as a basis for making sourcing.Sending Forecast to Supply Network Planning RELEASE TO Supply Network Planning (Module 2) This process makes the demand plan (forecast) available to the supply chain planner. deployment and transportation decisions.

Example of Forecasting with APO Demand Planning .

Agenda SAP APO  Main Functionalities  APO Architecture  APO Modules   Demand Planning Supply Network Planning .

Basics of Supply Network Planning Demand Plan Supplier Plant DC Customer  Mid-term Production-. Purchasing.and Transport Planning  Plans on basis of forecast figures from APO Demand Planning  SNP plans material flows along the supply chain  Priorization of demand  supply optimization .

Example of Supply Chain Network Plants Subcontractors Clients Distribution Centers Suppliers Ability to model the whole supply chain with constraints such as:  resource capacities  storage limits  safety stock  target stock levels  transportation capacities (TLB)  material availability .

Connections between Modeled Objects Elements of Supply Chain Supply Chain overview .

l Constraints: l Customer priority l Product priority Simultaneous product and resource planning l Production capacity Optimizer l Storage capacity l Transportation capacity l Lot sizes l Safety stock Result: Feasible orders.The Principle of the Optimizer The Principle of the Optimizer Demand-forecast. . priorities resources . stock transfers and purchase requisitions .

Example of Planning with Supply Network Planning .


Customer Life Cycle .

Material. Tools) Invoicing Reporting Marketing Internet Sales Pricing Catalog Basket Management Order Confirmation Order status and tracking Up/cross selling Internet Sales Internet Customer Sales Service CRM – BW Integration Mkt Campaign evaluation via BW Sales force activity monitoring Customer Analisys Internet Customer Self Service Customer Self Service Customer Care BW . Partner segmentation Service Installed Base Management Service Agreements Notifications Service Order Processing Management of Resources (Labour.SAP CRM Functions Mobile Sales Customer Info Visit Planning Vsit Management Visit report Contact person Competitive info Opportunities mySAP CRM Off Line MSA Mobile Sales Application Customer Interaction Customer Info Order Management Contact person Inbound/outbound calls DB info Script messages On Line IC Interaction Center Mobile Service Installed Base Calendar Service Process Service Confirmation Customer Info Product/Service Info MS Mobile Service Marketing Service Generating target list Executing call list Campaign Management Bus.

User Interface The Interaction Center offers two user interfaces working against the same CRM server: SAP GUI based HTML based WinClient WebClient .

Architecture .

Development of SAP CRM .

Sign up to vote on this title
UsefulNot useful