Skip to Content

Often when I required to design custom Screen it take much time for build up basic Structure like Creating Screen, PF-Status, Titlebar, adding basic Buttons like (Back, Cancel, Exit and Save) Corresponding Code lines for these buttons,  adding Modules in Flow Logic than Create corresponding Modules in Driver Program, often we need get set courser field and clear OK_CODE.

To get rid of all above time consuming steps I design on Template now I just need to copy this default template to new Program and start working on Basic Structure in a second. So it has made my life easier hope will help all of you to save your time.  Hope it will help the beginners to understand the basics.

Download .nugg file of that Template using link below and install this to your system using SAPLink.
SAPLink Package of Application

After installing active
1. ZFSL_SCREEN_TEMPLATE Main Program
2. 9001 Screen
3. MAIN_PF_STATUS PF-STATUS
4. MAIN_TITLE TITLEBAR

Let’s Start from Step 1

1. Copy the above Program using T-Code SE80 or SE38, give new program name in Target program text box as below.

image

2. From next window appear Select User Interface and Screens like in following Screen.

image

3. Give Package and Click save in new or existing transport request.

image

Your Base is ready, you can build your building now.

–> Double Click above Screen number in the Code it will leads you to the Flow Logic as shown below.

image

image

–> Click the Layout Button from the Application Toolbar to go to Screen Painter currently screen is blank you can add components as you require.

image

–> Now for Changing PF-STATUS or Title just Double Click on the Corresponding option below.

image

* Main Program Code

* Flow Logic of Screen 9001

To report this post you need to login first.

1 Comment

You must be Logged on to comment or reply to a post.

  1. Thomas Jung
    I’m sure that many people have and use such templates.  It is kind of you to share yours.  My only question/challenge is why not use an Object Oriented framework and avoid some of the copy of the template?  Although the classic dynpro approach isn’t highly OO centric, OO and MVC based frameworks can and have been built for classic dynpro.

    One of the major benefits of OO is avoid just such copy of templates.

    (0) 

Leave a Reply