Almost Everything About Transaction Launcher - Part II

Almost everything about Launch Transaction - Part II

Almost everything about Launch Transaction - Part II

TABLE OF CONTENTS

ISSUES & SOLUTIONS ................................................................................................................................ 3 OSS MESSAGE/INCIDENT OPENING TIPS .................................................................................................... 9 IMPORTANT NOTES:................................................................................................................................ 10

2

Almost everything about Launch Transaction - Part II

First of all I would like to thank all of you for such a tremendous response on the Part 1 of this article “Almost Everything about Launch Transaction – Part I”. This document has been long overdue and I apologize for the delay. The issues that I have been seeing lately are a little bit more complex, or let’s say out of the ordinary. Since the configuration, troubleshooting and debugging were already covered in Part I, and you are all experts in that area, in this document I will summarize some of the issues that I have seen with Launch Transactions and their solutions. The format may be similar to an FAQ, but I don’t think it qualifies as one. The scenario(s) you face may be different then what is covered here, but my goal is to at least point you in the right direction.

Issues & Solutions Issue 1: How can you switch on the local history status for input fields etc. in Launch Transaction? The functionality is possible in SAP GUI: Layout -> Options -> Local Data -> History Status "On". Solution: In SAPGUI for HTML, the history of input fields is provided by the browser. It is not a functionality of SAP GUI for HTML. Depending on the browser this functionality may work or may not work. This functionality will not work if you are running Internet Explorer running on Microsoft XP. Take a look at Note 314568 & 1591465 for details.

Issue 2: How can you set a window title for a Launch Transaction opened in a new browser Window? Solution: There is no customizing option available to achieve this. At least it was not available at the time of publication of this document. You would have to enhance ICMP_LTX/LaunchTransactionAdmin.js file to meet your requirements. You can try the following example: after line: ltx_window = window.open(url, ltx_window_name, "resizable=yes"); add line: ltx_window.document.title = "TestName";

Issue 3: Transaction Launcher is opening a page with blank boxes. Solution: Ensure that the corrections as well as screen configuration according to Note 914112 are in place. If the issue persists, then upgrade your kernel to the latest patch level as per Note 1901813.

Issue 4: If you execute a Launch Transaction in a separate browser window, it is opened in the background

3

Almost everything about Launch Transaction - Part II

Solution: Implement Note 1919208, clear both server and browser cache and retest.

Issue 5: When you execute a Launch Transaction you encounter a Cross-Site-Scripting-Popup, pointing to Note 1427124. You have verified that all the conditions within the Note have been met. Solution: In transaction SICF, verify that service UICMP_LTX is active. If the issue persists, run an HTTP Watch trace to see which service is inactive, and activate it.

Issue 6: When launching ECC transactions like VA03, VA01, etc. from CRM WebClient UI on Internet Explorer using launch transactions, you encounter an initial message stating that “Launch transaction is starting” but afterwards only a blank screen is displayed. The same works fine on Google Chrome. Solution: Implement Note 1521043 in your CRM system, clear browser and server cache and retest.

Issue 7: Launch Transaction displays a blank screen. Solution: Implement Note 1620007.

Issue 8: Transaction Launcher is slow compared to SAPGUI. Solution: Launch Transaction will always be slow compared to SAPGUI. For example when you access ECC from CRM using Transaction Launcher, the traffic is HTTP and the call is made to CRM and then to ECC. Then the connection is established, but the information is still flowing through the browser instead of a direct connection with the application server.

Issue 9: When you try to enter the date in an ECC Sales Order or any other document using Launch Transaction you notice that the days of the week scroll up or down along with the dates, making it very difficult for the user to select the correct day & date. Solution: This issue is fixed in SAP_BASIS 7 SP 20 (please see Note 1368461). If for some reason you are unable to upgrade, you can use the following workaround: 1. When you are in ECC via Launch Transaction click on any date field 2. Then click on Menu -> Help -> Settings 3. In the pop-up click on F4 tab 4. In Display area select Dialog and then click on the green checkmark

4

Almost everything about Launch Transaction - Part II

Issue 10: You notice that the Launch Transaction screen is truncated. Solution: Update your kernel to latest SP and it will resolve the issue.

Issue 11: When you click a back button on Launch Transaction, instead of it navigating back to the previous screen you end up on a blank screen. Solution: Check and see what BUS object you are using on the target system. TSTC_UIF does not support back button.

