SAP Web Reporting

Web RFC and Web Reporting 1
SAP Web Reporting
SAP Web Reporting is a WebRFC application that enables World Wide Web users to get
immediate access to information in the R/3 System (provided they have the authorizations).
By placing URLs in Web pages, you can:
• offer reports to be started dynamically

• make pre-generated lists that are stored in report trees available for display
• allow users to browse report trees in the SAP Reporting Browser.
You can execute most SAP reports from the Web without any modification. Exceptions to this
rule are reports that call other transactions or reports that perform uploads and/or downloads.
Additionally in this release, you cannot process standard interactive events in a report.
However, if you develop a new report for the Web, you can set links to other Web pages or
function modules.
In the SAP Web Reporting environment, the connection between the HTTP server and an R/3
System is provided by the SAP Internet Transaction Server (ITS). If you set up Web pages
with URLs that link to the R/3 System, and a user selects one of these by clicking on the link,
the request is forwarded to the ITS. The ITS then communicates with the R/3 System by
Remote Function Call (RFC). On the R/3 side, a dispatcher program receives the requests and
executes them when they arrive.
The following graphic illustrates the process:
WebRFC Interface: Interaction Between Internet Transaction Server and R/3
When you access the R/3 System via the SAP Graphical User Interface (SAPgui), you follow
the usual logon procedures and enter certain logon information. This includes your user name
and password, together with any other relevant information (such as language). Your user
authorizations then determine what you can or cannot do.
Logon Procedures
When you access the R/3 System as a Web user, the same procedure applies. You click on a
URL that points to a WebRFC application (that is, a function module specified as an entry
point), and you see a logon page where you enter your logon information. What you are then
allowed to do again depends on your user authorizations in the R/3 System.
With WebRFC applications, you can predefine logon information in URLs by specifying
values for any of the parameters listed in the following table.
Accessing R/3 from the Web
The WebRFC Gateway Interface

Logon information in URLs
URL parameter Example value Description

~service XGWFC ITS service name
~client 000 Client
~login WEBLOGIN SAP user name
~password ******** SAP user password
~language E Language
The ~service parameter is mandatory, since it specifies the SAP Internet Transaction Server
(ITS) file that contains the information required to access an R/3 System.
The ITS service XGWFC is a standard ITS service that provides Web users with access to SAP
WebRFC applications. You can specify this service directly in a URL.
Example:
/scripts/wgate.dll?~service=XGWFC&_FUNCTION=WWW_GET_TREE_LIST
This URL uses function module WWW_GET_TREE_LIST, which connects Web users to the
standard SAP Reporting Browser. However, the logon information is incomplete. The URL
specifies the service, but not the client, user name, password, or language. A Web user who
clicks on this URL would see a logon screen requesting the user to enter the missing
information.
The more logon information you specify in the URL, the less the user is required to enter on
the logon screen.
Example:
/scripts/wgate.dll?~service=XGWFC&~language=E&_FUNCTION=WWW_GET_TREE
_LIST
This URL specifies the language. Therefore, a Web user who clicks on this URL would see a
reduced logon screen.
If a URL contains all the necessary logon information, the Web user gains immediate access to
R/3.
For security reasons, you should exercise caution when specifying passwords in URLs.
Logon information is stored in the ITS for the duration of a user's terminal session.
Authorizing Access to Data and Reports
The logon procedure described in Logon Procedures is acceptable in an Intranet environment

