To define a simple tabstrip control, you must:
To find out how to create a tabstrip control in the alphanumeric Screen Painter, refer to
Procedure
Defining the Tabstrip Area.
To define a tabstrip area using the graphical layout editor:
The element name of the tabstrip control is the name that you use to declare the tabstrip control in your ABAP program using the following statement:
Defining The Tab Titles
By default new tabstrip controls come with two tab titles. In technical terms, you process tab titles exactly like pushbuttons. If you want your tabstrip control to have more than two tab titles, you must change the Tab titles attribute..
Attribute |
Meaning |
Name |
Name of the pushbutton that forms the tab title |
Text |
Text for the button |
Icon name |
Icon to be displayed as part of the title. |
FctCode |
Function code that triggers the PAI event. When the user clicks the tab, the function code is placed in the system field SY-UCOMM. |
FctType |
A tab title may have the function type <P> or <SPACE>. To scroll locally at the frontend, use type <P>. In this case, the PAI event is not triggered when the user chooses a tab title, and there is no data transfer to the application server. |
Just like normal pushbuttons, you can assign dynamic texts to tab titles.
Assigning a Subscreen Area
You must assign a subscreen area to each tab page. If you are using local scrolling at the frontend (function type <P>) you must assign a separate subscreen area to each tab page.
If you are scrolling at the backend (function type <SPACE>), you can use one shared subscreen area for all tab pages.
To assign a subscreen area to a tab page:
You can also assign the subscreen area manually by entering the name of the subscreen name in the reference field attribute. Note that this only works if you are using backend scrolling.
Programming the Flow Logic
This explanation of the flow logic is restricted to that necessary to include the appropriate subscreen screens in the right subscreen areas in the tabstrip control. There are two ways of doing this, depending on the scrolling method you are using.
Local Scrolling at the Frontend
If you are using frontend scrolling, you must include subscreen screens in all of your subscreen areas in the tabstrip control.
You can do this in the screen flow logic as follows:
Note that you can take the individual subscreen screens from different ABAP programs.
Scrolling at the Application Server
If you are scrolling at the application server, you only need to include one subscreen at a time in a single subscreen area.
To do this, you must:
Result
You have now created a tabstrip control in the Screen Painter, and determined whether the tab pages should be scrolled at the frontend or on the application server.
You can now turn your attention to programming the reaction to user input in your tabstrip control.
For further information about handling tabstrip controls in your ABAP programs, refer to the
Tabstrip Control section of the ABAP Programming Guide.