ppt 6 - elite bps and ip

ELITE BPC 7.5 NW PARTNER TRAININGBusiness Planning and Simulation (BPS) & Integrated Planning (IP)

Enterprise Performance Management RIG

© 2010 SAP AG. All rights reserved. /

Before BPC…

R/3 based planning (i.e.: SAP R/3 Cost Center Planning)

SAP purchased OutlookSoft in 2007. The main OLS product was rebranded into what we now call BPC. Prior to this time, SAP had offered a number of planning solutions that have be extensively incorporated by thousands of customers. Two of the main solutions are:

Business Planning and Simulation (BPS, SEM, SEM-BPS, BW-BPS)The original BPS application were generically part of a suite of applications called Strategic Enterprise Management (SEM). SEM consisted of a planning application (BPS), score card application (Cockpit Manager, Scorecard application (Balanced Scorecard), and consolidations (BCS).

Integrated Planning (IP, BI-IP, BW-IP) IP was first made available with the introduction of Netweavertechnology in 2004. The IP application is built upon similar structures in BPS, but incorporate advanced web design features for enhanced data presentation as well as an unique web administration development console (IP Planning Modeler).


Business Planning and Simulation

Highlights of BPS:Planning on aggregated levels (for example, cost center group)Flexible modeling of data structures based upon BW transactional info providers (now called “real time info providers”)Flexible design of end-user environmentAdditional reference data (previous years, other versions)User-definable HTML layouts with grids, texts, logos, planning functions (Web Interface Builder or WIB)Integration of planning functions delivered by SAP (copy, distribution, etc)Integration of customer-defined planning functions (“FOX” formula language)Planning workflow support using Status and Tracking systemIntegration with SAP’s enterprise portalBPS Variables could be defined and used within the planning displays as well as the planning functions (but BW variables could not be used by BPS) – this was a key gap with the BPS integration with BW.



T-code BPS0 is delivered in Netweaver:

GUI based configuration development.Development tools included the BPC Planning Workbench, Planning Folders, Web Interface Builder, and the Status and Tracking System.



BPS GUI: GUI based configuration developmentAbility to connect to a variety of BW cubes to display and plan data.Relied upon BW ETL to load dataUsed standard BW info objects but required the definition of BPS specific planning areas to connect these objects into BPS.



BPS Structure BPS configuration is based upon several layers, each defining smaller data sets and associated planning functions.The Planning Ares is the top node, followed by the Planning Level and the Planning Package.The Planning Method and Parameter Set allow definition of functions and layouts.



BPS Structure The BPS structure allowed a 1:N (one to many( relationship between upper and lower level structures. This feature allowed easy compartmental developed of specific business process.



BPS Structure:Each organizational level in BPS provided addiotnal restrcictions on the data set to be processed.Example shown illustrates the use of a BPS variable to restrict fiscl year period.



Formula Extension (FOX) Code (example):*******Total Burden Cost Move - to next two years ***DATA EMP TYPE ZEMPLOYEE.DATA BNWID TYPE Z_BUDGTID.DATA ITEM TYPE 0SEM_POSIT.DATA UOM TYPE 0UNIT.DATA CURR TYPE 0CURRENCY.DATA FY TYPE 0FISCYEAR.DATA FY1 TYPE 0FISCYEAR.DATA FY2 TYPE 0FISCYEAR.

FY = VARV('PLNYEAR').

IF FY = '0000'.MESSAGE E001(/MSG01) WITH 'FISCYEAR NOT SET, VALUE = 'FY.ENDIF.

FY1 = TMVL(FY,1).FY2 = TMVL(FY,2).

FOREACH ITEM, UOM, CURR, EMP, BNWID.

{0DUR_ACTUAL, #, FY1, 'P000001', H, EMP,BNWID} ={0DUR_ACTUAL, #, FY, 'P000001', H, EMP,BNWID}.


{0AMOUNT, USD, FY1, 'P000002', #, EMP,BNWID} ={0AMOUNT, USD, FY, 'P000002', #, EMP,BNWID}.

{0AMOUNT, USD, FY2, 'P000002', #, EMP,BNWID} ={0AMOUNT, USD, FY, 'P000002', #, EMP,BNWID}.



ENDFOR.

FOX code provide a means to create customized functions for the BPS user.FOX code can be thought of as a record manipulation tool. Specific records could easily be defined within the FOX program.The FOX code instruction set provide loops, conditional statement, variable manipulation, and messaging functions.In addition to FOX, BPS was delivered with a significant set of predefine functions.Functions could be grouped for sequential execution with Planning Sequences.



LayoutsLayouts were required for BPS planning and display of data.The layouts did not have a lot of features and the resulting display of data restricted to limited design. One or more layouts could be group into a Planning Folder (GUI) or into a web based display using the Web Interface Builder.



Planning Folder (GUI based)The Planning Folder was able to group one or two planning layout displays along with buttons to access planning functions.



Web Interface Builder -provide an easy to configure web based collection of BPS functionality, including variables selections, multiple layout displays, and planning function access.


Integrated Planning

Highlights:Common end user interface - Single planning and reporting end user interface (BW Query)One tool to create reporting queries and manual planning layouts – Decreases initial implementation time and complexities, solution lifecycle maintenance, end user training effort. Includes the sharing of key objects such as variables, filters, user exits to support enhancements)Web interface builder = BI Web Application Designer (WAD) - Decreases initial implementation time and complexities, solution lifecycle maintenance, end user training effort when creating/maintaining planning applications over the webAbility to use calculated key figures in planning layouts – Decreases need for pesky planning functions to perform some basic mathematics; these are then reused in reporting/analysis to ensure formula methodology consistencyPlanning Wizard – Simplifies the power users ability model resulting in lower training and less confusion leading to higher end user efficienciesAbility to use BW Variables on the filter (i.e. planning package) – Simplifies implementation time and complexities as well as solution lifecycle maintenance Planning sequences embedded in BI Process Chains – Provides consistent approach to performing calculations during or after BW data loads and/or transformations. Ensures planning calculations are carried out at right time with no time delay and reduces administrator time commitment.


Integrated Planning

The multiple areas requiring develop effort and as a result required multiple skill sets to efficiently design. This was sometimes a problem on some projects!


Integrated Planning

The web-based Planning Modeler is the central application where the complete modeling and customizing for the BI-Integrated Planning is done. In the modeler, one maintains the different planning related objects like aggregation levels and planning functions and the relationships among these objects.

You access the planning modeler via t-code RSPLAN:

WEB BASED CONFIGURATION!!


Integrated Planning

Planning Area

Aggregation Level

Planning Filter

Planning Functions

Planning Sequences

Define data provider and characteristic relationships

Define data regions

Refine data region

Delivered functions, exits, FOX (same as in BPS)

Grouping of Planning

Functions

IP Structure:


Integrated Planning

Aggregation Level

MultiProvider

Query or Planning Function

Real-Time InfoProvider

InfoCube

Great for Plan vs. Actual reporting!

The IP architecture allowed access to IP specific planning cubes, but also access to basic BW cube data. This greatly simplified Plan vs. Actual reporting designs.


Integrated Planning

Query Designer and BW Variables

IP used BW Queries instead of BPS Layouts to present data.BW filters and BW variables were re-usable in IP queries.


Integrated Planning

Data visualization: Query Designer and Planning

Queries options provided the ability to switch a data display from view only to fully interactive planning.Additional features included automatic disaggregation after planning on a parent node.


Integrated Planning

Web Application Designer (WAD):

Long used by the BW reporting community to web enable reports, the WAD worked seamlessly with IP to create full featured web displays, providing features such a variable control, dropdown lists, unlimited query display, tab strip formatting, and hundreds of additional design features.


Integrated Planning

Web Application Designer:

WAD used drag and drop design.Hundreds of different design options were available to the web application designer.


Current and future …

BW-BPS is no longer being developed and should not be used for new projects. BPS is still delivered in current versions of BW, as a result any existing investment is protected.Integrated Planning is still being developed and implemented at some customers. Its main strength (compared to BPC) is IP’s ability to access BW info providers directly and to use existing BW queries to display data. The main weakness of IP (as compared to BPC) is IP’s reliance on BW data model and existing BW object definitions, resulting in more difficult business process modeling and simulations. This reliance on the BW data model keeps lowers the ability to conform a data model into one that is agile enough to meet volatile business users needs. It can said: “IP is more IT centric in its philosophy, and BPC is more business user centric in its approach”.


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, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States 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, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.HTML, XML, XHTML and W3C 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. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, Clear Enterprise, SAP BusinessObjects Explorer 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 other countries.Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP France in the United States and in other countries. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG.This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice.SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence.The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.

© 2010 SAP AG. All Rights Reserved

ppt 6 - elite bps and ip

Documents