<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: WEB DYNPRO in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/web-dynpro/m-p/2498001#M564255</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check this link&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw04s/helpdata/en/31/3bc041a1236724e10000000a1550b0/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04s/helpdata/en/31/3bc041a1236724e10000000a1550b0/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw04s/helpdata/en/e6/2c4b29dc87c6409d6469ec390e8f3d/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04s/helpdata/en/e6/2c4b29dc87c6409d6469ec390e8f3d/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Arun&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 16 Jul 2007 11:28:24 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-07-16T11:28:24Z</dc:date>
    <item>
      <title>WEB DYNPRO</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/web-dynpro/m-p/2498000#M564254</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;please give me some basic idea of web dynpro.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards&lt;/P&gt;&lt;P&gt;debjani&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Jul 2007 11:26:21 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/web-dynpro/m-p/2498000#M564254</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-16T11:26:21Z</dc:date>
    </item>
    <item>
      <title>Re: WEB DYNPRO</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/web-dynpro/m-p/2498001#M564255</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check this link&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw04s/helpdata/en/31/3bc041a1236724e10000000a1550b0/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04s/helpdata/en/31/3bc041a1236724e10000000a1550b0/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw04s/helpdata/en/e6/2c4b29dc87c6409d6469ec390e8f3d/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04s/helpdata/en/e6/2c4b29dc87c6409d6469ec390e8f3d/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Arun&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Jul 2007 11:28:24 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/web-dynpro/m-p/2498001#M564255</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-16T11:28:24Z</dc:date>
    </item>
    <item>
      <title>Re: WEB DYNPRO</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/web-dynpro/m-p/2498002#M564256</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check the link&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_47x200/helpdata/en/15/0d4f21c17c8044af4868130e9fea07/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_47x200/helpdata/en/15/0d4f21c17c8044af4868130e9fea07/content.htm&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Sesh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Jul 2007 11:29:02 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/web-dynpro/m-p/2498002#M564256</guid>
      <dc:creator>seshatalpasai_madala</dc:creator>
      <dc:date>2007-07-16T11:29:02Z</dc:date>
    </item>
    <item>
      <title>Re: WEB DYNPRO</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/web-dynpro/m-p/2498003#M564257</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please check this link.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.sdn.sap.com/irj/sdn/webdynpro" target="test_blank"&gt;https://www.sdn.sap.com/irj/sdn/webdynpro&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Reward points&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Jul 2007 11:31:04 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/web-dynpro/m-p/2498003#M564257</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-16T11:31:04Z</dc:date>
    </item>
    <item>
      <title>Re: WEB DYNPRO</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/web-dynpro/m-p/2498004#M564258</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you are looking for &amp;lt;b&amp;gt;WEB-DYNPRO for ABAP&amp;lt;/b&amp;gt;, then go thru the follwing link&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://saptechnical.com/Tutorials/WebDynproABAP/WebDynproABAPMain.htm" target="test_blank"&gt;http://saptechnical.com/Tutorials/WebDynproABAP/WebDynproABAPMain.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Reward points for helpful ans&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Aarti&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Jul 2007 11:46:03 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/web-dynpro/m-p/2498004#M564258</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-16T11:46:03Z</dc:date>
    </item>
    <item>
      <title>Re: WEB DYNPRO</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/web-dynpro/m-p/2498005#M564259</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;B&gt;&lt;/B&gt;&lt;/P&gt;&lt;P&gt;Web Dynpro&lt;/P&gt; is the SAP NetWeaver programming model for user interfaces and provides support when developing the Web representation of business applications. The Web Dynpro model is based on the Model View Controller paradigm, and has the following features that build on the classic dynpro model:&lt;BR /&gt;&lt;BR /&gt;· Clear separation of business logic and display logic&lt;BR /&gt;&lt;BR /&gt;· Uniform metamodel for all types of user interfaces&lt;BR /&gt;&lt;BR /&gt;· Execution on a number of client platforms.&lt;BR /&gt;&lt;BR /&gt;· Extensive platform independence of interfaces&lt;BR /&gt;&lt;BR /&gt;&lt;B&gt;&lt;P&gt;Structure&lt;/P&gt;&lt;/B&gt;&lt;BR /&gt;In Web Dynpro, each user interface is always made up of the same basic elements (such as UI elements or events triggered by the user). These basic elements are declared using Web Dynpro tools. The event handling is programmed in separate source code areas which are executed automatically at runtime when the event is triggered.&lt;BR /&gt;&lt;BR /&gt;&lt;B&gt;&lt;P&gt;Metamodel Concept&lt;/P&gt;&lt;/B&gt;&lt;BR /&gt;When creating a Web Dynpro application, you use the Web Dynpro tools to describe the properties and functions of the application. The data created in this way is stored in tables as metadata. At a later time, the necessary source code, which is executed at runtime, is created from this metadata. Therefore, the metadata itself is independent of the rendering technique used at runtime.&lt;BR /&gt;&lt;BR /&gt;Graphical Development Tools&lt;BR /&gt;To support this declarative concept, the SAP NetWeaver Developer Studio contains a range of Web Dynpro tools. You can therefore generate a large proportion of a Web Dynpro application using the tools provided, without having to create your own source code. This applies to the following parts of the application:&lt;BR /&gt;&lt;BR /&gt;· Data flow between the front end and back end&lt;BR /&gt;&lt;BR /&gt;· Layout of the user interface&lt;BR /&gt;&lt;BR /&gt;· Properties of user interface elements&lt;BR /&gt;&lt;BR /&gt;The Web Dynpro tools enable you to create source text areas manually within generated source texts. These areas are not changed if the source code is regenerated.&lt;BR /&gt;&lt;BR /&gt;Separation of Business Logic and Display Logic&lt;BR /&gt;Implementing Web Dynpro enables you to clearly separate business logic and display logic. A Web Dynpro application runs on the front end and has local or remote access to the back end system via a service. This means that the display logic is contained in the Web Dynpro application, while the business logic and the persistence of the business objects run in the back end system. The following options are currently available for connecting Web Dynpro applications and the back end system:&lt;BR /&gt;&lt;BR /&gt;· An interface generated using adaptive RFC, through which BAPIs of an SAP system can be called&lt;BR /&gt;&lt;BR /&gt;· An interface for calling Web services&lt;BR /&gt;&lt;BR /&gt;· A self-generated interface&lt;BR /&gt;&lt;BR /&gt;The source code required for connecting the Web Dynpro application can be generated from a UML definition of the Web Dynpro interface. A UML definition can be imported into the Web Dynpro tools as an XML file.&lt;BR /&gt;&lt;BR /&gt;Implementation of the Model View Controller Paradigm&lt;BR /&gt;Every Web Dynpro application is structured according to the Model View Controller paradigm:&lt;BR /&gt;&lt;BR /&gt;· The model forms the interface to the back end system and thus enables the Web Dynpro application access to data.&lt;BR /&gt;&lt;BR /&gt;· The view is responsible for the representation of the data in the browser.&lt;BR /&gt;&lt;BR /&gt;· The controller lies between the view and the model. The controller formats the model data to be displayed in the view, processes the user entries made by the user, and returns them to the model.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;The creation of applications using Web Dynpro is structured in Web Dynpro components. The following sections provide a detailed description of the most important parts of a Web Dynpro component.&lt;BR /&gt;&lt;BR /&gt;&lt;B&gt;&lt;P&gt;PPT on webdynpro&lt;/P&gt;&lt;/B&gt;&lt;BR /&gt;&lt;A href="http://wendtstud1.hpi.uni-potsdam.de/sysmod-seminar/SS2005/presentations/12-WebDynpro-Overview.ppt" target="test_blank"&gt;http://wendtstud1.hpi.uni-potsdam.de/sysmod-seminar/SS2005/presentations/12-WebDynpro-Overview.ppt&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;B&gt;&lt;P&gt;Webdynpro Start&lt;/P&gt;&lt;/B&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/webcontent/uuid/28113de9-0601-0010-71a3-c87806865f26?rid=/webcontent/uuid/8921447c-0501-0010-07b4-83bd39ffc7be" target="test_blank"&gt;https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/webcontent/uuid/28113de9-0601-0010-71a3-c87806865f26?rid=/webcontent/uuid/8921447c-0501-0010-07b4-83bd39ffc7be&lt;/A&gt; &lt;A href="original link is broken"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;B&gt;&lt;/B&gt;&lt;/P&gt;&lt;P&gt;Webdynpro general concepts&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/webcontent/uuid/063bc942-0a01-0010-e7ae-d138e97acb5a" target="test_blank"&gt;https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/webcontent/uuid/063bc942-0a01-0010-e7ae-d138e97acb5a&lt;/A&gt; &lt;A href="original link is broken"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;B&gt;&lt;/B&gt;&lt;/P&gt;&lt;P&gt;Developing ABAP applications using Web Dynpro&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www50.sap.com/businessmaps/8729920B31E343F099B71340B15F06DB.htm" target="test_blank"&gt;http://www50.sap.com/businessmaps/8729920B31E343F099B71340B15F06DB.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Web Dynpro ABAP &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/db22242d-0701-0010-28a2-aeaa1fefd706" target="test_blank"&gt;https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/db22242d-0701-0010-28a2-aeaa1fefd706&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope that the following also helps you.&lt;/P&gt;&lt;P&gt;Web Dynpro for ABAP (WD4A, WDA) is the SAP standard UI technology for developing Web&lt;/P&gt;&lt;P&gt;applications in the ABAP environment. It consists of a runtime environment and a graphical&lt;/P&gt;&lt;P&gt;development environment with special Web Dynpro tools that are integrated in the ABAP&lt;/P&gt;&lt;P&gt;Workbench (SE80).&lt;/P&gt;&lt;P&gt;Web Dynpro offers the following advantages for application developers:&lt;/P&gt;&lt;P&gt;? The use of declarative and graphical tools significantly reduces the implementation&lt;/P&gt;&lt;P&gt;effort&lt;/P&gt;&lt;P&gt;? Web Dynpro supports a structured design process&lt;/P&gt;&lt;P&gt;? Strict separation between layout and business data&lt;/P&gt;&lt;P&gt;? Reuse and better maintainability by using components&lt;/P&gt;&lt;P&gt;? The layout and navigation is easily changed using the Web Dynpro tools&lt;/P&gt;&lt;P&gt;? Stateful applications are supported &amp;#150; that is, if the page is changed and the required&lt;/P&gt;&lt;P&gt;data remains intact so that you can access it at any time throughout the entire&lt;/P&gt;&lt;P&gt;application context.&lt;/P&gt;&lt;P&gt;Note that stateless applications are not possible.&lt;/P&gt;&lt;P&gt;? Automatic data transport using data binding&lt;/P&gt;&lt;P&gt;? Automatic input check&lt;/P&gt;&lt;P&gt;? Automatic operation of the Web Dynpro application using the keyboard&lt;/P&gt;&lt;P&gt;? User interface accessibility is supported&lt;/P&gt;&lt;P&gt;? Full integration in the reliable ABAP development environment&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Web Dynpro Architecture&lt;/P&gt;&lt;P&gt;Definition&lt;/P&gt;&lt;P&gt;Web Dynpro is the SAP NetWeaver programming model for user interfaces (UIs).&lt;/P&gt;&lt;P&gt;The Web Dynpro model is based on the Model View Controller paradigm, and has the&lt;/P&gt;&lt;P&gt;following features that build on the classic dynpro model:&lt;/P&gt;&lt;P&gt;? Clear separation of business logic and display logic&lt;/P&gt;&lt;P&gt;? Uniform metamodel for all types of user interfaces&lt;/P&gt;&lt;P&gt;? Execution on a number of client platforms.&lt;/P&gt;&lt;P&gt;? Extensive platform independence of interfaces&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Structure&lt;/P&gt;&lt;P&gt;Metamodel Concept&lt;/P&gt;&lt;P&gt;Web Dynpro provides support for developing Web representation of a business application.&lt;/P&gt;&lt;P&gt;You use specific tools to describe the properties of a Web Dynpro application in the form of&lt;/P&gt;&lt;P&gt;Web Dynpro metadata. The necessary source code is then generated automatically and&lt;/P&gt;&lt;P&gt;executed at runtime. In addition to the events offered by the framework, you can also define&lt;/P&gt;&lt;P&gt;your own events for a Web Dynpro application. However, the event handling must always be&lt;/P&gt;&lt;P&gt;programmed in separate source code areas which are executed automatically when the event&lt;/P&gt;&lt;P&gt;is triggered at runtime.&lt;/P&gt;&lt;P&gt;In Web Dynpro, each user interface is always made up of the same basic elements. These&lt;/P&gt;&lt;P&gt;elements of the metamodel can be statically declared using Web Dynpro tools.&lt;/P&gt;&lt;P&gt;It is also possible to implement elements of the metamodel at runtime and to change them or&lt;/P&gt;&lt;P&gt;reintegrate them at runtime. Using these implementations, you can make any changes or&lt;/P&gt;&lt;P&gt;enhancements to a user interface that has been created by declarative methods by&lt;/P&gt;&lt;P&gt;generating new interface structures at runtime.&lt;/P&gt;&lt;P&gt;This means that you can combine declarative processes and the implementation of source&lt;/P&gt;&lt;P&gt;code.&lt;/P&gt;&lt;P&gt;Graphical Development Tools&lt;/P&gt;&lt;P&gt;To support this declarative concept, both the SAP NetWeaver Developer Studio and the&lt;/P&gt;&lt;P&gt;ABAP Workbench contain a range of Web Dynpro tools. You can therefore generate a large&lt;/P&gt;&lt;P&gt;proportion of a Web Dynpro application using the tools provided, without having to create your&lt;/P&gt;&lt;P&gt;own source code. This applies to the following parts of the application:&lt;/P&gt;&lt;P&gt;? Data flow between the front end and back end&lt;/P&gt;&lt;P&gt;? Layout of the user interface&lt;/P&gt;&lt;P&gt;? Properties of user interface elements&lt;/P&gt;&lt;P&gt;The Web Dynpro tools enable you to create source text areas manually within generated&lt;/P&gt;&lt;P&gt;source texts. These areas are not changed if the source code is regenerated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Separation of Business and Application Logic&lt;/P&gt;&lt;P&gt;Using Web Dynpro enables a clear separation of business logic and display logic. A Web&lt;/P&gt;&lt;P&gt;Dynpro application runs on the front end and has local or remote access to the back end&lt;/P&gt;&lt;P&gt;system via a service. This means that the display logic is contained in the Web Dynpro&lt;/P&gt;&lt;P&gt;application, while the business logic and the persistence of the business objects run in the&lt;/P&gt;&lt;P&gt;back end system. The following options are currently available for connecting Web Dynpro&lt;/P&gt;&lt;P&gt;applications and the back-end system:&lt;/P&gt;&lt;P&gt;? An interface generated using adaptive RFC, through which BAPIs of an SAP system&lt;/P&gt;&lt;P&gt;can be called&lt;/P&gt;&lt;P&gt;? An interface for calling Web services&lt;/P&gt;&lt;P&gt;? A self-generated interface&lt;/P&gt;&lt;P&gt;The source code required for connecting the Web Dynpro application can be generated&lt;/P&gt;&lt;P&gt;from a UML definition of the Web Dynpro interface. A UML definition can be imported&lt;/P&gt;&lt;P&gt;into the Web Dynpro tools as an XML file.&lt;/P&gt;&lt;P&gt;Conversion of the Model-View-Controller&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Conversion of the Model-View-Controller Programming Model&lt;/P&gt;&lt;P&gt;Every Web Dynpro application is structured according to the Model View Controller&lt;/P&gt;&lt;P&gt;programming model:&lt;/P&gt;&lt;P&gt;? The model forms the interface to the back end system and thus enables the&lt;/P&gt;&lt;P&gt;Web Dynpro application access to data.&lt;/P&gt;&lt;P&gt;? The view is responsible for the representation of the data in the browser.&lt;/P&gt;&lt;P&gt;? The controller lies between the view and the model. The controller formats&lt;/P&gt;&lt;P&gt;the model data to be displayed in the view, processes the user entries made by the&lt;/P&gt;&lt;P&gt;user, and returns them to the model. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;/people/thomas.jung/blog/2006/06/20/web-dynpro-abap-demonstration-videos&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw04s/helpdata/en/77/3545415ea6f523e10000000a155106/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04s/helpdata/en/77/3545415ea6f523e10000000a155106/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward all helpfull answers&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Pavan&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Jul 2007 12:11:21 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/web-dynpro/m-p/2498005#M564259</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-16T12:11:21Z</dc:date>
    </item>
  </channel>
</rss>

