Integration BW-BPS Overview

Integration BW-BPS, CRManalytics and APO-DP
Inga Wiele
Product Manager BI SAP NetWeaver PM
Scope of this presentation

This session is focussing on collaborative planning in the BW environment. R/3 planning is only covered peripherally. After attending this session you will: be able to explain the scope of the different planning tools offered by SAP which facilitate BW functionality understand the basic concepts of integrating financial, sales and production planning using BW-BPS and APO be aware of the opportunities and limitations in integration scenarios know different landscape alternatives and be able to apply them to your existing landscape take first steps towards your own collaborative planning scenario.
SAP AG 2004, Title of Presentation / Speaker Name / 2
Content
Business Challenges Scope of different planning tools* BW-BPS, CRManalytics, APO Integration Features How to achieve integration of the BW-based planning tools Summary
* focus on SAP BW environment

Keeping control of strategic goals

Strategic targets must be broken down to operational goals
Board of directors
Increase Return on Investment ROI = (Sales Costs) / Capital Invested
Production
Finance Sales
Optimize production utilization

Reduce overhead costs
Increase sales volume
Different/Competing targets
Goals of different areas may compete
Profit Goals
St t
Production
production planning
capacities / materials
purchase planning Purchase
quantity / purchase prices
sales planning Sales
quantity / revenues
$
Product Cost Cost Center
product cost planning
product prices / cost of goods sold & manufactured
cost center planning
activity prices / budget
Integrated planning cycle
Strategic Planning and Target setting on group level
Operational Planning and Budgeting in the business units
Plan evaluation
Headcountplanning
Reconciliation of operational plans with strategic targets Production planning
Operational Planning
Sales planning Strategic Targets (z.B. Operating Profit + 4%, Market share+10%) August
Marketing planning
Strategic Planning
December
Heterogeneous planning landscapes

Different planning tasks are supported with different tools
Missing link between master data and transactional data No integration between different planning applications Many interfaces Lack of coordination tools (process control)
Procurement Plan Investment Plan Financial Plan Financial Reporting
Profitability Plan
Sales Plan
Sales Reporting
Marketing Plan Production Plan Production Reporting
HR Plan
Content

Opportunities offered by SAP planning products

SAP offers modules that complement to a closed loop planning..e.g. APO Supply Network Planning Demand Planning Sales qty (unconstrained)
Sales qty (constrained) Cost of Goods (fix/variable)
BW-BPS Profit Planning Profitability Targets
CRManalytics Sales Planning
Marketing costs
Sample Planning Scenario

1) Top-down financial target setting on business units 2) Bottom-up mid-term sales planning (sales-oriented: restrictions are not considered) 3) Bottom-up mid-term sales planning (logistics-oriented: capacity restrictions are considered 4) Rolling short-term sales planning 5) Rolling short-term Production planning 6) Link to sales order processing (Logistics & Production Execution) 7) Plan-Actual comparison
Planning across organizational boundaries

BW-BPS Financial Planning Planning in CRM APO Supply Chain Planning
Profit Planning Cost Planning Investment Planning Balance Sheet Planning Value Based Planning
Sales Planning & Forecasting Accounts Partners Opportunities Promotions Territories Marketing & Campaigns Services
Demand Planning
Supply Network Planning Transportation Planning
Integrated planning across applications
mySAP mySAP ERP ERP
mySAP mySAP CRM CRM
SAP SAP Industry Industry Solutions Solutions
SAP NetWeaver BI
SAP SAP ... ... Custom-built Custom-built applications applications
SAP NetWeaver BI provides the platform for integrated planning across heterogeneous business applications for cross functional Legacy Legacy business planning. System System
What is BW-BPS?
With BW-BPS (Business Planning and Simulation), SAP delivers tools for generic planning supporting a planning process that allows to build a planning model which integrates global strategic planning and specific operational planning problems in a closed loop process, with a strong focus on business processes across the enterprise. This functionality brings together planning, budgeting, and forecasting with monitoring, reporting, and analysis, bundled into one software installation and one support package cycle.
BPS helps you to plan, budget, and forecast by providing functions such as: Top-down planning and bottom-up contribution with a rich set of planning functions A planning framework that lets you create and maintain planning models An user interface for manual planning and analysis Tools for process control (i.e. status tracking and monitoring)
CRMa: Analytical Scenarios
Analytical Scenarios provide you with predefined packages and content, which contribute the appropriate Insights to drive customer-centric processes
CRM Analytics - Overview

