Download pdf - Module Pool

India SAP CoE, Slide 1

AB1011-AB1011-Module pool Programming- Module pool Programming- v1.0v1.0


Module pool programmingModule pool programming

1 Introduction

2 Syntax Description

3 Demonstration

4 Exercises

5 HelpMe


Module Pool program.

Module Pool Program (also called Online programs , dialog programs, or transactions) do not produces lists. These programs are a collection

of screens, their Flow Logic, and the code within the main ABAP program.

A dialog program offers:

• A user-friendly user interface• Format and consistency checks for the data entered by the user• Easy correction of input errors• Access to data by storing it in the database.


PurposePurpose For performing any kind of task in SAP R/3 system, a transaction is used. For performing any kind of task in SAP R/3 system, a transaction is used.

SAP provides a standard set of transactions to manipulate data in the SAP provides a standard set of transactions to manipulate data in the system. But sometimes, the need to create a customer specific transaction system. But sometimes, the need to create a customer specific transaction arise due to following reasons :arise due to following reasons :

Standard SAP may not support that task.Standard SAP may not support that task. A particular transaction needs to be customized to suit the customer A particular transaction needs to be customized to suit the customer

requirements .requirements .

A transaction (also called module pool programs, dialog programs) is A transaction (also called module pool programs, dialog programs) is defined as a collection of screens (the actual, physical image that the users defined as a collection of screens (the actual, physical image that the users sees), their Flow Logic (code behind the screens ), and the code within the sees), their Flow Logic (code behind the screens ), and the code within the main ABAP program.main ABAP program.


Program Attributes

Title

Type “M”

Application

Online program name must begin with either a

“Y” or “Z”.

Go back to Repository Browser, not source

code.

“With TOP INCL.” should be checked.

Creating an Online ProgramCreating an Online Program


Module Pool Program Components

Top Include

PBO Modules

PAI Modules

ABAP

Subroutines


• An online program consists not only of the screens and their Flow Logic, An online program consists not only of the screens and their Flow Logic, but also ABAP program components: Global data, PBO modules, PAI but also ABAP program components: Global data, PBO modules, PAI modules, and subroutines.modules, and subroutines.

• Global data: It is declared in the Top Include program. Global data: It is declared in the Top Include program.

• PBO and PAI modules: It contain the main processing logic of online PBO and PAI modules: It contain the main processing logic of online program and are “called” from within the Flow Logic of the screens.program and are “called” from within the Flow Logic of the screens.

• The subroutines (if necessary) are in a separate include program. The subroutines (if necessary) are in a separate include program.

Module Pool Program


Transaction Code

Transaction Text

F8

Program Name Initial Screen

required required required

Executing an Online Program



1 Introduction

2 Syntax description

3 Demonstration

4 Exercises

5 HelpMe


Tools used:Tools used: When creating an module pool program, you will use many tools within When creating an module pool program, you will use many tools within

the ABAP Development Workbench: Screen Painter, ABAP Editor, the ABAP Development Workbench: Screen Painter, ABAP Editor, Menu Painter, ABAP Dictionary, and Repository Browser.Menu Painter, ABAP Dictionary, and Repository Browser.

• ABAP Editor (SE38) – To maintain main ABAP program. Program contains data declarations and modules.

Online Programming | 2.01 | August -2003Slide 2

IBM Global Services

© Copyright IBM Corporation 2003

Developing Online Programs

Repository Browser

Screen Painter ABAP Editor

ABAP Dictionary

Menu Painter


•Screen Painter(SE51)– used to maintain components of screen.•Menu Painter(SE41) – Used to design GUI.

•Maintain Transaction(SE93) – To create transaction code for program.

•Object Navigator (Repository Browser)(SE80) - You should always use the object navigator for online programs because you will be able to see the hierarchy. From this hierarchy list, you will be able to branch to the Screen Painter, ABAP Editor, Menu Painter, and ABAP Dictionary.

•You should always use the Repository Browser to create online programs because the system will automatically maintain an online program’s sub-objects and you will be able to see the hierarchy list of these sub-objects. From this hierarchy list, you will be able to branch to the Screen Painter, ABAP Editor, Menu Painter, and ABAP Dictionary.

Tools used:


Creating a ProgramCreating a Program• Create a program using transaction SE38. Program name as Z_MODULE_TRAINING.• Program type should be Module Pool. Save and activate the program.

• Use object navigator(SE80) to further develop the object.


Program StructureProgram Structure• Module pool program when viewed from SE80 transaction will have Module pool program when viewed from SE80 transaction will have

structure as below,structure as below,


Assigning transaction codeAssigning transaction code• Dialog program is executed using transaction code. We can not execute Dialog program is executed using transaction code. We can not execute

this like normal report using execute or pressing F8 button.this like normal report using execute or pressing F8 button.

• Transaction is created using SE93 transaction or from object browser by Transaction is created using SE93 transaction or from object browser by right clicking on transaction, click on create. Give name and description right clicking on transaction, click on create. Give name and description and select the radio button Program and screen (dialog transaction)and select the radio button Program and screen (dialog transaction)


Use of ScreenUse of Screen

• Screen is a interface between user and SAP.Screen is a interface between user and SAP.

• Using screen user can provide input to program and in turn program will Using screen user can provide input to program and in turn program will display result on screen.display result on screen.

• Screen is made up of screen elements such as text box, input/output Screen is made up of screen elements such as text box, input/output field, check box, radio button etc.field, check box, radio button etc.

• One of the strength is that screen elements are combined with the One of the strength is that screen elements are combined with the ABAP dictionary to allow check the consistency of the data that user ABAP dictionary to allow check the consistency of the data that user has entered.has entered.


Screen PainterScreen Painter

• To start the Screen Painter, choose the corresponding pushbutton on the To start the Screen Painter, choose the corresponding pushbutton on the initial screen of the ABAP Workbench or enter Transaction SE51. initial screen of the ABAP Workbench or enter Transaction SE51.

• Best practice is to go to transaction SE80, enter program name and you Best practice is to go to transaction SE80, enter program name and you can perform one of the below,can perform one of the below,

1. Create new screens. 1. Create new screens.

2. Test an existing screen. 2. Test an existing screen.

3. Create new components for an existing screen3. Create new components for an existing screen..

• Screen is always created for an existing program.Screen is always created for an existing program.


Overview of Screen Painter

Screen PainterScreen

Attributes

Screen Layout

Field Attributes

Flow Logic


Developing ScreenDeveloping Screen

• From Object navigator (SE80) we can create the screen as shown, From Object navigator (SE80) we can create the screen as shown,

• Click on Screen, right click and select create option. Click on Screen, right click and select create option.

• Now enter screen number.Now enter screen number.



Screen numbers can be up to 4 characters long, all of which must be Screen numbers can be up to 4 characters long, all of which must be digits.digits.

The number 1000 is reserved for table screens and report selection The number 1000 is reserved for table screens and report selection screen.screen.

Screen numbers from 9000 are reserved for customer-specific screens.Screen numbers from 9000 are reserved for customer-specific screens.

The use of screen numbers is namespace-dependent.The use of screen numbers is namespace-dependent.

For screens in programs in the SAP namespace, numbers less than 9000 For screens in programs in the SAP namespace, numbers less than 9000 are reserved for SAP screens, numbers between 9000 and 9500 are are reserved for SAP screens, numbers between 9000 and 9500 are reserved for SAP partners, and numbers greater than 9500 are for reserved for SAP partners, and numbers greater than 9500 are for customers.customers.


• For screens in programs in the Customize namespace, any four digit For screens in programs in the Customize namespace, any four digit number can be used as screen number except 1000 as mentioned above.number can be used as screen number except 1000 as mentioned above.

• Usual practice is to have screen numbers for customize module pool Usual practice is to have screen numbers for customize module pool program, starting with 100 then continue as 200, 300 etc.program, starting with 100 then continue as 200, 300 etc.

• Enter screen number and click on create.Enter screen number and click on create.




Enter description and save.Enter description and save. Check the screen and activate it.Check the screen and activate it.


Screen AttributesScreen Attributes

• Short descriptionShort description – Describes screen purpose– Describes screen purpose

