Die Präsentation wird geladen. Bitte warten

Die Präsentation wird geladen. Bitte warten

Transaction Launcher for beginners

Ähnliche Präsentationen

Präsentation zum Thema: "Transaction Launcher for beginners"—  Präsentation transkript:

1 Transaction Launcher for beginners
Joaquin Fornas SAP Active Global Support April 10, 2008

2 Agenda Transaction Launcher Basic Processing Services Customizing
Some useful tools

3 What is Transaction Launcher?
The transaction launcher is a tool that system administrators use to allow agent access to business transactions directly from the IC WebClient screen. It is essentially a collection of shortcuts to available functions or transactions within SAP CRM, Enterprise R/3 systems, and other external applications.

4 Transaction Launcher Architecture
The transaction launcher can start: SAP GUI for HTML transactions via the Internet Transaction Server (ITS) from both Enterprise R/3, SAP CRM, and IS-U systems People-Centric User Interface (UI) transactions from SAP CRM IS-U front office processes from IS-U systems URL based transactions from external applications or SAP systems Information can be passed to and from the IC WebClient and the launch transaction, depending upon Customizing. For example, the confirmed business partner can be passed to an Enterprise R/3 sales order and the created document can be returned.

5 Agenda Transaction Launcher Basic Processing Services Customizing
Some useful tools

6 What is a service?(I) In order for you to log onto the SAP system and start a Web application, the Internet Transaction Server (ITS) requires a relevant Internet service. A service is created as a development object in the Workbench and includes further components that represent components of an ITS-based Web application. Transaction launcher used old ITS services CRM_CIC_RABOX and CCMP_RABOX New transactions IC_LTX (for CRM), IC_LTXR (for R/3 system with PI Release Track from 2004_1_46C to 2004_1_500), and IC_LTXE (for ERP 2005) have been created to overcome the display problems related BOR based transactions for IC Web Client Transaction Launcher. These transactions replace ITS services CRM_CIC_RABOX and CCMP_RABOX. Note contains hints to migrate from the old service to the new transaction.

7 How to display the services
Services CRM_CIC_RABOX and CCMP_RABOX can be displayed in transaction SE80 as an “Internet Service” Services must always be “published” in order to work!!! Note describes the changes to be done in the systems CRM 5.0, CRM 5.1, CRM 5.2 and SAP CRM 2007 to replace the service CRM_CIC_RABOX with the transaction IC_LTX Internet Service help is here: 5/frameset.htm

8 How to display WebGui Services (I)
In order to make WebGui services work, the following Internet services must be published: IAC SYSTEM WEBGUI

9 How to display WebGui Services (II)
Transactions IC_LTX and IC_LTXE can be displayed as function groups: This means that the transaction only can be launched in HTML mode!!

10 Activate RABOX services
If RABOX services are being used, they must be activated in transaction SICF The service to activate is /default_host/sap/bc/gui/sap/its: See notes and for details.

11 Agenda Transaction Launcher Basic Processing Services Customizing
Some useful tools

12 Transaction launcher logical system and URL
Transaction CRMS_IC_CROSS_SYS In this transaction, the RFC destination and the services are mapped WebGui Service RABOX Service

13 Defining Logical Systems and URLs(I)
Transaction CRMC_IC_LTX_URLS This transaction is used ONLY for URL based applications 4/frameset.htm

14 Defining Logical Systems and URLs(II)
The URL parameters can also be passed to the transaction launcher. If the “request method” is “GET”, the application will pick up the parameters and send them to the URL. BSP/Non BSP URL: Means if the URL comes from SAP (BSP URL) or from an external source (Non BSP URL) “Hide Dialog” flag: If marked, no data loss warning will appear. The usual question is “Where do I get these parameters from?” The answer is that they are provided in the URL itself or must be provided by HTTP experts, we are not responsible for finding out these URL parameters.

15 Transaction Launcher Wizard: Start
Transaction SPRO-> CRM-> Interaction Center WebClient->Basic Functions-> Transaction Launcher-> Configure Transaction Launcher (Wizard)

16 Transaction Launcher Wizard: Entries
Launch Trans. ID: Identifier of the transaction to be launched Component Set: Name of the GENIL object that is being used. If you want to use the generic one, just leave this field blank. Usually, only the first field is filled, the other fields are left blank, which means that the runtime framework profile will be taken from the IC profile customizing.

17 Transaction Launcher Wizard: Technical details
Description: Naming for the Transaction Launcher ID defined in the previous step. Class Name: Name of the class to be generated by the wizard Stateful: If marked, launch transaction is executed in a new window Raise Veto: Determines whether a message is provided to agents if they select End and a launch transaction is still open .

