Customization of SAP Sales Manager 2.5

SAP How-to Guide SAP Mobility Customization of SAP Sales Manager 2.5 A Branded Service provided by SAP Rapid Innovation Group Applicable Releases: SAP Sales Manager 2.5 Target Audience: CRM consultants Mobility consultants ABAP programmers Version 1.0 August 2013

Copyright.SAP AG. All rights reserved 2013 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, PowerPoint, Silverlight, and Visual Studio 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, z10, z/vm, z/os, OS/390, zenterprise, PowerVM, Power Architecture, Power Systems, POWER7, POWER6+, POWER6, POWER, PowerHA, purescale, PowerPC, BladeCenter, System Storage, Storwize, XIV, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX, Intelligent Miner, WebSphere, Tivoli, Informix, and Smarter Planet are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the United States and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countries. Oracle and Java are registered trademarks of Oracle and its affiliates. 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. Apple, App Store, ibooks, ipad, iphone, iphoto, ipod, itunes, Multi-Touch, Objective-C, Retina, Safari, Siri, and Xcode are trademarks or registered trademarks of Apple Inc. IOS is a registered trademark of Cisco Systems Inc. RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry Torch, BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry App World are trademarks or registered trademarks of Research in Motion Limited. Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps, Google Mobile Ads, Google Mobile Updater, Google Mobile, Google Store, Google Sync, Google Updater, Google Voice, Google Mail, Gmail, YouTube, Dalvik and Android are trademarks or registered trademarks of Google Inc. INTERMEC is a registered trademark of Intermec Technologies Corporation. Wi-Fi is a registered trademark of Wi-Fi Alliance. Bluetooth is a registered trademark of Bluetooth SIG Inc. Motorola is a registered trademark of Motorola Trademark Holdings LLC. Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAP HANA, 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 Business Objects Software Ltd. Business Objects is an SAP company. Sybase and Adaptive Server, ianywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc. Sybase is an SAP company. Crossgate, m@gic EDDY, B2B 360, and B2B 360 Services are registered trademarks of Crossgate AG in Germany and other countries. Crossgate is an SAP company. 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.

Document History Document Version Description 1.00 The first official release of this guide. August 2013

Typographic Conventions Type Style Example Text Description Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options. Cross-references to other documentation Icons Ic on Description Caution Note or Important Example Recommendation or Tip Example text Example text Example text <Example text> EXAMPLE TEXT Emphasized words or phrases in body text, graphic titles, and table titles File and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools. User entry texts. These are words or characters that you enter in the system exactly as they appear in the documentation. Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system. Keys on the keyboard, for example, F2 or ENTER.

Table of Contents 1. Overview... 1 1.1 About the How-to-guide... 1 1.2 Who Should Use This Guide... 1 1.3 Business Use Case... 1 1.4 Background Information... 1 2. Customization Overview... 1 2.1 Data flow Overview... 1 3. Technical Details... 2 3.1 DO - Standard Data Objects... 3 3.2 DT - Data Tables:... 3 3.3 CT - Complex tables... 4 4. Add New Field to CRM Opportunity Header... 5 4.1 Updating the BAPI Wrapper Configuration... 6 4.2 Updating the Mobile Data Object Configuration... 6 4.3 Mobile Application Configuration... 7 4.4 Extending the Java Classes... 7 4.5 Adding the field to the SAP Sales Manager 2.5 UI screens (Agentry Editor)... 8 4.5.1 Add Property to the Object... 8 4.6 Add field PurposeLabel and Purpose to the Opportunity Detail View Screen Set... 9 5. Extensibility Options... 12 5.1 User Profile Parameter... 12 5.2 Static Value in Range Format... 13 5.3 Syclo Filter Class Handler... 14 5.4 Runtime Session Data... 14 6. Summary... 15 7. General References and Links... 15