Issue 12: You notice that only Error messages are displayed. Message types Success, Information, Warning are not shown. Solution: Check the ITS URL in transaction CRMS_IC_CROSS_SYS. The host name should be a fully qualified host name (server.domain.com). If it is anything like IP address or logical system name, you will encounter this issue. The code in CRM looks for the FQHN. Changing the URL to use anything other than FQHN is not supported.

Issue 13: Locks are not released on objects when using Launch Transaction. Solution: Implement Note 1852002.

Issue 14: Why is the Launch Transaction handler class generated in a $TMP package (local object). Solution: The Launch Transaction handler class is generated in package $TMP and is therefore not transported. However, the Transaction Launcher entry and the dataflow definition are transported. They contain all the information which is needed to re-generate the Transaction Launcher handler class. You can also manually reassign a different package to the handler class, and initiate a transport, if necessary. It is usually expected that you just transport the configuration settings and then using the same to re-generate the class in the target systems. However, in some cases you might just want to transport the class to a target system from say, the DEV system. Therefore this option of re-assignment of packages and transport is also provided. There is another important reason that you might want to generate new classes and additional customizing in the target directly (typically Q systems). Usually such Q systems do not have targets to transports to and hence it is not made compulsory.

Issue 15: Keys in drop down fields are not visible in Launched Transaction window.

5

Almost everything about Launch Transaction - Part II

Solution: Add parameter ~webgui_combobox_with_keys 1 in your GUI configuration via SICF. For example, execute transaction SICF -> enter the service where the issue occurs -> in the "Service Data" tab, click on "GUI configuration". Once completed, re-publish the WEBGUI service as per point 6 in Note 816973. For more details, please refer to the following Notes: 495409 Enable (display of/sort by) combobox keys 1155789 Dropdown list box revised 314568 SAP GUI for HTML functionality / Limitations / Sp. Behavior

Issue 16: You are experiencing an issue when using Transaction Launcher Wizard. When you try to configure a BOR method, there are NO drop down values displayed for Parameters field. You end up with a runtime error stating “OBJECTS_OBJREF_NOT_ASSIGNED_NO in class CL_IC_LTX_WIZ_TECH_ABSTRACT” Solution: Make sure you check “Show keys with dropdown lists” checked in the SAPLOGON PAD

Issue 17: Standard and custom icons are not displayed in the Launch Transaction window. Solution: Implement Note 1148291.

Issue 18: In Launch Transaction search window, the search criteria shows the word : "Hugo". Solution: For SAPGUI for HTML applications to be displayed correctly. The screen resolution expected is 1024x768 (Frame size in which ITS is loaded). This is explained in Note 26417 which is 6

Almost everything about Launch Transaction - Part II

referenced in Note 943004. In order to avoid the problem reported kindly launch ITS (transaction launch) in a new window rather than in the same work area. This should resolve the issue. As this is a requirement of ITS as such, the calling framework application cannot control the resolution of the SAP GUI for windows.

Issue 19: When trying to download table contents that are accessed via Launch Transaction, you encounter a JavaScript error or a short dump. Solution: Update you Kernel to the latest patch level. Also take a look Note 1555523.

Issue 20: You encounter issues when trying to open a PDF in a Launched Transaction window. In HTTP Watch log you can see that the link sent is //.pdf. Solution: Implement attached Note 1556590 in the target system.

Issue 21: Transaction Launcher using IC based Business Role to OBN Portal navigation is not working. Error “Failure in OBN Call - TypeError: 'CRMUIFPortalC' is undefined”. Solution: It is not possible to achieve OBN from Transaction Launcher in case of IC Business Roles since CRM WebClient for IC based roles must be launched from the Portal using external integration which is equivalent to launching CRM WebClient standalone. Take a look at “How to integrate CRM WebClient UI & NetWeaver Enterprise Portal”

Issue 22: After you display a dialog box and then execute an action to close it, the dialog box remains open and displays the initial screen of the screen. Solution: Implement Note 1512781; clear both server and browser cache and retest.

Issue 23: When creating an ERP order via Launch Transaction you notice that the email address is truncated. As a result longer email addresses are not valid anymore. Solution: Check the email import parameter of the BOR you are calling. For example EmailCP is of type BUT000-NAME_LAST which is restricted to size 40. You may have to make a copy of the standard BOR object and increase the size of the parameter in question. Keep in mind that you will have to regenerate the Launch Transaction handler class after making changes to the object.

Issue 24: You encounter the following errors: Message 1: Inside Catch some problem! Message 2: Object does not support the property or method. Backend trigger event 7