Strengths of Analysis and Planning with mySAP CRM
CRM Analytics is based on an established and scalable BI solution Prepackaged analytical applications cover all relevant business questions relating to CRM Portal integration together with strong web publishing functionality support easy distribution of information Data reliability and consistency is guaranteed by a common world of metadata and extractors Comprehensive predictive intelligence supports prospective analysis A broader perspective of corporate data helps you to connect and link your insights beyond CRM with SCM, Financials, HR, and so on Tight business process integration with operational CRM Ready-to-run Business Content CRM Analytics is embedded in a company-wide business planning solution, as well as in a business analytics and strategy management solution
How do BW-BPS and CRManalytics work together?

BW-BPS offers generic functions to
Modelling Manual planning Automatic planning Process coordination
BW-BPS is the planning platform for CRManalytics CRManalytics delivers

preconfigured planning content additional CRM specific functionality based on the modelling and processing features of BW-BPS
What is SAP APO?

SAP Advanced Planner and Optimizer (APO) Supports network-oriented planning and optimization Provides flexible and adaptive advanced planning capabilities that support the full spectrum of supply planning requirements Integrates and synchronizes supply planning and execution information for timely decision-making Integrates supply planning with other network processes (e.g., CRM, SRM, PLM)
APO-DP is the integration point to BW based planning
Main SAP APO planning applications:

Demand Planning (DP) Supply & Distribution Planning (SNP & CTM) Production Planning & Detailed Scheduling (PP/DS & CTM) Transportation Planning & Vehicle Scheduling Global Available to Promise (GATP)
APO-DP: Overview
APO Demand Planning helps you match required supply with demand through state-of-the art capabilities that include:
Multilevel planning support: View, forecast and plan product demand at any stage, from initial concept to final manufacturing. Complex forecasting support: Leverage onlinge analytical processing to handle your most complex forecasting challenges. Create, manage and integrate multiple forecasts, promotions and budget plans. Data analysis: View demand data in planning tables or graphics, using slice and dice and bill of material explosion options. Statistical forecasting support: Use a comprehensive toolbox of proven forecasting methods and develop forecasts based on up to the minute data. Promotional support: Plan, track, manage and support trade promotion programs to improve effectiveness and predictability
APO-DP - Summary
Business benefits / value:
Planning of complete supply chain incl. partners (e.g. retailer, supplier) Planning based on business structures (Bill of material, worklist) Inventory reduction Resource balancing Cost reduction Increased customer satisfaction
Planning methods:
Network-oriented (e.g. Bill of material) Forecasts based on historical data Promotion planning
BW-BPS Architecture: Overview

SAP Enterprise Portal
Frontend Clients
SAP BW-BPS
Planning Planning Folders Folders Web Web Interfaces Interfaces Interface Interface for for CRManalytics CRManalytics
API
BPS Planning Workbench
Planning Methods (Layouts, Functions) Planning Area, Planning Level, Planning Package
SAP BW
OLAP Database
Plan Data
Master Data
BW-BPS Architecture: Overview

SAP Enterprise Portal
Frontend Clients
SAP BW-BPS
Planning Planning Folders Folders Web Web Interfaces Interfaces Interface Interface for for CRManalytics CRManalytics
API allows to enhance standard BPS user interfaces or to build own user interfaces
API
Planning Area covers 1 InfoCube, multi planning area groups several planning areas BPS Planning Workbench
Planning methods work in all types of planning areas and may e.g. copy data from one planning area to another
Planning Methods (Layouts, Functions) Planning Area, Planning Level, Planning Package
SAP BW
Planning Area can read and write on transactional InfoCubes and just read from nontransactional InfoCubes
OLAP Database
Transactional InfoCube
Plan Data
Master Data
Comparison aspects: BW-BPS