1. Overview 1.1 About the How-to-guide This guide explains various customization options available with the SAP Sales Manager 2.5 application. It provides a brief overview of the different ways to achieve the customization in SAP Sales Manager 2.5. 1.2 Who Should Use This Guide This documentation is intended for all consultants who extend the SAP CRM Sales mobile application including CRM consultants, Mobility consultants and ABAP programmers. 1.3 Business Use Case You have implemented the SAP Sales Manager 2.5 and need to customize the mobile application to meet your requirement. SAP Sales Manager 2.5 is built on the SAP Agentry Platform which provides extensibility, customization and restriction capabilities to address most complex business needs. Latest version of CRM Sales Mobile is SAP Sales Manager 2.5. 1.4 Background Information CRM Mobile Sales 2.0.x/2.1.x is based on DOE + SUP architecture and SAP Sales Manager 2.5 is based on SAP Agentry Platform. Existing customers of CRM Mobile Sales 2.0.x/2.1.x might have customized the mobile application and might need to do the same on SAP Sales Manager 2.5. For new implementation of SAP Sales Manager 2.5, customer might need to perform customization to meet their business needs. This document provides different ways to customize mobile application. In reality customer need to analyze implementation details and provide detailed analysis on the changes to be done via different enhancements techniques and find a suitable way listed in this document to carry forward with their customization. 2. Customization Overview 2.1 Data flow Overview To perform customization in SAP Sales Manager 2.5, it is necessary to understand the data flow between SAP CRM system and the Mobile device and how this flow can be adjusted to allow additional fields or attributes to be inserted in appropriate places. The following diagram gives a high-level overview of the data flow from SAP CRM to the device and from the device to SAP CRM. September 2013 1

SAP CRM Sales Manager 2.5 Business Objects Tables (Existing Fields) A New Fields (Added using AET) Agentry SAP Framework (Config Panel) Mobile Data Object Configuration ResultSet Field Selection + Data Filters DT Data Tables CT Complex Tables DO Standard Data object Create Get Update Master Data/Transactions BAPI + Customer BAdIs BAPI Wrapper Configuration Agentry Server Agentry Editor Objects Transactions Screen Sets Actions Fetches Rules Steps Pushes Service Events Business Objects * Java Layer Mobile Device SAP Sales Manager 2.5 App (ios, Android) 3. Technical Details Any new field or table added in the CRM system is mapped to three kinds of Data Objects for the Sales Manager 2.5 application. DO - Standard Data Object: A multi-dimensional representation of a business object with multiple tables representing different subsets of the business object. DT - Data Table: A simple representation of SAP business objects KEY and VALUE. CT - Complex Table: A two-dimensional representation of a business object with a single table of multiple columns. CAUTION: Mobile data objects should be created, copied, or changed only by the mobile application developer or system administrator. September 2013 2

3.1 DO - Standard Data Objects If the field added is a simple input field, text type, date/time picker etc. can be accessed by BAPIs for the relevant standard data object 3.2 DT - Data Tables: If the field has a DDLB or a key value pair entry, then we need to add a Data Table which has the underlying table from CRM backend with these key value pairs exposed to the mobile app through the relevant BAPIs for data tables September 2013 3

3.3 CT - Complex tables If the field requires more than two columns for e.g., process type comes from the SPRO Config for Transaction Types and needs more than just key value pairs to determine the same for a leading business category. These values are mapped in the BAPI for the respective complex table. Java layer has business objects which map the Java Object properties to these fields in the BAPI and the Java object methods call the relevant BAPIs to perform the various create/update/read transactions from the device UI. The mapping is done in the Config Panel portal Mobile Application Configuration SAP_SALES MANAGER_25 September 2013 4

The Agentry Screens, Transactions, Actions, Fetches, and all screen elements which get data from CRM backend are on top of the Java layer. Any change to a data flow from or to the screen has to be processed via the Java layer. 4. Add New Field to CRM Opportunity Header As an example we add a new field to the CRM Opportunity Header detail screen on the CRM Web UI using AET. Field Label: Table: Technical Field: Table Type: Values: Purpose and is available after adding through AET in the table CRMD_ORDERADM_H. ZZORDERADM_H0101. DDLB In Value Range (Office, Home, Mobile) September 2013 5

