Sample basic program 4 dialog programming

hi
can any one send me the sample code 4 simple dialog programming....

Hi Sandy,
Simple Dialog Programming:
PROCESS BEFORE OUTPUT.
MODULE 0250_STATUS.
LOOP.
MODULE STATUS_0120.
ENDLOOP.
LOOP.
MODULE STATUS_0110.
ENDLOOP.
LOOP.
MODULE STATUS_0100.
ENDLOOP.
PROCESS AFTER INPUT.
MODULE REFRESH_0250.
LOOP.
MODULE USER_COMMAND_0120.
ENDLOOP.
LOOP.
MODULE USER_COMMAND_0110.
ENDLOOP.
For example, if the user enter the Delete Screen, you will make all the Fields non-Editable.
*& Module 0250_STATUS OUTPUT
text *
MODULE 0250_STATUS OUTPUT.
SET PF-STATUS 'Z250'.
SET TITLEBAR 'Z250'.
IF OKSAVE = 'DEL'.
Make the SAVE Menu button inactive
SET PF-STATUS 'Z250' EXCLUDING 'SAVE'.
Make all the Fields non-Editable
LOOP AT SCREEN.
SCREEN-INPUT = 0.
MODIFY SCREEN.
ENDLOOP.
ENDIF.
For example, if the user enter the Modify Screen, you will make all the Fields Group 1 that
have a 'M' non-Editable.
You specify the 'M' for Group 1 using the Screen Painter Attribute
IF OKSAVE = 'MOD'.
Make the DELE Menu button inactive
SET PF-STATUS 'Z250' EXCLUDING 'DELE'.
Make all the Fields Groups 'M' non-Editable
LOOP AT SCREEN.
check screen-group1 = 'M'.
SCREEN-INPUT = 0.
MODIFY SCREEN.
ENDLOOP.
ENDIF.
CLEAR OKCODE.
ENDMODULE.
Regards,
Priyanka.

Similar Messages

Beginning Dialog Programming

Dear Friends,
I want to begin with dialog programming in ABAP. So, please tell me how to start & where to look out for the good examples. Please tell me about the examples in IDES also.
Bye,
Nishant

Nishant,
I found the book 'ABAP/4 Programming the SAP R/3 System' critical to my success when I started learning Dialog Programming 2 years ago.
This book covers other issues as well, but there are a 120 pages devoted to the basics of Dialog Programming.
It also covers ABAP Objects, reports, interactive reports, and building all types of dictionary objects.
http://tinyurl.com/9a6t4
Make sure to get 2nd Edition.
Hope this helps,
Brett

Basic Dialog Programming

Hello Everybody and hello World.
I would like to know how to do a basic dialog programming..
Can anyone help me?Please....
give me some advice....Im very eager to learn that dialog programming
Thanks in advance
aVaDuDz

hi
INTRODUCTION TO DIALOG PROGRAMMING
OVERVIEW
There are programs in every domain that require certain amount of user interaction .Such requirements in ABAP are fulfilled with the help of a user dialog and dialog programming which encapsulates the entire logic pertaining to the required user dialog.
One needs to take care that user interactions with the system are comfortable and user friendly along with being logically coherent.

