Embed Size (px)
Citation preview
How to Model Portal Content Using SAP Visual Composer – No Programming Required!Scott CairncrossSAP Labs
Creating Analytics Apps
BI and Analytics
Why Analytics?
Application Modeling and the Visual Composer
Wrap-up
Creating Analytics Apps
BI and Analytics
Why Analytics?
Application Modeling and the Visual Composer
Wrap-up
© SAP AG 2006, 4
A 45-degree front-office view
of the customer
Ineffective Decisions – With the Best of Effort
Lack of complete visibility equals poor decisions!
IF YOU DEPLOY SILOED CRM ANALYTICS
Your conclusion:This is a great account, a real “A-Customer”
Your Action:Continue as is; everything seems to go well
What you know:Big dollar volumeLoyal relationshipZero open casesFirst-call resolution 90%Average call time is less thanthree minutes
Your conclusion:This is a very non-profitable account
Your Action:Urgent need for action, convert customer into profitable customer, or discontinue focus, maybe move to indirect channel
YOU MIGHT MISS THETRUE 360° CUSTOMER VIEW
Front-office Information
Costs and Margins Information
Delivery and ReturnInformation
PaymentInfo.
What you additionally know:
Low-margin purchasesHigher product returnsBig-order backlogMore disputed invoicesFrequent rush ordersOverall: Low profitability, weak customer loyalty, small per-order value
© SAP AG 2006, 5
The Challenge
Execution not aligned with corporate strategyClear and measurable performance goals are missingIndividual objectives of contributors not aligned with strategyPoor feedback and no corrective actions
Ineffective decision-making processesDecisions delayed, or made on “gut feel” onlyKey stakeholders not involved, information only available to small “elite”BI and knowledge management disconnected from processes and applications
© SAP AG 2006, 6
The Challenge (cont.)
Missing timely insights into trends, events, and opportunitiesOnly after-the-fact reporting, and lack of right-time insightOpportunities frequently missed, and critical events frequently ignoredOperations, while effective, need to be “smarter” (e.g., to improve customer retention, to alert of “material events,” to fine-tune supply chain execution)
Business insights disconnected from the business processBusiness users work as human integratorsIn the absence of in-context insights, people operate off of incomplete information
© SAP AG 2006, 7
Controlling(BW)
Logistics(SCE)
Sales(CRM)
Production(SCP)
Fulfillment(FC)
Fin.-Dept.(FIN)
Customer
Creation and Release Delivery Request
4
UpdateInventory
Accounting
7Update
Inventory
6
DeliveryExecution
5
Request Global ATP
2
Global ATP Check
3
ReceivesASN
9
ReleaseASN
8
1
Creation Sales OrderFulfillment
Request
Creation Purchase
Order
Example: The Sales-Order Fulfillment Process
© SAP AG 2006, 8
Controlling(BW)
Logistics(SCE)
Sales(CRM)
Production(SCP)
Fulfillment(FC)
Fin.-Dept.(FIN)
Customer
Creation and Release Delivery Request
4
UpdateInventory
Accounting
7Update
Inventory
6
DeliveryExecution
5
Request Global ATP
2
Global ATP Check
3
ReceivesASN
9
ReleaseASN
8
1
Creation Sales OrderFulfillment
Request
Creation Purchase
Order
Example: The Sales-Order Fulfillment Process (cont.)
Strategic business decisions require timely
information from many sources
© SAP AG 2006, 9
Business Processes Require Information
“This is a keycustomer!”
“Any missedsales?”
“Will be backin inventory”
“Delays?”
“Extra effortcosts money”
© SAP AG 2006, 10
Business Processes Require Information (cont.)
“This is a keycustomer!”
“Any missedsales?”
“Will be backin inventory”
“Delays?”
“extra effortcosts money”
Questions and Insights show the way to
process improvement!
© SAP AG 2006, 11
Information Requires Analytics
Returnsper
Customer
DeliveryPerformance
Accuracy
InventoryForecast
CLTV
DefectionRisk
© SAP AG 2006, 12
Enterprise Services Architecture and SAP Analytics: A Key Building Block
SAP NetWeaverBusiness Process Platform
SAP NetWeaverBusiness Process Platform
ERPSupplier
ERPSupplier
CRMSupplier
CRMSupplier
SRMBuyerSRM
Buyer
SRMinternal
SRMinternal
ERPinternal
ERPinternal
Third-Party
internal
Third-Party
internal
Enterprise Services
Repository
Enterprise Services
Repository
PEOPLEPRODUCTIVITY
EMBEDDEDANALYTICS
SERVICECOMPOSITION
LIFECYCLE MANAGEMENT
Composites
Enterprise ServicesImplementations by SAP
Enterprise ServicesImplementations by SAP
SERVICEENABLEMENT
BUSINESS PROCESSPLATFORM
SAP Analytics
© SAP AG 2006, 13
The Challenge: Provide Timely Business Insights
ChallengeEffective decision-making require a holistic view on enterprise information in a given contextHistorical and operation data needs to be integrated from disparate SAP and non-SAP sources
SolutionIntegrated transactional and analytical contextExtend ESI model to host documents and analyticsBusiness-Object-based, semantic views for information access
Allow for seamless drill-through without loss of semanticsUniform service infrastructure
© SAP AG 2006, 14
The Challenge: Provide Flexibility and Low TCO
ChallengeAnalytic applications are hard to code, and even harder to modifySystem landscape creates IT dependenciesBusiness changes cannot easily propagate to analyticsBusiness Intelligence has historically offered “after-the-fact”reporting tools
SolutionAssemble applications from logical “widgets,” creating a model-driven environment without any codeFocus on the logical model, not the data modelCreate a dynamic user experience without forcing business users to preplanLeverage services to merge transactional, collaborative, and analytic steps
© SAP AG 2006, 15
The Challenge: Empower the Business User
ChallengeAnalytics development typically completely centralizedIT organizations become the bottleneck in creating new reports and queriesBusiness users require insights within the “window of opportunity”
TacticalOperationalStrategic
SolutionEnable business users to create or modify their own analytics –reducing IT bottleneckManaged self-service environmentAd-hoc creation of KPIs, hierarchies, queries, and semantic viewsEliminating the cryptic nature of typical BI queries and replacing them with logical data models
Creating Analytics Apps
BI and Analytics
Why Analytics?
Application Modeling and the Visual Composer
Wrap-up
© SAP AG 2006, 17
Visual Composer: Introduction
What is the Visual Composer?Visual Composer is a visual modeling tool that enables sophisticated content development for SAP Enterprise Portal
Works by dragging and dropping appropriate objects and establishing relationships between themNo coding required
Visual Composer is completely Web-basedBusiness consultants can sit next to the business users and access Visual Composer from any machineThey can build or customize to reflect business needs on demand
© SAP AG 2006, 18
Visual Composer: Introduction (cont.)
What is the Visual Composer? (cont.) Visual Composer is a modeling tool that generates code, as well as a debugger, tester, and documentation creator. It is independent from any platform, technology, or language.
Currently Visual Composer produces iViews based on Java, JSP and HTMLB, and FLASH (Web Dynpro-planned)It allows you to connect to SAP BAPIs, SAP BI Queries,and Views (Web Services)Extension kits are currently being built by different groups to enable Visual Composer to generate other programming models
© SAP AG 2006, 19
Visual Composer: Goals and Motivation
Visual Composer was developed to provide a visual tool that enables customers to quickly and easily develop content, thereby:
Minimizing the time and effort to create contentLeading to quicker go-live decisionsReducing Total Cost of Ownership (TCO)Increasing Return on Investment (ROI)
What Visual Composer provides in the current version:Simplified process for creating iViews over SAP R/3 and BI Systems in order to eliminate the need of writing Java/ASP codeFlexibility to process data received from RFCs and BAPIs, as well as BI Queries and Views, eliminating the need of to write ABAP code, by providing operation-like sorting, arranging out in ascending or descending order, or putting filters on fields
© SAP AG 2006, 20
Visual Composer: Functionality
What Visual Composer provides in the current version:Simplified process for creating iViews over SAP R/3 and BI Systems
In order to eliminate the need of writing Java/ASP code
Flexibility to process data received from RFCs and BAPI, as well as BI Queries and Views
To avoid having to write ABAP code, by providing operations like sorting, arranging out in ascending or descending order, or putting filters on fields
© SAP AG 2006, 21
Visual Composer: Target Users
Browser-based
Intuitive modeling and design
Rapid application development
Prototyping
Code-free development
Support of JSP and HTMLB; planned support for Web Dynpro metadata
Business Application Developer
Business Application Developer
J2EE/ABAP/.NETDeveloper
J2EE/ABAP/.NETDeveloper
Content Admin
Content Admin
Business Expert
Business Expert
TechnologyFocus
BusinessFocus
© SAP AG 2006, 22
Enterprise Software Delivery Lifecycle – Today
End User (LOB)
= Roles/Personas
1. Define 2. Configure 3. Develop 4. Deploy
Business Owner (LOB)
Developer (IT)
Administrator (IT)
(12) Develop app.
(16) Stress test
Business Analyst (IT)
(1) Define high-level process requirements
Application Consultant (IT)
(6) Map process to application; gap analysis – config.
(11) Define technical specification
(17) Move to prod.
(4) Approve process design
(9) Analyze gaps
(8) Identify gaps – Dev.
(5) Process handover
(10) Process handover (requirements/specs)
(13) Debug and test
(14) Functional testing
(15) Approve application
(7) Configure app.
(2) Define process requirements
(3) Create Process Model
Show me the money!
© SAP AG 2006, 23
Scenario: The Business Expert and the Developer
The business expert identifies the need of a business scenario He/she needs to configure and extend an existing application The developer can view the application model in his/her development environment The developer
Codes a new service. He/she composites a new service out of three existing ones.He/she codes a new Java software component in the development studio Another developer creates a new software component using .NET visual studio
The developers deploy their objects into SAP NetWeaverThe business expert opens the model. The objects created by the developer are available for him/her. He/she embeds them into themodel.He/she deploys to SAP NetWeaver and triggers a workflow for the SAP NetWeaver administrator for application approval and deployment to production He/she uploads his/her new model to the application discussion group in SDN to share it with the development community
© SAP AG 2006, 24
Enterprise Software Delivery Lifecycle – Tomorrow
End User (LOB)
= Roles/Personas
1. Define 2. Configure and
Orchestrate3. Develop and
Extend4. Deploy
Business Owner (LOB)
Developer (IT)
Administrator (IT)
(12) Develop app.
(16) Stress test
Business Analyst (IT)
(1) Define high-level process requirements
(11) Generation of technical specification
(17) Move to prod.
(3) Create Business-Oriented Process Model
(4) Approve process design
(9) Analyze gaps(6) Configure app.
(10) Define gap requirements using Process view
(13) Debug and test
(14) Functional testing
(15) Approve application(5) Select services to
support process
(2) Define process requirements
(7) Configure/Model UI
(8a) Release to QA
(8b) Generation of technical specification
• Business analyst does application design, prototypes, adaptation, and configuration
• Interacts with the developer to receive building blocks• Development cycle is reduced to a month
• Develops back-end services and UI elements • Develops complicated parts of the model
(e.g., complex dynamic expressions)
© SAP AG 2006, 25
SAP NetWeaver Technology Map
User Productivity Enablement
Running an Enterprise Portal
Enabling User Collaboration
Business Task Management
Mobilizing Business Processes
Enterprise Knowledge Management
Data Unification Master Data Harmonization Master Data Consolidation Central Master Data Management Enterprise Data Warehousing
Business Information Management
Enterprise Reporting, Query,and Analysis
Business Planning and Analytical Services Enterprise Data Warehousing
Business Event Management Business Event Resolution Business Task Management
End-to-End Process Integration
Enabling Application-to-Application Processes
Enabling Business-to-Business Processes
Business Process Management
Enabling Platform Interoperability
Business Task Management
Custom Development Developing, Configuring, and Adapting Applications Enabling Platform Interoperability
Unified Lifecycle Management Software Lifecycle Management SAP NetWeaver Operations
Application Governance and Security
Authentication and Single Sign-On Integrated User and Access Management
Consolidation Enabling Platform Interoperability SAP NetWeaver Operations Master Data Consolidation Enterprise Knowledge
Management
Enterprise Services Architecture – Design and Deployment
Enabling Enterprise Services
IT Practices IT Scenarios
On the concept of IT practices and IT scenarios …
© SAP AG 2006, 26
SAP NetWeaver Technology Map (cont.)
User Productivity Enablement
Running an Enterprise Portal
Enabling User Collaboration
Business Task Management
Mobilizing Business Processes
Enterprise Knowledge Management
Data Unification Master Data Harmonization Master Data Consolidation Central Master Data Management Enterprise Data Warehousing
Business Information Management
Enterprise Reporting, Query, and Analysis
Business Planning and Analytical Services Enterprise Data Warehousing
Business Event Management Business Event Resolution Business Task Management
End-to-End Process Integration
Enabling Application-to-Application Processes
Enabling Business-to-Business Processes
Business Process Management
Enabling Platform Interoperability
Business Task Management
Custom Development Developing, Configuring, and Adapting Applications Enabling Platform Interoperability
Unified Lifecycle Management Software Lifecycle Management SAP NetWeaver Operations
Application Governance and Security
Authentication and Single Sign-On Integrated User and Access Management
Consolidation Enabling Platform Interoperability SAP NetWeaver Operations Master Data Consolidation Enterprise Knowledge
Management
Enterprise Services Architecture – Design and Deployment
Enabling Enterprise Services
IT Practices IT Scenarios
On the concept of IT practices and IT scenarios …
© SAP AG 2006, 27
Principles of Application Modeling
A good application-modeling language should be based on the principles of end-user programming:
ExploratorySimplicity ReusabilityDirectnessExpressivenessExtensibility
These principles affect both the model representation and the modeling tool
© SAP AG 2006, 28
Exploratory Environment
Enable experimental changes to be made (and undone) quickly and with minimal effort encourage iterative development
Automate mechanical-model composition and configuration tasks:Reorganize and rewire the model by dragging and dropping (while keeping the model consistent without bothering the user)Supply default values to avoid/postpone tedious specification Provide wizards for rapid creation of common design templates
© SAP AG 2006, 29
Simplicity
Use few, highly reusable, highly understandable concepts (interactors, infoshapes, states, ports)
Use simple and scalable visual representation:Box-and-line graphics (can be drawn by hand)Show essence and hide detailsExploit topology (e.g., connections, containment, proximity) to increase possible permutations without increasing visual complexity
© SAP AG 2006, 30
Additional Principles
ReusabilityReuse is very important because it allows non-programmers to build on the work of programmers or more sophisticated designers
Directness – everything runs “immediately”Continuous execution breaks down the barrier between the static program (abstract) and the dynamic execution that it induces (more concrete)
ExpressivenessUse spreadsheet concepts (formulas and cells) to express complex and dynamic user interface logicEnable reuse of programmed components, but avoid exposing programming concepts (classes, interfaces, inheritance)
ExtensibilityExtend the language by adding new modeling elementsExtend the application reach by supporting new run time platforms
© SAP AG 2006, 31
Visual Composer Design-Time Environment
Creating Analytics Apps
BI and Analytics
Why Analytics?
Application Modeling and the Visual Composer
Wrap-up
© SAP AG 2006, 33
Flash
“Zero Programming” Paradigm
Visual Composer Storyboard
HTML/B
Visual Composer
Model
Visual Composer
Model
1) Storyboard•The storyboard is used to draw and compose model diagrams using an intuitive visual notation. Editors and wizards provide multiple approaches to the design process: • Freestyle vs. pattern-based design (or mixed)
• Data-driven vs. UI-driven design (or mixed)
2) Modeling LanguageThe model is stored in a model repository using a proprietary modeling language called GML. This modeling language is designed for expressiveness and extensibility to ensure it can cover all aspects of the application definition.
3) SAP NetWeaver BI KitA prefabricated kit enables automatic code generation based on SAP NetWeaver BI and other data providers without any coding
© SAP AG 2006, 34
Create an Application Using Visual Composer – Processes
DevelopingFor building applications, Visual Composer makes use of pre-built components. For R/3 systems, the pre-built components are either BAPIs or RFCs. For SAP BI systems, the pre-built components are queries and views.
ModelingVisual Composer allows you to easily model a freestyle application.
TestingVisual Composer provides built-in tools to easily check the model and application for errors
Configuring and adaptingConfigure the application to your needs to improve the user experience
UpgradeTo upgrade your application, you can either change the BAPI/RFC order or implement a new one using Visual Composer
Developing Modeling Testing Configuring and Adapting Upgrade
© SAP AG 2006, 35
Developing Modeling Testing Configuring and Adapting Upgrade
Creating Applications Using SAP NetWeaver Visual Composer
AS ABAP:ABAP Workbench
EP:UI RuntimePersonali-zation
(12) Personalize implicitly or explicitly or as permitted by the administrator
EP:Visual Composer
(3) Model freestyle application
(2) Discover BAPI/RFC
(5) Run applicationin preview
(4) Check modelfor errors
(9) Customize application if applicable
(8) Reconfigure/ change application if necessary
(14b) Upgrade model by switch tonew BAPI
(14a) No action required
EP:Portal ContentStudio
(7) Check application within portal (11) Redefine roles
(6) Deploy in portal(10) Redesign page
(13a) Change BAPI/RFC
(13b) Implement new BAPI/RFC
(1) ImplementBAPI/RFC
© SAP AG 2006, 36
Developing Modeling Testing Configuring and Adapting Upgrade
Creating Applications Using SAP NetWeaver Visual Composer (cont.)
AS ABAP:ABAP Workbench
EP:UI RuntimePersonali-zation
(12) Personalize implicitly or explicitly or as permitted by the administrator
EP:Visual Composer
(3) Model freestyle application
(2) Discover BAPI/RFC
(5) Run application in preview
(4) Check model for errors
(9) Customize application if applicable
(8) Reconfigure/ change application if necessary
(14b) Upgrade model by switch to new BAPI
(14a) No action required
EP:Portal ContentStudio
(7) Check application within portal (11) Redefine roles
(6) Deploy in portal(10) Redesign page
(13a) Change BAPI/RFC
(13b) Implement New BAPI/RFC
(1) Implement BAPI/RFC
© SAP AG 2006, 37
Creating a Popup iView
Creating a Popup iViewStart with a basic modelas shown on the rightSelect the Input Form and choose Configure from the task-panel toolbarClick on the plus icon Select Push Button fromthe listChoose a Field name
© SAP AG 2006, 38
Creating a Popup iView (cont.)
Creating a Pop-up iView(cont.)
Create a layout similarto the one shown on the rightDo an alternative clickon the Choose Bank button Select Properties from the context menuChoose the Action taband enter an action name (make sure to have Custom action selected)
© SAP AG 2006, 39
Creating a Popup iView (cont.)
Creating a Popup iView(cont.)
Drag out from InputForm and choose Open PopupIn the Select Popup iView window, choose Create new iViewMake sure that the eventconnected to the Popup iView is named accordingly (such as CHOOSE_BANK)Do an alternative click on the Popup icon andselect Drill Drown
© SAP AG 2006, 40
Creating a Popup iView (cont.)
Creating a Popup iView(cont.)
Create a new (Popup) iView similar to the modelon the rightCreate a start point with only BANK_CTRYand remove MAX_ROWSfrom the required listCreate an end point withBANK_CTRY and BANK_KEY and renamethe event (such as CLOSE)Do an alternative click on Bank List Grid and chooseCustomize ToolbarCreate a new button to trigger the custom event (such as CLOSE)Finally, map the fields in the original iView accordingly
© SAP AG 2006, 41
Creating a Wizard
Creating a WizardStart with the basic model as shown on the rightChoose Composefrom the task-panel toolbar and createthree layers (such asEnter Country, SelectBank, and View Details)Change the modelaccordingly, as shownon the right
© SAP AG 2006, 42
Creating a Wizard (cont.)
Creating a Wizard (cont.)Create transitions by choosing the different layers and dragging thegreen dot to build a connection between the layersCreate buttons for thedifferent steps using custom events accordingly to the Popup iView exampleThe model should looksimilar to the one on the rightNote: There is a built-inevent for going one step back
© SAP AG 2006, 43
Basic Model
Create the following model:Choose Data ServicesBank Getlist (BAPI_BANK_GETLIST) and Bank GetDetail(BAPI_BANK_GETDETAIL)and connect themCreate input form, table view, and form view accordinglyCreate a start point with the values “DE” for BANK_CTRY and 10 for MAX_ROWSMap fields between services accordinglyDesign layout as shown
© SAP AG 2006, 44
Demo
Demo
© SAP AG 2006, 45
Demo (cont.)
Demo
© SAP AG 2006, 46
Demo (cont.)
Demo
Creating Analytics Apps
BI and Analytics
Why Analytics?
Application Modeling and the Visual Composer
Wrap-up
© SAP AG 2006, 48
Data Connectivity via the BI VC Extension Kit
Connectivity to BI systems defined in the portal based on:
BI Java Connectors:BI XMLA Connector (OLAP data sources such as SAP BW 3.x)BI ODBO Connector (ODBO-compliant OLAP data sources) BI JDBC Connector (relational JDBC-compliant data sources) BI SAP Query Connector (a component of the SAP Web Application Server Basis)
The SAP BI Connector against an SAP BI systemThe “BI connector” gives you direct access to services needed for the SAP BI-specific integrationThis comprises services for design time, as well as runtime, e.g., object access (including History and Favorites), metadata access, and data access
© SAP AG 2006, 49
Business Explorer Suite (BEx)
Business Explorer Suite and VC Integration
Visual Composer BI Integration
UDI
XMLASAPQuery JDBC ODBO
BEx Query Designer
Information Broadcasting
Web Analyzer
WebApplication
DesignerMS Excel
Add-inReport
Designer
BEx Web
DB Connect BAPI Service
API File XML/A
BEx AnalyzerBI Pattern
BI Consumer Services
BI Platform
Data Warehouse
Enterprise Portal
Analytic Engine Meta Data Mgr
BI Connector
© SAP AG 2006, 50
Overview – Relational Connectors
SAP JCo SAP Query – a component of SAP’sWeb Application Server that allows you to create custom reports without any ABAP programming knowledge.
SAP operational applications
Examples:Data in transactional systems such as R/3, Ad-hoc, and Operational Reporting
BI SAP Query Connector
JDBC driverSun’s JDBC (Java Database Connectivity) –the standard Java API for Relational Database Management Systems (RDBMS)
Relational data sources: Over 170 JDBC drivers
Examples:Teradata, Oracle, Microsoft SQL Server, Microsoft Access, DB2, Microsoft Excel, text files such as CSV
BI JDBC Connector
System Requirements
Technology based on:
Access to:Connector
© SAP AG 2006, 51
Overview – Multi-Dimensional Connectors
System Requirements
Technology based on:
Access to:Connector
None Microsoft’s XMLA (XML for Analysis) -– Web services-based, platform-independent access to OLAP providers. Exchanges analytical data between a client application and a data provider working over the Web, using a SOAP-based XML communication API.
OLAP data sources
Examples:MS Analysis Services, Hyperion, MicroStrategy,and BW 3.x
BI XMLA Connector
Microsoft Windows 2000/NT/XP
Microsoft’s OLE DB for OLAP – the established industry-standard OLAP API for the Windows platform.
OLAP data sources: OLE DB for OLAP-compliant data sources
Examples:Microsoft Analysis Services, SAS, Microsoft PivotTable Services
BI ODBO Connector
© SAP AG 2006, 52
Overview – BW Web API Connector
System Requirements
Technology based on:
Access to:Connector
BW 3.5 SPS 14BW Web APISAP NetWeaver BISAP BI Connector
NOTE: The BW Web API system is created using the standard SAP R/3 system types; the system type needs to be specifically labeled as an SAP BW system type
1. Dedicated Application Server for R/3 System (used in our example)
2. R/3 System via Connection String 3. R/3 System with Load Balancing
© SAP AG 2006, 53
BI Integration Wizard
BI Integration WizardThe BI Integration Wizard (formerly known as BI Query Wizard) gives you access to multiple data sources either via the Java Connectors or the BI ConnectorThe BI Integration Wizard is used to create query templates (e.g., percentage share, Top N, Freestyle, etc.)The set of templates available depends on whether the data service you have selected is an OLAP or a relational data serviceDepending on the Java Connector that is used, you can also work with an SQL or MDX editor directly
© SAP AG 2006, 54
Model RepositoryJ2EE DB
Web browser/Client
Deploy iView
Portal page
Architecture of the VC BI Integration
SVG plug-in/MSXML parser
Visual Composer Server
SAPBI and BEx
non-SAP
SAPQuery XMLA JDBC ODBO
SAPEnterprise
BIConnector
SAPConnector
EP
Connector Framework
Visual Composer Portal Add-on
System Landscape
J2EE
Design time
Runtime
© SAP AG 2006, 55
How Visual Composer and Flex Work Together
Venn Diagram
Flat Line Graph
Pie Chart Grid
Rotation Rich View
Bar Graph
Form View
Chart View
Visual Composer withembedded Flex Server
Macromedia Flex MXML Compiler
SWF Files
SAP J2EE Engine
Macromedia .war file
Server
Design Time
MXML and ActionScript
Deployment
CompiledSAP
Analytics ApplicationData Services
SAP, Non-SAP(OLAP, Relational)
Visual Composer
Model
Runtime SAP Analytics Applicationon End-User Client
Library of FlexComponents
© SAP AG 2006, 56
SAP NetWeaver VC and BEx Web Application Designer
Web Application Designer Focus The BEx Web Application Designer lets business analysts build BI Web Applications and Dashboards:
That can fully leverage SAP BI’s analysis and planning services
With the BEx Web Application Designer, you can access SAP BI andthird-party BI data
And build highly interactive planning and analysis applications
© SAP AG 2006, 57
SAP NetWeaver VC and BEx Web ApplicationDesigner (cont.)
Visual Composer BI Kit FocusThe VC BI Kit can access SAP and non-SAP (including OLAP and relational) data via the BI Java Connectors
And lets business users build applications that are highly integrated with transactional data such as that from an ERP systemSAP BI is only one of many possible data providers
Visual Composer’s current focus is not on multi-dimensional analysisand planning
These services are only provided via the BEx Web Application Designer
Creating Analytics Apps
BI and Analytics
Why Analytics?
Application Modeling and the Visual Composer
Wrap-up
© SAP AG 2006, 59
Further Information
Public Webwww.sap.comSAP Developer Network: www.sdn.sap.com*SAP Customer Services Network: www.sap.com/services/SAP Service Marketplace: www.service.sap.com/nw-vc*
Related SAP Education Training Opportunitieshttp://www.sap.com/education/
* Requires login credentials to the SAP Service Marketplace
© SAP AG 2006, 60
For More Information: Access the SAP Developer Network – www.sdn.sap.com*
The central hub for the SAPtechnology community
Everyone can connect, contribute and collaborate – consultants, administrators,and developersFocus around SAP NetWeaver and SAP xApps
High quality of technical resourcesArticles, how-to guides, Weblogs, collaborative areas, discussion forums and downloads, toolkits, and code samples
A collaboration platform, not a one-way street
SAP experts from customers, partners and SAP
SDN is powered by SAP NetWeaver™Built on the SAP Enterprise PortalFeaturing collaboration capabilities of SAP Knowledge Management
© SAP AG 2006, 61
7 Key Points to Take Home
SAP Analytics provides a true 360-degree customer view, integrating the expertise of business users in real timeVisual Composer has the potential to expose valuable information within the context of a business processSAP BI and non-SAP BI fit together with Visual Composer for the building of analytic applicationsVisual Composer’s three-step approach involves flexible design, a modeling language, and automatic code generationA good application modeling language should be based on the principles of end-user programming; it should be exploratory, simple, direct, expressive, and extensibleCreating a simple analytic application requires an understandingof the basics of the design-time environment and the overall goal of the toolYou can create query templates with the BI Integration Wizard, with access to multiple data sources
© SAP AG 2006, 63
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, Outlook, and PowerPoint 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, and Informix are trademarks or registered trademarks of IBM Corporation.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. MaxDB is a trademark of MySQL AB, Sweden.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 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.
Copyright 2006 SAP AG. All Rights Reserved
