Below are the steps for displaying data within an ABAP WebDynpro table.

Below are the steps for creating a simple ABAP WebDynpro.
Step 1
Execute transaction SE80

Step 2 – Create Web Dynpro component
Select Web Dynpro component/application from drop down and create new Web Dynpro component with a Web Dynpro window. Give the window a name of your choice e.g. INIT_WINDOW

A little background history for those who know BOR

VERY HELPFUL TIP!   If you are an ABAP OO programmer and never did any code in the Business Object Repository, skip this section... you don't need to know about it, and you probably don't want to know either.

Once upon a time, in the land of BOR (Business Object Repository), there were 3 types of attributes:

1. Database attributes
2. Virtual attributes
3. Status attributes

Database attributes were always the easiest of attributes - just say what table and field you want to read and the BOR would generate some code to read all the data from a record of the table. You just had to fill in the blanks. Then you could add other database attributes referring to the same table and they would all use the same pre-generated code. Easy for workflow devlopers, but not always the most efficient way to read code, as you may only be using one or two fields but you still read the entire table row.

Virtual attributes were the most useful type of attribute as you could derive anything here including complex values, structures, tables, and instances of other objects.

Status attributes were a neat trick for business objects that used SAP status management, but most programmers didn't even know they existed. By using a special interface, and filling in the code behind a few predefined virtual attributes, you could then generate a yes/no flag to indicate if a particular status of that object was active.

In ABAP OO we no longer make the distinctions between these different types of attributes. So what do you lose? No more pre-generated code. And what do you gain? Flexibility and control over how your attributes are coded so that you can make the code as performance-efficient as possible.

Tip!  Wanting to find whether a status attribute is set or not? Just call function module STATUS_OBJECT_READ with the status object number. All the statuses set for that object will be returned.

Read entire blog here https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/4203

This is number 6 in a series of blogs on ABAP OO for workflow, so you it would be a really good idea to make sure you have worked through the first 5 blogs. The examples we'll use here continue on from those we used in the earlier blogs.

Here's the list of the earlier blogs:

1. Why use ABAP OO with Workflow?
2. Getting started with ABAP OO for Workflow ... using the IF_WORKFLOW interface
3. Using ABAP OO with Workflow Tasks
4. Raising ABAP OO events for Workflow
5. Using ABAP OO attributes in Workflows and Tasks

• Template for making a class
• Template for calling a class
• Subclass
• Template for calling a class
• Using a class as a parameter for a method
• Interfaces
• Events

1. Public attributes  

2. Private attributes

3. Instance attributes 

4. Static attributes 

5. Public methods 

6. Private methods 

7. Constructor method 

8. Static constructor 

9. Protected components 

10. Polymorphism