Migration to SAP Sales Manager 2.5 from CRM Sales Mobile 2.0.x/2.1.x

SAP How-to Guide SAP Mobility Migration to SAP Sales Manager 2.5 from CRM Sales Mobile 2.0.x/2.1.x A Branded Service provided by SAP Regional Implementaion Group Applicable Releases: SAP Sales Manager 2.5 Target Audience: CRM consultants Mobility consultants ABAP programmers Version 1.0 April 2013

Copyright 2012 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, 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. May 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 1.5 General References and Links...1 2. Migration Overview...2 2.1 Migration Paths...2 2.2 Migration Activities...2 2.3 Migration Assumption...2 3. Migration Requirements...3 3.1 System Requirements...3 3.2 Skill Set Requirement...3 3.3 Pre-Migration Tasks...3 3.4 SAP Notes related to Migration...4 4. Migration Process...4 4.1 Extract Configuration Data from CRM Sales Mobile 2.0.x/2.1.x...4 4.2 Import Configuration Data into SAP Sales Manager 2.5...5 4.3 Remap ABAP Codes...8 4.4 Remap Custom Enhancement Fields...9 4.5 Remap Distribution Rule Set...9 4.6 Post Migration Steps... 10 5. Additional Information... 11

1. Overview 1.1 About the How-to-guide This guide explains the migration path to migrate your existing CRM Sales Mobile 2.0.x/2.1.x environment to SAP Sales Manager 2.5. It provides a brief overview of the different steps involved in migration process to 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 CRM Sales mobile 2.0.x/2.1.x versions and would like to stay up to date with SAP releases of CRM Sales mobile. 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 Syclo Agentry Platform. Since they are two different technologies there is no straight forward way to upgrade. This document only provides different ways to perform migration. 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 migration steps. 1.5 General References and Links Installation and Upgrade Guides are available at: http://service.sap.com/instguides SAP Sales Manager 2.5 guides are under: SAP Components -> SAP Mobile Applications - > SAP Business Suite -> SAP CRM Sales 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 2012 1

2. Migration Overview 2.1 Migration Paths Migration Path for both versions of CRM Sales Mobile 2.0 and 2.1 is same. Matrix below indicates various migration options that are available for your current CRM Sales Mobile 2.0.x/2.1.x. 2.2 Migration Activities Migration process mainly focuses on following activities: Migration of IMG configuration of CRM Sales Mobile 2.0.x/2.1.x into Configpanel of SAP Sales Manager 2.5. Create Custom Enhancement (CE) fields that were part of CRM Sales Mobile 2.0.x/2.1.x landscape in the CRM system where SAP Sales Manager 2.5 add-on is installed. Remapping of BADIs needs to be done manually 1 in the CRM system where SAP Sales Manager 2.5 add-on is installed. Migration of DOE Distribution Rules that were customized into the Configpanel of SAP Sales Manager 2.5. The next few sections will cover these Migration activities in more detail 2.3 Migration Assumption Following are assumptions made for the Migration of existing CRM Sales Mobile 2.0.x/2.1.x. Has a list of Custom Enhancement (CE) fields that were part of CRM Sales Mobile 2.0.x/2.1.x landscape. Has a list of BADI mappings that were part of CRM Sales Mobile 2.0.x/2.1.x landscape. September 2012 2