• Original languageOriginal language – Default logon language – Default logon language

• PackagePackage – Identifies the package with which screen is saved – Identifies the package with which screen is saved

• Last changed on/byLast changed on/by – Date & time screen is last changed – Date & time screen is last changed

• Last generationLast generation – Date & time screen is last generated. – Date & time screen is last generated.


Screen AttributesScreen AttributesScreen Type –Screen Type –• Normal Normal – Default setting– Default setting

• Subscreen Subscreen – To indicate the screen as a subscreen– To indicate the screen as a subscreen

• Modal dialog box Modal dialog box – used to display details in a dialog box. Used for data – used to display details in a dialog box. Used for data input, confirmation/error/help messages.input, confirmation/error/help messages.

• Selection screenSelection screen – Identifies selection screen. The system sets this – Identifies selection screen. The system sets this attribute automatically.attribute automatically.

SettingsSettings• Hold dataHold data – – On checking this, system can hold entries made on the On checking this, system can hold entries made on the

screen at runtime. System automatically displays this data if the user calls screen at runtime. System automatically displays this data if the user calls the particular screen again.the particular screen again.


Screen AttributesScreen AttributesSettingsSettings• Switch off runtime compressSwitch off runtime compress – – On setting this option, the screen is not On setting this option, the screen is not

compressed at runtime.compressed at runtime.

• Template non executableTemplate non executable – – This attribute is primarily for internal use by This attribute is primarily for internal use by SAP. SAP.

• Hold scroll positionHold scroll position – On setting the attribute, the scroll position is – On setting the attribute, the scroll position is retained when the user returns to the screen after processing another retained when the user returns to the screen after processing another screen.screen.

• Without application tool barWithout application tool bar – – To suppress the display of the application To suppress the display of the application toolbar belonging to the current program status.toolbar belonging to the current program status.

Other AttributesOther Attributes• Next ScreenNext Screen – – Next screen number to be displayed. Next screen number to be displayed.


Screen AttributesScreen AttributesOther AttributesOther Attributes• Cursor positionCursor position – – Identifies the screen element that contains the cursor when a Identifies the screen element that contains the cursor when a

screen is first displayed. If you leave this field blank, the system uses the first screen is first displayed. If you leave this field blank, the system uses the first screen field that can accept input. screen field that can accept input.

• Screen groupScreen group – – Specifies a four-character identifier of a group of associated Specifies a four-character identifier of a group of associated screens.screens.

• Line/ColumnsLine/Columns – – Occupied Occupied –– Specifies the size of the screen area currently occupied with Specifies the size of the screen area currently occupied with

screen elements screen elements MaintainedMaintained – – Size of the screen in rows/columns. Size of the screen in rows/columns.

• Context menu Context menu – It will hold a routine name required to set up the context – It will hold a routine name required to set up the context menu in the program. This routine connects the screen (elements) from the menu in the program. This routine connects the screen (elements) from the Screen Painter to the context menu of the program.Screen Painter to the context menu of the program.


Screen Layout ModeScreen Layout Mode

The Screen Painter has a layout editor that you use to design your screen The Screen Painter has a layout editor that you use to design your screen layout. layout.

It works in two modes:It works in two modes:

• Graphical modeGraphical mode – – Drag and drop interface is used, similar to a drawing Drag and drop interface is used, similar to a drawing tool. tool.

• Alphanumeric modeAlphanumeric mode – – Keyboard and menus are used for designing. Keyboard and menus are used for designing.

Both modes offer the same functions but use different interfaces. Graphical Both modes offer the same functions but use different interfaces. Graphical mode of screen designing is commonly used.mode of screen designing is commonly used.


Screen DesigningScreen Designing• We have learnt about creating a screen.We have learnt about creating a screen.

• To start screen design, click on layout button on screen.To start screen design, click on layout button on screen.

• Graphical Screen painter will start loading.Graphical Screen painter will start loading.


Components of Layout EditorComponents of Layout Editor• Element paletteElement palette – Used for creating screen elements. These can be drag – Used for creating screen elements. These can be drag

& dropped on screen.& dropped on screen.

• Work AreaWork Area –– Screen design is done in this area. Screen design is done in this area.

• Element barElement bar – screen element attributes appear in this line. You can also – screen element attributes appear in this line. You can also change these attributes in the corresponding field.change these attributes in the corresponding field.


Creating Radio Button

Radio ButtonRadio Button

•Click on the Radio Button Icon and Click on the Screen.

•Create at least two Radio Buttons

•Name the Radio Buttons and Activate it.


Defining Radio Button GroupDefining Radio Button Group

Assign Radio Buttons into one Group.

Select the Radio Buttons and Follow the steps.


• Click on the Check Box Icon and Click on the Screen.

• Name the Check Box and Activate it.

• Special input/output fields that the user can either select (value ‘X’) or deselect (value SPACE). Checkbox elements can be linked with function codes.

Creating Check Box

Check BoxCheck Box

Name the Check box


Screen ComponentsScreen Components

• Screen element properties can be seen in Screen element properties can be seen in detail by double clicking on the element.detail by double clicking on the element.

• Properties of an element can be set here, Properties of an element can be set here, such as variable length, F4 help, such as variable length, F4 help, input/output, mode of display etc.input/output, mode of display etc.

• Best practice is to define screen elements Best practice is to define screen elements by adopting the corresponding field from by adopting the corresponding field from the ABAP Dictionary. However, you can the ABAP Dictionary. However, you can also use field descriptions that you defined also use field descriptions that you defined in your program. To do this you must in your program. To do this you must generate the program first.generate the program first.


Screen ElementsScreen Elements

Screen elements are, Screen elements are, • Text fieldText field• Input/Output fieldInput/Output field• Check boxCheck box• Radio buttonRadio button• Push buttonPush button• Tab stripTab strip• BoxBox• Sub screen areaSub screen area• Table controlTable control• Custom controlCustom control• Status IconStatus Icon

Each element will have unique name.

Function code will be assigned for push buttons, tab titles in tab strip controls, Input/output fields with the "Dropdown box" attribute.

Each element will have its position on screen, visible/definite length, mode of display etc.


Screen ElementsScreen ElementsPush Button –Push Button –• Can be placed on screen by drag Can be placed on screen by drag

& drop from Element palette.& drop from Element palette.

• To set the properties, double To set the properties, double click on it. click on it.

• Each screen element should Each screen element should have unique name.have unique name.

• In addition to that push button In addition to that push button will have text and function code will have text and function code assigned to it.assigned to it.


Function Code for Push Buttons, check box, Radio Button

Assign Parameter ID to Input / Output Field

Dict. Tab is Selected

Program Tab is Selected

Tick If Input or Output Box

Entries in (*********)

Choose if want to Make the Field Mandatory

Screen ElementsScreen Elements


Screen ElementsScreen ElementsOnce screen is designed, it should be saved and checked for errors and activated. Screen looks as below,

Input Box


Testing ScreenTesting Screen• Screen can tested by executing F8 or click on buttonScreen can tested by executing F8 or click on button


Testing ScreenTesting Screen


Flow LogicFlow Logic

• Default flow logic for any screen is generated as shown below,Default flow logic for any screen is generated as shown below,


Menu PainterMenu Painter

• In all programs GUI consists of a menu bar, a standard toolbar, an In all programs GUI consists of a menu bar, a standard toolbar, an application toolbar and title bar.application toolbar and title bar.

• A program’s GUI is created in A program’s GUI is created in Menu PainterMenu Painter..

• To Create a Menu for a screen, in flow logic uncomment MODULE To Create a Menu for a screen, in flow logic uncomment MODULE STATUS_0400. in PBO eventSTATUS_0400. in PBO event

PROCESS BEFORE OUTPUT.PROCESS BEFORE OUTPUT.

MODULE STATUS_0400.MODULE STATUS_0400.

PROCESS AFTER INPUT.PROCESS AFTER INPUT.

* MODULE USER_COMMAND_0400.* MODULE USER_COMMAND_0400.


Menu PainterMenu Painter• Now double click onNow double click on STATUS_0400. A pop up window will appear. Click STATUS_0400. A pop up window will appear. Click

