SAP NetWeaver Enterprise Search: Configuring SAP GUI for HTML access URLs in SAP NetWeaver Search UI
The SAP NetWeaver Enterprise Search Java UI is the central access point for searching different backend systems attached to the Enterprise Search appliance. An example of a search session using the Java UI is shown in the screen shot in fig. 1.
Fig. 1: Example for a search session using the SAP NetWeaver Enterprise Search Java UI.
SAP’s Enterprise Search solution offers, beside other beneficial functionality, the possibility to search data of different backend systems, e.g. SAP ERP 6.0 systems. This flexibility makes it necessary to support a wide range of access to the content in the search result list, e.g. to generate application dependant URLs to backend Web applications.
Basically, you can configure any access link to client side applications (locally installed application) as well as to Web based applications based on the Search Object Connector Template specific Response Attributes (more details on http://help.sap.com/ (http://help.sap.com/) ). The access link could use parameters based on the Response Attributes which are resolved dynamically at runtime respectively when the result list is rendered. Fig. 2 shows different user interfaces for accessing SAP ERP 6.0 customer data based on SAP GUI and on SAG GUI for HTML.
This blog explains the configuration steps for accessing customer data of SAP ERP 6.0 systems using SAP GUI for HTML.
Fig. 2: Access to business object details via SAP GUI (left) and SAP GUI for HTML (right).
The information in this blog about SAP NetWeaver Search is valid for the releases SP0 to SP2 and for ERP 6.0 backend systems.
URL Schema for launching transactions in SAP GUI for HTML
The URL schema for launching SAP transactions in SAP GUI for HTML consists of following parts:
<host.domain>| Fully qualified domain name of the host that runs the ITS, myserver.mycompany.com |
<port>| Port of the ICM service |
<webgui_path>| Path to ITS / SAP GUI for HTML handler |
?∼transaction=| Keyword for transactions |
<transaction></td><td>The transaction code with optional additional information</td></tr></tbody></table>It is also possible to define customer specific parameters which could be used in the definition of the access URL. E.g. in case you search for several business objects in a single system this could reduce the maintenance effort. h3. Fixed Part of the URL
<p>The fixed part of the URL consists of the protocol, the fully qualified host (hostname and domain) and port at which the backend system’s ITS can be reached, and the path to the ITS.</p><p>The procedure for determining the fixed part of the URL differs depending on whether the backend runs an external ITS (e.g. ITS 6.20 standalone for R/3 4.7) or an integrated one (NetWeaver 2004 and higher). NetWeaver 2004 and higher with internal ITS. The approaches described here can be used for accessing BOs of SAP ERP 6.0 systems. Typically, these systems are connected as search service provider to the Enterprise Search. </p><p>The fixed part can be e.g. retrieved from the backend system by calling the function module SITSP_GET_URL. Execute this function module in the transaction SE37 on the target backend system to get the fixed part of the URL which is shown in the export parameter OUT_ABS_URL.</p>h3. Variable Part of the URL
The <transaction> parameter contains the transaction code and the transaction specific data. The transaction specific could use parameters which are resolved dynamically and are refered the variable part of the URL based on response attributes. Its schema is: <p>***<TCODE> <PARAMETERMAPPING> respectively ***<TCODE>%20<PARAMETERMAPPING> escaped (encoded).</p><p>The character *** makes SAP GUI skip the initial screen.</p><p>The parameter <PARAMETERMAPPING> itslef consists of a list of attribute value pairs:</p><p><FIELD_1>=<VALUE_1><FIELD_2>=<VALUE_2>…;<FIELD_N>=<VALUE_N> respectively <FIELD_1>%3D<VALUE_1>%3B%20<FIELD_2>=<VALUE_2>%3B%20<FIELD_N>=<VALUE_N> escaped (encoded).</p><p>The parameters <FIELD_1>, etc. needs to be replaced by transaction specific technical names of the parameters without the characters “<” and “>”.</p><p>Example: Launching transaction XD03 (see fig. 3) and displaying the data for the customer CUSTOMER04, sales organization 1000, distribution channel 10, and division 00 would require the following transaction parameter:</p><p>transaction=*XD03%20RF02D-KUNNR%3DCUSTOMER04%3B%20RF02D-VKORG%3D1000%3B%20RF02D-VTWEG%3D10%3B%20RF02D-SPART%3D00}, e.g. $. </p><p>Finally, the complete encoded URL in this example based on the fixed and changing part for an internal ITS looks like the following:</p><p>http://<host.domain>:<port>/sap/bc/gui/sap/its/WEBGUI?<br />~transaction= *XD03%20RF02D-KUNNR%3D$%3B%20RF02D-VKORG%3D$%3B%20RF02D-VTWEG%3D$%3B%20RF02D- SPART%3D$
Before starting to configure the Enterprise Search Java UI you should test the URL by just pasting it into the address bar of your web browser.
Configuring the Enterprise Search Java UI
After assembling the access URL to transactions in SAP GUI for HTML, which might be the most time consuming part of the configuration, the Enterprise Search Java UI connectors or connector templates could be configured.
Basically, the following steps need to be done:
Delete any assignment of a response attribute to the link area, since now not the standard value is used but a customer specific one
Create a new response attribute, e.g. use the name “link_webgui”
Check the flags for Visible and Calc and assign this property to the link area
Enter the complete access URL into the text field of the parameter “Is Calculated Attribute” as shown in the screen shot.
It shows the configuration of the attribute link_webgui.
Choose Save all changes
Test the configuration .
The configuration steps need to be done for every connector or connector template configured in the Enterprise Search appliance.