To make the migration process easy and not to mis s any of t he c onfigurati on data related to CRM Sales 2.0.x/ 2.1.x, following Pre-Mi gration Tasks that needs to be taken care: Extending SAP CRM Sales mobile app 2.1 using custom enhancement fields Has a list of custom DOE rule set that were part of CRM Sales Mobile 2.0.x/2.1.x landscape.. Note: Source code based customization is NOT included in this migration scope 3. Migration Requirements Following section details the System requirement, Skill Set requirement and Pre-Migration tasks that need to be performed for Migration of CRM Sales Mobile 2.0.x/2.1.x to SAP Sales Manager 2.5. 3.1 System Requirements To migrate data from CRM Sales 2.0.x/2.1.x to SAP Sales Manager 2.5, following system requirements to be met: An existing landscape with CRM Sales Mobile 2.0.x/2.1.x infrastructure is in place to perform the migration. SAP Sales Manager 2.5 add-on is installed on SAP CRM backend system to accept the migration data from CRM Sales Mobile 2.0.x/2.1.x. Agentry Server Version 6.0.30 is installed in the landscape and connected to CRM system where SAP Sales Manager 2.5 add-on is installed.. Mobile devices installed with SAP Sales Manager 2.5 mobile application is connected to Agentry server. 3.2 Skill Set Requirement The data migration from CRM Sales 2.0.x/2.1.x to SAP Sales Manager 2.5 involves some manual steps depending upon the customization involved in CRM Sales Mobile 2.0.x/2.1.x landscape i.e.) CE fields, BADI wrappers, custom DOE rule set etc. SAP CRM knowledge and understand customer CRM Sales process. Understand the functionality SAP Agentry Server. Understand the functionality of CRM Sales 2.0.x/2.1.x. SAP ABAP/Java programming and application UI definition knowledge. 3.3 Pre-Migration Tasks Identify the CRM Sales 2.0.x/2.1.x customization in the existing landscape. Identify the BADI s that were created for CRM Sales 2.0.x/2.1.x. List the CE fields that were created for CRM Sales 2.0.x/2.1.x List out the custom DOE Distribution Rule set for CRM Sales 2.0.x/2.1.x September 2012 3

3.4 SAP Notes related to Migration Following are list of SAP Notes that are related to Sales Manager 2.5 Migration 1834577 - Migration from CRM Sales 2.1 to CRM Sales Manager 2.5 1846849 - CRM Sales 2.5 Configuration Upload from legacy CRM 1867019 - CE field report for CRM Sales 2.1/2.0 4. Migration Process Following is a flow chart which details various stages of Migration process from CRM Sales Mobile 2.0.x/2.1.x to SAP Sales Manager 2.5. 1 2 3 4 Extract Configuration Data from CRM Sales Mobile 2.0.x/2.1.x Import Configuratio n data into SAP Sales Manager 2.5 Remap 2.x BADI s and Implement CE Fields of 2.x in Sales Manager 2.5 Post Migration steps in Sales Manager 2.5 4.1 Extract Configuration Data from CRM Sales Mobile 2.0.x/2.1.x First step is to extract configuration data from CRM Sales 2.0.x/2.1.x system. Following are detail descriptions on extracting the configuration data. 1. Logon to the CRM backend system where CRM Sales 2.0.x/2.1.x add-on was installed. 2. Execute t-code SE38 and create a Z*** program with the code and steps detailed in the SAP note # 1834577 Migration from CRM Sales 2.1 to CRM Sales Manager 2.5. 3. Execute the program that is created to extract the configuration data of CRM Sales 2.0.x/2.1.x. 4. An XML file will be created in the directory C:\XMLFile with the Configuration Data of CRM Sales 2.0.x/2.1.x. September 2012 4

4.2 Import Configuration Data into SAP Sales Manager 2.5 Next step is to import configuration data into SAP Sales Manager 2.5 which was extracted in section 4.1. Following are detail descriptions on importing the configuration data into Sales Manager 2.5. 1. Logon to the CRM backend system where Sales Manager 2.5 add-on is installed. 2. Execute t-code SE38 and create following two programs with the code and steps detailed in the SAP note # 1846849. Program1: ZSSLM25_MIGRATION_DATA_INCL Program2: ZSSLM25_MIGRATION_PROG 3. Execute the program ZSSLM25_MIGRATION_PROG to import the XML file with the content of CRM Sales 2.0.x/2.1.x configuration data. September 2012 5

4. Execute the program ZSSLM25_MIGRATION_PROG to import the XML file with the content of CRM Sales 2.0.x/2.1.x configuration data. 5. Under Legacy Customizing Data Settings, provide the location of XML file that was generated in section 4.1. 6. Then choose following check boxes. These options will allow you to see the configuration data that is been imported; this is check point for customer before migrating the data. Print Customizing Input Statistics Print Customizing Input Detail September 2012 6