on Yes.on Yes.

• Module will be created as below,Module will be created as below,*&---------------------------------------------------------------------**&---------------------------------------------------------------------**& Module STATUS_0400 OUTPUT*& Module STATUS_0400 OUTPUT*&---------------------------------------------------------------------**&---------------------------------------------------------------------*module STATUS_0400 output.module STATUS_0400 output.* SET PF-STATUS 'xxxxxxxx'.* SET PF-STATUS 'xxxxxxxx'.* SET TITLEBAR 'xxx'.* SET TITLEBAR 'xxx'.• endmodule. " STATUS_0400 OUTPUTendmodule. " STATUS_0400 OUTPUT



• Uncomment the line Uncomment the line SET PF-STATUS 'xxxxxxxx'. aSET PF-STATUS 'xxxxxxxx'. and replace nd replace 'xxxxxxxx‘ with name ‘STATUS_400’.'xxxxxxxx‘ with name ‘STATUS_400’.

• Click on STATUS_400. Click Yes on the pop-up.Click on STATUS_400. Click Yes on the pop-up.



• Enter description and choose the status type as Normal screen which is Enter description and choose the status type as Normal screen which is default.default.



• Click on to expand the menu bar, application toolbar and function Click on to expand the menu bar, application toolbar and function keys. keys.

• System and Help are default in menu barSystem and Help are default in menu bar


Creating Menu barCreating Menu bar

• To create a user defined menu enter the name of the menu and doubleTo create a user defined menu enter the name of the menu and double click on it. We can define options for the menu here as below,click on it. We can define options for the menu here as below,


Creating Application Tool barCreating Application Tool bar

• Application tool bar can also be created in same way as menu bar.Application tool bar can also be created in same way as menu bar.


Assigning function keysAssigning function keys

• We can assign code to existing function keys. Only keys for which code We can assign code to existing function keys. Only keys for which code is assigned will be active. We can see this when the menu painter is is assigned will be active. We can see this when the menu painter is executed.executed.


ExecutionExecution• We can test the menu painter by clicking on F8 key or execute buttonWe can test the menu painter by clicking on F8 key or execute button

• Enter a screen number and title if you want to simulate a whole screen. Enter a screen number and title if you want to simulate a whole screen. If you do not enter a screen number, the system simulates the status If you do not enter a screen number, the system simulates the status using an empty test screen. using an empty test screen.


ExecutionExecution

• Output as below, New Menu is added, Find Item in Application tool bar, Output as below, New Menu is added, Find Item in Application tool bar, Save, Back & Print button on standard tool bar enabled.Save, Back & Print button on standard tool bar enabled.


More on Flow LogicMore on Flow Logic

• Flow logic refers to code behind the screens. It is the code that processes Flow logic refers to code behind the screens. It is the code that processes a screen. a screen.

• Flow Logic commands are different than ABAP commandsFlow Logic commands are different than ABAP commands (e.g., IF … ENDIF is not valid in Flow Logic). (e.g., IF … ENDIF is not valid in Flow Logic).

• Dynamic Processor (DYNPRO) controls the flow logic and prepares Dynamic Processor (DYNPRO) controls the flow logic and prepares data to be displayed on the screen.data to be displayed on the screen.


More on Flow LogicMore on Flow Logic• Each screen has its own Flow Logic which is divided into four main events:Each screen has its own Flow Logic which is divided into four main events:

• PROCESS BEFORE OUTPUT (PBO)PROCESS BEFORE OUTPUT (PBO) - event processed before the - event processed before the screen is displayed.screen is displayed.

• PROCESS AFTER INPUT (PAI) -PROCESS AFTER INPUT (PAI) - event processed after the user has event processed after the user has invoked a function code (e.g., clicked on a pushbutton) or pressed the invoked a function code (e.g., clicked on a pushbutton) or pressed the ‘Enter’ key.‘Enter’ key.

• Process on Value Request (POV) -Process on Value Request (POV) - Triggered when the user requests Triggered when the user requests Value help (F4) Value help (F4)

• Process on Value Request (POH) -Process on Value Request (POH) - Triggered when the user requests Triggered when the user requests field help (F1) field help (F1)

• Each screen must be generated. If you make a change to any component of a Each screen must be generated. If you make a change to any component of a screen, the screen must be re-generated before execution.screen, the screen must be re-generated before execution.


Keywords supportedKeywords supported• Keywords supported by flow logic events are as below,Keywords supported by flow logic events are as below,

Keyword Function

MODULE Calls a dialog module in an ABAP program

FIELD Specifies the point at which the contents of a screen field should be transported

ON Used in conjunction with FIELD

VALUES Used in conjunction with FIELD

CHAIN Starts a processing chain

ENDCHAIN Ends a processing chain

CALL Calls a sub screen

LOOP Starts processing a screen table

ENDLOOP Stops processing a screen table


PBO EventPBO Event• By default the module created in PBO event will be likeBy default the module created in PBO event will be like MODULE STATUS_<screen number>MODULE STATUS_<screen number> Ex:-MODULE STATUS_0100.Ex:-MODULE STATUS_0100.

• This module will be processed before the screen is displayed.This module will be processed before the screen is displayed.

• By default this module will be commented. To use this uncomment and double By default this module will be commented. To use this uncomment and double click on it to get the module created.click on it to get the module created.

*&---------------------------------------------------------------------**&---------------------------------------------------------------------* *& Module STATUS_0100 OUTPUT*& Module STATUS_0100 OUTPUT *&---------------------------------------------------------------------**&---------------------------------------------------------------------* module STATUS_0100 output.module STATUS_0100 output. * SET PF-STATUS ‘XXX'.* SET PF-STATUS ‘XXX'. * SET TITLEBAR 'xxx'.* SET TITLEBAR 'xxx'. endmodule. " STATUS_0100 OUTPUTendmodule. " STATUS_0100 OUTPUT


PBO EventPBO Event

• Menu bar and title bar can be set in this module.Menu bar and title bar can be set in this module.

Menu Bar-Menu Bar-• To set menu bar uncomment the SET PF_STATUS and give a name to To set menu bar uncomment the SET PF_STATUS and give a name to

status as , status as , SET PF-STATUS 'STATUS100'.SET PF-STATUS 'STATUS100'.

• Double click on STATUS100 and click yes to create GUI status.Double click on STATUS100 and click yes to create GUI status.


PBO EventPBO EventTitle BarTitle Bar• To assign a title uncomment SET TITLEBAR and give a name as,To assign a title uncomment SET TITLEBAR and give a name as, SET TITLEBAR 'TITLE100'.SET TITLEBAR 'TITLE100'.

• Double click on TITLE100 and click yes to create GUI title. Enter title as Double click on TITLE100 and click yes to create GUI title. Enter title as below and click on , save and activate.below and click on , save and activate.

• Once all the modules in the PBO block are processed, the system copies Once all the modules in the PBO block are processed, the system copies the content of the fields in the ABAP work area to their corresponding the content of the fields in the ABAP work area to their corresponding fields in the screen work area.fields in the screen work area.


PAI EventPAI Event• Default module in PAI event will be Default module in PAI event will be MODULE USER_COMMAND_<screen number>.MODULE USER_COMMAND_<screen number>. Ex:- Ex:- MODULE USER_COMMAND_0100.MODULE USER_COMMAND_0100.

• This event is triggered once the user invokes function code or presses Enter This event is triggered once the user invokes function code or presses Enter key on the screen.key on the screen.

• System variable System variable SY-UCOMMSY-UCOMM will hold the function code assigned to the will hold the function code assigned to the screen elements (push button, radio button, check box etc).screen elements (push button, radio button, check box etc).

• Within the above module code has to written to branch to group of code Within the above module code has to written to branch to group of code based on the function code from SY-UCOMM.based on the function code from SY-UCOMM.

• The system copies the contents of the fields in the screen work area to their The system copies the contents of the fields in the screen work area to their corresponding fields in the ABAP work area once user clicks Enter key on corresponding fields in the ABAP work area once user clicks Enter key on screen or any function code is invoked.screen or any function code is invoked.


