CL_BMA_HTML_ADAPTER - BOR Migration: Encapsulation of HTML Event Processing
RFUMSV00 - Advance Return for Tax on Sales/Purchases General Material DataThis documentation is copyright by SAP AG.
Functionality
The class encapsulates a simple event administration for the HTML control ( CL_GUI_HTML_VIEWER).
When generating objects of this class, the link to a HTML control is produced. The HTML page in this control can define several types of hyperlinks that are edited using this class:
- Standard Internet hyperlinks on Web pages and FTP servers, for example, according to the capabilitiesof the Web browser that is implementing the SAP HTML control on the front end, such as http://www.sap.com.For links to the Intranet, particularly to the BFA Web server, you must make sure that the names of the respective documents (for example BAPI documentation guidelines) are always kept the same.
- R/3 transactions with the syntax: SAPEVENT:CALLTRANSACTION/[transaction code]
- R/3 reports with the syntax: SAPEVENT:SUBMITREPORT/[report name]
- Function modules that do not define any parameters for their interface, with the syntax: SAPEVENT:CALLFUNCTION/[function module name]
- Function modules that define an import parameter for their interface, with the syntax:
SAPEVENT:CALLFUNCTION_EX/[function module name]
These function modules must define precisely one import parameter PARENT as a type reference to IF_BMA_WORKITEM.This parameter carries the context of the migration task. (The last line is specifically for the usage in the BOR migration environment)
- Subprograms of an R/3 program that have not defined any parameters for their interface, with the syntax: SAPEVENT:PERFORM_EX/[program name]/[subprogram name] scheduled!!
- Subprograms of an R/3 program that have an import parameter with the syntax: SAPEVENT:PERFORM_EX/[programname]/[subprogram name]. These subprograms must be defined in the form [subprogram name] using PARENTtype reference to IF_BMA_WORKITEM#. This parameter carries the context of the migration task. (The last two lines are specifically for the usage in the BOR migration environment)
- Logical information objects (LOIO) of the KW, with the syntax: SAPEVENT:SHOWLOIO/[structure LOIO]/ [object LOIO]
- Special KW R/3 links to an ABAP program with the syntax: SAPEVENT:/SHOWINFOOBJECT/[ABAP programname]/[link name]. Links to the standard main program (see class constants) can be called with the syntax SAPEVENT:/SHOWINFOOBJECT/[link name]
When using the calls CALLFUNCTION_EX and PERFORM_EX an event is triggered in each case, since the context-carryingparameter must be configured application-specific. The initiator must implement event handlers that perform the final call. (In the BOR migration, this occurs in theCL_BMA_MIGITEM_VIEWER class, for example).
Relationships
Example
The following example shows a HTML page with event definitions that can be edited using this class:
<ss
<html>
<head><script language="JavaScript">
function jump_to(target){
window.location.href = target;
}
</script>
<title>Sample Assistant</title>
</head>
<body>
<p><h1><strong><big><em>Initial Steps</em></big></h1></font>
<ul>
<li>Check whether the name of the business object is available as a class name<br>
--> <a href="sapevent:calltransaction/se24">Class Builder</a></li>
</ul>
<ul>
<li>Generate the interface
<input type="button" value="Generate Interface" name="make_if" onClick="javascript:jump_to('sapevent:perform/sapltbasr/borassi_build_if')">
</li></ul></body></html>
Notes
Further information
For more information, see the specifications for the BOR Migration Assistant.
BAL Application Log Documentation rdisp/max_wprun_time - Maximum work process run time
This documentation is copyright by SAP AG.
Length: 4677 Date: 20120526 Time: 092551 triton ( 163 ms )