7. There are two options available on the type of Migration Script we can use: Use Standard Migration Script will use the migration script that is provided by SAP as part of the note # 1846849. Use Manual Migration Script will give the option to use custom migration script. If you planned to use this option, provide the migration script file location that will be used. 8. Provide the transport request number that you want to move these configuration data changes to QA and Production environments. 9. Runtime Options will allow you to run the migration script or not. By checking the box, you are allowing the migration script to run and populate the configuration data into respective tables. Note: If you are running this script for the first time, it is recommended to execute the program without checking this box. 10. Migration Segment Options will allow you to select which of the configuration data that you want to bring into Sales Manager 2.5. Migration program will not bring the configuration data if the check box is not selected. September 2012 7

Once the Configuration data is migrated, next step is to remap BADIs, create CE fields and transfer DOE rule set. 4.3 Remap ABAP Codes ABAP code can be enhanced multiple ways. 1. BADI implementation. In CRM 2.0.x/2.1.x following BADIs are available. Following BAdIs are available to handle Custom Enhancement fields. Enhancement Spot: /MSA/CRM_MOBILE_SALES Data Object BAdI definition Activity Lead Opportunity Business Partner Quotation Sales Order Survey List of Values customizing for Master Data List of Values customizing for Transactions /MSA/BADI_ACTIVITY /MSA/BADI_LEAD /MSA/BADI_OPPORTUNITY /MSA/BADI_BUSINESS_PARTNER /MSA/BADI_QUOTE /MSA/BADI_SALESORDER /MSA/BADI_SURVEY /MSA/BADI_CUST_MD /MSA/BADI_CUST_TA The following section explains how BAdI is delivered. Transaction: SE18 Enhancement Spot: /MSA/CRM_MOBILE_SALES For Opportunity, four methods are available. For implementing Custom Enhancement fields, CREATE, GETDELTA, GETLIST, GETDETAIL and CHANGE methods are relevant. September 2012 8

Method GETLIST GETDETAIL CREATE CHANGE Comments Custom Logic can be added. Custom Logic can be added. Custom Logic can be added. Custom Logic can be added. 2. Implicit enhancements. 3. Explicit enhancements. 1. Enhancement Point 2. Enhancement Section 3. BAdis For CRM Sales Manager 2.5 All these enhancements had to be manually included in 2.5 BADIs appropriately after detailed analysis. Ideal way is to custom copy the code in to relevant data object and appropriate CURD method. This development should be executed by developer with proper analysis and design. 4.4 Remap Custom Enhancement Fields How to guide for implementing custom enhanced fields for 2.0.x/2.1.x - http://scn.sap.com/docs/doc-32984 How to guide for implementing custom enhanced fields for 2.5 SAP Note 1867019 Provides a report which has to be executed in customer system to identify number of custom field implemented by customer. Using this report as reference the how to guide on custom enhance fields for 2.5 has to be executed by customer. 4.5 Remap Distribution Rule Set There various distribution models supported by CRM Sales Manager 2.5 By default it is based on partner function employee responsible. Distribution Model Detail Other -- Customer or Partner defined distribution model. 1. How to enhance distribution model with BADI approach given above? Enhancement Option a. Enhancement Option MDO Configuration b. Enhancement Option - BAdI September 2012 9

