Business Suite Analytics - Archive€¦ · Objects tools immediately across the whole Suite Solves...

Business Suite Analytics

Embedded Analytics – Business Objects Integration – Scenario Overview

SAP AG

May 2010

© 2010 SAP AG. All rights reserved. /

Business Objects Integration Scenarios

for SAP Business Suite 7 Innovations 2010

Scenario 1

Embedding in Tabular Structures

Scenario 2

Embedded Launch of

Crystal Reports / Xcelsius Content

Scenario 3

Embedded UI Components

Scenario

Description

Leveraging SAP GUI ALV and Web

Dynpro ALV (incl. POWER List) and

transfer data to Crystal Reports as

layout option

Using default layouts for all tabular

structures without specific efforts

Standard content using Crystal

Reports and Xcelsius following

Simplified Reporting approach

Role, process and application

integration via Launchpad

Tight coupling of Xcelsius content

within SAP Business Suite

applications

Xcelsius content integrates into

the process

Value

Proposition

Use state of the art Business

Objects tools immediately across the

whole Suite

Solves issue of printing / formatting

for lists

Customers can easily build own

content (may require additional

licenses)

Significant improvements in the

areas of formatted reporting and

dashboards

Scenario uses established lifecycle

management processes of BI

Content

Customers can easily build own

content (may require additional

licenses)

Shows highest level of integration

Seamless end user experience

Tool

Decision

for 2010

Shipment

Crystal Reports Crystal Reports

Xcelsius

Xcelsius

Crystal ReportCrystal Report


Business Objects Integration Scenario 1

Embedding in Tabular Structures

Central idea:

Using Crystal Reports as layout option for

Web Dynpro ALV and SAP GUI ALV.

Key rational:

Default layout:

Enable usage of Business Objects tools immediately

across all ALVs within the whole suite (e.g. for printout

or as starting point to define Customized Crystal

Reports)

Customized Crystal Reports:

Using formatting features on top of ALV data.

Customers can easily define their own reports as well.

Crystal Report


How to Create a Specific Crystal Report

and Assign it as ALV Layout Option

Start ALV

Display generated layout

for Crystal Report

Edit generated layout in

Crystal Report Designer

(additional license

needed)

Save new Crystal Report

as ALV layout option


Use cases:

Printout and formatting purposes (therefore Crystal Reports is most important for that scenario)

Environment:

Web Dynpro ABAP ALV (incl. POWER List)

SAP GUI ALV (more precisely ALV Grid)

SAP content delivery:

SAP is able to define and deliver Generic Crystal Report (that can be used out of any respective tabular

structure e.g. for printout purpose) this enables the Business Suite to use Business Objects tools (i.e.

in this case Crystal Reports) immediately across the whole Suite)

SAP is also able to define and deliver Specific Crystal Reports for dedicated ALV layouts (which then can

be used as alternative UI)

Software lifecycle fully integrated with ALV layout procedure

Customers‘ options:

Customers can use the Generic Crystal Reports and Specific Crystal Reports delivered by SAP without

having the Crystal Reports Designer.

Customers are also able to define their own Generic and Specific Crystal Reports and attach them to the

respective ALV layouts (in that case of course the Crystal Report Designer is required).

This may require additional licensens.

Scenario variants:

In place as layout option (replace ALV table by Crystal Report)

Starting the Crystal Report directly in place without displaying the grid first

(i.e. POWER List etc. only for data retrieval)


Embedding in Tabular Structures - Details


Technical Prerequisites:

Scenario 1

Business Suite 7

Innovations 2010

SAP GUI 7.10

NW 7.02

Crystal Reports

Viewer for SAP

Business Suite

Applications

Client Server

Crystal Reports 2008 SP02

(only for design time)



Embedded Launch of Standard Content

Central ideas: Develop and deliver standard BI content

using Crystal Reports and Xcelsius

following Simplified Reporting approach

Data retrieval via BI Queries

Crystal Reports and Xcelsius content is

being launched (parameterized) via

Launchpad.

Key rational:

Business Objects reports are fully integrated into

BI content development & deployment and

leverage existing BI Content (investment

protection).

Within SAP Business Suite, portal roles use

