Pop-up box in dialog programming

Hi,
Is it possible to add a pop-up box inside dialog programs?..if so can someone show me how?
thanks!

hi,
it is possible to display popup box inside the dialog programs.
follow this sample program, it clearly explains the logic.......
FLOW-LOGIC CODE.
PROCESS ON VALUE-REQUEST.
 FIELD SFLIGHT-CONNID MODULE HELP-FOR-CONNID.
CODE FOR MODULE POOL PROGRAM.
MODULE HELP-FOR-CONNID INPUT.
 DATA: begin of it_itab occurs 0,
 connid1(45),
 end of it_itab.
 refresh it_itab.
 it_itab-connid1 = 'possible vales for connectionid'.
 append it_itab.
 select * from sflight.
 it_itab-connid1 = sflight-connid.
 append it_itab.
 endselect.
 ****here call FM to display pop-up box
 call function 'popup_with_table_display'
 exporting
 endpos_col = 45
 endpos_row = 25
 startpos_col = 10
 startpos_row = 1
 titiletext = 'text'
 tables
 valuetab = it_itab.
the above program display the list of possible values for the field connid in popup-box.
regards,
Ashok Reddy

Similar Messages

Handle text using list box in dialog program

hi,
I am working on dialog program , Created two fileds , one is list box type I/O field and another is i/O field which displays text based on value selected in list box.
Please provide any inf how to Handle text using list box value in dialog program.
thanks