PAI Event- Sample CodePAI Event- Sample Code*&---------------------------------------------------------------------**&---------------------------------------------------------------------**& Module USER_COMMAND_0100 INPUT*& Module USER_COMMAND_0100 INPUT*&---------------------------------------------------------------------**&---------------------------------------------------------------------*MODULE user_command_0100 INPUT.MODULE user_command_0100 INPUT. CASE sy-ucomm.CASE sy-ucomm. WHEN 'ENT'.WHEN 'ENT'.

SELECT ebeln ebelp bukrsSELECT ebeln ebelp bukrs INTO CORRESPONDING FIELDS OF TABLE it_poINTO CORRESPONDING FIELDS OF TABLE it_po FROM ekpoFROM ekpo WHERE ebeln = po_no.WHERE ebeln = po_no.

WHEN 'BCK'.WHEN 'BCK'. LEAVE TO SCREEN 0.LEAVE TO SCREEN 0. ENDCASE.ENDCASE.ENDMODULE. " USER_COMMAND_0100 INPUTENDMODULE. " USER_COMMAND_0100 INPUT


Includes Includes

• To have structured way of code it is best practice to have includes.To have structured way of code it is best practice to have includes.

• There should be a TOP include which will have the data declarations.There should be a TOP include which will have the data declarations.

• Include for PBO modules, include for PAI modules.Include for PBO modules, include for PAI modules.

• Include for POV and POH modules if any.Include for POV and POH modules if any.


IncludesIncludes

• To create include right click on object name, select Include from the To create include right click on object name, select Include from the Create menu.Create menu.


IncludesIncludes• We can gave the include names as Z<Program>_TOP, Z<Program>_PBO, We can gave the include names as Z<Program>_TOP, Z<Program>_PBO,

Z<Program>_PAI. This will help to understand which modules are covered in each include.Z<Program>_PAI. This will help to understand which modules are covered in each include.

• Each include program will insert a include statement in the main program.Each include program will insert a include statement in the main program.


Message StatementMessage Statement

• The “MESSAGE” statement is used to issue user messages.The “MESSAGE” statement is used to issue user messages.

• Syntax isSyntax is MESSAGE <tnnn> [WITH <var1> <var2> <var3> <var4>].MESSAGE <tnnn> [WITH <var1> <var2> <var3> <var4>].

t – Message typet – Message type nnn –Message Numbernnn –Message Number WITH – This is optional. It is needed if variables are used in a message. WITH – This is optional. It is needed if variables are used in a message.

A message can contain up to four variables, indicated with an A message can contain up to four variables, indicated with an ampersand (&) in the message text.ampersand (&) in the message text.

• We can code the Message statement in the PAI event.We can code the Message statement in the PAI event.


Message TypesMessage Types• S: success

• I: information

• A: abend

• X: exit

• W: warning

• E: error X

The message type determines where the message is displayed and what action the user can or must take on the current screen.

I


MessagesMessages

• SuccessSuccess message is displayed at the bottom of the screen. message is displayed at the bottom of the screen.

• If you have next screen then the message will be displayed at the bottom If you have next screen then the message will be displayed at the bottom of the next screen.of the next screen.

• InformationInformation message is displayed in a dialog box in same screen. message is displayed in a dialog box in same screen.

• After pressing Enter key on dialog box user will be taken to next screen. After pressing Enter key on dialog box user will be taken to next screen. The user is not restricted from going on to the next screen.The user is not restricted from going on to the next screen.


MessagesMessages

• Abend Abend message is displayed on the current screen in a dialog box.message is displayed on the current screen in a dialog box.• The user cannot make any changes to the values on the current screen.The user cannot make any changes to the values on the current screen.• After pressing the ‘Enter’ key on the dialog box, transaction will be After pressing the ‘Enter’ key on the dialog box, transaction will be

terminated.terminated.

• ExitExit message is identical to the ABEND message except that the transaction is message is identical to the ABEND message except that the transaction is terminated with a short dump instead of the message in a dialog box.terminated with a short dump instead of the message in a dialog box.

• WARNINGWARNING message is displayed at the bottom of the current screen. message is displayed at the bottom of the current screen.

• On pressing the ‘Enter’ key on the current screen, the user will be taken to the On pressing the ‘Enter’ key on the current screen, the user will be taken to the next screen even if no changes were made on the current screen . Thus user is next screen even if no changes were made on the current screen . Thus user is not restricted from going on to the next screen.not restricted from going on to the next screen.


MessagesMessages

• ERRORERROR message is displayed at the bottom of the current screen. message is displayed at the bottom of the current screen.

• The user must make changes to the values on the current screen.The user must make changes to the values on the current screen.

• On pressing the ‘Enter’ key on the current screen, the user will be taken On pressing the ‘Enter’ key on the current screen, the user will be taken to the next screen only if the appropriate corrections were made on the to the next screen only if the appropriate corrections were made on the current screen.current screen.

• If no corrections were made, the error message would be redisplayed at If no corrections were made, the error message would be redisplayed at the bottom of the current screen.the bottom of the current screen.

• When a warning or error message is triggered the system will stop at When a warning or error message is triggered the system will stop at current screen, prompting the user to make corrections. However the current screen, prompting the user to make corrections. However the input fields on the screen will be disabled for input.input fields on the screen will be disabled for input.


Handling Error messagesHandling Error messages

• There are 2 ways to issue error/warning messages.There are 2 ways to issue error/warning messages.

– Issue an error or warning message with the Flow Logic SELECT statement.Issue an error or warning message with the Flow Logic SELECT statement.– Define valid values for a screen field with the Flow Logic VALUES statement.Define valid values for a screen field with the Flow Logic VALUES statement.

• FIELDFIELD statement is a Flow Logic command, not an ABAP command. statement is a Flow Logic command, not an ABAP command.

• The purpose of the “FIELD” statement is to keep a single screen field open for The purpose of the “FIELD” statement is to keep a single screen field open for input after an error or warning message is issued.input after an error or warning message is issued.

• FIELD statement is used in PAI event.FIELD statement is used in PAI event.

• Syntax is: Syntax is: FIELDFIELD <screen field> <screen field> MODULE MODULE <module name>.<module name>.


FIELD with select statementFIELD with select statement• Screen field can be validated against entry in database table.Screen field can be validated against entry in database table.

• To validate Purchase order number in PAI module,To validate Purchase order number in PAI module, PROCESS AFTER INPUT.PROCESS AFTER INPUT.field PO_NO module PO_CHECK.field PO_NO module PO_CHECK.MODULE USER_COMMAND_0100.MODULE USER_COMMAND_0100.

Module PO_CHECK is as below,Module PO_CHECK is as below, module paycheck input.module paycheck input.

data: lv_ebeln type ekko-ebeln.data: lv_ebeln type ekko-ebeln. select single ebeln into lv_ebelnselect single ebeln into lv_ebeln from ekko where ebeln = PO_NO.from ekko where ebeln = PO_NO. if sy-subrc ne 0.if sy-subrc ne 0. message e003(Z6).message e003(Z6). endif.endif.

endmodule. " po_check INPUTendmodule. " po_check INPUT


Error for invalid inputError for invalid input

• Error for Purchase order when invalid number is entered.Error for Purchase order when invalid number is entered.


FIELD with Values CheckFIELD with Values Check

• The Flow Logic VALUES statement defines a set of valid values for the screen field specified in the FIELD statement.

• If the value entered in this field is not in the valid set, an error message will be issued by the system.

PROCESS AFTER INPUT. field PO_NO values ('1', '100').

• This indicates PO_NO can take input as either 1 or 100. For any other value system will through error and the field will be open for input.

• With VALUES parameter for field, we can get a list of possible values by clicking on the drop-down arrow of the screen fields or pressing the ‘F4’ key. It will list the values mentioned.


Values optionValues option

• PO_NO with values 1 and 100.PO_NO with values 1 and 100.


CHAIN StatementCHAIN Statement

• To keep multiple screen fields open for input after an error or warning To keep multiple screen fields open for input after an error or warning message is displayed, you need to use the “CHAIN” and “ENDCHAIN” message is displayed, you need to use the “CHAIN” and “ENDCHAIN” Flow Logic commands. Flow Logic commands.