What is a user dialog?
Any kind of user interaction with the system can be called as a user dialog:
1) Entering data on the screen.
2) Clicking a button.
3) Navigation between screens.
Need of dialog programming
In a typical dialog, the system displays a screen on which the user can enter or request information. As a reaction on the user input or request, the program executes the appropriate actions: it branches to the next screen, displays an output, or changes the database.
Example
A travel agent wants to book a flight. The agent enters the corresponding data on the screen. The system either confirms the desired request, that is, the agent can book the flight and the customer travels on the desired day on the reserved seat to the chosen destination, or the system displays the information that the flight is already booked up.
To fulfill such requirements, a dialog program must offer:
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.
ABAP/4 offers a variety of tools and language elements to meet the requirements stated above in the dialog programs.
Why dialog programming is also known as module pool?
Dialog Programming consists of screens and corresponding ABAP program. Screens call dialog modules in the associated ABAP program from their flow logic. Type M programs serve principally as containers for these dialog modules, and hence dialog programming is also known as module pools. A module pool program is a program type which is not executable directly. You can not just run by hitting F8 like a report program. You must tie a transaction code to a screen in order to start the program.
VARIOUS COMPONENTS OF A DIALOG PROGRAM
Unlike report, interface or any conversion development which generally entails the creation of one autonomous program which can be executed independently of other objects, dialog program development entails development of multiple objects none of which can be executed on its own. Instead all objects are linked hierarchically to the main program and are executed in a sequence dictated by the Dialog Main Program.
Components of a dialog program
1) Transaction
2) Screen
3) GUI status
4) ABAP program
All these components are explained in detail below.
1) TRANSACTION :
The transaction starts a screen sequence. You create transaction codes in the Repository Browser in the ABAP Workbench or using Transaction SE93. A transaction code is linked to an ABAP program and an initial screen. As well as using a transaction code, you can start a screen sequence from any ABAP program using the CALL SCREEN statement.
2) SCREEN
As a user of an R/3 system, one is always confronted with screens. From the moment one logs on, one can see a screen and one must perform actions on this screen. All those screens are components of ABAP programs. Generally, we define the screens of an ABAP program with the Screen Painter tool of the ABAP.
In the R/3 system, screens are program objects that consist of two parts. First, they have a layout that defines the front end appearance of the window that is presented to the user. Second, they have a flow logic that is executed on the backend by the application server. The screen flow logic is a program layer between the front end and the actual ABAP application program at the backend. The language used to program screen flow logic has a similar syntax to ABAP, but is not part of ABAP itself. Unlike ABAP programs, the screen flow logic contains no explicit data declarations. You define the screen fields by placing elements on the screen mask instead. When you define screen fields by referring to data types in the ABAP Dictionary, the runtime environment automatically creates dialogs for field help, input help, and error handling that depends on the semantics of the data type in the dictionary.
The screen flow logic is similar to an ABAP program in that it contains processing blocks. These processing blocks are event blocks that are triggered by the ABAP runtime environment. The most important event blocks are:
PROCESS BEFORE OUTPUT
The respective event (PBO) is triggered after the PROCESS AFTER INPUT (PAI) processing of the previous screen and before the current screen is displayed.
PROCESS AFTER INPUT
The respective event (PAI) is triggered when the user chooses a function on the current screen.
PROCESS ON HELP REQUEST
This event is triggered when function key F1 is pressed.
PROCESS ON VALUE REQUEST
This event is triggered when function key F4 is pressed.
The main task of these processing blocks is to call ABAP dialog modules using the MODULE statement. During the PBO event, you can call any dialog module in the ABAP program that is marked with the addition OUTPUT. In the PAI event, you can call any dialog module program that is marked with the addition INPUT. The screens of an ABAP program can share the dialog modules of that program. You use the dialog modules called during PBO to prepare the screen and the dialog modules called during PAI to react to the user input.
Each screen of an ABAP program has a unique screen number. The screens of an ABAP program can be combined to form screen sequences. Screen sequences are either built statically by setting the following screen in the Screen Painter or dynamically by overriding the static setting in the ABAP program. The last screen of a screen sequence is always the one where the following screen is set to zero.
HANDLING USER INTERACTIONS
A user can interact in various ways with screens. We distinguish between actions that trigger PAI and those that dont. In general, filling input fields with values does not trigger PAI.
Actions that do trigger PAI include:
Choosing a pushbutton on the screen.
Choosing a specially prepared check box or radio button on the screen.
Choosing a function in the menu, standard toolbar, or application toolbar.
Choosing a function key on the keyboard.
ATTRIBUTES OF SCREEN
Like all objects in the R/3 Repository, screens have attributes that both describe them and determine how they behave at runtime. Important screen attributes for ABAP programming:
 Program
The name of the ABAP program (type 1, M, or F) to which the screen belongs.
 Screen number
A four-digit number, unique within the ABAP program that identifies the screen within the program. If your program contains selection screens, remember that selection screens and Screen Painter screens use the same namespace. For example, if you have a program with a standard selection screen, you may not contain any further screens with the number 1000. Lists, on the other hand, have their own namespace.
 Screen type
A normal screen occupies a whole GUI window. Modal dialog boxes only cover a part of a GUI window. Their interface elements are also arranged differently. Selection screens are generated automatically from the definition in the ABAP program. You may not define them using the Screen Painter. A subscreen is a screen that you can display in a subscreen area on a different screen in the same ABAP program.
 Next screen
Statically-defined screen number, specifying the next screen in the sequence. If you enter zero or leave the field blank, you define the current screen as the last in the chain. If the next screen is the same as the current screen, the screen will keep on calling itself. You can override the statically-defined next screen in the ABAP program.
 Cursor position
Static definition of the screen element on which the cursor is positioned when the screen is displayed. By default, the cursor appears on the first input field. You can overwrite the static cursor position dynamically in your ABAP program by using SET CURSOR FIELD <f>
 Screen group
Four-character ID, placed in the system field SY-DYNGR while the screen is being processed. This allows you to assign several screens to a common screen group. You can use this, for example, to modify all of the screens in the group in a uniform way. Screen groups are stored in table TFAWT.
 Hold data
If the user calls the screen more than once during a terminal session, he or she can retain changed data as default values by choosing System -> User profile -> Hold data.
VARIOUS SCREEN ELEMENTS
A screen can contain a wide variety of elements, either for displaying field contents, or for allowing the user to interact with the program (for example, filling out input fields or choosing pushbutton functions). We use the Screen Painter to arrange elements on the screen.
We can use the following elements:
 Text fields
Display elements, which cannot be changed either by the user or by the ABAP program.
 Input/output fields and templates
Used to display data from the ABAP program or for entering data on the screen. Linked to screen fields.
 Dropdown list boxes
Special input/output fields that allow users to choose one entry from a fixed list of possible entries.
 Checkbox elements
Special input/output fields that the user can either select (value X) or deselect (value SPACE). Checkbox elements can be linked with function codes.
 Radio button elements