Task
Bottom-up mid-term sales planning (sales-oriented: restrictions are not considered Bottom-up mid-term sales planning (logistics-oriented: capacity restrictions are considered Rolling short-term sales planning Rolling short-term Production planning Link to sales order processing (Logistics & Production Execution Plan-actual comparison
Planning Tool
CRMa /BWBPS APO
The main benefit of BW- BPS is its generic nature: almost any planning application may be built. Compared to APO it offers value based planning (incl. calculation with prizes), simulation with independent KPIs and currency translation. BW-BPS is the integration basis for sales planning in the financial plan. In addition BW-BPS offers workflow coordination and monitoring of the overall planning process. Compared to APO-DP the main difference is that there is no network typical calculation (e.g. Bill of material explosion).
CRMa/ BWBPS APO APO BW
BW-BPS is the basis for CRM analytics (CRMa).

CRManalytics (CRMa) Architecture: Overview

SAP Enterprise Portal SAP BW-BPS
Strategic Strategic Service Service Planning Planning
SAP CRM Application Server

Marketing Marketing & & Campaign Campaign Planning Planning Trade Trade Promotion Promotion Planning Planning Opportunity Opportunity Planning Planning
Sales Sales Planning Planning & & Forecasting Forecasting
CRM / BW Mapping
CRMa Planning Services BW-BPS Planning Workbench

SAP BW
Plan Data Master Data
Enhanced Layouts
BPS Layouts
CRManalytics (CRMa) Architecture: Overview

SAP Enterprise Portal SAP BW-BPS
Strategic Strategic Service Service Planning Planning
CRManalytics specific user interface embedded in CRM application
SAP CRM Application Server

Marketing Marketing & & Campaign Campaign Planning Planning Trade Trade Promotion Promotion Planning Planning Opportunity Opportunity Planning Planning
Sales Sales Planning Planning & & Forecasting Forecasting
Planning applications (BWBPS preconfigured for sales planning purposes)
CRM / BW Mapping Enhanced Layouts
CRMa Planning Services BW-BPS Planning Workbench

SAP BW
Plan Data Master Data
BPS Layouts
Additional CRM specific planning functionality
Comparison aspects: CRM analytics

Task
Planning Tool
CRMa /BW-BPS APO
CRManalytics delivers preconfigured planning content focussing on display and planning of the market point of view based on BWBPS. Additional CRM specific functionality includes frontend distribution functionalities and complex customer hierarchies (Business Partner). Direct integration to CRM business partner master data. The enhanced BPS planning layouts of CRManalytics are embedded in the CRM promotion management (campaign planning).
CRMa/ BW-BPS APO APO BW
CRManalytics is fully based on the modelling and processing features of BW-BPS.

CRManalytics: BW-BPS + CRM specific functions
CRManalytics is fully based on BW-BPS architecture CRManalytics offers additional functionality focussing on CRM related tasks (enhanced BPSLayouts, additional planning services) on top of BWBPS Integration between CRManalytics and APO works through BW-BPS
APO-Architecture: Overview
B U S I N E S S W A R E H O U S E APO Extractors
Planning Area
Remote Cube Info Cubes

BW Staging Engine Time Series
Release
Orders
liveCache
R/3
R/3 Extractors
Info Structures Orders
CIF / PI
APO-Architecture: Overview
B U S I N E S S W A R E H O U S E APO Extractors
APO Planning areas can either read from BW-Cube or LC but write only to LC
Frontend: Planning books
Planning Area
Remote (LC) is the main Cube The liveCache data storage for APO Info Cubes
BW Staging Engine Orders
liveCache is used in APO-DP (time-series) and APO-SNP, PP/DS, TP/VS, GATP (Orders) Time Series
Release
liveCache
R/3
R/3 Extractors
Info Structures Orders
CIF / PI
APO-Architecture: Important Notes

SAP APO contains an embedded SAP BW for technical Reasons :
The SAP BW within SAP APO is NOT meant to replace a separate external SAP BW for reporting purposes You may also have an external, separate SAP BW in your mySAP SCM landscape :
No
release synchronization is required between the external SAP BW and the SAP BW inside SAP APO. Only the extractors must be compatible.
BW-BPS/APO: Integration Features

z BW is the data storage for BW-BPS data z From non-transactional InfoCubes BWBPS can only read data z BW-BPS can read and write data from/to transactional InfoCubes z The liveCache (LC) is the data storage for APO z On a direct way APO can only read data from BW z Data can be transferred from the liveCache back to BW by using the extractor technology from BW
BPS and APO can work remote together with other BWs BW-BPS Multi-Planning areas can read from multiple BWCubes. Multi Planning Area Read Data from APO BPSCube Extract Data from BW APO-DP APO Planning areas can either read from BW-Cube or LC but write only to LC APO- Planning Area Extract Data from LC APORead Data through liveCache Cube APO Planning Area
and use BPS- functions to move, map, convert data between source and target (copy, planning language(FOX), exits)
Comparison aspects: APO

Task
Planning Tool
CRMa /BWBPS APO
APO-DP is the integration module of APO-SNP to BWbased planning. APO-SNP evaluates the feasability of the sales plan based on capacity restrictions. Additional planning functionality such as Bill of material explosion and special forecast functions. The market view is reduced to the location as the most important characteristic in order to reduce data volume and redundant customer master data.
CRMa/ BWBPS APO APO BW
APO is a planning tool dedicated to logistics planning. It represents the product related view through its proximity to the ERP master data.
Conclusion
BW-BPS is the integration module in a collaborative planning scenario. APO Supply Network Planning
Demand Planning Sales qty (unconstrained)
Sales qty (constrained) Cost of Goods (fix/variable) SAP BW-BPS Custom built planning application Profit Planning
Profitability Targets
CRManalytics planning application Sales Planning
Marketing costs
Content

Repetition up to this Point

BW-BPS
Uses BW as data storage Reads from and writes to transactional BW InfoCubes Reads from non-transactional BW InfoCubes
APO-DP
APO-DP reads data from BW InfoCubes APO-DP writes data to liveCache Extracts data from liveCache to BW InfoCubes
Exchange of plan data between BW-BPS and APO aided by BW technogy
simple, stable integration

no additional interfaces necessary
Challenge: Data Transformation

Master Data Management
BW-BPS: BW is the one and only master data server -> integration via reference APO-DP: Has its own master data management but can copy master data from BW -> integration via copying APO-SNP: Has its own master data management and works on fixed characteristics -> real-time integration to R/3 Challenge:. Heterogeneous system infrastructure causes the need for mapping and transformation functionality between system borders
Currency Handling
BW-BPS: Multiple currencies and currency transformation supported APO: Data is kept in one currency for each planning area (ad hoc currency translation is available for display purposes)
Unit Handling
BW-BPS: Multiple units supported (but no transformation of noncompatible units APO: No multiple units -> One unit for each planning area
Data Transformation between BPS and APO

How to achieve data transformation Alternative 1: BPS pushs and pulls data from/to APO
Multi Planning Area in BW for BPS and APO InfoCube
Data structures equal: Use Copy Function Data structures different: Use Fox Fomula to map structures
Alternative 2: APO pulls data from BPS / BPS pulls data from APO
Data from transactional BW InfoCube can be read by APO Changed data in APO is extracted to non-transactional InfoCube Multi Planning Area in BPS for BPS and APO InfoCube
Data structures equal: Use Copy Function Data structures different: Use Fox Formula to map structures
Note:
APO-InfoCubes should consist at least of the following InfoObjects

9AVERSION (Planning Verision) 9ALOCNO (Location) -> only if APO-SNP is used 9AMATNR (Product) -> only if APO-SNP is used
If data should be available in an InfoCube it has to be extracted from Live Cache (non-transactional InfoCube)
Data Transformation: Mapping in BW-BPS

Characterisitics BW-BPS
z Plant (0PLANT) zMaterial (0MATERIAL) z Version (0VERSION) zCalendar Year/ Week (0CALWEEK)
Characterisitics APO-DP
z APO Location (9ALOCNO) z APO Product (9AMATNR) z APO Planning Version (9AVERSION) z Calendar Year/Week (0CALWEEK)
Key Figures BW-BPS:

z Sales quantity (0COPASLQTY) z Revenue (0COPAREVEN) z Sales Discounts (0COPADISCT) z Net sales (0COPANETSL)
Key Figures APO-DP

z Sales quantity (0COPYSLQTY) z Revenue (0COPYREVEN) z Sales Discounts (0COPYDISCT) z Net Sales (0COPYNETSL)
Mapping example: APO data is in planning area APO1, BPS data is in planning area BPS1 Multi planning area APOBPS groups the two basic areas Characteristic for product in APO1: 9AMATNR Characteristic for product in BPS1: 0Material Product 18 in planning area APO1 = Product 40 in planning area BPS1 Formula in multi planning area:
{0COPASLQTY,Product40,#,BPS1}={0COPYSLQTY,#,Product18,APO1}
One mapping rule for each key figure Transformation from Product18 to Product40 (different technical attributes) Mapping of data in Planning Area APO1 and BPS1. # marks characteristics that dont exist in the corresponding InfoCube.
Challenge: Aggregation, Disaggregation, Derivation

Location and Product are the limitations in APO. Define mapping and distribution rules accordingly
Different Planning Levels

BW-BPS: Planning Level can be set up in a flexible way based on characteristics and key figures in BW BW-BPS: disaggregation (function) not mandatory APO-DP: Planning Level can be set up in a flexible way based on characteristics and key figures in BW APO-DP: data always disaggregated to lowest level APO-SNP: Fixed planning level (Location / Product) Challenge: Aggregation/Distribution/Derivation of characteristic dimensions between components
Set up time conversion in Different Time Dimensions BW-BPS BW-BPS: Can work on different time dimensions in parallel. No according to APO predefined conversion function between time dimensions. time conversion APO: Can work on different time dimensions in parallel. Predefined conversion function between time dimensions Workaround: CreateVersion Management automatic planning BW-BPS: Version is a characteristic. No automatic version management available functions in BW-BPS in order to automate APO: automatic version management available version management.
BW-BPS and APO-DP: Commonalities and Differences
Common:
BW is available for read access Redundancies in maintenance of functions, user interfaces, master data may occur
Different:
User Interfaces Planning functions / Planning Services Master Data Concept Planning Applications
Evaluate what to do where. Develop integration concept which features the right functions according to your business needs.
Content

Scenario: BW-BPS/CRManalytics & APO & R/3

SAP BW BPS SAP APO SAP R/3
Custom built profit planning: Initial topdown target setting on business units Bottom-up midterm sales planning (logisticoriented) 2 1 Link to sales order processing (Logistics & Production Execution)
CRManalytics planning application: Bottom-up mid-term sales planning (sales-oriented)
1 Rolling short-term sales planning Rolling short-term Production planning 3
Landscape for Integration Scenario

BW-BPS APO
Multi Planning Area
Planning Area
BPS-Planning Area (remote)

APO Data
Planning Area (local)

BPS Data
liveCache
Extractor
T = Transactional Cube Back

Type 1: BPS -> APO

BW-BPS APO
BPS pushs data to APO

BPS must provide data on right aggregation level
Data distribution: Use BPS distribution function -> Top Down Data aggregations: Define a specific Planning Level -> Bottom Up to achieve the right aggregation
Multi Planning Area
Planning Area

APO Data

BPS Data
liveCache
Extractor
T = Transactional Cube
Copy data to non-transactional APO InfoCube
Data extraction: BW-Update Rules may be used for mapping and flexible adaptation
APO planning area reads data from non-transactional APO InfoCube APO planning area writes to liveCache
Back
Type 2: APO -> BPS

BPS pulls data from APO
Data is extracted from liveCache to non-transactional APO-Cube BPS reads data from nontransactional APO InfoCube (remote) direct access (Note: BPS may also read data from local APO InfoCube in this case the data must be copied from the remote APO InfoCube in advance)
BW-BPS APO
Multi Planning Area
Planning Area

APO Data

BPS Data
liveCache
Extractor
T = Transactional Cube
Copy data to transactional BPS InfoCube

Data structures equal: Use BPS Copy Function to Data structures different: Use BPS Fox Formula to map structures BW-Update Rules may be used for flexible adaptation
Back
Type 3: APO-DP -> APO-SNP (R/3)

Release APO-DP to APO-SNP Transfer of data supports conversion of time dimensions and distribution on locations and products
Back
Content

Take action
Set up round table integration team involve:

Project sponsor from board Controlling Production Sales
Project success depends on management support! Keep in mind that targets may be competing
Discuss integration opportunities:

landscape (depends on your companies situation) master data concept must be designed for integration needs
Build small prototype for a single product or product group Evaluate and improve prototype Deploy to a broader scope
Continously evaluate and improve collaborative planning process!!!
Keep in mind: Integration is not a matter of system support only it is a continous effort of people collaborating across departmental boarders and may involve cultural changes.
7 Key points to take away.

Planning across departmental boarders becomes vital for the overall success of companies in turbulent environments SAP enables closed-loop collaborative planning through BWBPS, CRManalytics and APO BW-BPS is the platform for CRManalytics APO is delivered with a BW for data storage and analysis BW-BPS is the main basis for stable integration of the different planning tools in the BW environment Integration through BW-BPS does not require additional interfaces Collaborative and integrated planning requires committment of all affected parties
Copyright 2004 SAP AG. All Rights Reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express
permission of SAP AG. The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other
software vendors.
Microsoft, WINDOWS, NT, EXCEL, Word, PowerPoint and SQL Server are registered trademarks of
Microsoft Corporation.
IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390,
OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix and Informix Dynamic ServerTM are trademarks of IBM Corporation in USA and/or other countries.
ORACLE is a registered trademark of ORACLE Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, the Citrix logo, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, MultiWin and other
Citrix product names referenced herein are trademarks of Citrix Systems, Inc.
HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C, World Wide Web Consortium,
Massachusetts Institute of Technology.

JAVA is a registered trademark of Sun Microsystems, Inc. JAVASCRIPT is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and
implemented by Netscape.
MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver and other SAP products and services mentioned herein
as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves information purposes only. National product specifications may vary.

Integration BW-BPS Overview

Caricato da

Informazioni sul documento

Descrizione originale:

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Integration BW-BPS Overview

Caricato da

Copyright:

Formati disponibili

Integration BW-BPS, CRManalytics and APO-DP

Scope of this presentation

SAP AG 2004, Title of Presentation / Speaker Name / 2

* focus on SAP BW environment

Keeping control of strategic goals

Increase Return on Investment ROI = (Sales Costs) / Capital Invested

Optimize production utilization

Reduce overhead costs

Increase sales volume

purchase planning Purchase

quantity / purchase prices

sales planning Sales

product cost planning

product prices / cost of goods sold & manufactured

cost center planning

activity prices / budget

Integrated planning cycle

Strategic Planning and Target setting on group level

Operational Planning and Budgeting in the business units

Reconciliation of operational plans with strategic targets Production planning

Heterogeneous planning landscapes

Marketing Plan Production Plan Production Reporting

SAP AG 2004, Title of Presentation / Speaker Name / 7

* focus on SAP BW environment

Opportunities offered by SAP planning products

Sales qty (constrained) Cost of Goods (fix/variable)

BW-BPS Profit Planning Profitability Targets

CRManalytics Sales Planning

SAP AG 2004, Title of Presentation / Speaker Name / 9

Sample Planning Scenario

SAP AG 2004, Title of Presentation / Speaker Name / 10

Planning across organizational boundaries

Supply Network Planning Transportation Planning

Integrated planning across applications

mySAP mySAP ERP ERP

mySAP mySAP CRM CRM

SAP SAP Industry Industry Solutions Solutions

SAP SAP ... ... Custom-built Custom-built applications applications

SAP AG 2004, Title of Presentation / Speaker Name / 12

SAP AG 2004, Title of Presentation / Speaker Name / 13

CRMa: Analytical Scenarios

CRM Analytics - Overview

How do BW-BPS and CRManalytics work together?

BW-BPS is the planning platform for CRManalytics CRManalytics delivers

SAP AG 2004, Title of Presentation / Speaker Name / 16

What is SAP APO?

Main SAP APO planning applications:

SAP AG 2004, Title of Presentation / Speaker Name / 17

SAP AG 2004, Title of Presentation / Speaker Name / 18

SAP AG 2004, Title of Presentation / Speaker Name / 19

BW-BPS Architecture: Overview

BPS Planning Workbench

SAP AG 2004, Title of Presentation / Speaker Name / 20

BW-BPS Architecture: Overview

Comparison aspects: BW-BPS

CRMa/ BWBPS APO APO BW

BW-BPS is the basis for CRM analytics (CRMa).

CRManalytics (CRMa) Architecture: Overview

SAP CRM Application Server

Sales Sales Planning Planning & & Forecasting Forecasting

CRMa Planning Services BW-BPS Planning Workbench

SAP AG 2004, Title of Presentation / Speaker Name / 23

CRManalytics (CRMa) Architecture: Overview