MOB230 – Developing Simple Mobile Applications Using OData
Wednesday 8:00 a.m.
This is an alternative method for developing mobile apps for SAP. The OData method differs from MBO method in that OData requires one less server-side process. The device makes calls directly into the backend system (through an SAP gateway and SUP), bypassing the MBO data modeller. This is a more simple footprint, but you lose the potential benefit of caching all results in the middleware and retrieving only the results you need to display on the device.
CD205 – Technology Preview: ABAP Programming Model Evolution
Wednesday 9:15 a.m.
2. Improvements to the data modeling concept and type system w.r.t. table relationships. It sounds like many of these improvements are in preparation for making SAP R/3 available for the SAP HANA system.
3. Enhancement to service consumption and data binding outside of Web Dynpro. I don’t get this yet – is it for standard ABAP or mobile or what? It was all theory – no example.
4. Listened to an overview of the Advanced Query Language (AQL) – again in support of SAP HANA. This is basically a copy of .NET’s LINQ to SQL, only in ABAP. Looks pretty neat and provides performance improvements in that it only retrieves data requested instead of traversing nested loops to get at related data.
CD260 - SAP NWBC: Enhancing SAP GUI With the Side Panel
Wednesday 10:30 a.m.
NetWeaver Business Client NWBC can be used either as a desktop installation or as NWBC for HTML, access through the browser. In the 2nd case, no client installation is required. PFCG is used to configure role-based menus and side panels in NWBC. Floor Plan Manager (FPM) is used to design simple UIs for transactional data. Page Builder is used to combine views from disparate, related content into one screen. This is awesome. Just listening I can think of many business cases for this: reviewing financial report – show sidebar of specific BW chart; reviewing material – show sidebar of current AMPL; in the enhanced MIGO ‘KEG Material’ tab, move the classification table and AMPL to sidebars to make room if additional fields are requested. SAP has developed and provided a number of side panel CHIPs out of the box.
MOB265 - OData Mobile App using SUP via SAP NetWeaver Gateway
Wednesday 2:15 p.m.
OData is short for Open Data. It’s a REST-based protocol that is becoming popular because it uses less bandwidth than SOAP. The SAP NetWeaver Gateway is a piece of software that is installed into SAP NetWeaver and talks OData. The SUP is an application that provides reverse proxy and user management services for devices and talks to the SAP NetWeaver Gateway. There are open source alternatives to the SUP. Entity modeler file (.edmx) was generated using Visual Studio 2010 (coming to Eclipse later). Great lab. I learned a lot about the back-end portion of the development. I skipped the 2nd half (regarding SUP and Eclipse) to check out some other lectures.
MOB105 - Mobilizing SAP Workflow Approvals at HD Supply
Wednesday 4:30 p.m.
HD Supply is a big Blackberry shop. Explored three potential solutions for mobile delivery of workflow. Choice: Leapfactor (not Sybase!). The team utilized SAP Workflow to create a standard SAP approval step to be placed in the SAP Inbox. Next a task was scheduled to retrieve changes to workflow inbox items and push it to the mobile device. The development of the mobile application was not discussed in detail.
TEC203 - SAP User Interface Strategy and Roadmap
Wednesday 5:15 p.m.
No strategy. Just a review of every possible UI option.
BI105 - SAP HANA: How to Set Up a High Value Analytic Scenario
Wednesday 5:45 p.m.
1. SAP HANA comes as a big empty black box. The first step is to model your data. You transfer the data to HANA in-memory db. Develop a Business Object (BOBJ) to query HANA. Then design a web report to use the BOBJ.
2. There is something called the HANA Studio used to create the tables in HANA. You need to create all necessary tables: KNA1, MARA, T001W, etc. At some point, there will be a way to model your tables from ERP and import them to HANA – it’s not there yet. Next you need to maintain the source/target system connection. Today this is NOT simple. Next you load the data: tables, BW extractors, files, web services.
3. HANA has three views: attribute view, analytical view, calculation view. You use these to create measures and dimensions. HANA is NOT a replacement of SAP BW. In ~60 days, HANA is a potential database for BW. Starting to get the idea on this: move all the data as-is to HANA; write a calculation view that performs calculations in memory to transform to the result data; display report.