Web UI Questions
Web UI Questions
View
The view handles the visual output. It is responsible for rendering the output and relevant UI
controls, such as data fields and push buttons. All output is received from the controller for
rendering. All user input is passed from the view back to the controller for processing.
Controller
The controller handles the interaction logic and provides the link between a view and a model of a
MVC application. A controller receives all keyboard and mouse input from the view. Based on
these events, the controller can decide how to react, for example, by accessing data from the
model or triggering the navigation to a different view
Model
The model of the IC WebClient BSPs consists of contexts and context nodes that link the fields of
a view to the underlying business layer (the BOL). This linking is referred to as binding.
Each data field on a view visualizes an attribute of a context node.
Model of BSP page contains context and context nodes which will link the fields in the View to
BOL layer. This linking is called data binding.
We have two tools, EEWB and AET (Available in SAP CRM 7.0 only).
Using UI Configuration tool in component workbench we can make these fields visible in Web UI.
In Transaction BSP_WD_CMPWB, open any component, enhance the component, and right click
on the Context 'Views' and create view using the Standard BOL entity(model node), or value
nodes. Using the UI configuration makes the fields available. Once the view is created, we can
assign it to main Window or Overview page in runtime repository. Then the new assignment block
will be available.
5. Steps for creating new component and make it available in Web UI (Expert level)
Transaction code: BSP_WD_CMPWB, enter the new component name and click on
create
Give the name of the main Window
Create views using BOL entities and make the fields visible using UI configuration
Assign the views to main window in runtime repository
Create Inbound plug for main Window.
Go to SPRO-->Customer Relationship Management--> UI Framework--> Technical Role
Definition--> Define Work Area Component Repository, add new entry with Component
name and main window, create Target ID by maintaining Inbound definition with Inbound
plug name.
Create a new logical link with new Target ID, add the logical link to existing Work center
or create new work center, add the work center to Navigation bar profile.
Assign the navigation bar profile to Business role.
Go the search component, Identify the underlying BOL entity, go to BOL entity structure
and append with new fields
New fields will be available in UI configuration, move the new fields to visible fields
section.
For all the Sales/Service transaction related searches will call the Badi enhancement spot
ES_CRM_RF_Q1O_SEARCH.
Create a new implementation for this enhancement spot with filter value same as BOL
entity name,
Write the logic in SEARCH method of implementation class.
Custom controller is used to share the data between different views. Custom controller holds the
data for entire session.
Declare variable in implementation calls with ref to interface IF_BSP_WD_POPUP, write the logic
in event handler or method which is calling, and use the CREATE_POPUP of interface
IF_BSP_WD_WINDOW_MANAGER to create popup by passing required fields depending upon
the popup types.
10. How to hide/display fields based the certain field values (Expert level)
Expose the context nodes and interface mainwindow in runtime repository of custom component
and define component usage in standard component usage.