Special input/output fields that are combined into groups. Within a radio button group, only a single button can be selected at any one time. When the user selects one button, all of the others are automatically deselected. Radio button elements can be linked with function codes.
 Pushbuttons
Elements on the screen that trigger the PAI event of the screen flow logic when chosen by the user. There is a function code attached to each pushbutton, which is passed to the ABAP program when it is chosen.
 Frame
Pure display elements that group together elements on the screen, such as radio button groups.
 Subscreens
Area on the screen in which you can place another screen.
 Table controls
Tabular input/output fields.
 Tab strip controls
Areas on the screen in which you can switch between various pages.
 Custom Controls
Areas on the screen in which you can display controls. Controls are software components of the presentation server.
 Status icons
Display elements, indicating the status of the application program.
 OK field
Every screen has a twenty-character OK_CODE field (also known as the function code field) that is not displayed directly on the screen. User actions that trigger the PAI event also place the corresponding function code into this field, from where it is passed to the ABAP program. You can also use the command field in the standard toolbar to enter the OK field. To be able to use the OK field, you need to assign a name to it.
All screen elements have a set of attributes, some of which are set automatically, others of which have to be specified in the Screen Painter. They determine things such as the layout of the screen elements on the screen. You can set the attributes of screen elements in the Screen Painter - either for a single element, or using the element list, which lists all of the elements belonging to the current screen. Some of the attributes that you set statically in the Screen Painter can be overwritten dynamically in the ABAP program.
 3) GUI STATUS
Each screen has a GUI status. This controls the menu bars, standard toolbar, and application toolbar, with which the user can choose functions in the application. Like screens, GUI statuses are independent components of an ABAP program. You create them in the ABAP Workbench using the Menu Painter.
4) PROGRAM
Each dynpro refers to exactly one ABAP/4 dialog program. Such a dialog program is also called a module pool, since it consists of interactive modules. Each screen and GUI status in the R/3 System belongs to one ABAP program. The ABAP program contains the dialog modules that are called by the screen flow logic, and also process the user input from the GUI status. ABAP programs that use screens are also known as dialog programs.
In a module pool (type M program); the first processing block to be called is always a dialog module. However, you can also use screens in other ABAP programs, such as executable programs or function modules. The first processing block is then called differently; for example, by the runtime environment or a procedure call. The screen sequence is then started using the CALL SCREEN statement.
DATA TRANSFER BETWEEN SCREEN AND ABAP PROGRAM
During PAI, the system automatically transports all screen fields to identically named global ABAP program fields. At the end of the last PBO module, and before the screen is displayed, all of the data is transported from the ABAP program to any identically named fields in the screen. By standard, all screen data is transported immediately before PAI processing starts. But for the dedicated handling of screen fields for example, to carry out an error dialog you can control the moment at which data is passed from screen fields to their corresponding ABAP fields by using the FIELD statement in the screen flow logic.
regards
navjot
reward points if helpfull

What is difference between report programming and dialog programming?

hi,
what is difference between report programming and dialog programming? plz provide some example code
bye

ABAP programming
Basically reports are used to read database and represent the results in lists.
Reports are collections of processing blocks that the system calls depending on events.
We can use reports to evaluate data from database tables.
Reports are stand alone programs and controlled by events.
A report itself never creates events
steps in report:
Processing the selection screen
Reading the database
Evaluating the data and creating lists
Outputting a list.
1st u write simple logics, after that u can enhance the code as step by step.
http://venus.imp.mx/hilario/Libros/TeachYrslfAbap4/index.htm
http://help.sap.com/saphelp_47x200/helpdata/en/d1/802cfc454211d189710000e8322d00/frameset.htm
http://www.sapdev.co.uk/reporting/reportinghome.htm
Dialog Programming
Structure of a Dialog Program
A dialog program consists of the following basic components:
Screens (dynpros)
Each dialog in an SAP system is controlled by dynpros. A dynpro (DYnamic PROgram) consists of a screen and its flow logic and controls exactly one dialog step. The flow logic determines which processing takes place before displaying the screen (PBO-Process Before Output) and after receiving the entries the user made on the screen (PAI-Process After Input).
The screen layout fixed in the Screen Painter determines the positions of input/output fields, text fields, and graphical elements such as radio buttons and checkboxes. In addition, the Menu Painter allows to store menus, icons, pushbuttons, and function keys in one or more GUI statuses. Dynpros and GUI statuses refer to the ABAP/4 program that control the sequence of the dynpros and GUI statuses at runtime.
ABAP/4 module pool
Each dynpro refers to exactly one ABAP/4 dialog program. Such a dialog program is also called a module pool, since it consists of interactive modules. The flow logic of a dynpro contains calls of modules from the corresponding module pool. Interactive modules called at the PBO event are used to prepare the screen template in accordance to the context, for example by setting field contents or by suppressing fields from the display that are not needed. Interactive modules called at the PAI event are used to check the user input and to trigger appropriate dialog steps, such as the update task.
All dynpros to be called from within one transaction refer to a common module pool. The dynpros of a module pool are numbered. By default, the system stores for each dynpro the dynpro to be displayed next. This dynpro sequence or chain can be linear as well as cyclic. From within a dynpro chain, you can even call another dynpro chain and, after processing it, return to the original chain.
Check this link for basics.
http://sap.mis.cmich.edu/sap-abap/abap09/index.htm
Check this link for Dialog Programming/Table Control
http://www.planetsap.com/Tips_and_Tricks.htm#dialog
Check this SAP Help for Dialog Program doc.
http://help.sap.com/saphelp_nw04/helpdata/en/9f/db9cdc35c111d1829f0000e829fbfe/content.htm
Check this SAP Help link for Subscreens.
http://help.sap.com/saphelp_nw70/helpdata/en/9f/dbabfe35c111d1829f0000e829fbfe/content.htm
Check this link for subscreen demo program.
http://abapcode.blogspot.com/2007/05/demo-program-to-create-subscreen-in.html
Also check this link too.
http://abapcode.blogspot.com/2007/06/dialog-programming-faq.html
http://help.sap.com/saphelp_nw04/helpdata/en/9f/db9cdc35c111d1829f0000e829fbfe/frameset.htm
http://sap.mis.cmich.edu/sap-abap/abap09/sld004.htm
http://help.sap.com/saphelp_nw04/helpdata/en/52/670ba2439b11d1896f0000e8322d00/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/52/670c17439b11d1896f0000e8322d00/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/52/670c17439b11d1896f0000e8322d00/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/9f/db9ccf35c111d1829f0000e829fbfe/frameset.htm
http://abapprogramming.blogspot.com/

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