Almost everything about Launch Transaction - Part II

Solution: Corrections for the above errors are in Notes 1422502 & 1422536. The Note description states that it is specific for FireFox. However, the same implies for Internet Explorer as well.

Issue 25: When executing a Launch Transaction you encounter 'Method of BOR object (fop name) does not exist' error. Solution: Implement Note 1700903 in your target system and retest. In case of Local ITS for executing a FOP (Front Office Process), the whitelist check in include LIC_LTXF01 -> form check_security_with_token should be done only for FOP name i.e. Definition 1 of LTX, as FOP will not have methods. For this implement Note 1771695 should resolve the issue. Issue 26: You are unable to open a URL based Launch Transaction in a separate window. Solution: URL based Launched Transactions can only be successful if the WebSite in question can be launched within an iFrame. Use the following sample, replacing the src with the URL of your target. Save it as an html file and execute: /html>

Issue 27: You have configured 2 different URLs with the same LOGSYS in transaction CRMS_IC_CROSS_SYS and would like them to be executed based on your business requirements. What you notice is that sometimes the incorrect URL is getting called. Solution: Basically, the customizing for the transaction launcher URL and the mapped logical system maintained in transaction CRMS_IC_CROSS_SYS is just a static way of determining the remote system. With release CRM 7.0 and higher, the application has come with a feature to identify the remote dynamically as some cases need it. For example, invoices of different remote systems should be displayed. There are basically three different possibilities to read the logical system dynamically: • If the line in CRMS_IC_CROSS_SYS has the indicator MULTISYS then before creating the Launch Transaction the systems looks into the global data context (GDC) for an entry with the id LOGICAL_SYSTEM, which can mainly happen in the interaction center. (See CL_CRM_IC_ACTION_UTIL->GET_LOGSYS_FROM_MAPPING). If there is any value in the GDC then it will be passed to the launch transaction instead of the default. (See CL_CRM_UI_LTX_HANDLER_FAC_BOR -> IF_IC_LTX_HANDLER_FACTORY~GET_HANDLER_INSTANCE)

8

Almost everything about Launch Transaction - Part II

• • •

It is also possible to change LOGSYS within the CONSTRUCTOR of the Launch Transaction handler class. Starting WEBCUIF701 a BAdI can adjust the LOGSYS as well. (See CL_CRM_UI_LTX_ABSTRACT->CALL_LTX_EHS_ADJUST_LOGSYS) Starting WEBCUIF701 an entity can pre-define the LOGSYS that is to be used by a launch transaction. This is especially useful if a search result contains entries of different systems. If the user clicks one of them it is possible to transport this entity to the Launch Transaction. There it is unpacked and if a LOGSYS is in there then it will be used. (See CL_UICMP_LT_CUCOLTX_IMPL->PROVIDE_HANDLER_BY_ENTITY)

Issue 28: You have configured Launch Transaction to execute an OBN (Object Based Navigation in NetWeaver Enterprise Portal) to open in a separate browser window. You notice that every time you execute it, there is an empty browser window that is opened as well. Solution: The Launch Transaction is configured to open Portal in a separate browser window. It would be like opening google.com in a separate window so that is ok. So far so good. Now the navigation does not stop there. Instead after the execution it is triggering something additional OBN. From CRM's Launch Transaction perspective, as soon as the Portal window is open (the blank one) it's job is done. The reason why the window is blank is because you are not displaying anything in the window. Instead it is opening a blank iView and triggering further navigation. One way would be add logic to the Launch Transaction handler class, to close the he window after x amount of seconds to allow the actual url to be launched before the it is closed. You could use simple JavaScript code such as to close the window, once a counter max value is reached or something like that. But at the end of the day, it is pure consulting. Issue 29: You have configured a Launch Transaction and upon execution you are encountering runtime error “ITS_CANT_LOAD_INCLUDE” or “ICEXECUTE is unknown”. Solution: Ensure that the necessary components required for Transaction Launcher are installed on the target system. WEBCUIF is required for transaction IC_LTXE & IC_LTX. These transactions in turn make use of some generic function modules which belong to BBPCRM or SAP_APPL. So along with WEBCUIF component, either BBPCRM or SAP_APPL component is necessary.

OSS Message/Incident Opening Tips If you are unable to resolve the issue you are facing and need to open an OSS incident for SAP kindly ensure the following: 1. If the issue is related to Confirm/End buttons etc. (IC based Business Role functionality) open up a message under CRM-IC-ABO component. 2. If the issue is only faced with WebDispatchers or proxies, open up an incident under BC-CST-WDP 9

