Linked to URL which can be call web browser.
Reuse entities of the main component to UI.
Reuse methods and data defined.
Use views closed.
Metal Model Declaration
Framework that generate custom source code
Processing in Background
Method of class defined in own system
Function Modules (via RFC) in Back-end system
Web Services via web service client object
Let place SELECT statement in your controller methods directly
The fewer lines of hand-written code, better
Clean separation of the business and user interfaces
Write a lot of code HTML
UI as Windows and Views
UI Elements as Input field and buttons
UI as interaction of program embedded between Model and controller
Global Data is not related to the UI
A node must exist in the context of the controller acting as the mapping origin.
The nodes may also child nodes or attributes.
The mapping origin controller must not be a view controller.
The controller containing the mapped node must declare the use of the mapping origin controller as a used controller.
Business Interaction layer
User Interaction layer
Binding Layer: Request and response.
Meta model declarative
To defined the navigation between to views, you need to reate exit and entry points for each view using outbound and inbound data.
Only then can you specify the navigation flow using navigation link.
Don`t let navigation between two or more views.
Outbound and Inbound plugs are joined together using navigation links.
Plugs outbound and inbound, methods.
Reports and Module pools
Web Dynpro component
Context of the window controller embedding the related view
Controller attribute of the related view controller
Context of the related view controller
Context of the related component controller
Here's an interesting quiz for you.