• These statements group the “FIELD” statements and the “MODULE” These statements group the “FIELD” statements and the “MODULE” statements together. statements together.

• The basic syntax of these statements is:The basic syntax of these statements is: CHAIN.CHAIN.

FIELD: <f1>, <f 2>,... FIELD: <f1>, <f 2>,... MODULE <mod1>. MODULE <mod1>. FIELD: <g1>, <g 2>,... FIELD: <g1>, <g 2>,... MODULE <mod2>. MODULE <mod2>. ... ... ENDCHAIN. ENDCHAIN.

• If an error or warning message is issued in <module name>, all the screen If an error or warning message is issued in <module name>, all the screen fields listed in the “FIELD” statements will be open for input.fields listed in the “FIELD” statements will be open for input.


Cursor PositionCursor Position

• By default, the cursor will be positioned in the first field open for By default, the cursor will be positioned in the first field open for input on a screen.input on a screen.

• Cursor position can be changed in two ways –Cursor position can be changed in two ways –

1. By setting the cursor position in PBO event- 1. By setting the cursor position in PBO event-

Syntax -Syntax - SET CURSOR FIELD <field name>SET CURSOR FIELD <field name>

Cursor will be placed on the screen field mentioned.Cursor will be placed on the screen field mentioned.

2. Cursor position in screen attributes- 2. Cursor position in screen attributes-

Mention the field name where cursor to be placed on screen Mention the field name where cursor to be placed on screen in cursor position attribute . in cursor position attribute .


Screen commandsScreen commands

• The The LEAVE SCREENLEAVE SCREEN statement ends the current screen and statement ends the current screen and calls the subsequent screen. calls the subsequent screen.

• When the system encounters the When the system encounters the “SET SCREEN <screen #>”“SET SCREEN <screen #>” ABAP statement, it ABAP statement, it temporarilytemporarily overrides the “Next Screen” overrides the “Next Screen” attribute with this <screen #> and the PAI processing attribute with this <screen #> and the PAI processing continues. After all PAI modules are executed, the system continues. After all PAI modules are executed, the system goes to the PBO event of goes to the PBO event of

<screen #>.<screen #>.


Screen commandsScreen commands

• ““LEAVE TO SCREEN <screen #>”LEAVE TO SCREEN <screen #>” ABAP statement, ABAP statement, terminates the screen’s PAI event and immediately goes to the terminates the screen’s PAI event and immediately goes to the PBO of <screen #>.PBO of <screen #>.

• The “LEAVE TO SCREEN <screen #> statement performs the The “LEAVE TO SCREEN <screen #> statement performs the functionality of two statements: “SET SCREEN <screen #>“ functionality of two statements: “SET SCREEN <screen #>“ and “LEAVE SCREEN”.and “LEAVE SCREEN”.

• ““CALL SCREEN <screen #>”CALL SCREEN <screen #>” ABAP statement, temporarily ABAP statement, temporarily suspends the current screen’s PAI processing and immediately suspends the current screen’s PAI processing and immediately goes to the PBO event of <screen #>. When control returns back goes to the PBO event of <screen #>. When control returns back to the “calling” screen, its PAI processing will resume.to the “calling” screen, its PAI processing will resume.


More on PAI modulesMore on PAI modules

All modules listed in the PAI event get executed from top to bottom.All modules listed in the PAI event get executed from top to bottom.

• We can control the execution of the modules using additions to We can control the execution of the modules using additions to MODULE.MODULE.

• Additions are,Additions are, ON INPUT ON INPUT ON REQUESTON REQUEST AT EXIT-COMMANDAT EXIT-COMMAND AT CURSOR-SELECTIONAT CURSOR-SELECTION


ON INPUTON INPUT• With the “ON INPUT” addition to the “MODULE” statement, a module will be executed With the “ON INPUT” addition to the “MODULE” statement, a module will be executed

only if the specified field’s value is not equal to the initial value appropriate to its data typeonly if the specified field’s value is not equal to the initial value appropriate to its data type

• Ex- blanks for character fields and zeroes for numeric fields. Ex- blanks for character fields and zeroes for numeric fields.

• The basic syntax for this conditional execution Flow Logic command is:The basic syntax for this conditional execution Flow Logic command is:

– FIELD <screen field> MODULE <module> ON INPUT.FIELD <screen field> MODULE <module> ON INPUT.

– The PAI <module> will be executed only if the value in <screen field> is not equal to its The PAI <module> will be executed only if the value in <screen field> is not equal to its initial value.initial value.

– The “ON INPUT” addition must be used with a “FIELD” statement because this The “ON INPUT” addition must be used with a “FIELD” statement because this condition depends on the value of a particular field.condition depends on the value of a particular field.


ON REQUESTON REQUEST

• With the “ON REQUEST”, a module will be executed only if a value has been entered in With the “ON REQUEST”, a module will be executed only if a value has been entered in the specified field since the screen was displayed.the specified field since the screen was displayed.

• The basic syntax for this conditional execution Flow Logic command is:The basic syntax for this conditional execution Flow Logic command is:FIELD <screen field> MODULE <module> ON REQUEST.FIELD <screen field> MODULE <module> ON REQUEST.

– The PAI <module> will be executed only if a value was entered in <screen field> The PAI <module> will be executed only if a value was entered in <screen field> since the screen was displayed.since the screen was displayed.

– The “ON REQUEST” addition must be used with a “FIELD” statement because this The “ON REQUEST” addition must be used with a “FIELD” statement because this condition depends on the value of a particular field.condition depends on the value of a particular field.

• If you want to conditionally execute a module that is coded within a If you want to conditionally execute a module that is coded within a “CHAIN … ENDCHAIN”, you must use ““CHAIN … ENDCHAIN”, you must use “ON CHAIN-REQUEST”.ON CHAIN-REQUEST”.


AT EXIT-COMMANDAT EXIT-COMMAND

• With the “AT EXIT-COMMAND” addition to the “MODULE” With the “AT EXIT-COMMAND” addition to the “MODULE” statement, a module will be executed only if the user invokes a statement, a module will be executed only if the user invokes a function code with the ‘E’ function type.function code with the ‘E’ function type.

• Function type assigning is explained in slide 73.Function type assigning is explained in slide 73.

• The basic syntax for this conditional execution Flow Logic The basic syntax for this conditional execution Flow Logic command is:command is:MODULE <module> AT EXIT-COMMAND.MODULE <module> AT EXIT-COMMAND.


AT EXIT-COMMANDAT EXIT-COMMAND

– The PAI <module> will be executed only if the user invokes a The PAI <module> will be executed only if the user invokes a FUNCTION type ‘E’.FUNCTION type ‘E’.

– The “AT EXIT-COMMAND” addition cannot be used with a The “AT EXIT-COMMAND” addition cannot be used with a “FIELD” statement.“FIELD” statement.

• If the user invokes a type ‘E’ function code, a module with the “AT If the user invokes a type ‘E’ function code, a module with the “AT EXIT-COMMAND” addition will be executed immediately. EXIT-COMMAND” addition will be executed immediately.

• It will be executed even before the automatic field checks.It will be executed even before the automatic field checks.


Assigning Function typeAssigning Function type

• Function type can be Function type can be assigned for screen assigned for screen buttons and for menu buttons and for menu painter keys.painter keys.

• In menu painter, click In menu painter, click on the required key. In on the required key. In the pop-up window the pop-up window select function type as select function type as ‘E’ from drop down.‘E’ from drop down.


AT CURSOR-SELECTIONAT CURSOR-SELECTION

• You can specify that a module should only be called if the cursor is You can specify that a module should only be called if the cursor is positioned on a particular screen element.positioned on a particular screen element.

• Syntax -Syntax - MODULE <mod> AT CURSOR-SELECTIONMODULE <mod> AT CURSOR-SELECTION..

• The module <mod> is called whenever the function code of the user The module <mod> is called whenever the function code of the user action is CS with function type S.action is CS with function type S.

• The module is called in the sequence in which it occurs in the flow logic.The module is called in the sequence in which it occurs in the flow logic.• It does not bypass the automatic input checks.It does not bypass the automatic input checks.


AT CURSOR-SELECTIONAT CURSOR-SELECTION