18 Transaction Launcher Wizard: Further Technical Details
Transaction Launcher type: Determines the kind of transaction to be launched: Front Office Transaction: Is the name of the Front Office process existing in the remote system. Name of the logical system where the FO process is created must be entered BOR Transaction: Is the name of the BOR transaction. People Centric Transaction (only for CRM5.0) URL Transaction: Is the URL defined in prior steps (CRMC_IC_LTX_URLS) For front office and BOR transactions, a logical system is needed. FO: Usually for ISU scenarios. Is a group of steps that are executed in the backend In CRM7.0, we can define object type and object action (only for CRM standalone scenarios).

19 Transaction Launcher Wizard: Transaction Parameters
The parameters for the URL to be launched are defined here. Also, the parameters to be sent to the BOR method or the FO process can be entered here.

20 Transaction Launcher Wizard: Activity Clipboard Integration
In case the result is expected to return to the activity clipboard, the name of the parameter that will be returned is entered here. Usually, this step is left blank

21 Transaction Launcher Wizard: Completition
Once the wizard is completed, the class that has been entered in the “technical details” step is generated. This class has always two important methods: IF_CRM_IC_ACTION_HANDLER~PREPARE_DATA_FLOW: Prepares the data to be sent to the URL, BOR method or FO process. IF_CRM_IC_ACTION_HANDLER~PROCESS_RETURN: Brings the data from the transactions into the IC.

22 Copy/Delete Launch Transactions
The wizard does not delete the entries directly. The entries must be copied or deleted in transaction CRMC_IC_ACTIONPROF In this transaction it is also possible to display the existing entries

23 Agenda Transaction Launcher Basic Processing Services Customizing
Some useful tools

24 Display BOR objects In order to display BOR objects, the repository must be called All objects have methods that will provide the interaction to be carried out with an object. Transaction SWO1

25 Method TSTC-EXECUTE In order to launch customer transactions, SAP provides object-method TSTC-EXECUTE Nevertheless, in for accessing customer transactions in the ICWebClient, this method must be modified to make it Synchronous. To check if method is synchronous, enter SWO1 and double click on TSTC-EXECUTE.

26 Display FO Processes In order to display a FO process, R/3 system must be accessed. Transaction is EWBC These processes always have a container (events that will be exchanged) and steps, that will contain methods that will be executed at runtime.

27 Testing a FO process If we want to perform the test of a FO process, we must test in transaction SWO1 of the ERP system the method EXECUTE of object CCPROCFO A breakpoint in the code of method EXECUTE must be set.

28 Sources of Information
Transaction Launcher general definition: /frameset.htm ITS services: 4260a5/frameset.htm Transaction launcher how-to guide: c10-dab6-bb202e209455?QuickLink=index&overridelayout=true

29 Thank you!

30 Copyright 2007 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. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, Business ByDesign, ByDesign, PartnerEdge 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 and associated logos displayed are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. The information in this document is proprietary to SAP. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided 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 have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence. The statutory liability for personal injury and defective products is not affected. 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 Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durch SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden. Einige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte können Softwarekomponenten umfassen, die Eigentum anderer Softwarehersteller sind. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, Business ByDesign, ByDesign, PartnerEdge und andere in diesem Dokument erwähnte SAP-Produkte und Services sowie die dazugehörigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Ländern weltweit. Alle anderen in diesem Dokument erwähnten Namen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich und dienen lediglich zu Informationszwecken. Produkte können länderspezifische Unterschiede aufweisen. Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP. Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderen Vereinbarung mit SAP. Dieses Dokument enthält nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP®-Produkts und ist für SAP nicht bindend, einen bestimmten Geschäftsweg, eine Produktstrategie bzw. -entwicklung einzuschlagen. SAP übernimmt keine Verantwortung für Fehler oder Auslassungen in diesen Materialien. SAP garantiert nicht die Richtigkeit oder Vollständigkeit der Informationen, Texte, Grafiken, Links oder anderer in diesen Materialien enthaltenen Elemente. Diese Publikation wird ohne jegliche Gewähr, weder ausdrücklich noch stillschweigend, bereitgestellt. Dies gilt u. a., aber nicht ausschließlich, hinsichtlich der Gewährleistung der Marktgängigkeit und der Eignung für einen bestimmten Zweck sowie für die Gewährleistung der Nichtverletzung geltenden Rechts. SAP übernimmt keine Haftung für Schäden jeglicher Art, einschließlich und ohne Einschränkung für direkte, spezielle, indirekte oder Folgeschäden im Zusammenhang mit der Verwendung dieser Unterlagen. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit. Die gesetzliche Haftung bei Personenschäden oder die Produkthaftung bleibt unberührt. Die Informationen, auf die Sie möglicherweise über die in diesem Material enthaltenen Hotlinks zugreifen, unterliegen nicht dem Einfluss von SAP, und SAP unterstützt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewährleistungen oder Zusagen über Internetseiten Dritter ab. Alle Rechte vorbehalten.

Herunterladen ppt "Transaction Launcher for beginners"

Ähnliche Präsentationen