Mobile Application Modeling for SAP CRM Mobile Applications for Laptops

Transcription

1 Mobile Application Modeling for SAP CRM Mobile Applications for Laptops Applies to: SAP CRM Mobile Applications for Laptop (all SPs of Release 5.0) Summary This document acts as a guide to developers who need to model Mobile Application for Laptop. It describes how each development object can be modeled using Mobile Application Studio. Author(s): Santosh V Company: SAP Labs India Pvt. Ltd. Created on: 06 March 2007 Author Bio Santosh V is a Development Lead for SAP Labs India. He has been working in the CRM Mobile Applications for Laptop area for close to 4 years. He has a total experience of 7 years in the software industry. He also specialises in developing Web Applications using ASP and ASP.Net SAP AG 1

2 Table of Contents Mobile Application Studio... 3 Solution Explorer... 3 Changelist Explorer... 4 Modeling Business Object Layer Objects... 5 Business Object... 5 Business Query... 5 Combo engine... 5 Business Rule... 5 Modeling User Interface Layer Objects... 6 Tile... 6 Anchor Modeling... 6 Tileset... 7 Anchor Modeling... 7 Business Component... 9 Application Generation Settings Related Content Copyright SAP AG 2

3 Mobile Application Studio Mobile Application Studio (MAS) provides a Visual Development Environment for modeling Mobile Applications for Laptop. Most of the modeling is done visually with very minimal need for manual coding. It has inherent support for change management and software logistics. Once the modeling is done, an effortless generation process generates the Mobile Application. The development landscape can be pictorially represented as below Solution Explorer The Solution Explorer in Mobile Application Studio displays all the Development Objects SAP AG 3

4 Changelist Explorer The Changelist Explorer in Mobile Application Studio displays all the changelists (Open, Released etc.). Any change made to a Development Object should be part of a changelist. The changelist has to be tested and released to baseline SAP AG 4

5 Modeling Business Object Layer Objects Business Object Modeling a Business Object is similar to modeling a class. A Business Object has Properties, Methods and Event Handlers. It can be bound to a BDoc or can be unbound. The Properties in the Business Object can be bound or unbound. And they can also be associated to a Combo Engine. In addition, Save Rules (fired when the Business Object is saved) and Delete Rules (fired when the Business Object is deleted) can be associated to the Business Object. Some Business Objects are also provided with User Exits which allow the customer to do some customizing. Business Query Modeling a Business Query is similar to modeling a query. Every Business Query has an underlying Query BDoc. The Properties of the Business Query are parameters to the BDoc. The result of the query will be a Business Collection. Combo engine A Combo Engine can be associated to a Property of a Business Object or Business Query. It returns a combination of Long Text and Short Text. It has an underlying query BDoc and parameters can be specified for the BDoc (for example, Hierarchical Combos). Business Rule Business Rule is a function which returns True or False based on validations done. It can be associated to a Business Object as a Save Rule or Delete Rule. It can also be added as a Property Rule for a Property to do Property level validations SAP AG 5

6 Modeling User Interface Layer Objects Tile The Controls in a tile can be bound or unbound. Every control in the tile should be associated with an anchor. There are three different types of tiles. They are Detail Tile Search Tile List Tile Anchor Modeling The anchors at the tile level are also called as Connectors. All controls in the tile should be present under an anchor and the anchor can be either bound or unbound. The bound anchor at the tile level links Business Object or Business Query Properties with the controls. It is also possible to have a hierarchy of connectors. The figures below illustrate the use of Connectors in the Business Partner Details tile SAP AG 6

7 Tileset A tileset contains tiles. It can have a maximum of 6 tiles. There are three different types of tilesets. They are Standard Find / Choice Custom Popups Anchor Modeling Anchors at the tileset level link data across the different tiles in the tileset. This can be done through Business Anchor Mapping or Business Anchor Hierarchy. The following are the characteristics of Business Anchor Mapping - Maps the business anchor of one interaction component to the business anchor of other interaction component. The mapped anchors have the same underlying Business Object. Example, used in List / Detail Tileset. The following are the characteristics of Business Anchor Hierarchy - Used to display related data. The underlying Business Objects of the anchors can be related through Relationships, Supply Method or Query Result. Example, used in Detail / List Tileset. The following figure illustrates the anchor modeling (both Business Anchor Mapping and Business Anchor Hierarchy) in the Business Partner -> Sales Transactions tileset SAP AG 7

8 In the Search tileset, Business Anchor Hierarchy is used and the anchors are related through Query result. The following figure illustrates the anchor modeling in the Employees -> Search tileset SAP AG 8

9 Business Component A Business Component contains tilesets. The data between tilesets can be connected through anchors at the tileset level. The following figure illustrates the anchor modeling in Business Component Employees SAP AG 9

10 Application An Application is a collection of Business Components. Each Application has a Short Name. Hyperlinks are designed at the Application level. Hyperlinks allow navigation across Business Components SAP AG 10

11 Generation Settings Once the changes are made to the development objects in the Business Object or User Interface layer, the changes have to be generated. Before generation, certain settings have to be done. The important setting in the Business Logic tab is Industry Template and the important setting in User Interface tab is Application SAP AG 11

12 Related Content Mobile.Net Client in SDN Introduction to Mobile Sales Application for Laptops Mobile Application Framework for Laptop Solutions 2006 SAP AG 12

13 Copyright Copyright 2006 SAP AG. All rights reserved. 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, Informix, i5/os, POWER, POWER5, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation. 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. 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. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. These materials are provided as is 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 not be liable for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. SAP does not warrant the accuracy or completeness of the information, text, graphics, links or other items contained within these materials. 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. Any software coding and/or code lines/strings ( Code ) included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, except if such damages were caused by SAP intentionally or grossly negligent SAP AG 13