You can find some of the key basics of the Web Dynpro Netweaver framework in my earlier post here. Today, lets have a look at the Phased Model framework functionality within the Web Dynpro framework. The phased model is a predetermined sequence of steps that need to be executed everytime there is a client request or response cycle. One important point to note here is that the phased model does not take care of component instantiation. It is only after all the components of the application have been instantiated that the phased model handles client requests or round trips during the lifecycle of the application.

Thus, there exists a one to one relationship between the phased model and the visible window. Each time a modal pop up window is displayed, it is processed using a new instance of the phased model. Some of the steps within the web dynpro programming phased model are discussed below:

1) First step is the receipt of an incoming request.

2) As a next step, the data from the incoming request is transferred to a client neutral location called the data container.

3) The 'doapplicationstatechange' step also known as the floating stage beacuse the creation of this step may vary depending upon the type of the incoming request.

4) The data in the request is validated against simple dictionary rules, however, if there are non validating actions, then the data request is sent as it is, without any validating steps in between.

5) Finally, as part of response rendering, an incoming request coming from an html client and after the post processing phase does not require any error messages, the user interface tree is passed on to the client. For non html requests, the UI data is rendered on to the screen without taking into account the fact that this might not be visible.

Related Posts

SAP EP Implementation Timelines
Meeting SAP Go-Live Deadline
SAP BW Implementation Guide
Business Process Definition for SAP Implementations