370 likes | 511 Views
Getting More From SAP. David Jobling, CTO, Avanade UK Steve Butcher, Senior Architect for Mobile Solutions, Avanade UK Stef Shoffren, Snr Principal Consultant, Avanade UK. Agenda. Introduction SAP and Performance Point Analytics SAP and Windows Mobile Q&A. Introduction.
E N D
Getting More From SAP David Jobling, CTO, Avanade UK Steve Butcher, Senior Architect for Mobile Solutions, Avanade UK Stef Shoffren, Snr Principal Consultant, Avanade UK
Agenda • Introduction • SAP and Performance Point Analytics • SAP and Windows Mobile • Q&A
Introduction • Thousands of SAP implementations worldwide – customised • Cost of client licences prohibits the dissemination of the data • ‘SAP Surround’ is a suite of patterns and techniques to make SAP data more available and easier to work with • Extract to SQL Server for low cost, high value reporting and analytics • Expose via new channels using stock technology such as .NET and Windows Mobile
Performance Point Analytics and SAP Customer Case Study Stef Shoffren
Customer Situation • Large, multi-national consumer goods company • Fragmented ERP systems • Converging onto SAP • Fragmented Reporting systems throughout Europe • Additional reporting requirements
Why not use SAP Bex? • SAP Business Explorer allows reporting on SAP BW held data but.... • Can be very slow • Unintuitive for users • Lacking in functionality • Within the customer, SAP BW is vertically separated by country
Why use Microsoft PerformancePoint Analytics • Clean easy to use interface • Web delivery of reports • Export to Excel functionality • Rich charting • Fast implementation times • High performance • European reporting possibilities
Parallel Projects • Sales Reporting • Large volumes • Data source: Multiple SAP BW databases • Promotional Analysis • Medium volumes • Data sources • Multiple SAP BW Databases • Siebel
SAP BW Terminology • InfoObject • A reference object (eg customer, product) • InfoCube • Self-contained dataset, normally localised to a business area (eg Direct Sales cube) • InfoSpoke • Mechanism to extract data from InfoObjects/InfoCubes
High Level Architecture • Web Front End Scale Out • Analysis Services Scale Out
Landscape Alignment BW Support Track 3 3 2 1 LEGEND F T PP P Change flow SSAS Support Track Data flow 2 1 3 PP P F / T SSASSQL 2005 SSAS Release Track BWNW 2004 U R D / T Production sized 3 3 1 1 E DR sized 2 3 Development sized 3 BW Release Track D T U R 3 3 3 1 E 3
Solution Development • Staged Rollout Sync’d with SAP Rollout • Major and Minor Release schedules aligned • Leveraged Avanade Global Delivery Network • Migrate Development offshore over time • Provide offshore support for long term cost effectiveness • Team Foundation Server for Source Control • Access to TFS for WAN – TFS Proxy?
Getting the Data out of SAP BW • SAP OpenHub Service Provides InfoSpokes • Specify DataSource (InfoObject or InfoCube) • Specify Mode (Delta or Full) • Specify Destination (Database or Flat file) • Limitations • Resetting of the source data in BW will reset the delta • InfoObjects need 2 InfoSpokes (1 for attributes, 1 for texts)
Adding Value with the ETL • SAP InfoObject provide a fragmented view of dimensions • Eg Product is split into 3 separate areas with no combined view • Value add: Provide a unified view of products • Bill of Materials are provided as separate measures • Only a few measures are provided for BOMS • Provide ANY measure with the ability to be analysed by BOM • ACA Analytics • ETL Framework • Lineage Tracking
Best Practices • Prevent Duplicate Runs • Use the OHREQUID to identify if data is already loaded • Use Delta InfoSpokes for large source datasets that are frequently changing • Need for Lineage Tracking
Futures • SQL Server 2008 • Multiple Readonly SQL Server Analysis Services Instances • C# for ETL coding • SSIS Performance Improvements • Additional Divisional Reporting • Financials
Mobile SAP Steve Butcher
Project Background • Customer Summary • Resources organisation present in 25 countries over five continents • 4,766 Employees, 1,716 UK based • Customer Relationship • Successfully introduced Windows Mobile as a viable alternative to BlackBerry • Deploying Windows Mobile across International countries as a platform for mobile messaging • Customer Challenge • Restricted access to SAP back office functionality restricted to internal network or VPN • Accessibility of Workflow and Business Intelligence through Enterprise Portal
Aims and Objectives • Aims and Objectives • Extend the reach of SAP systems • Enable users to interact with business workflow processes • Leverage the Windows Mobile platform • Minimise impact on SAP systems and development team • Inherit security levels and roles enforcing data access • Enhanced Functionality • Add functionality to filter data by column and row to easily view and navigate BI data • Ability to visualise data through chart representation • Corporate Programmes • Workplace of the Future
Proposed Mobile Solution • Utilise Avanade mobile solution platform to provide remote offline access to Enterprise Portal, Business Intelligence and SAP Workflow • Publish data through mobile application gateway using customer virtualisation environment 22
High Level Solution Architecture Mobile Enablement Platform (4 Main Elements) • Integration Layer • Mobile Application Gateway • Synchronisation Services • Device Application 23
Solution Components | SAP Integration • SAP Integration Layer • Enterprise Portal • Business Intelligence • Workflow 24
Solution Components | Mobile Application Gateway • Mobile Application Gateway (MAG) Functions • Extensible gateway controlling data flow • Processing of data retrieved through integration layer • Application workflow management • Data manipulation based upon business logic 25
Solution Components | Sync Services • Synchronisation Services Functions • Optimised data transfer mechanism • Offline data storage • Secure data transfer • Windows Active Directory integration • Network connectivity management • Scalable architecture based upon standard Microsoft technologies 26
Solution Components | Device Application • Device Application Functions • Data Presentation • User Credentials Capture • Data Updates • Synchronisation Initiation 27
Implementation Approach • Prototype integration options • Enterprise Portal: WebDAV • Business Intelligence: .NET SQL Data Provider • Workflow: Web Services • Implement mobile application gateway (MAG) • Design / Implement Solution Architecture • Utilise Production Virtual Environment • Publish to the Internet • Develop mobile application • Agree process flow • User Interface • Forms Navigation
Implementation Approach | Prototype SAP Integration • Enterprise Portal • Options: RSS, WebDAV • High Level Tasks: Access WebDAV folder, Process XML, Store in Database • Main Issues: .NET unable to access SAP WebDAV • Business Intelligence • Options: Direct Database Integration, Database Pass-through • High Level Tasks: Enable external access to SAP query, Prove access to SAP Query using SSRS, Store query output in DB • Main Issues: Data Serialisation • SAP Workflow • Options: .NET Connector, Web Services • High Level Tasks: Identify ABAP function, Remote Enabled, Create Web Service, Generate WSDL • Main Issues: External Web Service access, J2EE Server required
Implementation Approach | Mobile Application Gateway • High Level Tasks: • Design Solution Architecture • Implement Web Services • Implement SQL Replication • Main Issues: • .SQL Replication (SQL Mobile versions)
Implementation Approach | Mobile Application Gateway • High Level Tasks: • Deploy Mobile Application Gateway (MAG) on virtualization platform • Publish to Internet • Implement security model
Implementation Approach | Mobile Application Gateway • High Level Tasks: • Main Issues: • Users vs. Business Input • Process Flow • Forms Navigation • UI Design • Security (ACA Devices) 33