User Authorisations in Dialog Programming.

Hi Friends,
I have a small requirement, I want to create user authorisations in dialog programming.
Actually client requirement is he want to enter absence details of each and every branch.
For that i have created a cusom table and i also i have developed a dialog program inorder to update the details
and to retrive all the data i have created a report program also.
Now the client requirement is he want user authorisations while updating the data through dialog programming, that means if a user loging in that particular branch he want to enter the absence details pertaining to that branch only, when he tries to enter the details of other employee pertaining to another branch an error should be raised.
Actually in the client place they are using authrisation object as 'Z_WERKS'. The basis person has created this and provided for me.
Actually i have created an Authority check in module pool program.Here iam attaching my prog,
Pls provide me the sample code if at all available.
*& Include ZEMPTOP Module pool
PROGRAM ZEMP.
TABLES : ZABS,PA0001.
DATA : WA_PA0001 LIKE PA0001,
 V_ANS.
DATA: BEGIN OF Z_WERKS OCCURS 0,
 PERSA LIKE T500P-PERSA,
 NAME1 LIKE T500P-NAME1,
 END OF Z_WERKS.
*& Include ZEMPI01
*& Module USER_COMMAND_0100 INPUT
 text
MODULE USER_COMMAND_0100 INPUT.
CASE SY-UCOMM.
WHEN 'DISP'.
SELECT SINGLE * FROM ZABS WHERE PERNR = ZABS-PERNR.
IF SY-DBCNT <> 0.
*MESSAGE I000(Z00) WITH 'Details of' ZABS-PERNR .
else.
MESSAGE I000(Z00) WITH 'No Details Available to Display'.
ENDIF.
WHEN 'EXIT'.
LEAVE PROGRAM.
WHEN 'BACK' OR 'EXIT' OR 'CANCEL'.
LEAVE TO SCREEN 0.
WHEN 'CLS'.
CLEAR ZABS.
WHEN 'INS'.
INSERT ZABS .
ZABS-ABWTG = ZABS-ENDDA - ZABS-BEGDA + 1.
IF SY-DBCNT <> 0.
MESSAGE I000(Z00) WITH 'Personnel No' ZABS-PERNR
'inserted successfully'.
ENDIF.
CLEAR ZABS.
WHEN 'MOD'.
UPDATE ZABS.
ZABS-ABWTG = ZABS-ENDDA - ZABS-BEGDA + 1.
IF SY-DBCNT <> 0.
MESSAGE I000(Z00) WITH 'Personnel No' ZABS-PERNR
'Modified Successfully'.
ENDIF.
CLEAR ZABS.
*WHEN 'DEL'.
*CALL FUNCTION 'POPUP_TO_CONFIRM_LOSS_OF_DATA'
EXPORTING
 TEXTLINE1 = 'ARE YOU SURE'
 TEXTLINE2 = 'YOU WANT TO DELETE'
 TITEL = 'CONFIRMATION'
 START_COLUMN = 25
 START_ROW = 6
 DEFAULTOPTION = 'N'
IMPORTING
 ANSWER = V_ANS.
*IF V_ANS = 'J'.
*DELETE ZABS.
*IF SY-DBCNT <> 0.
*MESSAGE I000(Z00) WITH 'Personnel No' ZABS-PERNR
*'Deleted Successuflly'.
*ELSE.
*MESSAGE I000(Z00) with 'No Record to Delete'.
ENDIF.
*ENDIF.
ENDCASE.
ENDMODULE. " USER_COMMAND_0100 INPUT
*& Module GET_REC INPUT
 text