where each employee in a company has a separate R/3 user. However, it makes no sense, in
practical or security terms, for a company to set up individual users for thousands of customers,
just to allow them access to very limited amounts of information on the Internet.
If, for example, a telephone company has a report that displays customer telephone bill
information, and wishes to allow its customers to view their own bills over the Internet, there is
no need to set up a separate user for each customer. Instead, you can create one central user
and specify the user name and the password in the service file. You thus dispense with the need
for a logon screen and the customers get direct access to the information they require in the
appropriate WebRFC application.
If all customers are using the same user, the application must maintain and check user
authorizations before providing or denying access to specific data. A telephone company
wishing to allow its customers to view their own telephone bills would assign an ID (based on
a telephone number) and a password to every customer.
To achieve this, the WebRFC application has to take the following steps:
1. Generate an HTML page with fields for entering customer ID and password.
2. Require the user to enter these values in the Web page.
3. Check in the function module itself that the user has the authorization needed for the
requested data.
Customized Logon or Anonymous Logon?
In WebRFC applications, logon procedures are such that if you take no special action, the SAP
Internet Transaction Server (ITS) automatically sends the standard logon page described in
Logon Procedures. To continue, Web users must then enter the required SAP logon
information.
Alternatively, you could adopt a different approach and do either of the following:
• Opt for a customized logon procedure. To do this, you create your own HTML page,
combining standard ITS logon parameters and application-specific values in a single logon
form. For more information, see Customized Logon.
If you wish, you can devise your own customized logon procedure in HTML, using a
combination of logon fields and report selection criteria.
Example:
A telephone company has a report TELBILLS that displays customer telephone bill
information in response to the entry of a telephone number on the report selection screen.
To allow customers to view their own bills over the Internet, the company could create a
customized logon procedure where the SAP Internet Transaction Server (ITS) takes user
input from the HTML page and calls the report at once. This considerably reduces the
number of steps the user has to perform and also minimizes the link time.
You can define the following customized logon procedure in any suitable HTML editor:
<html>
<head><title>Customized Logon Page</title></head>
<body>
<B><FONT COLOR="#0000FF" SIZE=+3>CUSTOMER
INFORMATION</FONT></B></P>
<H2>Please log on</H2>
<form method="post" action="/scripts/wgate.dll?~service=XGWFC
&_FUNCTION=WWW_GET_REPORT&_REPORT=TELBILLS">
<table>
<tr><td>User:</td><td> <input name="~Login" value=""> </td></tr>
<tr><td>Password:</td><td> <input type=password name="~Password" value="">
</td></tr>
<tr><td>Language:</td><td> <select name="~Language">
<option value="D">German
<option selected value="E">English
</select>
</td></tr>
<tr><td>Telephone number:</td><td> <input name="_TELNO" value="">
</td></tr>
</table>
<p><input type=submit value="Logon"></p>
</form>
</body>
</html>
This code produces a customized logon screen.

