Hi all,
In my program i written the following code.
REPORT zmmgrexcdtl LINE-SIZE 233.
SELECTION-SCREEN : BEGIN OF BLOCK b1 WITH FRAME TITLE text-t02.
PARAMETER: finumber AS CHECKBOX ."INPUT OFF.
PARAMETER: grnumber AS CHECKBOX ."INPUT OFF.
SELECTION-SCREEN : END OF BLOCK b1.
IF finumber = 'X'.
SUBMIT ZMMGREXCDTL VIA SELECTION-SCREEN.
ENDIF.
IF grnumber = 'X'.
SUBMIT zgetgrno VIA SELECTION-SCREEN.
ENDIF.
Here according to the check box selected it will go to the screen of tat prgm.Now what i want is from tat screen if i am clicking the back button,it should come to the original screen from wer its called.
I think using set pf-status we can do tat..but i don't know how to implement it.
Any body please tell me how to do tat
Thanks in Advance,
Nitin.
3 Answers
-
Former MemberPosted on Jan 09, 2008 at 07:51 AMHi,
Dialog Status for Lists
To allow the user to communicate with the system when a list is displayed, the lists must be able to direct user actions to the ABAP program. As described in User Actions on Screens, function codes are used to do this. Function codes are maintained in the GUI status of the list screen. You define a GUI status using the Menu Painter tool in the ABAP Workbench. The system assigns function codes to list-specific user actions.
The most important of these functions is for selecting list lines by double-clicking. As described in Using a GUI Status, the double-click function is always linked to the F2 key. If a function code is assigned to the F2 key in the GUI status, it will be triggered when you double-click.
The Standard List Status
As with normal screens, you can define your own GUI status for lists and attach it to a list level using the SET PF-STATUS statement. If you do not set a particular GUI status, the system sets a default list status for the list screen in an executable program. In other programs, for example, when you call a list from screen processing, you must set this status explicitly using the statement
SET PF-STATUS space.
This default interface always contains at least the functions described in the Standard List section.
Unlike normal dialog statuses, the default list status is affected by the ABAP program.
If you define event blocks in your program using the event keywords AT LINE-SELECTION or AT PF<nn>, the system automatically assigns extra functions to other function keys that provide additional functions.
AT PF<nn> (obsolete)
All function keys of the keyboard F<nn> that are not used for predefined system functions, are set to the function codes PF<nn>, where <nn> is a number between 01 and 24. During list processing, the function codes PF<nn> are linked to the events AT PF<nn>. Choosing PF<nn> always triggers AT PF<nn>. You should no longer use event blocks for PF<nn>.
AT LINE-SELECTION
For this event, the F2 key (double-click) is assigned the function code PICK and function code Choose. The function also always appears in the application toolbar. During list processing, the PICK function code is assigned to the event AT LINE-SELECTION. PICK always triggers AT LINE-SELECTION.
All other function codes are either intercepted by the runtime environment or trigger the event AT USER-COMMAND. Function codes that trigger AT USER-COMMAND must be defined in your own GUI status. The easiest way to do this is to use the standard list status and add extra functions of your own to it.
Also refer to the document:
http://help.sap.com/saphelp_nw04/helpdata/en/9f/dba34635c111d1829f0000e829fbfe/content.htm
Regards,
Renjith Michael.
Add a comment
Add a comment