• You can also combine this MODULE statement with the FIELD You can also combine this MODULE statement with the FIELD statement:statement:

FIELD <f> MODULE <mod> AT CURSOR-SELECTION.FIELD <f> MODULE <mod> AT CURSOR-SELECTION.

• For more than one field:For more than one field:

CHAIN.CHAIN. FIELD: <f1>, <f 2>,... FIELD: <f1>, <f 2>,... MODULE <mod> AT CURSOR-SELECTION. MODULE <mod> AT CURSOR-SELECTION.ENDCHAIN.ENDCHAIN.


Modifying Screen FieldsModifying Screen Fields

• All fields of the current screen are stored in the system table All fields of the current screen are stored in the system table SCREEN SCREEN with with their attributes.their attributes.

• The The LOOP AT SCREENLOOP AT SCREEN statement places this information in the header statement places this information in the header line of the system table.line of the system table.

• We can modify the attributes of the fields and update the screen table using We can modify the attributes of the fields and update the screen table using MODIFY SCREENMODIFY SCREEN..

• Sample code:Sample code: loop at screen.loop at screen. if screen-name = 'GV_MATNR'. if screen-name = 'GV_MATNR'. screen-input = 1.screen-input = 1. modify screen.modify screen. endif.endif. endloop.endloop.


Modifying Screen FieldsModifying Screen Fields

• You can dynamically modify the following attributes of a field:You can dynamically modify the following attributes of a field:– ACTIVE ACTIVE – REQUIREDREQUIRED– INPUTINPUT– OUTPUTOUTPUT– INTENSIFIEDINTENSIFIED– INVISIBLEINVISIBLE– LENGTHLENGTH– DISPLAY 3DDISPLAY 3D– VALUE HELPVALUE HELP

• A field attribute is turned “on” with a value of 1. It is turned “off” with a value A field attribute is turned “on” with a value of 1. It is turned “off” with a value of 0.of 0.

• The statements LOOP AT SCREEN ... ENDLOOP define a loop around a The statements LOOP AT SCREEN ... ENDLOOP define a loop around a statement block.statement block.


Logical Unit of Work (LUW)Logical Unit of Work (LUW)

• LUW refers to a collection of actions performed at the database level as a complete LUW refers to a collection of actions performed at the database level as a complete unit.unit.In this ex: LUW is selecting A and B from the database, updating A, and deleting B. In this ex: LUW is selecting A and B from the database, updating A, and deleting B.

This would be the desired LUW because we would want to rollback all changes if any This would be the desired LUW because we would want to rollback all changes if any of these actions failed.of these actions failed.

Screen2

Screen1

Screen3

SELECT ASELECT B UPDATE A DELETE B

DatabaseTransaction

DatabaseTransaction

DatabaseTransaction


LUWLUW

• Changes will be saved (commit work) in database at the end of third Changes will be saved (commit work) in database at the end of third screen.screen.

• An SAP LUW will end with either the COMMIT WORK or An SAP LUW will end with either the COMMIT WORK or ROLLBACK WORK statement.ROLLBACK WORK statement.

• A logical unit consisting of dialog steps, whose changes are written to A logical unit consisting of dialog steps, whose changes are written to the database in a single database LUW is called an SAP LUW.the database in a single database LUW is called an SAP LUW.

• If an SAP LUW contains database changes, you should either write all If an SAP LUW contains database changes, you should either write all of them or none at all to the database. of them or none at all to the database.

• Include a database commit when the transaction has ended successfully, Include a database commit when the transaction has ended successfully, and a database rollback in case the program detects an error. and a database rollback in case the program detects an error.


LUWLUW

• Since database changes from a database LUW cannot be reversed in a Since database changes from a database LUW cannot be reversed in a subsequent database LUW, you must make all of the database changes for subsequent database LUW, you must make all of the database changes for the SAP LUW in a single database LUW.the SAP LUW in a single database LUW.

• In our example, we need to perform UPDATE A and DELETE B at the In our example, we need to perform UPDATE A and DELETE B at the end of third screen.end of third screen.


SAP LocksSAP Locks

• R/3 system contain lock mechanism for SAP LUWs called SAP Locks.R/3 system contain lock mechanism for SAP LUWs called SAP Locks.

• Lock object is created in ABAP Dictionary.Lock object is created in ABAP Dictionary.

• A lock object definition contains the database tables and their key fields A lock object definition contains the database tables and their key fields on the basis of which you want to set a lock.on the basis of which you want to set a lock.

• System automatically generates two function modules with the names System automatically generates two function modules with the names ENQUEUE_<lock object name> and DEQUEUE_<lock object name> ENQUEUE_<lock object name> and DEQUEUE_<lock object name> when a lock is generated. when a lock is generated.

• Locks can be set and released on corresponding database table by calling Locks can be set and released on corresponding database table by calling these function modules in program.these function modules in program.


SAP LocksSAP Locks• Consider below example, Consider below example,

• When user clicks on change, the program locks the relevant database object by calling the corresponding ENQUEUE When user clicks on change, the program locks the relevant database object by calling the corresponding ENQUEUE function. function.

• You can release the lock by calling DEQUEUE function when user clicks on SAVE or when user clicks on BACK button.You can release the lock by calling DEQUEUE function when user clicks on SAVE or when user clicks on BACK button.


Table ControlTable Control

• A table control is an area on the screen where the system displays data in a A table control is an area on the screen where the system displays data in a tabular form. It is processed using a loop.tabular form. It is processed using a loop.

• To create a table control, drag & drop table control from screen elements on To create a table control, drag & drop table control from screen elements on screen painter. Give a name to table control.screen painter. Give a name to table control.

• Select the table definition and fields clicking on Dictionary/Program fields Select the table definition and fields clicking on Dictionary/Program fields object button.object button.

• Each table control need to be declared in declaration part of the program as,Each table control need to be declared in declaration part of the program as, CONTROLS <ctrl> TYPE TABLEVIEW USING SCREEN <scr>.CONTROLS <ctrl> TYPE TABLEVIEW USING SCREEN <scr>. where <ctrl> is the name of the table control on a screen.where <ctrl> is the name of the table control on a screen.


Table ControlTable Control

• YouYou mustmust code a LOOP statement in both the PBO and PAI events for each code a LOOP statement in both the PBO and PAI events for each table in your screen.table in your screen.

• This is because the LOOP statement causes the screen fields to be copied This is because the LOOP statement causes the screen fields to be copied back and forth between the ABAP program and the screen field. back and forth between the ABAP program and the screen field.

• For this reason, at least an empty LOOP...ENDLOOP must be there.For this reason, at least an empty LOOP...ENDLOOP must be there.


Processing Table Control

Database

Internal Table with header

Internal Table with header

Screen


Table ControlTable ControlSample code -Sample code -

PROCESS BEFORE OUTPUT.PROCESS BEFORE OUTPUT. MODULE STATUS_0100.MODULE STATUS_0100.LOOP AT it_po INTO wa_ekpo WITH CONTROL tab2 CURSORLOOP AT it_po INTO wa_ekpo WITH CONTROL tab2 CURSOR tab2-current_line.tab2-current_line. ENDLOOP.ENDLOOP.

PROCESS AFTER INPUT.PROCESS AFTER INPUT.field po_no module po_check.field po_no module po_check. module exit_mod at exit-command.module exit_mod at exit-command.MODULE USER_COMMAND_0100.MODULE USER_COMMAND_0100.loop at it_po.loop at it_po.endloop.endloop.


SubscreenSubscreen• A subscreen is a screen that is displayed in a specified area of the main screen. A subscreen is a screen that is displayed in a specified area of the main screen.

• A subscreen cannot be displayed by itself.A subscreen cannot be displayed by itself.

• The subscreen displayed in the predefined area will depend on the user’s The subscreen displayed in the predefined area will depend on the user’s request on the main screen.request on the main screen.

• Subscreen is used to vary the fields displayed on a screen. As an example:Subscreen is used to vary the fields displayed on a screen. As an example:– The “main” screen contains the customer number, name, and a predefined The “main” screen contains the customer number, name, and a predefined