When a customer enters logon information and presses 'Logon' to continue, the standard
ITS logon page is suppressed and function module WWW_GET_REPORT calls report
TELBILLS that displays customer telephone bill information.
• Opt for an anonymous logon procedure. You do not have to implement a special
To define an anonymous logon procedure, you modify a report by adding parameters for
user ID and password. You then restrict the user account used by all customers to run only
this report.
Example :
A telephone company has a report CUSTBILL that displays customer telephone bill
information. To allow customers to view their own bills over the Internet, the company
could modify the report itself to display a logon screen that prompts for user name and
password. To check the authorization of each user, the company could add parameters
for customer ID (probably linked to the customer's own telephone number) and
password. Such a report would start as follows:
report custbill.
parameters: cust ID(20) obligatory, password(20) obligatory.
write: / 'Telephone Bill for Customer', cust ID.

...
To permit access from the Web, you define a special R/3 user that is only allowed to
execute this report.
You then create a new SAP Internet Transaction Server (ITS) service file (for example,
CUSTINFO.SRVC) and specify all logon parameters for the designated user. In this
case, the standard ITS logon page is suppressed, and the report selection screen
functions as a logon screen.
When you have modified the report, you restrict the user for all customers to run only
this report and, finally, place a URL similar to the following in your company's home
page:
/scripts/wgate.dll?~service=custinfo&_FUNCTION=WWW_GET_SELSCREEN
&_REPORT=CUSTBILL
WebRFC Administration
The fact that World Wide Web users can access information in R/3 just by clicking on a link in
a Web browser has obvious advantages, both for the users and for SAP. On the other hand,
there are other aspects to be taken into consideration when setting up user accounts for this
purpose.
For both practical and security reasons, it does not make sense to give thousands of users their
own individual R/3 accounts.
• It would not be worthwhile setting up separate users just to provide access to data
generated by one or two reports.
• Thousands of users automatically increase the risk of compromising the security of the
information in the R/3 System.
When setting up user accounts, SAP therefore recommends that you exercise caution. Give
users access only to reports and data they really need. Where large numbers of users are
accessing the same restricted amount of data, we recommend that you create one central
account because this is easier to control than large numbers of individual accounts. It also helps
to protect the information available in R/3 from unauthorized access.
The reports that you make available to Web users can appear in a report tree or Web browser.
However, you can only view report trees that have been explicitly flagged as enabled for SAP
Web Reporting in the SAP Reporting Browser. Since there is no default tree, we recommend
that you create your own report trees, containing only reports for viewing over the Internet or
Intranet.
Accessing SAP WebRFC Applications
To facilitate access to SAP WebRFC applications via the WebRFC Gateway Interface, the
SAP Internet Transaction Server (ITS) uses a gateway called SAPXGWFC.DLL. Once you
install the ITS, you have access to this service and other services. For more information, see
the documentation on ITS administration and tuning.
The link to SAP WebRFC applications uses the standard ITS service XGWFC installed in the
ITS service file directory. You can specify this service in the ~service parameter of a URL.
Example:
/scripts/wgate.dll?~service=xgwfc&_FUNCTION=WWW_GET_TREE_LIST
Function module WWW_GET_TREE_LIST accesses the SAP Reporting Browser, which

contains several report trees organized in a hierarchical structure. Each tree contains executable
reports and/or pre-generated lists.
You can either use the standard service or configure your own services.
NOTE:
When developing applications that get data from an R/3 System by Remote Function Call
(RFC), programmers can debug RFC calls through the SAPgui. Similarly, you can debug
WebRFC applications
WebRFC Gateway Service File Parameters
When you specify a service for a WebRFC call in a URL, the required parameter information
is taken from a service file called <service>.SRVC, which is in the service file directory of the
SAP Internet Transaction Server (for more information, see the documentation on ITS
administration and tuning). The service file directory also contains a special service file called
GLOBAL.SRVC, where you can specify settings or parameters that serve as defaults for all
services.
The ITS merges the parameters of the GLOBAL.SRVC file with the parameters of the service
file you specify, but the parameters in the specified service file always override those in the
GLOBAL.SRVC file.
Example:
If the ~client parameter in the GLOBAL.SRVC file is set to 000, but you want users to connect
to client 001, you set the ~client parameter in your service file to 001.
You can also override parameters in the GLOBAL.SRVC file by specifying blank values in
your service file.
Example:
If the ~client parameter in the GLOBAL.SRVC file is set to 000, but you want to allow users
to be able to enter any client on the logon screen, you set the ~client parameter in your service
file to blank.
The following service file parameters are standard ITS parameters. They can be specified in the
GLOBAL.SRVC file during ITS setup, but none of them are mandatory:
• ~AppServer
• ~Client
• ~Language
• ~Login
• ~LoginGroup
• ~MessageServer
• ~Password
• ~RouteString
• ~SystemName
• ~SystemNumber
Example of a Customized WebRFC Service File

If you configure your own services by setting up customized service files, place these files in
the service file directory on the SAP Internet Transaction Server (ITS). They should have the
file extension .srvc. You can specify the name of the service file as a value of the ~service
parameter.
Below is an example of a customized WebRFC service file. Please note that the ~XGateway
parameter is mandatory.
#
# Service description for WebRFC gateway
#
# Obligatory parameter
~XGateway sapxgwfc.dll
# R/3 connection settings
~RFCHostName ideshost.company.com
~RFCSystemType R3
~SystemName C01
~SystemNumber 00
# Anonymous user data
~Client 000
~Login weblogin
~Password test
~Language E
Generating URLs to Other Function Modules

WebRFC applications must not be dependent on the name of the CGI (or ISAPI or NSAPI)
program (for example, WGATE.DLL) used by the SAP Internet Transaction Server (ITS).
Therefore, do not use a hard-coded path to a CGI script or an ISAPI or NSAPI DLL running on
a Web server.
To avoid this problem, SAP provides a function module called WWW_URL_PREFIX, which
returns some strings that can be used as prefixes to construct URLs that call other function
modules.
Prefix Description Example

URL_GATE Path to wgate /scripts/wgate.dll
URL_PREFIX_SINGLE URL prefix for single- /scripts/wgate.dll?
session WebRFC ~service=XGWFC
applications
URL_PREFIX_MULTI URL prefix for multi- /scripts/wgate.dll?~se
session WebRFC ssion=xxx
applications
URL_PREFIX_IMAGES Path to directory that /SAP/ITS/graphics/W
contains graphics used ebRFC/
by WebRFC
application
URL_EXIT URL to ITS home
page
URL_PREFIX_MULTI should be used to construct further calls such as:
concatenate url_prefix_multi
'&_FUNCTION=WWW_GET_REPORT&_REPORT=RSM04000' to url.
Multi-session means that you can open several Web browser windows and run several separate
sessions for one WebRFC application. This is the usual way of implementing a WebRFC
application.
Single-session means that you can start a WebRFC application only once in a Web Browser.
Linking URLs to SAP Web Lists
To link a URL to a specific part of a line in the list generated by executing a report, use
function module WWW_SET_URL in your report as follows:
1. Generate the list line with the WRITE statement.

2. Call WWW_SET_URL directly after the WRITE statement.
3. Specify the offset of the desired link in the OFFSET import parameter.
4. Specify the length of the desired link in the LENGTH import parameter.
5. Specify the URL you want to link to as a literal or as a variable in the FUNC import
parameter.
6. Pass an empty internal table with structure W3QUERY to the tables parameter
QUERY_STRING.
When you run the report in the R/3 System, the resulting list has the same appearance as it
always does. However, when you start the report from a Web page, the specified part of the list
line is presented as a link. If you click on this link, you access the URL address.
REPORT W3HKTST1.
DATA QSTRING LIKE W3QUERY OCCURS 10.
DATA URL(100).
URL = 'http://www.sap-ag.de'.
WRITE: 'Web Reporting is brought to you by SAP AG '.
CALL FUNCTION 'WWW_SET_URL'
EXPORTING
OFFSET = 35
LENGTH = 6
FUNC = URL
TABLES
QUERY_STRING = QSTRING
EXCEPTIONS
INVALID_TABLE = 1
OTHERS = 2.
This report generates a list with the following output line:
'Web Reporting is brought to you by SAP AG '
By calling function module WWW_SET_URL, you link the URL 'http://www.sap-ag.de' to the
part of the output line that reads
'SAP AG'
If you start the report from the Web with the following URL:
/scripts/wgate.dll?~service=XGWFC&_FUNCTION=WWW_GET_REPORT&_REPORT=W3HKTST1
By placing the cursor on SAP AG, you see that the URL specified in the program
(http://www.sap-ag.de) is connected to this link.
Linking R/3 Function Calls to SAP Web Lists

You can use the technique of linking Web pages to SAP function modules to implement
interactive reporting in SAP Web reports. In the R/3 System, interactive reporting allows you
to generate drill-down lists from basic lists. For more information, see Interactive Lists.
Since interactive reporting in the R/3 System is such that the system itself stacks the lists
created in a report, you may want to program interactive reporting and use the ABAP/4 event
concept to react to user actions. However, this is not currently possible for Web Reporting
because, the report finishes after sending a basic list to the Web, and cannot react to further
user input.
To overcome this obstacle, you can link URLs to list lines that call SAP function modules.
Within these function modules, you can then program the task that you want the system to
perform after a particular user action on the Web list.
Function module WWW_SET_URL creates such URLs automatically and stores line-specific
information in a hide area
To implement the call to an SAP function module in the line of a Web list, use function module
WWW_SET_URL in your report as follows:
1. Fill an empty internal table of structure W3QUERY with the parameters you want to
pass to the function module. Structure W3QUERY has two fields, NAME and VALUE.
2. Create the list line with the WRITE statement.
3. Call WWW_SET_URL directly after the WRITE statement.
4. Specify the offset of the desired link in the OFFSET import parameter.
5. Specify the length of the desired link in the LENGTH import parameter.
6. Specify the function module that you want to call in the URL as a literal or as a variable
in the FUNC import parameter. Your function module must have the standardized
interface.
7. Pass the internal table with the parameters to the tables parameter QUERY_STRING.
In contrast to standard interactive reporting in ABAP/4, you must use the internal table
QUERY_STRING instead of the hide area to store information specific to a list line that you
want to use later during an interactive event. For more information, see The Hide Technique.
When you start such a report from the Web, the specified part of the list line is actually a link.
The URL of this link contains the call to the SAP function module passed in the FUNC
parameter and a list of the parameters stored in the internal table passed in the
QUERY_STRING parameter.
If you want to allow users who start reports from the R/3 System to perform the same activities
as Web users who start reports from the Web, include an interactive event key word in your
report program. For more information, see Event Control for Interactive Lists. With interactive
reporting on the Web, you store line-specific information with function module
WWW_SET_URL and not with the HIDE statement, so the system does not retrieve this data
automatically as it does for standard interactive events. Furthermore, since you want to perform
the same task in the R/3 system as from the Web, call the same function modules during an
interactive event.
The R/3 System provides function module WWW_GET_URL to perform this task. For each
interactive list line, this function module returns the same information ( function name and
parameters) as that stored with WWW_SET_URL.
After calling WWW_GET_URL, you can use the information returned to call the relevant
function module from within the R/3 System for each interactive event. Since the interface of
Web-enabled function modules is standardized, you need to program only one function call
with a dynamic function name. To supply the standardized interface, define two additional
internal tables pointing to the ABAP/4 Dictionary structures W3HTML and W3MIME in your
program. You can leave these tables empty.
Example:
The following report is connected to the logical database F1S:
REPORT W3HKTST2.
TABLES SPFLI.
DATA: QSTRING LIKE W3QUERY OCCURS 10 WITH HEADER LINE,
MYHTML LIKE W3HTML OCCURS 0 WITH HEADER LINE,
MYMIME LIKE W3MIME OCCURS 0 WITH HEADER LINE.
DATA FUNCT(100).
START-OF-SELECTION.
GET SPFLI.
REFRESH QSTRING.
QSTRING-NAME = 'CARRID'. QSTRING-VALUE = SPFLI-CARRID.
APPEND QSTRING.
QSTRING-NAME = 'CONNID'. QSTRING-VALUE = SPFLI-CONNID.
APPEND QSTRING.
WRITE: / 'O' HOTSPOT COLOR = 5,
SPFLI-CARRID ,
SPFLI-CONNID,
SPFLI-CITYFROM,
SPFLI-CITYTO.
CALL FUNCTION 'WWW_SET_URL'
EXPORTING
OFFSET =0
LENGTH =1
FUNC = 'SECONDARY_LIST'
TABLES
EXCEPTIONS
INVALID_TABLE = 1
OTHERS = 2.
IF SY-SUBRC NE 0.
WRITE / 'Error in that line!'.
ENDIF.
END-OF-SELECTION.
AT LINE-SELECTION.
IF SY-CUCOL = 2.
CALL FUNCTION 'WWW_GET_URL'
IMPORTING
FUNC = FUNCT
TABLES
EXCEPTIONS
OTHERS = 1.
IF SY-SUBRC NE 1.
CALL FUNCTION FUNCT
TABLES
HTML = MYHTML
MIME = MYMIME
EXCEPTIONS
OTHERS = 1.
IF SY-SUBRC = 1.
WRITE 'Error !!'.
ENDIF.
ENDIF.
This report generates a basic list from the database table SPFLI. By calling function module
WWW_SET_URL, the first column of each line is linked to a URL. For each URL, function
module SECONDARY_LIST is specified. The internal table QSTRING is filled with
parameter pairs and passed to WWW_SET_URL. QSTRING is cleared for each new list line.
You start the report from the Web with the URL:
/scripts/wgate.dll?_~service=xgwfc&_FUNCTION=WWW_GET_SELSCREEN&_REPORT=W3HKTST2
This displays the report selection screen. When you enter selection criteria and run the report, a
list similar to the following appears in your Web browser:
The URL of the fifth line looks like this:
href="/scripts/wgate.dll?_~service=xgwfc&_FUNCTION=SECONDARY_LIST&CARRID=LH&CONNID
=2402"
This URL includes the name of the function module as well as the parameter pairs for the
airline carrier and connection.
The source code of the function module SECONDARY_LIST is as follows:
FUNCTION SECONDARY_LIST.
REFRESH HTML.
REFRESH MIME.
CONTENT_TYPE = 'text/html'.
TABLES SFLIGHT.
DATA: MY_CARRID LIKE SPFLI-CARRID,
MY_CONNID LIKE SPFLI-CONNID.
LOOP AT QUERY_STRING.
IF QUERY_STRING-NAME EQ 'CARRID'.
MY_CARRID = QUERY_STRING-VALUE.
ENDIF.
IF QUERY_STRING-NAME EQ 'CONNID'.
MY_CONNID = QUERY_STRING-VALUE.
ENDIF.
ENDLOOP.
WRITE: MY_CARRID, MY_CONNID.
ULINE.
SELECT * FROM SFLIGHT WHERE
CARRID EQ MY_CARRID
AND CONNID EQ MY_CONNID.
WRITE: / SFLIGHT-FLDATE,
SFLIGHT-SEATSMAX,
SFLIGHT-SEATSOCC.
ENDSELECT.
CALL FUNCTION 'WWW_LIST_TO_HTML'

TABLES
HTML = HTML.
ENDFUNCTION.
First, this function reads the imported parameters from the internal table QUERY_STRING.
Then, it generates an output list in a SELECT loop. Finally, it sends the list to the Web.
If you click on a link in the Web list, the following drill-down list appears in your Web
browser:
If you start report W3HKTST2 in the R/3 System, the resulting basic list appears:
To make this list similar to the Web list, the first column is formatted as a hotspot. By clicking
on the hotspot, the user triggers the AT-LINE-SELECTION event.
In the processing block for this event, function module WWW_GET_URL is used to retrieve
the parameters stored for each line. Then, function module SECONDARY_LIST is called
dynamically with these parameters, and the following drill-down list appears:
This list has the same contents as the drill-down list that appears in your Web browser.
WWW_SET_URL
Description
Function module WWW_SET_URL is used to link URLs to specific parts of SAP list lines.
You must call this function module directly after the WRITE statement that outputs the list line
containing an interactive part.
Interface
Import parameters Function

OFFSET Offset of the part of the list line to be linked to a URL
LENGTH Length of the part of the list line to be linked to a URL
FUNC URL (direct address or R/3 function module)
Table parameter Function

QUERY_STRING If you specify a R/3 function module as a value for the FUNC
import parameter, you can use an internal table with structure
W3QUERY to pass parameters for the function module to the
URL.
Exception Function
INVALID_TABLE An exception is raised if the structure of the table passed to the
table parameter QUERY_STRING is invalid ( not of type
W3QUERY).
WWW_GET_URL
Function module WWW_GET_URL is used to retrieve information stored by function module

WWW_SET_URL for specific parts of SAP list lines.
You can call this function module during an interactive list event in the R/3 System.
Interface
Export parameter Function

FUNC Returns the function name sent to WWW_SET_URL for the list
line on which the interactive event occurs.
QUERY_STRING Fills an internal table with the structure W3QUERY with the
parameters passed to WWW_SET_URL for the list line on which
the interactive event occurs.
WWW_LIST_TO_HTML
Description
Function module WWW_LIST_TO_HTML is used to send lists created in a report program to

the Web.
Interface
Import parameter Function

LIST_INDEX Specifies the list index of the list to be sent. This parameter is
optional. The default value is 0 (basic list).

HTML Internal table with structure W3HTML. The function module
stores the list in this parameter.
WebRFC application, it you need only to modify the report by adding the parameters for
customer ID and password. You can then restrict the user account used by all customers to run
only this report and place the URL that executes the report in the company's home page. For
more information, see Anonymous Logon.
When specifying a URL that links to a report without a selection screen, call the standard
function module WWW_GET_REPORT, which gets and executes a report immediately and
displays the results.
/scripts/wgate.dll?~service=XGWFC&_FUNCTION=WWW_GET_REPORT&_REPOR
T=RDTEST01
If you want to allow users to enter selection criteria on the report selection screen before
executing a particular report, you must specify the function module
WWW_GET_SELSCREEN in your URL.
/scripts/wgate.dll?~service=XGWFC&_FUNCTION=WWW_GET_SELSCREEN&_REP
ORT=RDTEST03
If a URL contains function module WWW_GET_SELSCREEN, but the specified report has no
selection screen, the procedure is as for WWW_GET_REPORT - the report is executed at once
and the results are displayed.
/scripts/wgate.dll?~service=XGWFC&_FUNCTION=WWW_GET_SELSCREEN&_REP
ORT=RDTEST01

SAP Web Reporting

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SAP Web Reporting

Uploaded by

Copyright:

Available Formats

Web RFC and Web Reporting 1

SAP Web Reporting

• offer reports to be started dynamically

The following graphic illustrates the process:

WebRFC Interface: Interaction Between Internet Transaction Server and R/3

Accessing R/3 from the Web

The WebRFC Gateway Interface

Logon information in URLs

URL parameter Example value Description

Authorizing Access to Data and Reports

The logon procedure described in Logon Procedures is acceptable in an Intranet environment

Customized Logon or Anonymous Logon?

This code produces a customized logon screen.

write: / 'Telephone Bill for Customer', cust ID.

Accessing SAP WebRFC Applications

Function module WWW_GET_TREE_LIST accesses the SAP Reporting Browser, which

WebRFC Gateway Service File Parameters

Example of a Customized WebRFC Service File

Generating URLs to Other Function Modules

Prefix Description Example

URL_PREFIX_MULTI should be used to construct further calls such as:

Linking URLs to SAP Web Lists

1. Generate the list line with the WRITE statement.

This report generates a list with the following output line:

'Web Reporting is brought to you by SAP AG '

Linking R/3 Function Calls to SAP Web Lists

The following report is connected to the logical database F1S:

The URL of the fifth line looks like this:

The source code of the function module SECONDARY_LIST is as follows:

CALL FUNCTION 'WWW_LIST_TO_HTML'

Import parameters Function

Table parameter Function

Function module WWW_GET_URL is used to retrieve information stored by function module

Export parameter Function

Function module WWW_LIST_TO_HTML is used to send lists created in a report program to

Import parameter Function

Table parameter Function

You might also like