i. Distribution Enhancement BAdI /SYCLO/CL_CRMMD_BUPA_BADI. 1. Territory Based: Implement method GET_BUPA_IDS_BY_TERRITORY. 2. Partner Responsible: Implement method GET_BUPA_IDS_BY_RESP. 3. Sales Area: Implement method GET_BUPA_IDS_BY_SALESAREA. 4. Free Search: Implement method GET_BUPA_IDS_BY_CRITERIA. 5. Custom: Implement method GET_BUPA_IDS_BY_OTHERS. ii. Data Enrichment BAdI /SYCLO/CL_CRMMD_BUPA_BADI method ENRICH_BUPA_DETAIL_INFO. c. Enhancement Option Custom MDO Handler d. Enhancement Option Custom BAPI Wrapper 2. Filter settings through configuration panel. For example. A static filter rule in DOE for 2.1 can be converted to Configuration filter based on transaction type for 2.5. Screenshot above shows filter based on transaction type. 4.6 Post Migration Steps 1. QA Process: Validate consistency of the user data that is shown on Mobile devices of CRM Sales 2.1 with Sales Manager 2.5 data after performing above steps. 2. Update Configpanel Filters: Update the Configpanel filters accordingly with the issues/findings came out of QA process to make sure the data shown on Mobile devices is consistent in CRM Sale 2.0.x/2.1.x and Sales Manager 2.5 mobile applications. Iterate these Post Migration Steps until the user data is consistent in both versions of Mobile Applications. September 2012 10

5. Additional Information Following is some additional information related to the migration program and the tables where the configuration data will be stored in Sales Manager 2.5. 1. Migration program calls following two function modules of CRM Sales Mobile 2.0.x/2.1.x and extracts configuration data that is part of these two function modules. /MSA/CUST_MD_GETDETAIL /MSA/CUST_TA_GETDETAIL 2. Configuration data will be available to cross check before migrating to Sales Manager 2.5. a. ET_ATTACH_CTRL b. ET_AUTH_CUST_ACTIVITY c. ET_AUTH_CUST_BUPA d. ET_AUTH_CUST_CONEMP e. ET_AUTH_CUST_LEAD f. ET_AUTH_CUST_OPPT g. ET_CUST_BP_ROLES h. ET_CUST_MOB_N i. ET_CUST_MOB_ORG j. ET_CUST_PARTNER_FUNC k. ET_CUST_PF_CATEGORY l. ET_CUST_PRIORITIES m. ET_CUST_PROC_TYPES n. ET_CUST_REL_CATEGORY o. ET_CUST_SALES_STAGE p. ET_CUST_STAT_PROF q. ET_MRKT_ATTR_SET September 2012 11

SSLM21_CustData Status Comment BP N/A Controls from the client CONTACT N/A Covered by MDO 'SSLM25_CONTACT' Method 'CREATE'. Only 'BUR001' is supported. Employee creation from client is not supported in Sales 2.5 SALES_ARE Migrate MDO 'ZSSLM25_ACTIVITY_XX': DOF 'SALES_AREA' MDO 'ZSSLM25_OPPORTUNITY_XX': DOF 'SALES_AREA' MDO 'ZSSLM25_LEAD_XX': DOF 'SALES_AREA' MDO 'ZSSLM25_SALES_ORDER_XX': DOF 'SALES_AREA' MDO 'ZSSLM25_QUOTATION_XX': DOF 'SALES_AREA' NOTE_TYPE Migrate MDO 'ZSSLM25_ACTIVITY_XX': DOF 'NOTE_TYPE_HEADER' or 'NOTE_TYPE_ITEM' September 2012 12