Hi,
<li>Check the screen to know how to set I/O field to set as listbox.[ dropdown box picture|http://2.bp.blogspot.com/_O5f8iAlgdNQ/Sm7RBrqfjcI/AAAAAAAAFaU/RateViiVqrU/s1600-h/drop_down-754481.JPG]
<li>in the above screen we need to set FctCode for the dropdown box field so that when you select value from the dropdown box PAI event is triggered.
<li>screen flow logic like below
PROCESS BEFORE OUTPUT.
MODULE values_into_dropdown.
FIELD g_bukrs.
FIELD g_text.
PROCESS AFTER INPUT.
FIELD g_bukrs.
FIELD g_text MODULE get_bukrs_txt.
<li>Logic to fill Dropdown field with values.
PROGRAM sapmztest_dropdown.
DATA: g_bukrs TYPE t001-bukrs.
*& Module VALUES_INTO_DROPDOWN OUTPUT
MODULE values_into_dropdown OUTPUT.
TYPE-POOLS:vrm.
DATA:
 field TYPE vrm_id,
 it_values TYPE vrm_values,
 wa_values LIKE LINE OF it_values.
DATA: t001 TYPE t001 OCCURS 0 WITH HEADER LINE.
IF it_values[] Is INITIAL.
 SELECT * FROM t001 INTO TABLE t001 UP TO 10 ROWS.
 LOOP AT t001.
 wa_values-key = t001-bukrs.
 wa_values-text = t001-butxt.
 APPEND wa_values TO it_values.
 CLEAR wa_values.
 ENDLOOP.
ENDIF.
field = 'G_BUKRS'.
CALL FUNCTION 'VRM_SET_VALUES'
 EXPORTING
 ID = FIELD
 values = it_values.
ENDMODULE. " VALUES_INTO_DROPDOWN OUTPUT
*& Module get_bukrs_txt INPUT
MODULE get_bukrs_txt INPUT.
read table it_t100 into wa_t100 with key bukrs = g_bukrs.
g_text = t001-butxt.
ENDMODULE. " VALUES_INTO_DROPDOWN INPUT
I hope that it helps you.
Thanks
Venkat.O

List box in dialog programming

Hi Frnds,
              i am working on a complex scenario,
i want to print 3 list box.
first one i can show but the problem is with second one and third one.
first list box have three fields suppose
program
events
movies
when user will select either one , suppose he will select program
then in second listbox program releted entries should be displayed like fiction , non fiction.
and when he will select any entry then in third list box corresponding sub entries should be come.
all data i have in ztables.
i can make search help also.
any suggestion should be appreciated.
Thanks and Regards
vijay

Use this program!
TYPE-POOLS: vrm.
DATA: name TYPE vrm_id, list TYPE vrm_values, value LIKE LINE OF list.
TABLES: sscrfields.
Selection screen
List box
PARAMETERS: ps_parm AS LISTBOX VISIBLE LENGTH 10
                          USER-COMMAND abc.
Radio buttons
PARAMETERS: rb1 RADIOBUTTON GROUP ab MODIF ID bl2,
            rb2 RADIOBUTTON GROUP ab MODIF ID bl2,
            rb3 RADIOBUTTON GROUP ab MODIF ID bl3.
INITIALIZATION.
Populate list box values
name = 'PS_PARM'.
value-key = '1'. value-text = 'Line 1'. APPEND value TO list.
value-key = '2'. value-text = 'Line 2'. APPEND value TO list.
AT SELECTION-SCREEN OUTPUT.
Set list box with value
CALL FUNCTION 'VRM_SET_VALUES'
    EXPORTING
      id     = name
      values = list.
Control the display of screen components
LOOP AT SCREEN.
    IF ps_parm = 1.
      IF screen-name = 'RB1' OR screen-name = 'RB2' .
        screen-invisible = 0.
      ELSEIF screen-name = 'RB3'.
        screen-invisible = 1.
      ENDIF.
      MODIFY SCREEN.
    ELSEIF ps_parm = 2.
      IF screen-name = 'RB1' OR screen-name = 'RB2' .
        screen-invisible = 1.
      ELSEIF screen-name = 'RB3'.
        screen-invisible = 0.
      ENDIF.
      MODIFY SCREEN.
    ELSEIF ps_parm = space.
      rb1 = 'X'.
      clear: rb2,rb3.
      IF screen-name = 'RB1' OR screen-name = 'RB2' OR
         screen-name = 'RB3'.
        screen-invisible = 0.
        MODIFY SCREEN.
      ENDIF.
    ENDIF.
ENDLOOP.
AT SELECTION-SCREEN.
IF sscrfields-ucomm = 'ABC'.
ENDIF.
START-OF-SELECTION.
WRITE: / 'Parameter:', ps_parm.
And use:
AT-SELECTION-SCREEN on value request for p_yyyy.
if p_xxxx-key is not initial..
get the values required for second parameter...or listbox..
endif..
similarily for 3rd listbox also!

Modal Dialog box in Dialog Programe

I have create one Modal Dialog Box in Module Pool.
when i click on the 'X' on the top right side of that screen the Dialog box is not closed.
Can any one help on this?

For the Modal Dialog box you need to create the Status, while creating the status Choose the Status for Dialog box. that time you it will show different Status Options.
you need to set the status to the CANCEL(X) button , Then handle the Function in the PAI user_command module.
CASE sy-ucomm.
when 'CANCEL'.
leave to screen 0.
endcase.

Control of Text box in Dialog programming

Hai Friends
i am having problem in controlling the Text box in PAI of Screen. For eg. if it is command button with the use of Function name i can able to check or do validation in PAI.
As in the case of Textbox how to give the name for the text box and how to handle it in PAI for Validation.
Please
Badhri.

Are you talking about a text editor? IF so, what is the validation that you want to perform. Do you want to check to make sure that the user has entered something in the text editor?
If so, then just get the text from the text editor into an internal table, and check that internal table to make sure that something is in it.
 call method editor->get_text_as_r3table
 exporting
 only_when_modified = c_textedit_control=>false
 importing
 table = textlines
 exceptions
 others = 1.
 if textlines[] is initial.
 message e014.
 endif.
Regards,
Rich Heilman

Values not populating in list box in dialog programing.

hi,
i am facing a problem i.e. i am having a listbox on screen , in pbo i am filling that listbox with some values in an internal table.
But i am not able to populate the values i.e. while i am debugging the pai ......the list box is containing nothing.
So needed some help in this issue.
regards,
somesh

Hi,
Try to read these links. It will give you some pointers regarding on your problem.
<link-farm removed>
Revert if you have still any concern.
Thanks,
iostreamax
Edited by: Suhas Saha on Feb 21, 2012 8:50 AM

Question Related to Check-box in Dialog Program

Hi All-
I desgined check box in Table Control... In my Internal table I have 41 records, When user click on Select all button it selects only first 14 records from the table control...When the user uses page-down, then click on Select all, selects remaining 14 records and so on...
But how to select all the records at a time instead of using page-down...
Please advice me how to solve my problem!!!!
Thanks,
Sony

I would not suggest doing it like that. Instead move the MODULE USER_COMMAND outside of that loop.
* Screen Flow Logic
PROCESS AFTER INPUT.
LOOP AT i_x002 .
ENDLOOP.
MODULE user_command_0600 .
* Module coding
MODULE user_command_0600 input..
CASE sy-ucomm.
WHEN 'SELA'.
loop at i_x002.
i_x002-flag = 'X'.
MODIFY i_x002.
endloop.
WHEN 'DELA'.
loop at i_x002.
i_x002-flag = space.
MODIFY i_x002.
endloop.
ENDCASE.
endmodule.
Regards,
Rich Heilman

Declaring constant data in a list box - Dialog programming

i need to declarare some constant data 1...4 in list box in dialog programming i have done some coding its not working here is the code, can you plz tell me whats wrong in the code non of the values are displaying in drop downbox.
type-pools vrm.
DATA: name TYPE vrm_id,
list TYPE vrm_values,
value LIKE LINE OF list.
clear list.
REFRESH LIST.
value-key = '1'.
value-text = 'Sales & Distribution'.
append value to list.
value-key = '2'.
value-text = 'Material Management'.
append value to list.
value-key = '3'.
value-text = 'Finance & Controlling'.
append value to list.
CALL FUNCTION 'VRM_SET_VALUES'
EXPORTING
 id = 'LISTBOX1'
 values = list
EXCEPTIONS
ID_ILLEGAL_NAME = 1
OTHERS = 2
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.

I think your code is correct onlybut the problem may be where
you are passing the internal table to the FM 'VRM_SET_VALUES' ...
Try to use the following code..
CALL FUNCTION 'VRM_SET_VALUES'
EXPORTING
id = 'LISTBOX1'
values = list[]

Pop up Box while workflow executes an activity step

Hi Folks!
I dont know whether this is feasible or not, but please shoot your suggestions.
I want to display a pop up box in SAP GUI when a workflow executes a particular step. Basically, once my workflow starts, I have included a condition step (it checks the document type). So if the document type is 'X', then the workflow should proceed as usual. However, when the document type 's 'Y', the workflow should throw a pop up message over the screen and the workflow should terminate.
Now the reason why we want the pop up screen rather than an email/workitem is because we have two workflows that utilize the same business object (FIPP). There was a situation where an end user manually started *(thru 'services for object'-> start workflow) the wrong workflow for a document, due to which the document got posted without getting any approvals.
So what we would like to achieve is when the user manually starts the wrong workflow, the workflow should proceed and then when the check condition fails the user should get a pop up box immediately in SAP itself saying that the wrong workflow was started.
Your inputs/comments are most welcome.
Regards,
Anwar.

I am sorry but it is not possible to throw pop up every time, actually workflow consists of background task which got executed without user intervention and in those cases no pop up will come up.
You can get pop up box for dialog task (such as user decision etc)you have to write down business object method code for that.
there are many ways you can handle your situation:
1. Write down the Check FM for FIPP-Posted Event where you can check it whether it is approved or not, If not then do not complete the workflow and start some dialog WI and send across to approvers
(It is just outline, you have to formulate the solution around this outline).
2. Also you can check for BAdi or user Exit and directly can write down message for that, It seems more easy.
Cheers
Jai

Pop-up box

Hi to all experts,
I want to create a pop-up box at output and after selecting a single line it goes to the Related transaction (if in pop-up box have 5 program name then after selecting one program system goes to perticuler program on se38).
How can solve this issue, please give me detail with example.
Thanks in advance and reward also.
Regard : Deep.

Hi try the below example.
it is dynamic subroutine
FORM   sy_ucomm_for_pernr USING r_ucomm LIKE sy-ucomm rs_selfield TYPE
slis_selfield.
CASE rs_selfield-fieldname.
    WHEN 'PERNR'. " ==>in which field u want to click that field name(internal *table field name
      READ TABLE itap_main WITH KEY pernr = rs_selfield-value." ur popup menu table.
      IF sy-subrc EQ 0.
        SET PARAMETER ID 'PER' FIELD gi_main-pernr.
in se38 parameter id is 'RID'
        CALL TRANSACTION 'se38'.
      ENDIF.
ENDCASE.
ENDFORM.
good regards,
vallamuthu.m

How can I forward next page, and then pop-up a download dialog box.

My require is that pop-up a download dialog box after forwarding next page.
I have read the coding in the processFormRequest of current page like below,
but I find out that it only can pop-up a download dialog box,
however, it can't forward the next page.
pageContext.setForwardURL("OA.jsp?page=/oracle/apps/xxfm/fm002/webui/TEST001PG",
null,
OAWebBeanConstants.KEEP_NO_DISPLAY_MENU_CONTEXT,
null,
null,
true,
OAWebBeanConstants.ADD_BREAD_CRUMB_NO,
OAException.INFORMATION);
//set default file name: [YYYYMMDDhhmm_IN.EXCEL,FILE_NAME.csv]
StringBuffer strFileName
= new StringBuffer().append((pageContext.getCurrentDBDate().toString().substring(0, 16))
.replaceAll("-","").replaceAll(" ","").replaceAll(":",""))
.append("_IN.").append(strExcelFileName).append(".csv");
//give csv file content
BlobDomain csvFileBlob = (BlobDomain)am.invokeMethod("createCsvFile");
//setenv
HttpServletResponse response
= (HttpServletResponse)pageContext.getRenderingContext().getServletResponse();
response.setContentType("application/octet-stream");
response.setHeader("Content-Disposition", "attachment; filename="+strFileName.toString());
System.out.println("fileName : "+strFileName.toString());
//download
InputStream fileIn = csvFileBlob.getBinaryStream();
long fileLen = csvFileBlob.getBufferSize();
int readBytes = 0;
int totalRead = 0;
byte blockgbyte[] = new byte[65000];
response.setContentType("application/x-msdownload");
response.setContentLength((int)fileLen);
while((long)totalRead < fileLen)
readBytes = fileIn.read(blockgbyte, 0, 65000);
totalRead += readBytes;
response.getOutputStream().write(blockgbyte, 0, readBytes);
fileIn.close();
response.getOutputStream().flush();
I don't know what's matter in the app, can you tell me how to deal with it.
Thanks in advance.

Hi there,
I have a similar requirement. User will download search results in a CSV file after which I want either the page to be refreshed or to be able to goto a Confirmation page or navigate to another page.
I tried using setForwardURL / forwardImmediately / redirectImmediately methods as well as redirectToDialogPage. Since we use pageContext.setDocumentRendered(false); and response.getOutputStream().flush(); methods, the HttpResponse is already committed.
Hence, the page does not redirect to another page as Request is processed and Response is complete. In case of methods like setForwardURL A JSP forward redirects the same request object to the target URL.
Can anyone help here to achieve the expected requirement?
Thanks.

Pop up box is not handel in BDC program

hi to all experts,
in tcode ' IP10 ' one pop up box is came in simple processing and recording also. but when i used the system source code in program , this pop up box is not encounter on this conditions. how can i solve this issue.
Help is appriciated.
Regards:
Mahesh

hi,
if the warning message coming in a pop-up window then it can be supressed in the following way.
1. comment the lines of the code of bdc recording of that pop-up screen along with the perform of bdc ok code '=ENTE".
2. use the structure ctu_params and fill the correspondings fiels, particularly the field nobinpt = 'X' and then use this structure in the call transcation statement as
call transcation 'ME11'
using bdcdata
options from opt ( structure of ctu_params )
3. At the time of recording use the option of check box " no batch input session ".
regards,
Alok

Material on dialog programming

Hi al,
does anybody have good material on dialog programming.
SPECIALLY ON TABLE CONTROL
THANKS

Hi
Go thru this docu
 TRANSACTIONS
TABLE OF CONTENTS
TABLE OF CONTENTS 2
GENERAL INTRODUCTION TO TRANSACTION 5
Logical Unit of Work (LUW) 5
DYNPRO concept 6
SCREEN PAINTER 7
Using Screen Painter 7
Creating a new Screen 7
Designing of Screen 8
Selecting Screen Fields 9
Attributes of Screen Elements 9
Field List 10
Screen Flow Logic 10
MODULE POOL PROGRAMMING 12
Creation of Module Pool Program 12
Communication between Dynpro and Module Program 12
CREATION OF A COMPLETE TRANSACTION 12
Steps involved to create a complete transaction 12
Handling Function Code 13
THE FIELD CHECKS 14
Automatic Field Checks 14
About at Exit Command 15
In module pool program. 15
Flow Logic Validations 16
Module assign. 16
Module Pool Program Validations 17
DYNAMICALLY CALLING THE SCREENS 19
About Displaying Next Screen 19
Set Screen 20
Call Screen 20
Leave to screen 21
SUBSCREENS 22
TABLE CONTROLS 23
Features of Table Controls 23
Declaring of Table Control in the Module Pool Program 24
Designing Table Control on Screen 24
Passing data to Table Control 24
STEP LOOPS 27
Types of Step Loops 27
Switching To List Mode 28
Returning back from LIST mode 28
Process on HELP-REQUEST event 29
Value Request 30
THE SCREEN DISPLAYED IS POP-UP SCREEN AND CODE FOR THE FLOW LOGIC AND MODULE IS WRITTEN BELOW: 32
Need To Change Screen 34
Modifying the screen 34
Field Name Length Description 34
MODULE MODIFY_SCREEN. 35
LOOP AT SCREEN. 35
ENDMODULE.WORKING WITH MATCHCODE OBJECTS 35
WORKING WITH MATCHCODE OBJECTS 36
Creating Matchcode object 36
Creating Matchcode ids. 37
Using Matchcode 38
Creating Lock Objects 39
Activation of Lock Object 40
 GENERAL INTRODUCTION TO TRANSACTION
Transaction, in R/3 system is an operation that lets the user make necessary changes to the database. The entire R/3 system is nothing but set of business transaction. The data transfer from old system to SAP R/3 database, or modifying data, or deleting data, which is not required, is done through transaction.
For SAP system, Transaction is nothing but sequence of steps called as dialog steps and for user it is sequence of screens that appears one after the other depending upon the option he selects. The special transaction monitor called the SAP dispatcher handles the sequence of steps that takes place in any transaction. The main task of transaction is to update database table. The database table is not updated until a transaction is completed. All changes can be rolled back if the transaction has not finished.
The transaction contains two steps which are as following:
 Interactive phase: In this step, user enters the data, which needs to be inserted or deleted or modified on to the screen. There can be single screen or multiple screens depending upon the transaction. So this step can consist of single step or multiple steps. In this phase you prepare database record.
 Update phase: This phase processes the database record and updates the database table. Actual updating of database table takes place in this phase.
All the transactions are associated with transaction code. And all these codes are stored in a table TSTC.
Logical Unit of Work (LUW)
The R/3 system is multi user system and many users access the same information at the same time, which is mainly DATA. Consider the case where one user is modifying a record, and second user is trying to delete the same record. If the second user is successful in deleting the record then the first user will face problem for modifying the record that is already deleted. The avoid such situation, R/3 system has provided Logical Unit of Work, which is defined as a locking mechanism to protect transaction integrity. Of course, there are other measures, which ensures data integrity like check table i.e. foreign key relationship. Within SAP system there are three types of transaction and may be distinguished as:
 Database transaction known as LUW. It can be defined as a period in which operation requested must be performed as a unit, i.e. all or nothing operation. At the end of LUW, either of the database changes are committed or rolled back.
 Update transaction or SAP LUW. One SAP LUW can have several databases LUW. So a set of a database is either committed or rolled back. The special ABAP/4 command COMMIT WORK, marks the end of a SAP LUW.
 ABAP/4 transaction. Is made up of a set of related task combined under one transaction code. ABAP/4 transactions are for programming environment, in which ABAP/4 transaction functions like one complete object containing screens, menus and transaction codes.
R/3 system has provided in built locking mechanism, which defines the Logical Unit of Work. Also user can set his own locking mechanism. The LUW starts when a lock entry in the system table is created, and it ends when the lock is released.
To provide the user the facility to communicate with the table in order to modify or delete or insert data, R/3 has provided tool called SCREEN PAINTER. This tool allows you to design screen, process screen through program and update the database table. SAP has provided one and only one way to update the database table, i.e. transaction. Though you can update database table by using open SQL statement through program, SAP usually doesnt recommend this kind of updating. Many standard transactions are available to update standard table but if the need arises, the developer should be able to develop new transaction, which allows the updating of database tables. This can be achieved by using various components of screen painter.
Following are the few concepts and steps for creating entire new transaction.
DYNPRO concept
A dynpro refers to the screen + flow logic. With screen painter you can develop screen and flow logic. The relationship between screen, flow logic, and program can be shown as follows:
Dynpro, as figure indicates consist of screen and flow logic and places exactly one call to module pool program. A transaction consists of many screens and for each screen flow logic is attached. When the transaction is executed, the screen places a call to flow logic and flow logic in turn places a call to module pool program.
 A module program is usual ABAP/4 program that consist of modules and data declaration.
 ABAP/4 is an event driven language. In module pool program too, events get triggered and these events are handled in flow logic. Flow logic editor is subset of ABAP/4 editor. The system automatically displays the two important events for the flow logic.
 Screen is the important component of dynpro and can be created, designed by screen painter.
Screen Painter
A screen painter can be started by
Development workbench  Screen Painter
Or
SE51 transaction code.
Using Screen Painter
The process of creating a dynpro includes the creation and definition of all the needed screen components.
The steps involved in creating the dynpro are as follows:
 Create screen and attributes by using screen attribute screen.
 Select and place the needed fields within the screen by using dict/program fields.
 Establish the field attributes to which the screen belongs by using field list.
 Define the flow logic respect to the transaction to which it belongs by using flow logic.
Creating a new Screen
Steps involved are as follows:
 Enter the name of program and number of the screen
 Click on Create
 On screen attribute screen enter short description
 Enter screen type. Normally, you select NORMAL option for usual R/3 screen. Other options available are SUBSCREEN & MODAL DIALOG BOX. Modal dialog box is used to establish independent and interactive dialog box while subscreen is screen within screen.
 Next attribute to be passed is NEXT SCREEN. Here you need to specify the next screen number, which must be processed after the current one.
Designing of Screen
Screen can be designed by using FULL SCREEN EDITOR. You can go to full screen editor.
From screen attribute screen
By pressing full screen editor pushbutton
Or
From initial screen of screen painter.
There are two modes available with full screen editor.
 Graphical mode. The graphical mode works similarly to typical window application.
 Alphanumeric mode (rarely used).
Elements of screen
 Text Standard text or field labels.
 Entry - display field.
 Radiobutton All radiobutton must be associated with one group.
 Checkbox Normally used for YES/NO operations.
 Pushbutton Used for activating particular function.
 Boxes grouping together many screen elements.
 Subscreens This is a screen area in which you can display another screen.
 Table controls This area of screen is similar to table but should be treated as a loop.
 Status - Display output fields containing icon.
All these elements are on the control bar of full screen editor and can be placed on the screen work area by clicking and placing them wherever needed.
Selecting Screen Fields
Screen field can be either dictionary objects or program fields. Steps involved in the placing of fields on the screen are as follows:
Click the pushbutton Dict/program fields on the full screen editor
Or
Goto  dict/prog fields.
 Enter table name.
 Click Get from dictionary.
 Select fields.
 Click copy pushbutton.
 Position the cursor where you want those fields to be placed.
To adjust various screen elements, you can use drag and drop facility for screen elements.
Attributes of Screen Elements
The entire element of a screen has some attributes, which determines their behavior.
 General These attributes are directly managed by the screen painter like name of the element, or text of element or column width and various things associated with the screen.
 Dictionary These attributes are applicable to fields, which are from dictionary. Various components of dictionary can be attached to this element like search help, foreign key.
 Program.
 Display Behavior of the element with respect to their display feature.
Attribute dialog box can be displayed by
 Clicking on the ATTRIBUTE push button on the application tool bar.
 Double clicking on the element.
Field List
This list displays a list of all screen elements together with their screen attributes. One important element of Field list is OKCODE. Any pushbutton is associated with function code as in menu item in menu painter. When the user clicks the pushbutton this code is stored in OKCODE. This OKCODE is created by system without a name and is not visible on the screen. In ABAP/4 this field is work field and is nothing but an area wherein system stores the variable and is the last field of the field list and is invisible, hence user needs to give the name OKCODE. It is not mandatory to give the name OKCODE; developer can give any name to this field.
Screen Flow Logic
You can go to this screen either by
Initial screen of Screen painter  Flow logic
Or
From Screen attribute screen  Flow logic
When transaction is executed, the screen is displayed, user enters few fields, selects few functions. Later the screen is processed and processing of screen is done by flow logic. The events that are associated with screen are as follows:
 Process before Output (PBO)
 Process after input (PAI)
 Process on value request (POV)
 Process on help request (POH)
The system automatically displays two very important events or modules in flow logic i.e. PAI and PBO
PBO event
This event is triggered before the screen is displayed. The processing of screen before the display of screen is done in this event. For example, filling in default values in the screen fields.
PAI event
This event is responsible for processing of screen after the user enters the data and clicks the pushbutton. The processing of screen can include displaying another screen, or just displaying list or quitting the transaction itself and many more things. Usually it is displaying another screen. These operations can be carried out in the PAI event. OKCODE plays an important role in this operation.
POV event
Process on value request is triggered when the user clicks F4 key. You can handle this event when the user presses F4 key by writing code for the same in module pool program. Normally when the user presses F4, list of possible values is displayed. The standard list produced by system is adequate for applications you develop yourself. However, you can also have the option of setting up your own documentation and lists of possible values that are more detailed.
POH event
Normally when the user places the cursor on the field and presses F1 function key, the system displays its own Help for that particular field. You can add your own functionality to the Help button by writing code for the same in the POH event.
Module Pool Programming
This component though is not attached to the screen painter, plays important role in transaction. Normally, for reports, on line executable programs are written but for transaction, Module Pool Programs are written. The module pool program contains only modules to handle various events associated with screen and data declaration statements.
System divides the module pool program into several include program. These are global field, PBO modules, and PAI modules. It is entirely users decision whether to use these modules or write directly into main program.
Creation of Module Pool Program
You can create module pool program either through
Object browser
System automatically creates the module pool program and for these program which are created through object browser, system creates the include modules.
Or
ABAP/4 editor
It is similar to normal program creation. Type of program should be given M and is not created by system.
Communication between Dynpro and Module Program
For each screen, the system executes the flow logic, which contains corresponding events. The control is passed to Module Pool Program. Module Pool Program handles the code for these events and again passes back control to the flow logic and finally to screen. Unlike on line program, in this case, the control remains with flow logic. The switching of control between flow logic and module pool program and back is common process when user executes transaction.
Creation of a Complete Transaction
Steps involved to create a complete transaction
 Create module pool program.
 From screen painter create screens.
 Write flow logic for each screen.
 Write code for all the events in module pool program.
 Check for any error in screen and flow logic.
 Generate each and every component of screen i.e. flow logic and screen.
 Single screen can be tested using Screen Painter.
 Create transaction code through object browser.
 Generate the transaction code.
 User can execute the transaction by entering the transaction code in the command field.
Handling Function Code
The function code or OKCODE is the last field of Field list. Function code can be handled as follows:
During the Designing of the screen, a function code is assigned to pushbutton.
 In field list, developer needs to specify OKCODE as last field.
 In module program it is a global field and can be evaluated in the PAI event.
 A function code is treated in the same way, regardless it comes from pushbutton, menu item or any other GUI element.
A complete example for transaction is shown below:
If you have a screen like the one below:
When the user clicks on the Display button, you want to display details of sflight, with corresponding carrid and connid (which is entered by the user).
Module pool program to handle this particular screen is as follows:
Program YVTEST7.
TABLES: SFLIGHT.
DATA: OKCODE (4).
MODULE INPUT1 INPUT,
CASE OKCODE.
 WHEN DISP.
 SELECT * FROM SFLIGHT
 WHERE CARRID = SFLIGHT CARRID AND
 CONNID = SFLIGHT CONNID.
 ENDSELECT.
 LEAVE TO SCREEN 200.
 WHEN EXIT. LEAVE TO SCREEN 0.
ENDCASE.
ENDMODULE. INPUT1 INPUT
MODULE USER_COMMAND_0200 INPUT.
CASE OKCODE.
WHEN BACK. LEAVE TO SCREEN 100.
ENDCASE.
ENDMODULE. USER_COMMAND_0200 INPUT
When the user clicks on display, control is transferred to screen no. 200 on which you display sflight details & on the same screen, when user clicks on BACK button, he comes back to main screen.
Flow logic for screen 100 is as follows:
PROCESS AFTER INPUT.
MODULE INPUT.
Flow logic for screen 200
PROCESS AFTER INPUT.
USER_COMMAND_0200.
MODULES: Modules are handled in module pool program.
You need to write flow logic for screen 200 and design screen 200.
In case of transaction transfer of data from program to screen is automatic i.e. you need not transfer the data from program to screen explicitly. The fields, which you define in the screen receives the data from program and displays the same.
The Field Checks
As already mentioned Transaction is the only method, which SAP recommends to update the database tables. Data entered in the database table should be valid and correct. Data entered is validated at each and every point. ABAP/4 offers various methods to validate data and those are as follows:
 Automatic field checks
 Checks performed in the flow logic
 Checks performed in the ABAP/4 module pool program
Automatic Field Checks
These checks are based on the field information stored in the dictionary. These checks are performed by the system automatically when the user enters the data for the screen field. System performs these checks before PAI event is triggered. Types of field checks performed by system are as follows:
 Required input
While designing the screen, for particular screen field if you click the Req. Entry checkbox, the field becomes mandatory. When the transaction is executed if user leaves this particular field blank, the system displays error message. User cannot proceed until the user enters some data.
 Proper Data Format
Each field has its own data format whether it is table field or screen field. Whenever data is entered, system checks for the proper format of the data. For example date. Each user has its own format for date, which is defined in the user master record. If the date defined in the user master record is in the format DD/MM/YYYY, if the user enters the date, say, in YY/DD/MM, the user displays the error message. System also checks for the value of month or days. For example if month entered is greater than twelve then the error message is displayed.
 Valid Value for the Field
In data dictionary two tables are related by Primary key-Foreign key relationship. Whenever the user enters the data, the system checks for the check table values. Also in Domain, if you have fixed values, then the system checks for these values.
Automatic field checks are repeated each time the user enters the data.
About at Exit Command
Automatic field checks can be avoided by AT EXIT-COMMAND, which works exactly the same way as Cancel works on application tools bar. In the R/3 screen, if you want to quit the processing of that particular screen without entering the mandatory fields, user can click the Cancel button. Same functionality can be incorporated in the user-defined transaction by using AT EXIT-COMMAND. This module can be called before the system executes the automatic field checks and it goes without saying that before PAI event. Code for AT EXIT-COMMAND in flow logic and in module pool program can be written as follows:
In Flow Logic
Process After Input.
Module exit AT EXIT-COMMAND.
 In module pool program.
Module exit.
Case okcode.
When Exit.
Leave to screen 0.
To achieve this kind of functionality a pushbutton or menu item should be assigned a function type E. It tells the system to process this particular module before carrying out any field checks.
Flow Logic Validations
Consider the case where you want user to enter only LH and SQ for sflight-carrid. In this case, you are restricting value of a screen field. This cannot be achieved by automatic field check. Hence there is a need of additional validation. It can be done in flow logic by using following statement:
Field -
Values
Syntax
PAI.
Field sflight-carrid values (LH).
For multiple values
PAI.
Field sflight-carrid values (LH SQ).
Field sflight-price values (between 1000 and 2000).
In this case when the user enters the value, PAI is triggered and field is checked for that particular value. If the value entered happens to be wrong, that field is enabled for user to enter. If you have multiple Field statements in your flow logic, it is sequential execution.
Consider the following case:
PAI.
Module assign.
Field sflight-carrid values (LH SQ).
In ABAP/4
Module assign.
Data: carrid1 like sflight-carrid.
Carrid1 = sflight-carrid.
Endmodule.
In this case, Sflight-carrid is used in the flow logic before the field statement. The system will give invalid value or some previous value as the field sflight-carrid is used in module before it is checked i.e., field statement is after the module in which sflight-carrid is being used. The field is not available to the system unless it executes the field statement. Field statement transfers the values to the program and is done only once. If you dont have Field statement in your flow logic, transfer of values takes place in PAI event.
Consider one more case where you have multiple field statement.
PAI.
Field Sflight-carrid values (LH).
Field Sflight-connid values (0400 0500).
In this case if the user enters only carrid wrong, then this particular field is enabled and rest of the fields are disabled for user to input. Many times if the user enters wrong value for one field, then you might want to give option to user to enter all the fields, which is not possible by using Field statement only. This functionality can be achieved by CHAIN ENDCHAIN.
Syntax
Chain.
Field sflight-carrid value (LH).
 Field sflight-connid values (between 200 and 500).
Endchain.
Field sflight-price values (100 1000).
In this case, if the user enters wrong value only for carrid, both the fields i.e. carrid and connid are enabled as they are grouped together in the Chain statement. The field price will be disabled for input. Usually, logically related fields are grouped together with Chain-Endchain statement.
Module Pool Program Validations
Checking fields ABAP/4 program includes
 Field statement in flow logic.
 Module statement in ABAP/4 module pool Program.
Syntax
PAI.
Field sflight-carrid module <name>.
This module can be handled in the main program i.e. module pool program.
In ABAP/4 program
Module Check.
Select single * from sflight where carrid = sflight-carrid.
If sy-subrc ne 0.
 Message e001.
Endif.
In this case, field sflight-carrid is checked in the table for its existence.
Dynamically Calling the Screens
About Displaying Next Screen
Transaction is a sequence of screens, which are displayed one after the other. The next screen displayed depends upon the attributes of first screen. In attributes you need to give Next Screen number i.e. if next screen displayed should be 200 screen, then this number should be given in next Screen attributes. These are static attributes of the screen. By default, if nothing is specified in the program, the system branches out to the screen number, which is specified in the attribute screen.
But this doesnt happen always. If you have many pushbuttons on the screen like the one in the following case:
In this case, if user selects MARA pushbutton, then fields from Mara table are displayed. When the user clicks on the MARD, then the fields from MARD table are displayed. Depending upon users selection, the screen is branched out and this has to be done during runtime. This functionality can be achieved by dynamically calling the screen in module pool program.
The screen can branch out to new screen depending upon user selection. Following command in module pool program can do this:
 SET SCREEM
 CALL SCREEN
 LEAVE TO SCREEN <NUMBER>
All these commands override the specifications given in the attributes. This overriding is temporary. The values stored in the attribute are not changed.
Set Screen
Syntax
Set screen <number>.
In module pool program
Case okcode.
 When DISP.
 Set screen 200.
 When LIST.
 Set screen 300.
Endcase.
In this case, the entire processing of current screen takes place and then the system branches out to next screen. If you want to branch out to the next screen without processing the current screen, LEAVE SCREEN should be used along with the SET SCREEN.
For Example:
Case okcode..
 When DISP.
 Set screen 200.
 Leave Screen.
 When LIST.
 Set screen 300.
 Leave Screen.
Endcase.
When SET SCREEN is used, control cannot be transferred to the main screen or previous screen, unless you write code for the same.
Call Screen
Usually used for pop up screens. Many times, there is a need for user to enter additional information or secondary information on another screen or pop up screen. Once the user enters the data, he should be able to go back to main screen or to the screen where he started. This is not possible by using SET SCREEN. CALL SCREEN achieves this functionality.
Syntax
Call Screen 200.
Will simply call a screen number 200 from a main screen. Once the screen is displayed the user can enter all the data and return to the main screen by clicking BACK button.
To call screen as pop up screen the syntax is
Call screen starting at <col.no.> <line no>
 Ending at <col no> <line no>.
In this case window will be popped as window and user can close it by using BACK button.
Leave to screen
To SET a new screen without processing current screen, you need to use the following two statements together:
SET SCREEN 200.
LEAVE SCREEN.
Or a Single statement
LEAVE TO SCREEN 200.
Subscreens
A subscreen is a screen within screen. Consider the following case.
If user clicks on FIRST pushbutton, you want to display details of MARA table and if user clicks on the SECOND pushbutton, you want to display details of MARD table. You can do this by calling two different screens. But the information will be displayed on the next screen. Displaying data on the same screen is possible by using SUBSCREENS.
Step to create a subscreen are as follows:
 Create a subscreen area on MAIN screen and name it.
 Create a separate screen of subscreen type.
 Arrange the fields on this screen so that they fit in subscreen area exactly. Only when it is larger, the part of the screen that fits in the main area will be visible.
 Write code for calling subscreen in flow logic.
To call subscreen, from your flow logic, you need to include the statement both in PAI and PBO.
Syntax
PBO.
Call subscreen <area> including <prg name> <screen no>.
PAI.
Call subscreen <area>.
Area - is the name of the area on main screen.
Prg. Name - is the name of the module pool program.
Screen number - is subscreen screen number.
Some of the donts with subscreen are:
GUI status cannot be set to the subscreen
 OKCODE is not applicable to the subscreen.
 Subscreen cannot call another screen.
 It cannot contain AT EXIT-COMMAND.
You can call multiple subscreen in the same area (at any given point of time, only one subscreen can be called in the subscreen area) and is done dynamically during runtime by using variable screen number.
Table Controls
A table can be created in transaction. These tables when designed on the screen are called as SCREEN TABLES. These screen tables are of two types viz.
 Table controls
 Step loops
Though these are tables when code is written to handle them, the tables are treated as loops.
Features of Table Controls
 Data is displayed in the form of table when many records match the criteria.
 Table control gives user the feeling of an actual table.
 You can scroll through the table vertically and horizontally.
 You can select rows and columns
 Resize the width of a column
 You can have separator lines in between rows and columns
 Automatic resizing of the table when the user resizes the window.
In general table control includes all the features of an actual table and user gets the feeling that he is actually working with table. You can update information in table control and it can be updated in the database table by writing code for it.
Steps associated for creating complete screen table are as follows:
 Declaration of table control in module pool program.
 Designing of table control on the screen.
 Passing data to table in flow logic.
Declaring of Table Control in the Module Pool Program
Syntax
Controls TCI type Tableview using screen <screen no.>
When you use table control in a screen you must declare the structure in module pool program. Important fields of tableview are as follows:
 Lines number of displayable rows in a table.
 Top_line the row of table where the screen displays start.
 Current_line The row currently being processed inside a loop.
When you process the table control in flow logic depending upon where you want to start display of rows, you need to use these variables.
Designing Table Control on Screen
 To design table control on the screen, you need to click on Table in control bar and place it on the screen. You can adjust the length and width of table control.
 Name the table control. (Here you need to use same name which you have used for declaration of table control in module pool program)
 From dictionary object, select table fields and place them in the table control.
Passing data to Table Control
As already mentioned, table controls are tables but are treated like loops. Usually transfer of data from program to screen is automatic. But in case of table control, transfer of data is not automatic. You need to explicitly transfer the data to table control. ABAP/4 provides loop statement, which is associated with flow logic to transfer the data. Because table control is treated like a loop, data from where it is transferred should be a loop. You cannot transfer the data by only select statement; you need to put the data into internal table. ABAP/4 provides the LOOP statement, which is associated with the flow logic and allows you to loop through the table control and internal tables. In between LOOP-ENDLOOP, you can use most of the flow logic keywords like field values. Module etc.
You need to code a LOOP statement in both PBO and PAI event of the screen. With LOOP statement, you can transfer the data from program to table control and vice versa. That is, if user updates the value in the table control, you can update database table with its value. And this can be done in PAI event. So even if you are not updating database table through the table control, you need to put the LOOP statement in the PAI event also.
Syntax
PBO.
LOOP AT <internal table> with control <table control name> cursor <scroll variable>
PAI.
Loop at itab.
Proper usage of Table Control is as follows:
In flow logic.
PBO.
LOOP AT ITAB WITH CONTROL TC1 CURSOR TC1-TOP_LINE.
MODULE ASSIGN.
ENDLOOP.
PAI.
LOOP AT ITAB.
ENDLOOP.
Considering, we have following fields in table control and the screen looks like this:
In module pool program
CONTROL TC1 Type tableview using screen 200.
Module assign.
Sflight carrid = itab carrid.
Sflight - connid= itab - connid.
Sflight - fldate= itab fldate.
Endmodule.
The transfer of the data from program to table control takes place in steps and these steps are as follows:
 With LOOP AT statement the first row is picked up and placed in the header of the internal table.
 Whatever statements you have in between LOOP-ENDLOOP are executed. In this case, you have Module statement. In Module statement, value of internal table is assigned to table control field.
 The row in internal table is transferred to the first line of the table control as stated in the LOOP AT statement.
 The system encounters the ENDLOOP statement and Control is passed to the next line of the internal table.
 In the same way, all the records of the internal table are passed to the table control.
STEP LOOPS
Step Loops are type of screen table as already mentioned. Step loops are repeated blocks of field in a screen. Each block contains one or more fields and these blocks are repeated. Step loops arent like actual table. You can scroll vertically but not horizontally. Three steps are associated with creation of step loops:
 Creation of step loops on screen, which includes declaring fields on the screen and then defining the step, loops for these fields.
 Passing data to the step loop is exactly similar to the passing of data to table controls.
 In step loop, you dont need to define the step loop as such in the module pool program but the cursor needs to be defined in the program.
Types of Step Loops
 Static Static Step Loop (SSL) have fixed size that cannot be changed during the runtime. If user resizes the window, the size of the static step loop is not changed.
 Dynamic Dynamic Step Loop (DSL) is variable in size. When the user resizes the window, the system increases or decreases the number of the step loop blocks.
You can have only one dynamic step loop and can have as many static loops in your transaction.
Programming with the Static and dynamic step loop is exactly same. For the system or for the user it doesnt make any difference whether it is static or dynamic step loop. Only attribute, which you fix during designing of the step loop, is type attribute for step loop F for fixed i.e static and V for variable i.e. dynamic.
Writing code for Step Loop in the flow logic.
 PBO.
 Loop at itab cursor cl.
 Module set.
 Endloop.
 PAI.
 Loop at itab.
 Endloop.
Empty loop is must for both table control and step loop
LOOP AT statement for step loops and Table controls is similar. Loop At statement transfers the data to screen table. You need to have the Module to assign the values for the screen table.
In module pool program you need to define the cursor.
Date: CL TYPE i.
Cursor parameter tells which line of step loop display should start.
Module Set in module pool program assigns the values to step loop fields, which is similar to table controls.
Branching to List Processing
Switching To List Mode
You can display a list within a transaction.
You can produce a list from module pool program by using the command
Leave to List-Processing.
This statement switches the system from dialog mode to list mode. And from this point onwards until you return to dialog mode, you can use all the normal report statement like write, select or any other event.
Returning back from LIST mode
You can return back to dialog mode by clicking the BACK button.
You can have your GUI status and write code for the same. You can include the command LEAVE LIST-PROCESSING. When the system reaches this command, it leaves the list mode and returns to the dialog mode.
Help & Value Request
In any transaction, When the user presses F1 or ? on a field, System provides the help facility for that particular field. In dialog program, when F1 is pressed, help provided by R3 system is sourced from data element documentation. If this documentation is not present for that particular field or if user needs to display additional information for that particular field, then user defined help can be provided through PROCESS ON HELP REQUEST.
In ABVP/4 help can be provided to the user by:
Data element documentation: The F1 help can be enhanced, by adding an additional text for the data element in ABAP/4 dictionary.
It can be done with the help of following steps:
Place cursor on the screen field,
GOTO  DOCUMENTATION  DATA ELEMENT DOCUMENT
You can now extend the existing help.
USING THE PROCESS ON HELP-REQUEST.
If you dont have this event in a program, then the documentation of the field in the ABAP/4 dictionary is taken into consideration. If this event exits in the program then it is executed.
Process on HELP-REQUEST event
This event is triggered when user presses F1 on a screen field. You need to handle this event in flow-logic by specifying the fields and attaching the module to it.
Syntax
PROCESS ON HELP REQUEST.
FIELD SFLIGHT-CARRID MODULE HELP-FOR-CARRID.
In module pool program
MODULE HELP.
Write : `This is field is from sflight table
Write : / It is of four Character.
ENDMODULE.
When the user presses F1 on this particular field, then this message will be displayed on the screen.
Value Request
Whenever the user presses F4 on the screen field list of possible values, particular fields are displayed. If the standard value-help is inadequate or if you want to display additional fields or with different combination of fields, developer can program this in PROCESS ON VALUE-REQUEST event in the flow-logic and subsequent module in the module pool program. When the user presses F4, list of possible values are displayed either from matchcode objects or check table or help view or domain. Each one of them is explained briefly.
Matchcode objects: Are aggregated dictionary objects and detailed procedure to create these objects is explained in the later part of the material.
Check Table: If a check table is assigned to the table field and if the user presses F4 for that particular field, then all the key fields are displayed.
Domain Values: The values defined in the domain are displayed. These values are set in domain when the domain is created in the dictionary.
Help views: In cases where the check table is not sufficient, you can create a help view with this check table, which gives additional information like explanatory text for the fields of the check table.
PROCESS ON VALUE_REQUEST.
Each time the user presses F4 on the screen field, following algorithm is called internally.
When the user presses F4 on flight number, the following screen is displayed.
The screen displayed is pop-up screen and code for the flow logic and module is written below:
Flow-logic code

Using CheckBox / Radio-Button Control in Dialog Program

Dear Friends,
Please let me know the way to use check-box / radio-button control in dialog programs. Where & how to define them & write the logic.
If possible provide a small example.
Regards,
Alok.

Hi,
goto tcode abapdocu.. abap user dialogs - screens-processing screens you will get examples for all --pushbutt6ons radiobutton checkboxes everything
here is a sample code for you
PROGRAM demo_dynpro_check_radio .
DATA: radio1(1) TYPE c, radio2(1) TYPE c, radio3(1) TYPE c,
 field1(10) TYPE c, field2(10) TYPE c, field3(10) TYPE c,
 box TYPE c.
DATA: ok_code TYPE sy-ucomm,
 save_ok TYPE sy-ucomm.
CALL SCREEN 100.
MODULE user_command_0100 INPUT.
save_ok = ok_code.
CLEAR ok_code.
CASE save_ok.
 WHEN 'RADIO'.
 IF radio1 = 'X'.
 field1 = 'Selected!'.
 CLEAR: field2, field3.
 ELSEIF radio2 = 'X'.
 field2 = 'Selected!'.
 CLEAR: field1, field3.
 ELSEIF radio3 = 'X'.
 field3 = 'Selected!'.
 CLEAR: field1, field2.
 ENDIF.
 WHEN 'CANCEL'.
 LEAVE PROGRAM.
ENDCASE.
ENDMODULE.
flow logic:
PROCESS BEFORE OUTPUT.
PROCESS AFTER INPUT.
MODULE user_command_0100.
regards,
pankaj singh.

reward if helpful

Can we show the applet in a pop-up box

Two questions:
1. Closing the applet:
In my applet, I want to enable the user to enter new text. There is a button that once pressed should cause the Aplet to disappear!! I call stop() on the applet once the button is pressed in ActionPerformed(after doing some checking) but the browser screen with Applet stays on the screen.
2. I would like to open the applet in a box in the middle of the screen instead of it opening in the browser widnow (replacing what was there). Can I do that? and I would want the pop up to disappear once I am done!
Thanks a lot
merdaad

Your Applet is embedded in the web page and the only way I know of to make it disappear is to move to another page.
One workaround would be to make the Appet invisible - set it to 0 x 0 or to the same background colour as the HTML background. From your Applet pop up a new Dialog containing the necessary field buttons etc which you can dispose of when a button is clicked.
Or, why not pop up your Applet in a new browser window with no toolbars, menus, address bars etc. Set the new window margins to 0 all round and set the window to appear in the centre of the screen and to be the same size as your Applet and your Applet. will look like it running in its own window rather than IE . You can do this with a bit of javascript on your main HTML page. Search on google for lots of examples. To close this on a button click you can maybe use some Java - Javascript communication. Search these forums for some examples.
A couple of ideas that should get you started.

Pop-up box in dialog programming

Similar Messages

Maybe you are looking for