4.1 Updating the BAPI Wrapper Configuration The BAPI Wrapper: /SYCLO/CRMBTX_DOOPPORT_GET maps all the fields from one order tables for an opportunity, i.e. all the ET_* export tables from CRM_ORDER_READ to the Java class object properties for the Opportunity object. Since any new field added in CRM backend via AET will add the field to the ORDERADM_H table for the header enhancement, this field will be available in the export table ET_ORDER_HEADER. So no change is required to this BAPI wrapper. 4.2 Updating the Mobile Data Object Configuration Following are steps that need to be performed to update the Mobile Data Object Configuration. Go to the DO-Standard Data Object of Opportunity in Agentry Framework: Data Object ID: SSLM25_OPPORTUNITY ResultSet Field Section: Table CRMD_ORDERADM_H* The newly added field ZZORDERADM_H101 will be part of the table fields, available to be exposed to the application. Click on the Field Active checkbox. This enables the field to be mapped to the Java object class properties. Go to DT-Data Table in Agentry Framework: Create a new Data Table with following naming convention: Data Object Id: SSLM25_OPPORTUNITY_PURPOSE Description: SSLM 2.5 Opportunity Purpose Define Filter: Get Method GET Filter PURPOSE Reference Table Name CRMC_PRUPOSE_T (Table having the values as per the logged-in language) Reference Field Name PURPOSE DO Handler - /SYCLO/CL_CRMMD_OPP_PURPOSE_DO For creating the DO Handler class you need to follow the following steps: 1.) Create the handler /SYCLO/CL_CRMMD_OPP_PURPOSE_DO 2.) Inherit the superclass /SYCLO/CL_CORE_DT_HANDLER 3.) Redefine the methods GET_DATA_TABLE /SYCLO/IF_CORE_FILTER_SERV~GET_DATA_FILTER_LIST /SYCLO/IF_CORE_FILTER_SERV~GET_DATA_FILTER_VALUESET For an example implementation, you can refer to the handler /SYCLO/CL_CRMMD_OPP_ORIGIN_DO September 2013 6

4.3 Mobile Application Configuration From the home page of the Agentry SAP Framework, click on Mobile Application Configuration and select the Mobile Application SAP_SALES_MANAGER_25 and go to the Parameters tab and add following parameter to the list: Parameter Group: SAPOBJECT Parameter Name: Opportunity Parameter Value: com.syclo.sap.component.opportunity.object.opportunity The Java object will be extended and named com.syclo.sap.customer.opportunity.object.opportunity. This will be covered in the Java Classes section below. So the entry above has to be changed to the new enhanced Java package. Another new parameter needs to be added here with the details below: Parameter Group: DT_MDOID Parameter Name: DTOpportunityPurpose Parameter Value: SSLM25_OPPORTUNITY_PURPOSE This is to retrieve the DDLB values from the table created in the backend to the Java object which will have this field as its property. All fetches, create, search, update etc. are mapped from Java layer to the ABAP Add-on BAPI Wrappers. So as an example, the fetch from Java is mapped to the BAPI Wrapper mentioned above: Parameter Name: com.syclo.sap.component.opportunity.bapi.opportunityfetchbapi Parameter Value: /SYCLO/CRMBTX_DOOPPORT_GET Similarly for creating an opportunity, this is the following mapping: Parameter Name: com.syclo.sap.component.opportunity.bapi.opportunityaddbapi Parameter Value: /SYCLO/CRMBTX_DOOPPORT_CRT 4.4 Extending the Java Classes The property Purpose has to be added to the Java business Object for Opportunity. As an example implementation, the screenshot below shows a ZOpportunity class extending the core class Opportunity. September 2013 7