area for a subscreen.area for a subscreen.– One subscreen contains customer address information.One subscreen contains customer address information.– Another subscreen contains customer bank information.Another subscreen contains customer bank information.


Creating SubscreenCreating Subscreen• In main screen,In main screen,

– In the screen layout, place the screen element ‘subscreen’ on layout. In the screen layout, place the screen element ‘subscreen’ on layout.

– You can set the length and width of the subscreen by double clicking You can set the length and width of the subscreen by double clicking on subscreen.on subscreen.

– Provide unique name to subscreen, save and activate it.Provide unique name to subscreen, save and activate it.

Subscreen


Creating SubscreenCreating Subscreen• Create a subscreenCreate a subscreen

– Create a screen as given in earlier slides.Create a screen as given in earlier slides.– Screen type should be subscreen. Screen type should be subscreen.

– Specify the screen length and height as in main screen.Specify the screen length and height as in main screen.

– Save the subscreen and go to screen layout. Here subscreen are will Save the subscreen and go to screen layout. Here subscreen are will be displayed.be displayed.


Creating SubscreenCreating Subscreen

• User can design in the subscreen area as below,User can design in the subscreen area as below,


Call subscreen in PBOCall subscreen in PBO

• To include a subscreen in a predefined area on the “main” screen, use the To include a subscreen in a predefined area on the “main” screen, use the “CALL SUBSCREEN” statement in the “main” screen’s PBO event. “CALL SUBSCREEN” statement in the “main” screen’s PBO event.

• syntax :syntax :CALL SUBSCREEN <area> INCLUDING <program> <subscreen CALL SUBSCREEN <area> INCLUDING <program> <subscreen #>.#>.

– <area> : name of the subscreen area defined on the “main” screen. This <area> : name of the subscreen area defined on the “main” screen. This subscreen area will be the location of the subscreen. This <area> subscreen area will be the location of the subscreen. This <area> cannotcannot be enclosed in single quotes.be enclosed in single quotes.

– <program> : name of the program where the subscreen exists<program> : name of the program where the subscreen exists. .


Call subscreen in PBOCall subscreen in PBO

– <subscreen #> : number of the subscreen to display in the subscreen area.<subscreen #> : number of the subscreen to display in the subscreen area.– The <program> and <subscreen #> can be literals (i.e. enclosed in single The <program> and <subscreen #> can be literals (i.e. enclosed in single

quotes) or variables.quotes) or variables.

• When the “CALL SUBSCREEN” statement is encountered in the “main” When the “CALL SUBSCREEN” statement is encountered in the “main” screen’s PBO event, the system executes the PBO event of the subscreen. Then, screen’s PBO event, the system executes the PBO event of the subscreen. Then, the system returns to finish the PBO event of the “main” screenthe system returns to finish the PBO event of the “main” screen..


Call subscreen in PAICall subscreen in PAI• If the subscreen contains any PAI code, use the “CALL SUBSCREEN” If the subscreen contains any PAI code, use the “CALL SUBSCREEN”

statement in the PAI event of the “main” screen. statement in the PAI event of the “main” screen.

• Syntax :Syntax : CALL SUBSCREEN <area>.CALL SUBSCREEN <area>.

– The <area> is the name of the subscreen area defined on the “main” The <area> is the name of the subscreen area defined on the “main” screen. This <area> screen. This <area> cannotcannot be enclosed in single quotes. be enclosed in single quotes.

• The “CALL SUBSCREEN” statement must be used to invoke the PAI The “CALL SUBSCREEN” statement must be used to invoke the PAI event of the subscreen. event of the subscreen.

- When the “CALL SUBSCREEN” statement is - When the “CALL SUBSCREEN” statement is encountered in the “main” screen’s PAI event, the encountered in the “main” screen’s PAI event, the system system executes the PAI event of the subscreen. executes the PAI event of the subscreen.


Call subscreen in PAICall subscreen in PAI

– Then, the system returns to finish the PAI event of the “main” screen.Then, the system returns to finish the PAI event of the “main” screen.

– Without this “CALL SUBSCREEN” statement in the PAI event of the Without this “CALL SUBSCREEN” statement in the PAI event of the “main” screen, the PAI event of the subscreen cannot be processed by “main” screen, the PAI event of the subscreen cannot be processed by the system.the system.

• If the subscreen does not contain any PAI code, this “CALL SUBSCREEN” If the subscreen does not contain any PAI code, this “CALL SUBSCREEN” statement is statement is notnot needed in the PAI event of the “main” screen. needed in the PAI event of the “main” screen.

• In both the PBO and PAI of the “main” screen, the “CALL SUBSCREEN” In both the PBO and PAI of the “main” screen, the “CALL SUBSCREEN” statement cannot be used inside a “LOOP” or a “CHAIN”.statement cannot be used inside a “LOOP” or a “CHAIN”.


Subscreen RestrictionsSubscreen Restrictions

• The following ABAP/4 statements The following ABAP/4 statements cannotcannot be used in a subscreen’s PBO be used in a subscreen’s PBO or PAI modules (instead, they must be used in the “main” screen):or PAI modules (instead, they must be used in the “main” screen):

– SET PF-STATUSSET PF-STATUS– SET TITLEBARSET TITLEBAR– SET SCREENSET SCREEN– LEAVE TO SCREENLEAVE TO SCREEN– CALL SCREENCALL SCREEN

– Note: These ABAP/4 statements in a subscreen will pass a syntax Note: These ABAP/4 statements in a subscreen will pass a syntax check; however, they will result in runtime errors.check; however, they will result in runtime errors.


Tab Strip ControlsTab Strip Controls

• Each tab page consists of a tab title and a page area. Each tab page consists of a tab title and a page area.

• If the area occupied by the tab strip control is too narrow to display all of If the area occupied by the tab strip control is too narrow to display all of the tab titles, a scrollbar appears, allowing you to reach the titles that are not the tab titles, a scrollbar appears, allowing you to reach the titles that are not displayed. displayed.

• Tab strips allow users to access multiple sub screens on one normal screen. Tab strips allow users to access multiple sub screens on one normal screen.

• This allows for a more intuitive user interface by logically separating the This allows for a more intuitive user interface by logically separating the information presented to the user into different headings. information presented to the user into different headings.

• The user can sort through the information by clicking on a corresponding The user can sort through the information by clicking on a corresponding tabtab

A tab strip control is a screen object A tab strip control is a screen object consisting of two or more pages.consisting of two or more pages.


Tab Strip Control componentsTab Strip Control components

TabTtitle Tab PageTab Title Row

Scrolling


• Tab TitleTab Title – Title of the component to which user can – Title of the component to which user can navigate. They are push buttons.navigate. They are push buttons.

• Tab title rowTab title row - All tab titles will appear in a row. - All tab titles will appear in a row.

• Tab PageTab Page - A tab page contains a collection of fields that logically - A tab page contains a collection of fields that logically belong together. Tab pages are implemented using subscreens. belong together. Tab pages are implemented using subscreens.

• For designing and using tab strip controls, see Transaction For designing and using tab strip controls, see Transaction BIBSBIBS . .

Tab Strip Control componentsTab Strip Control components



•Tab strip controls allow you to place a series of screens belonging to an application on a single screen, and to navigate between them easily. •From a technical point of view, a tab page is a sunscreen with a pushbutton assigned to it, which is displayed as the tab title.

When you create a tab strip control, you must: ……….

1. Define the tab area on a screen and the tab titles.

2. Assign a subscreen area to each tab title.3. Program the screen flow logic.4. Program the ABAP processing logic.


Assigning a Subscreen Area to a Tab Title

1. Paging in the SAPgui

PROCESS BEFORE OUTPUT. ... CALL SUBSCREEN: area1 INCLUDING [prog1] dynp1, area2 INCLUDING [prog2] dynp2, area3 INCLUDING [prog3] dynp3, ...PROCESS AFTER INPUT. ... CALL SUBSCREEN: area1, area2, area3, …

2. Paging on the application server

PROCESS BEFORE OUTPUT. ... CALL SUBSCREEN area INCLUDING [prog] dynp. ...

PROCESS AFTER INPUT. ... CALL SUBSCREEN area.



