Anwendungsentwicklung mit ABAP Objects: Tobias Trapp Thorsten Franz: Books – Title, Anwendungsentwicklung mit ABAP Objects. Authors, Thorsten Franz, Tobias Trapp. Published, ISBN, , Export Citation. Title, Anwendungsentwicklung mit ABAP Objects SAP press · SAP technisch. Authors, Thorsten Franz, Tobias Trapp. Publisher, Galileo Press,
|Published (Last):||17 August 2004|
|PDF File Size:||5.12 Mb|
|ePub File Size:||12.54 Mb|
|Price:||Free* [*Free Regsitration Required]|
Unfortunately, anwendujgsentwicklung customers are still not willing to more forward any use Web Dynpro, UI5 or any of the other modern technologies out there.
But it helps you to create an object orientated report and to handle the dynpro logic and events. It provides you the abstract basic classes for main screens and sub screens. These classes provide some functions like the object orientated access to tab anwendungsenntwicklung, to set the title and status, raising messages or to handle events triggered from the GUI. Since the BUS screen classes are defined as abstract you must create your own local class and inherit from the proper super class.
In my example, I have one Dnypro which acts as my only main screen. This example should give you nawendungsentwicklung first impression of the framework.
Similar authors to follow
The implementation of the class very light. All we must do is to call the Dynpro. Now we have our Dynpro class. It does not contain any logic but it is enough to create and show our Dynpro. But wait — we have a Dynpro class but no Dynpro yet.
The Dynpro is created like any other Dynpro you have created in your life before. I have created a normal screen that objectz a label only. The Dynpro does not yet communicate with the framework and therefore with our screen class. First, we must program some code in the Dynpro flow logic.
BUS Screen Framework – Introduction | SAP Blogs
As we have learned the flow logic hands over the event handling to our screen class. For the ones who wonder where we have defined the function codes: A later example will show how to use a customer own status. The screen class raises an event and we must have a handler that listens to it. There is nothing wrong with adding the handler method into the xnwendungsentwicklung class but I prefer a dedicated class.
The only action we perform is to leave the screen. If objdcts was another main screen before the program would return to the previous screen, otherwise the program ends.
Next we must program some logic to call our screen, register the handler and display the screen. Personally, I like to put my Dynpros into function groups. Therefore, I have created a simple function module that calls our screen. For this purpose, we need the only form routine. We must implement this anwendungsenwticklung routine and return an instance of the screen class. October 6, 5 minute read.
The Dynpro Class Since the BUS screen classes are anwenvungsentwicklung as abstract you must create your own local class and inherit from the proper super class. In a later tutorial, you will see what is the reason for that.
We have created a screen abwendungsentwicklung for our main screen The Handler Class As we have learned the flow logic hands over the event handling to our screen class. We have created a screen class and Dynpro for our main screen Call the Screen and register the Handler Next we must program some logic to call our screen, register the handler and display the screen.
We have created the handler class that listens to the PAI event. We have programmed the logic to call the screen and register the handler. You must be Logged on to comment or reply to a post. November 19, at 6: Open link in a new tab. No search term specified.
Search or use up and down arrow keys to select an item.