Launchpads as access point for the most

important reports nonregarding the technology

behind. Also Business Objects reports can be

launched that way.


Business Client Enterprise Portal

End User

EnvironmentP

us

h

Launchpad Pu

llReport

Access

Business Query

Classic InfoSet / DataSource

Business Data Provisioning

Direct Access Staging

Suite

Database

Data

Provisioning

Reporting

Scenarios

SAP BI GRC

…

Application Process

Business Suite Analytics


Formatted Report

Example of Crystal Report Based on BI Query


Dashboard

Example of Excelsius Dashboard Based on BI Query


Use cases:

For formatted reporting Crystal Reports (as successor of Report Designer) shall be used.

For dashboarding Xcelsius is the go to solution. Xcelsius may also be used for visualization purposes.


For Crystal Reports and Xcelsius SAP it is possible to develop, deliver & maintain standard content (in

analogy to what has been done with BI content so far).

For investment protection of the existing content the content definition takes place on top of existing or

new BI content (BI query as unified data interface to various consumers).

This includes the possibility to create Crystal Reports and Xcelsius dashboards directly on Classical

InfoSets in the backend (via queries on Transient InfoProviders).

Business Objects tools provide added value (e.g. significantly increased usability and display options) and

at the same time the idea of independency of frontend tool decision and backend data provisioning (i.e.

backend scalability) remains.

Customers‘ option:

Customers can consume delivered Business Objects content but can also define their own (based on

existing BI content or their own BI based reports).

The latter may require additional licenses.

Scenario variants:

Launch reports via Launchpad iView.

Launchpad may also be used inplace within an application. In this case the Launchpad will be able to

hand over application context to the respective report.

Direct integration into Enterprise Portal via iView.


Embedded Launch of Standard Content - Details


SAP GUI 7.10

Xcelsius 2008

Enterprise SP02


Client Server

Flash Player

Report Launchpad

Modifications

Business Suite 7 Innovations 2010

NW 7.02

BI_CONT

7.05

BI_CONT_EXT

7.05


Scenario 2 with Xcelsius


Start Menu

Entries for XC/CR

SAP GUI 7.10

Client Server

SAP BusinessObjects

Integration for SAP Solutions

XI 3.1 Service Pack 02

Crystal Reports 2008 SP02


Report Launchpad

Modifications

Business Suite 7 Innovations 2010

SAP NetWeaver

BW 7.02

BI_CONT

7.05

BI_CONT_EXT

7.05

SAP BusinessObjects

Integration for SAP Solutions

XI 3.1 Service Pack 02

BusinessObjects Enterprise

XI 3.1 SP02


Scenario 2 with Crystal Reports



Apps with UI Embedded Analytical Components

Central idea:

Xcelsius components become part

of SAP Business Suite applications.

Web Dynpro UI Islands for Flash

(Flash Islands) are used for this

(respective BSP solution is used for

SAP CRM).

Key rational:

Showing tight application and UI

integration of Analytical

Components based on Xcelsius.

One- and two-way communication

between application and integrated

Analytical Component is supported.


Environment:

Web Dynpro ABAP applications (e.g. built with FPM (Floorplan Manager))

Web Dynpro Java applications (e.g. built with Visual Composer)

BSP applications also supported (for CRM)


SAP is able to develop and deliver applications including UI embedded analytical components based on

Xcelsius.

Customers‘ options:

Customers may use applications delivered by SAP.

Customers can also develop own applications including UI embedded analytical components based on

Xcelsius.

Scenario variants:

Tightly embedded analytical components

UI integration plus tight data integration

Information exchange between application and analytical component is be possible in both directions

(e.g. hand over material to be purchased from application to analytical component; selection of

supplier within the analytical component (e.g. according to criteria such as prices, conditions,

discounts, adherence to delivery dates); hand over selected supplier from analytical component to

application).

Information exchange between application context and analytical component takes place via variable

mapping.


Apps with UI Embedded Analytical Components - Details


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

Business Suite Analytics - Archive€¦ · Objects tools immediately across the whole Suite Solves...

Documents

Transcript of Business Suite Analytics - Archive€¦ · Objects tools immediately across the whole Suite Solves...