MDO 'ZSSLM25_OPPORTUNITY_XX': DOF 'NOTE_TYPE_HEADER' or 'NOTE_TYPE_ITEM' MDO 'ZSSLM25_LEAD_XX': DOF 'NOTE_TYPE_HEADER' or 'NOTE_TYPE_ITEM' MDO 'ZSSLM25_SALES_ORDER_XX': DOF 'NOTE_TYPE_HEADER' or 'NOTE_TYPE_ITEM' MDO 'ZSSLM25_QUOTATION_XX': DOF 'NOTE_TYPE_HEADER' or 'NOTE_TYPE_ITEM' EXCL_STATUS Migrate MDO 'ZSSLM25_ACTIVITY_XX': DOF 'EXCL_USER_STAT_CODE' MDO 'ZSSLM25_OPPORTUNITY_XX': DOF 'EXCL_USER_STAT_CODE' MDO 'ZSSLM25_LEAD_XX': DOF 'EXCL_USER_STAT_CODE' MDO 'ZSSLM25_SALES_ORDER_XX': DOF 'EXCL_USER_STAT_CODE' MDO 'ZSSLM25_QUOTATION_XX': DOF 'EXCL_USER_STAT_CODE' SURVEY N/A Covered by MDO 'SSLM25_SURVEY_DEFINITION' STATUS_PROFILE N/A Covered by MDO 'SSLM25_PROC_TYPE_STATUS'. FACT_SHEET N/A Not supported in SSLM2.5??? FOLLOWUP Migrate MDO 'SSLM25_FOLLOWUP_CONTROL_TRAN': DOF 'FOLLOWTRN_FILTER' ATTACHMENT N/A Not supported in SSLM2.5??? GENERAL_CONFIG N/A MARKETING_ATTR Migrate MDO 'SSLM25_MKT_ATTRIBUTE_SETS': DOF 'CLASS', 'CLASS_GROUP' MDO 'SSLM25_MKT_ATTRIBUTES': DOF 'CLASS', 'CLASS_GROUP' MDO 'SSLM25_MKT_ATTRIBUTE_VALUES': DOF 'CLASS', 'CLASS_GROUP' COUNTRY N/A Covered by MDO 'SSLM25_COUNTRY' BP_TITLE N/A Covered by MDO 'SSLM25_BP_TITLE' CURRENCY N/A Covered by MDO 'SSLM25_CURRENCY' PROCTYPE_CATEGORY N/A Covered by MDO 'SSLM25_TRANSACTION_TYPE' ACTIVITY_GOAL N/A Not supported in Sales 2.5 STATUS N/A Covered by MDO 'SSLM25_PROC_TYPE_STATUS'. September 2012 13

PRIORITY N/A Covered by MDO 'SSLM25_PROC_TYPE_PRIORITY', 'SSLM25_OPPORTUNITY_PRIORITY' PROCESS_TYPE N/A Covered by MDO 'SSLM25_TRANSACTION_TYPE' SALES_STAGE N/A Covers by MDO 'SSLM25_SALES_STAGE' OPPT_STATUS N/A Covered by MDO 'SSLM25_PROC_TYPE_STATUS'. OPPT_SALES_STAGE N/A Covered by MDO 'SSLM25_SALES_STAGE' RELATION_CATEGORY N/A Covered by MDO 'SSLM25_BP_REL_TYPE' PART_FUNC N/A Covered by MDO 'SSLM25_PARTNER_DET_PROC' BP_ROLE N/A Not supported on Device PART_FUNC_CATEGORY N/A Different usage in SSLM2.5 TRANSPORT_ZONE N/A Not used in SSLM2.5 REGION N/A MDO 'SSLM25_REGION' provides complete region list UOM N/A MDO 'SSLM25_COMPOSITE_PRODUCT' provides Product UoM complex table. LANGUAGE N/A Migration Possible. Not recommended ACTIVITY Migrate MDO 'ZSSLM25_ACTIVITY_XX': DOF 'PROCESS_TYPE', 'PARTNER_FCT' MDO 'SSLM25_ACTIVITY_COMPOSITE', COMPOSITE COMPONENT LIST LEAD Migrate MDO 'ZSSLM25_LEAD_XX': DOF 'PROCESS_TYPE', 'PARTNER_FCT' MDO 'SSLM25_LEAD_COMPOSITE', COMPOSITE COMPONENT LIST OPPORTUNITY Migrate MDO 'ZSSLM25_OPPORTUNITY_XX': DOF 'PROCESS_TYPE', 'PARTNER_FCT' MDO 'SSLM25_OPPORTUNITY_COMPOSITE', COMPOSITE COMPONENT LIST SALES_ORDER Migrate MDO 'ZSSLM25_SALES_ORDER_XX': DOF 'PROCESS_TYPE', 'PARTNER_FCT' MDO 'SSLM25_SALESORDER_COMPOSITE', COMPOSITE COMPONENT LIST QUOTATION Migrate MDO 'ZSSLM25_QUOTATION_XX': DOF 'PROCESS_TYPE', 'PARTNER_FCT' MDO 'SSLM25_QUOTATION_COMPOSITE', COMPOSITE COMPONENT LIST September 2012 14

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