Almost everything about Launch Transaction - Part II

3. If the issue in related to functionality in a WebGUI window, then choose component BC-FES-WGU (see Note/KBA 1877395). 4. If you are encountering issues with ITS itself, then BC-FES-ITS would be the correct component (see Note/KBA 1877395). 5. If you would like to configure SSO between CRM and the target system(s), then choose component BC-SEC-LGN 6. For all other Launch Transaction issue, the correct component would be CA-WUIAPF. 7. When opening a message be sure to - advise which CRM system SAP should connect to - Launch Transaction’s target system - detailed steps to duplicate, including Business Role - a backend CRM user with authorization to check customizing & debugging - make sure that both WebClient UI’s URL and the ITS are accessible over SAPROUTER - duplicate and record the issue using HTTP Watch and attach it to the message

Important Notes: 1360904 914112 1247621 986257 900814 1385426 1360019 1298695 1388655 1139385 816973 1261669 1512781 902859 1362533 1135335 990216 866660 1148829 1643230 1055324

SAP GUI for HTML: Application services do not start ITS service CRM_CIC_RABOX causes UI problems LTX: No data loss popup of transaction launcher in portal CRM Web UI: Protocol switch in HTTPS scenarios CRM: Generating URLs in proxy scenarios Use basis code for creating URLs Check existence of function module remotely (URL creation) Parameters not passed to launch transaction Transaction ICEXECUTE is unknown Error message 00031 - Transaction ICEXECUTE is unknown ITS 7.00 - preclarification and basic problem analysis RFC connections are not closed SAP GUI for HTML: Initial screen is displayed in dialog box ITS based launch transaction do not close the session ITS based launch transactions do not close sessions ITS based launch transactions do not close sessions FAQ: Display problems for SAPGUI transactions via ITS Syntax error in launch transaction handler class Locally executed launch transactions ignore HTTPURLLOC LTX - Method &2 of BOR object &1 does not have a UI POST parameters lost during redirect 10

Almost everything about Launch Transaction - Part II

985587 974794 962265 1248650 1458437 1523735 1494398 314568 980772 1571428 1555349 1324015 1503066 1311813 1556590 1620007 1707739 1620942 1270522 1521043 1700903 1771695 1555523 1148291 1013376 314568 1496565 1901813 1890755 1857550 1867186 1875095 1653911 1653919

Launch transaction handler class fails with syntax errors 'Hide Dialog' setting for a URL launch transaction Launch transaction wizard fails with syntax errors for BOR Back Button on Transaction Launched leads to an blank screen Prepare old LTX remote part for local ITS of WEBCUIF701 JAVA error 'CATparams is undefined' in transaction HREIC (CRM Web UI ) LTX - SAP GUI for HTML has rendering errors SAP GUI for HTML functionality / Limitations / Sp. Behaviour SAP ITS & SAP integrated ITS: Support for Java VMs Empty new win on "keep work area" with incomplete dataflow ITS: ~disconnectonclose and ~flickerfree have no effect SAP GUI for HTML: URL or POST parameters with "[]" indexes ALV grid view: Checkbox cannot be edited or changed LTX - Hide data receive screen of LTX remote part TIFF image or PDF file will not be displayed in webGUI Response registration is missing Transaction launcher in new window causes problems on End Unauthorized use of appl. functions in Transaction Launcher Initial window size for SAP GUI for HTML ICF system logon: No logon screen Transaction launcher not launching for FRONT OFFICE PROCESS Transaction launcher not launching for Front Office Process WebGUI Java applet security redesign SAP GUI for HTML: Parameter ~webgui_icon_toolbar FAQ Note: CRM WebClient Transaction Launcher SAP GUI for HTML functionality / Limitations / Sp. Behavior Zooming in Internet Explorer and others is not supported ITS: URL with start transaction is not executed SAP GUI Transactions from WebClient UI Launch transaction error "EWB_PROCLX is missing in XXX system" Scrolling issues in F4 help for date fields in WebGUI (accessed using/not using Launch Transaction) After an upgrade the launch transactions are not displayed and you are encountering a blank screen Transaction Launcher window closes when ending interaction Data Loss Popup of Transaction Launcher in Interaction Center (IC) WebClient or WebClient UI

11

www.sap.com

© 2014 SAP AG. All rights reserved. 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.