4.5 Adding the field to the SAP Sales Manager 2.5 UI screens (Agentry Editor) The screen elements involved in accessing this field on the screen are the following: Opportunity Object OpportunityDetailView Screen Set OpportunityDetailView_Detail_iPad Screen PurposeLabel Field Purpose Field These are the steps to add the Purpose field to the Opportunity Detail View Screen: 4.5.1 Add Property to the Object To add property Purpose to the Object Opportunity Navigate to SAP-SALES-> SAP_SALES_MANAGER_25 Application->Modules->Objects-> Opportunity Object Go to Properties. The screenshot below shows a view of the properties list for the Opportunity Object. September 2013 8

Add a new property Purpose of data type String to this list. Use the + icon on top of the list. Screenshot below shows the new property added. 4.6 Add field PurposeLabel and Purpose to the Opportunity Detail View Screen Set In the Agentry Editor navigate to following location: SAP-SALES-> SAP_SALES_MANAGER_25 Application->Modules->Screen Sets- >OpportunityDetailView-> Screens-> OpportunityDetailView_Detail_iPad->Fields Opportunity Detail View Field List September 2013 9

Add Purpose level to the Field list by clicking on the + sign under Fields menu. Add Purpose place holder (where the value will be displayed) to the Field list September 2013 10

Set the position for the Label and the Place Holder Test the application to see the new field Purpose in the Detail View of Opportunity Object. September 2013 11

5. Extensibility Options In this section we will look into the Extensibility Options that are available in Agentry SAP Framework of Sales Manager 2.5. The Data Object Filter (DOF) Rule Type available under Data Filter tab gives us the ability to extend the Sales Manager application to custom needs. Following four options are available for DOF Rule Type: User Profile Parameter Static Value in Range Format Syclo Filter Class Handler Runtime Session Data 5.1 User Profile Parameter Data that is coming onto Sales Manager Mobile application from CRM system can be filtered out using the DOF Rule Type User Profile Parameter that is passed to CRM system during authentication. By selecting this rule Type, the data will be filtered depending upon the Parameter ID s defined in the CRM system for a particular user. September 2013 12

5.2 Static Value in Range Format Second option for the DOF Rule Type is Static Value in Range Format. In this option customers can implement a BADI on the filter value Z for respective Data Object. Once the BADI is implemented, select that Z filter value in the framework during configuration as shown in the picture below. September 2013 13

5.3 Syclo Filter Class Handler Third option for the DOF Rule Type is Syclo Filter Class Handler. Create data filter handler /SYCLO/ZCL_CRMBTX*** for this particular class handler and select it under Syclo Data Filter Handler and select the handler that was created. In this option the interface method of the Handler class will retrieve the data depending upon the logic defined. 5.4 Runtime Session Data Final option for the DOF Rule Type is Runtime Session Data. Create data filter handler /SYCLO/ZCL_CRMBTX*** for this particular class handler and select it under Syclo Data Filter Handler and select the handler that was created. In this option the interface method of the Handler class will retrieve the data depending upon the logic defined. September 2013 14

6. Summary The customization described in this guide is for one particular filter value for a particular Get method of the Data Object Accounts. Similarly, the customization can be extended to many filters that are available for other Data Objects like Activity, Lead etc. With the flexibility available in Agentry SAP Framework of Sales Manager 2.5 customer can meet their day to day scenarios. For more information on the SAP Sales Manager Configuration Objects, please refer to Section 6 of the Configuration Guide of Sales Manager 2.5 7. General References and Links SAP Sales Manager Software is available at: http://service.sap.com/ SAP Support Portal Software Downloads Installations and Upgrades A Z Index M SAP Mobile Solutions SAP Sales Manager Installation and Upgrade Guides are available at: http://service.sap.com/instguides SAP Components SAP Sales Manager Sales Manager 2.5 Help Documentation: http://help.sap.com Mobile Mobile Apps in SAP Business Suite SAP CRM Ramp-up Learning Map Content: http://service.sap.com/rkt SAP for Mobile Business SAP Mobile Apps for Sales SAP Sales Manager 2.5 SAP Community Network: http://scn.sap.com Solutions Customer Relationship Management CRM Mobile Apps September 2013 15

www.sap.com/contactsap www.sdn.sap.com/irj/sdn/howtoguides