Handling in the ABAP Program

Create a control for each control in the declaration part of yourprogram using the following statement:

CONTROLS ctrl TYPE TABSTRIP.

PROCESS BEFORE OUTPUT. ...

Assign the function code of the corresponding tab title to the component Activetab:

ctrl-Activetab = fcode.

PROCESS AFTER INPUT …

Activetab contains the function code of the last active tab title on the screen.



Programming the Flow Logic

The flow logic is restricted to that necessary to include the appropriatesubscreen screens in the right subscreen areas.

Local Scrolling at the Front-end Include subscreen screens in all of your subscreen areas in the tab strip control.

PROCESS BEFORE OUTPUT.CALL SUBSCREEN: <subscreen_area1> INCLUDING [<progname 1>] <subscreen_scrn 1>, <subscreen_area2> INCLUDING [<progname 2>] <subscreen_scrn 2>,

<subscreen_area3> INCLUDING [<progname 3>] <subscreen_scrn 3>,

PROCESS AFTER INPUT CALL SUBSCREEN: <subscreen_area1>, <subscreen_area2>, <subscreen_area3>,



Programming the Flow Logic

The flow logic is restricted to that necessary to include the appropriatesubscreen screens in the right subscreen areas.

Scrolling at the Application Server Include one subscreen at a time in a single subscreen area.

PROCESS BEFORE OUTPUT.

CALL SUBSCREEN < subscreen_area> INCLUDING [<progname>] <subscreen_scrn>.

PROCESS AFTER INPUT

CALL SUBSCREEN < subscreen_area>.



Step loopsStep loops

• Step loops are considerable less flexible than table controls.Step loops are considerable less flexible than table controls.

• Used to group screen elements together. A step loop is a repeated series of Used to group screen elements together. A step loop is a repeated series of loop blocks. A loop block consists of one or more loop lines of graphical loop blocks. A loop block consists of one or more loop lines of graphical screen elements.screen elements.

• Loop blocs can be defined as fixed or variable.Loop blocs can be defined as fixed or variable.

– In a fixed loop, the lower limit of the loop area always remains as In a fixed loop, the lower limit of the loop area always remains as originally defined. originally defined.

– For a variable loop, the number of repetitions is adjusted dynamically in For a variable loop, the number of repetitions is adjusted dynamically in the screen program to suit the size of the current window. the screen program to suit the size of the current window.


Creating a Step loopCreating a Step loop

• Open a screen in the layout editor. Open a screen in the layout editor.

• In one or more lines, create the elements you want to repeat. In one or more lines, create the elements you want to repeat.

• Select all the elements on the desired line(s) as a group. Select all the elements on the desired line(s) as a group.

• Choose Edit Choose Edit Grouping Grouping Step loop Step loop Define. Define.

• Your element lines now make up a single step loop block. The block includes the original elements Your element lines now make up a single step loop block. The block includes the original elements with their attributes and a predefined number of repetition blocks. with their attributes and a predefined number of repetition blocks.

• Each repetition contains a copy of the first block without attributes.Each repetition contains a copy of the first block without attributes.

• The repetition blocks are consecutively numbered, so that you can establish a reference to a The repetition blocks are consecutively numbered, so that you can establish a reference to a particular line.particular line.


Step loopsStep loops• To use a Step-Loop block in an online program, you must create one work To use a Step-Loop block in an online program, you must create one work

area for the Step-Loop block. To hold all the lines of a Step-Loop block in the area for the Step-Loop block. To hold all the lines of a Step-Loop block in the program’s memory area, use an internal table.program’s memory area, use an internal table.

Ex:-TYPES: BEGIN OF TY_REC,Ex:-TYPES: BEGIN OF TY_REC, MATNR TTPE MARA-MATNR,MATNR TTPE MARA-MATNR,

MATKL TYPE MARA-MATKL,MATKL TYPE MARA-MATKL, END OF TY_REC.END OF TY_REC. DATA: GT_MARA TYPE TABLE OF TY_REC WITHDATA: GT_MARA TYPE TABLE OF TY_REC WITH

HEADER LINE.HEADER LINE.

• For Step loop the flow logic statement loop must be coded in both PBO and For Step loop the flow logic statement loop must be coded in both PBO and PAI event. One form of the Flow Logic “LOOP” statement is;PAI event. One form of the Flow Logic “LOOP” statement is;

LOOP.LOOP.. . . <flow logic statements> . . .. . . <flow logic statements> . . .ENDLOOP.ENDLOOP.


Main screen Flow logic Main screen Flow logic

Main screen flow logic for calling subscreen.Main screen flow logic for calling subscreen.

PROCESS BEFORE OUTPUT.PROCESS BEFORE OUTPUT.

MODULE STATUS_0100.MODULE STATUS_0100.

call subscreen SUB1 including 'Z_MODULE_TRAINING' '0110'.call subscreen SUB1 including 'Z_MODULE_TRAINING' '0110'.

PROCESS AFTER INPUT.PROCESS AFTER INPUT.

call subscreen SUB1.call subscreen SUB1.

MODULE USER_COMMAND_0100.MODULE USER_COMMAND_0100.


Additions with ABAP OOPSAdditions with ABAP OOPS

• Enjoy SAP controls (ALV Grid , ALV Tree, HTML controls etc) can be Enjoy SAP controls (ALV Grid , ALV Tree, HTML controls etc) can be displayed in screen. displayed in screen.

• To place these grids we need to have screen element Custom Control To place these grids we need to have screen element Custom Control placed on the screen.placed on the screen.

• Also we need to have ABAP OOPS knowledge. ( Refer package SLIS Also we need to have ABAP OOPS knowledge. ( Refer package SLIS for examples)for examples)


Process on HelpProcess on Help

• This event is a user programmed help.This event is a user programmed help.

• If the user presses the ‘F1’ key with the cursor is positioned in <screen If the user presses the ‘F1’ key with the cursor is positioned in <screen field>, the <supplemental documentation> will be displayed along with field>, the <supplemental documentation> will be displayed along with the data element’s short text and documentation.the data element’s short text and documentation.

• The only other Flow Logic statement that can be used in the POH event The only other Flow Logic statement that can be used in the POH event is:is: FIELD <screen field> MODULE <module>.FIELD <screen field> MODULE <module>.


Process on ValueProcess on Value

• This event is a user-programmed help that occurs when the user presses This event is a user-programmed help that occurs when the user presses F4 with the cursor positioned on a screen field.F4 with the cursor positioned on a screen field.

• The modules specified in the subsequent FIELD statement is called The modules specified in the subsequent FIELD statement is called instead of the SAP help. instead of the SAP help.

• Syntax is:Syntax is: FIELD <screen field> MODULE <module>.FIELD <screen field> MODULE <module>.



1 PrepareMe


3 Demonstration

4 Exercises

5 HelpMe

Introduction


DemonstrationDemonstration

Please refer the attached document for demo example.Please refer the attached document for demo example.

Microsoft Word Document



1 Introduction


3 Demonstration

4 Exercises

5 HelpMe


ExercisesExercises

Please refer the attached documents for hands-on.Please refer the attached documents for hands-on.

• Exercise 1 – This covers input/output, radio button, table control, screen Exercise 1 – This covers input/output, radio button, table control, screen navigation, flow logic events, Menu painter.navigation, flow logic events, Menu painter.

• Exercise 2 – This covers tab strip, subscreen, table control, 4 flow logic Exercise 2 – This covers tab strip, subscreen, table control, 4 flow logic events, screen navigation, menu painter.events, screen navigation, menu painter.





1 Introduction


3 Demonstration

4 Exercises

5 HelpMe


HelpMeHelpMe

• ReferRefer help.sap.comhelp.sap.com

• Refer Transaction code Refer Transaction code ABAPDOCUABAPDOCU (check in drop down ABAP User (check in drop down ABAP User Dialogs) for documentation and examplesDialogs) for documentation and examples

• For screen elements and controls (table control, tabstrip) refer transaction For screen elements and controls (table control, tabstrip) refer transaction BIBSBIBS..

• Refer package SLIS for examples of ALV grids, ALV Tree.Refer package SLIS for examples of ALV grids, ALV Tree.