7th IEEE International Symposium on Applied (omputational lntelJigence and Informatics· May 24-26, 2012 • Timi�oara, Romania
A case-study about a web business application
implemented in different SAP VI technologies
A.D.Berdie*, M.Osaci*, I. Muscalagiu* and G. Prostean**
'
Politehnica University of Timisoara, Engineering Faculty of Hunedoara, Depament of Electrical Engineering and
Computer Industry, Hunedoara, Romania
"
Politehnica University of Timisoara, Faculty of Magement in Production and Trsportation, Timisoara, Romania
adela.berdie@fih.upt.ro, mihaela.osaci@fih.upt.ro, ionel.muscalagiu@fih.upt.ro, gabriela.prostean@mpt.upt.ro
Absact- This paper proposes a case study about a web
business application implemented in three SAP (System
Application and Products in Data Processing) UI (user
interfaces) technologies: Web Dynpro (WD) ABAP
(Advanced Business Application Programming), Floorplan
Manager (FPM) and Customer Relationship Management
(CRM) WebClient UI. This study is comparatively realized:
both in terms of application achievement, and also in terms
of the obtained front end time displayed to the end-user.
The application is based on SAP database tables and the
measurements performed to obtain the front end time to the
user are made for the same query in the database with the
help of Inteet Explorer HTTP Watch tool.
I. SAP UI TECOLOGS
During the time, SAP developed many products and
solutions that e implemented by a lot of UI
technologies. One of the SAP solutions is SAP Business
Suite and is based on the SAP technology platform called
SAP NetWeaver (NW). This platform contains a set of
cooperative technologies that provide inteal
connectivity between SAP modules and exteal
connectivity with other systems. For AB developers,
the SAP NW technologies and tools include Web Dynpro
ABAP which includes the Floorplan Manager and, for
SAP CRM, the WebClient UI Framework.
A. Web Dynpro ABAP
Web Dynpro ABAP is the UI development platform
preferred om many ABAP developers, and enables the
creation and configuration of web UIs for complex
applications according to the business users' needs. This
ework, realized in according to the Model View
Controller (MVC) padi, is completely integrated in
the ABAP Workbench and contains both an execution and
a aphical development environment with special Web
Dynpro tools.
The Web Dynpro ABAP applications e developed in
the ABAP Workbench (transaction SE80). The creation
of applications using Web Dynpro is stctured
in Web Dynpro components [1], see Fig.1:
•
component interface - provides the user's or
other components' access to the inner workings
of a component;
•
C_t
C
• Coe
• Events
• Metods
t
Corol
'Co
• Events
• Meods
npro Coon . t
--
• View Hier⌒
• Nagation
Figure I. Web Dynpro component
component usage - defines a component usage
and can embed other components into a
component;
•
controller - data flow and binding that are
handled through the controllers;
•
view - is the visible area for the UI that contains
all the view elements;
•
window - using windows, the views can be
arranged in complex screen layout;
•
context - via contexts, used to do all the data
processing in a application;
•
view element - is the smallest part of a view,
d describes a visible area in the client.
A Web Dynpro component can contains several Web
Dynpro views. Each view contains a hierarchic set of
context variables. These variables serve as data
containers and can be accessed programmatically. An
event logic can be attached e.g. to a button or to an input
field. The views are connected with inbound and
outbound plugs. These are usually triggered by
navigation events. A Web Dynpro application c be
created when the component is ready. She delivers
the to start the application in the browser as in [2].
The behaviour of the component is proammed
within its controllers. Every controller can implement
different tes of methods. They are [3]:
•
the hook methods, which interfere with the
proam flow at certain times;
•
the event handler methods, which e
implemented to respond to events of controller,
to action received om the client, and to events
of navigation plugs;
•
the supply nction methods, which populate the
context attributes of the context node elements;
•
other additional methods that manage data and
control logic.
978-1-4673-1014-7/12/$31.00 ©2012 IEEE -111 -