MODULE GET_REC INPUT.
SELECT SINGLE * FROM PA0001 INTO WA_PA0001
 WHERE PERNR = ZABS-PERNR.
MOVE: WA_PA0001-PERNR TO ZABS-PERNR,
 WA_PA0001-ENAME TO ZABS-ENAME,
 WA_PA0001-GSBER TO ZABS-GSBER,
 WA_PA0001-WERKS TO ZABS-WERKS.
ZABS-ABWTG = ZABS-ENDDA - ZABS-BEGDA + 1.
ENDMODULE. " GET_REC INPUT
*& Module CHECK_AUTH_WERKS INPUT
 text
MODULE CHECK_AUTH_WERKS INPUT.
*SELECT PERSA INTO TABLE _WERKS FROM T500P
 WHERE PERSA = ZABS-WERKS.
AUTHORITY-CHECK OBJECT 'Z_WERKS'
ID 'PERSA' FIELD Z_WERKS-PERSA.

You need to test the sy-subrc after the authority check - that will indicate whether the user has the authorisation or not.. you also often include the activity being tested e.g. generally 03 = Display, 02 = Update etc
AUTHORITY-CHECK OBJECT 'S_TRVL_BKS'
ID 'ACTVT' FIELD '03'
ID 'CUSTTYPE' FIELD 'B'.
IF not SY-SUBRC is initial.
MESSAGE E... "put your exception here...
ENDIF.
see [Programming Authorization Checks |http://help.sap.com/saphelp_nw04/helpdata/en/52/6712ac439b11d1896f0000e8322d00/content.htm] for more info.
Jonathan

Select-Options in dialog program

Hi there,
I'm using a selection-screen in a dialog program, I declared it in the TOP.
Selection-screens
SELECTION-SCREEN BEGIN OF SCREEN 101 AS SUBSCREEN.
parameters: p_lifnr type lfa1-lifnr obligatory ,
p_werks type t001w-werks obligatory .
SELECT-OPTIONS:
s_licha FOR zbrtconsig-licha.
SELECTION-SCREEN END OF SCREEN 101.
I have to use the event at selection-screen on value-request for s_licha-low, and I need the values from the fields p_lifnr and p_werks. the problem is:
If I only fill the fields p_lifnr, p_werks and click on F4 for s_licha, the values of p_lifnr and p_werks are not updated, they are empty. Only wether I do an Enter this fields is updated.
Thanks,
Alexandre Nogueira

Hi,
i am not clear about your problem, please expalin it clearly.
use FM : DYNP_VALUES_UPDATE to update screen fields.
use FM : DYNP_VALUES_READ to read screen fields.
use SET /GET Parameter id's to set parameters
this FM will update the screen fields before to PBO event.
check this link for sample code :
Re: Issue Related to Module pool
Regards
Appana

In dialog programming i want to leave the current transaction

Hi,
In dialog programming i want to leave the current transaction and come out to the standard sap initial screen.
Please advise me how can i apply.
Thanks.

Basic question, please search before posting.
Thread locked.
Thomas

Select-option field in dialog programming

hi guys,
i need to declare field matnr as select-option range in dialog programming..how can i code it in the module program?

This questions has been answered many times (even in february)
- search sdn wiki (2 commented samples at [SELECT-OPTIONS on Dialog programming screen|http://wiki.sdn.sap.com/wiki/display/ABAP/SELECT-OPTIONSonDialogprogrammingscreen] and [Select-Options in Module Pool Programming|http://wiki.sdn.sap.com/wiki/display/ABAP/Select-OptionsinModulePoolProgramming])
- search abap online help ([SELECTION-SCREEN - AS SUBSCREEN |http://help.sap.com/abapdocu_70/en/ABAPSELECTION-SCREEN_SUBSCREEN.htm] with sample at [Selection Screens as Subscreens |http://help.sap.com/abapdocu_70/en/ABENSEL_SCREEN_SUBSCREEN_ABEXA.htm])
Regards,
Raymond

Need help in dialog programming

Hello gurus,
I have started my career in ABAP and many questions are bothering me.Would need support from all of u there...
I am studying Dialog programming but not able to get the exact flow of how it actually works.I am following a book titled Advanced ABAP by Gareth B ruyn and Lyfareff.
Still it is not getin clear...can someone help me with that...Step by step procedure to do dialog programming...I am learning on version 4.7...
Also, If we have a field name how can we find out in which tables that same field is present..i.e.how can we search for the different tables for the same field...
Thanks in Advance..
Cheers:Jim

Hi Jimmy,
DIALOG Programming
You can also check the transaction ABAPDOCU which gives you lot of sample programs.
Also you can see the below examples...
Go to se38 and give demodynpro and press F4.
YOu will get a list of demo module pool programs.
One more T-Code is ABAPDOCU.
YOu can find more examples there.
See the prgrams:
DEMO_DYNPRO_TABLE_CONTROL_1 Table Control with LOOP Statement
DEMO_DYNPRO_TABLE_CONTROL_2 Table Control with LOOP AT ITAB
Check the below link:
http://wiki.ittoolbox.com/index.php/FAQ:What_is_module_pool_program_in_abap%3F
http://help.sap.com/saphelp_46c/helpdata/en/35/26b1aaafab52b9e10000009b38f974/content.htm
http://sap.mis.cmich.edu/sap-abap/abap09/sld011.htm
http://sap.mis.cmich.edu/sap-abap/abap09/index.htm
http://www.geocities.com/ZSAPcHAT
http://www.allsaplinks.com/files/using_table_in_screen.pdf
http://help.sap.com/saphelp_webas630/helpdata/en/9f/db9cdc35c111d1829f0000e829fbfe/content.htm
http://www.sapdevelopment.co.uk/dialog/dialoghome.htm
http://www.sap-img.com/
http://help.sap.com/saphelp_46c/helpdata/en/08/bef2dadb5311d1ad10080009b0fb56/content.htm
http://www.sapgenie.com/links/abap.htm
http://help.sap.com/saphelp_nw04/helpdata/en/c9/5472fc787f11d194c90000e8353423/frameset.htm
http://help.sap.com/saphelp_47x200/helpdata/en/52/670ba2439b11d1896f0000e8322d00/frameset.htm
http://www.allsaplinks.com/dialog_programming.html
http://sap.mis.cmich.edu/sap-abap/abap09/
Other useful links:
http://sap.mis.cmich.edu/sap-abap/abap09/index.htm
Other links:
http://help.sap.com/saphelp_nw2004s/helpdata/en/fc/eb2d40358411d1829f0000e829fbfe/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/10/e7dbde82ba11d295a40000e8353423/content.htm
For Screens
http://help.sap.com/saphelp_47x200/helpdata/en/e4/2adbef449911d1949c0000e8353423/content.htm
Screen elements
http://help.sap.com/saphelp_47x200/helpdata/en/47/e07f5f2b9911d2954f0000e8353423/content.htm
Processing Screens
http://help.sap.com/saphelp_47x200/helpdata/en/47/e07f682b9911d2954f0000e8353423/content.htm
Complex Screen elements
http://help.sap.com/saphelp_47x200/helpdata/en/fd/02da2a61d811d295750000e8353423/content.htm
Also
From Menu Environment->Examples->ABAP examples
or Using the Tcode ABAPDOCU you can learn Module pool programs.
Reward if useful.
Thanks
Aneesh.

Triggering a workflow through a dialog program

I tried to trigger a workflow through a dialog program using FM. I also created BOR and workflow(SWDD). The dialog program basically deletes a sales order and then a workflow should trigger. I am not able to see the email. Am I missing anything here?
Pls find below the coding..'ZCSS_SO1' is the BO.
Data : g_objtype LIKE SWR_STRUCT-OBJECT_TYP,
G_OBJKEY LIKE SWR_STRUCT-OBJECT_KEY,
G_EVENT LIKE SWR_STRUCT-EVENT.
data begin of l_input_container occurs 0.
include structure swcont.
data end of l_input_container.
data: v_vbeln like vbak-vbeln.
g_objtype = 'ZCSS_SO1'.
g_event = 'DELETE'.
G_OBJKEY = 'SALESDOCUMENT'.
CALL FUNCTION 'SWC_ELEMENT_SET'
EXPORTING
element = 'ELEMENT'
field = 'VALUE'
tables
container = l_input_container.
CALL FUNCTION 'SWE_EVENT_CREATE_IN_UPD_TASK'
EXPORTING
objtype = g_objtype
objkey = G_OBJKEY
event = g_event
tables
event_container = l_input_container.
commit work.

Hi Chandri,
You can firstly check whether the code you have written below is triggering the BO event or not by switching on the trace using transaction SWELS , then running the transaction (dialog program mentioned below). After, switch off the trace and then view the trace from transaction SWEL.
Your BO and event should show up in the trace.
Regards,
Aditya
p.s. also for the mail, check what method u are using?

Listbox and data read in dialog program

Hi Experts
 I want to display the data as listbox in the dialog program, the data has to be read from the database as we see some standard transactions.
 How to display the data into listbox, whether we need to write coding or can we set the property of the field.
 Pls advise me.
Regards
Rajaram

i am giving here sample code for list box.hope it helps.thank you.
TYPES : BEGIN OF ty_code,
 code TYPE zcomp_ys-comp_code,
 END OF ty_code.
TYPES : BEGIN OF ty_comp,
 code TYPE zcomp_ys-comp_code,
 language TYPE zcomp_ys-language,
 comp_name TYPE zcomp_ys-comp_name,
 country TYPE zcomp_ys-country,
 END OF ty_comp.
DATA : it_code TYPE STANDARD TABLE OF ty_code WITH HEADER LINE,
 it_comp TYPE STANDARD TABLE OF ty_comp WITH HEADER LINE.
 SELECTION SREEEN
SELECTION-SCREEN : BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
PARAMETER : p_code LIKE it_code-code AS LISTBOX VISIBLE LENGTH 10.
SELECTION-SCREEN : END OF BLOCK b1.
 AT SELECTION-SCREEN OUTPUT
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_code.
 SELECT comp_code FROM zcomp_ys INTO TABLE it_code.
 CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
 EXPORTING
 DDIC_STRUCTURE = ' '
 retfield = 'CODE'
 PVALKEY = ' '
 DYNPPROG = ' '
 DYNPNR = ' '
 DYNPROFIELD = ' '
 STEPL = 0
 WINDOW_TITLE =
 VALUE = ' '
 value_org = 'S'
 MULTIPLE_CHOICE = ' '
 DISPLAY = ' '
 callback_program = 'ZAL_REPT_LISTBOX_YS'
 CALLBACK_FORM = ' '
 MARK_TAB =
IMPORTING
 USER_RESET =
 TABLES
 value_tab = it_code
 FIELD_TAB =
 RETURN_TAB =
 DYNPFLD_MAPPING =
EXCEPTIONS
 PARAMETER_ERROR = 1
 NO_VALUES_FOUND = 2
 OTHERS = 3
 IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
 ENDIF.
 START-OF-SELECTION
START-OF-SELECTION.
SELECT comp_code language comp_name country FROM zcomp_ys INTO TABLE
it_comp WHERE comp_code EQ p_code.
 LOOP AT it_comp.
 WRITE : / it_comp-code,
 IT_COMP-COMP_NAME,
 IT_COMP-LANGUAGE,
 IT_COMP-COUNTRY.
 ENDLOOP.

How to learn dialog programming?

I'm familiar with report programming, but rarely know on how to build a dialog program.
Please tell me:
What is the procedure of dialog programming?
Where I can find the turtorials?

Hi Xia liu,
DIALOG Programming
You can also check the transaction ABAPDOCU which gives you lot of sample programs.
Also you can see the below examples...
Go to se38 and give demodynpro and press F4.
YOu will get a list of demo module pool programs.
One more T-Code is ABAPDOCU.
YOu can find more examples there.
See the prgrams:
DEMO_DYNPRO_TABLE_CONTROL_1 Table Control with LOOP Statement
DEMO_DYNPRO_TABLE_CONTROL_2 Table Control with LOOP AT ITAB
Check the below link:
http://wiki.ittoolbox.com/index.php/FAQ:What_is_module_pool_program_in_abap%3F
http://help.sap.com/saphelp_46c/helpdata/en/35/26b1aaafab52b9e10000009b38f974/content.htm
http://sap.mis.cmich.edu/sap-abap/abap09/sld011.htm
http://sap.mis.cmich.edu/sap-abap/abap09/index.htm
http://www.geocities.com/ZSAPcHAT
http://www.allsaplinks.com/files/using_table_in_screen.pdf
http://help.sap.com/saphelp_webas630/helpdata/en/9f/db9cdc35c111d1829f0000e829fbfe/content.htm
http://www.sapdevelopment.co.uk/dialog/dialoghome.htm
http://www.sap-img.com/
http://help.sap.com/saphelp_46c/helpdata/en/08/bef2dadb5311d1ad10080009b0fb56/content.htm
http://www.sapgenie.com/links/abap.htm
http://help.sap.com/saphelp_nw04/helpdata/en/c9/5472fc787f11d194c90000e8353423/frameset.htm
http://help.sap.com/saphelp_47x200/helpdata/en/52/670ba2439b11d1896f0000e8322d00/frameset.htm
http://www.allsaplinks.com/dialog_programming.html
http://sap.mis.cmich.edu/sap-abap/abap09/
http://www.sapdevelopment.co.uk/dialog/dialoghome.htm
http://help.sap.com/saphelp_webas630/helpdata/en/9f/db9cdc35c111d1829f0000e829fbfe/content.htm
http://sap.mis.cmich.edu/abap-00/
http://www.allsaplinks.com/files/using_table_in_screen.pdf
http://help.sap.com/saphelp_46c/helpdata/en/08/bef2dadb5311d1ad10080009b0fb56/content.htm
http://www.sapgenie.com/links/abap.htm
http://help.sap.com/saphelp_nw04/helpdata/en/c9/5472fc787f11d194c90000e8353423/frameset.htm
http://www.sapdevelopment.co.uk/dialog/dialoghome.htm
http://help.sap.com
http://www.sapgenie.com/abap/example_code.htm
http://help.sap.com/saphelp_47x200/helpdata/en/52/670ba2439b11d1896f0000e8322d00/frameset.htm
http://www.allsaplinks.com/dialog_programming.html
http://www.sapbrain.com/TUTORIALS/default.html
http://www.sappoint.com/abap/spmp.pdf
http://sappoint.com/abap.html
http://www.sap-img.com/abap.htm
http://sap.ittoolbox.com/code/archives.asp?i=10&t=450&a=t
http://www.sapdevelopment.co.uk/dialog/dialoghome.htm
http://www.sap-img.com/abap/
http://www.sapdevelopment.co.uk/dialog/dialoghome.htm
http://www.sap-img.com/
http://www.sappoint.com/faq/faqdiapr.pdf
http://www.allsaplinks.com/dialog_programming.html
check these links.
http://sap.mis.cmich.edu/sap-abap/abap09/index.htm
http://www.sapdevelopment.co.uk/dialog/dialoghome.htm
http://help.sap.com/saphelp_webas630/helpdata/en/9f/db9cdc35c111d1829f0000e829fbfe/content.htm
http://www.allsaplinks.com/dialog_programming.html
http://www.sapbrain.com/TUTORIALS/default.html
http://www.sappoint.com/abap/spmp.pdf
http://help.sap.com/saphelp_nw04/helpdata/en/c9/5472fc787f11d194c90000e8353423/frameset.htm
http://www.sapgenie.com/abap/example_code.htm
http://www.sap-img.com/
http://help.sap.com/saphelp_46c/helpdata/en/08/bef2dadb5311d1ad10080009b0fb56/content.htm
http://www.sapgenie.com/links/abap.htm
http://help.sap.com/saphelp_nw04/helpdata/en/c9/5472fc787f11d194c90000e8353423/frameset.htm
http://www.sapdevelopment.co.uk/dialog/dialoghome.htm
http://www.allsaplinks.com/dialog_programming.html
http://www.allsaplinks.com/files/intro_to_dialog_prg.pdf
Other useful link:
http://sap.mis.cmich.edu/sap-abap/abap09/index.htm
Other links:
http://help.sap.com/saphelp_nw2004s/helpdata/en/fc/eb2d40358411d1829f0000e829fbfe/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/10/e7dbde82ba11d295a40000e8353423/content.htm
For Screens
http://help.sap.com/saphelp_47x200/helpdata/en/e4/2adbef449911d1949c0000e8353423/content.htm
Screen elements
http://help.sap.com/saphelp_47x200/helpdata/en/47/e07f5f2b9911d2954f0000e8353423/content.htm
Processing Screens
http://help.sap.com/saphelp_47x200/helpdata/en/47/e07f682b9911d2954f0000e8353423/content.htm
Complex Screen elements
http://help.sap.com/saphelp_47x200/helpdata/en/fd/02da2a61d811d295750000e8353423/content.htm
Hope this resolves your query.
Reward all the helpful answers.
Regards

ALV Grid Dialog Program Variant Problem

Hi Gurus-
Please help!!! I got the following problem-
The ALV dialog screen will have fields with display options as well as a number of fields as input options (editable). Based on user inputs in the input fields and other displayed fields, the user selects "Process"/F8 and it calls the BAPI_MATERIAL_EDIT functions to update material.
The problem is, I want to use variants in the input fields (Maybe REUSE_ALV_VARIANT_F4) when I select a variant it loops through the selected rows and fills out the input fields with the values stored in the variant. I want to use sample ALV grid program such as BCALV*.
The question is, can I use variants in ALV grid dialog program and if yes, how do I define variants to loop through and fill out the values in the input/editable fields on the ALV grid?
Any help will be greatly appreciated! Rep points for sure!
Thanks!!!

hi james ,
look at this link u will get an idea .
http://www.sapfans.com/forums/viewtopic.php?f=13&t=229912
http://sgstocks.tripod.com/alvgrid_control.htm
thanks,
Gaurav.
Edited by: gaurav.singh on Apr 20, 2010 7:53 AM

Popup_to_confirm in dialog program

hi,
 i m using popup to cnfirm in dialog programing , my req is when i go to put a entry it will ask for yes no or cancel if press yes then it will sav if no then back to screen if cancel then leave program, i got the theme but i m not getting the way to put the code in my flow for saving,
please help me if u have any sample code for single input dialog programming with this popup.
thanks inadvance
vijay dwivedi
marks will b sure*

Hi i want to replace this function module of following code
CALL FUNCTION 'POPUP_TO_CONFIRM_STEP'
 EXPORTING
 textline1 = text-004
 titel = text-005
 cancel_display = space
 IMPORTING
 answer = ldf_ok_code.
The 'POPUP_TO_CONFIRM_STEP' module is replaced with
CALL FUNCTION 'POPUP_TO_CONFIRM'
EXPORTING
TITLEBAR = ' '
DIAGNOSE_OBJECT = ' '
 TEXT_QUESTION =
TEXT_BUTTON_1 = 'Ja'(001)
ICON_BUTTON_1 = ' '
TEXT_BUTTON_2 = 'Nein'(002)
ICON_BUTTON_2 = ' '
DEFAULT_BUTTON = '1'
 DISPLAY_CANCEL_BUTTON = ' '
USERDEFINED_F1_HELP = ' '
START_COLUMN = 25
START_ROW = 6
POPUP_TYPE =
IV_QUICKINFO_BUTTON_1 = ' '
IV_QUICKINFO_BUTTON_2 = ' '
IMPORTING
 ANSWER = ldf_ok_code
TABLES
PARAMETER =
EXCEPTIONS
TEXT_NOT_FOUND = 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.
Please reply what all parameters do i need to use for the POPUP_TO_CONFIRM function module. I am not able to find the textline1and titel parameters which is available in 'POPUP_TO_CONFIRM_STEP' in POPUP_TO_CONFIRM func module. Please help me in ths regard.

Sample basic program 4 dialog programming

Similar Messages

Maybe you are looking for