topic Re: reports in Application Development and Automation Discussions

reports

Former Member — Mon, 05 Mar 2007 02:16:06 GMT

Hi Friends ,

How to define menu interface for report ...

is it possible or not ?.

Regs ,

Murthy

Re: reports

RichHeilman — Mon, 05 Mar 2007 02:25:12 GMT

Yes, it is. You simply need to define the menu structure in a custom gui status and call this status in your report program before either the selection screen is thrown or your output is thrown.

set pf-status 'MAIN'.

Regards,

Rich Heilman

Re: reports

Former Member — Mon, 05 Mar 2007 02:28:18 GMT

hi,

write the command,

set pf-status 'AA'.

in your program.Double click on "AA', it will take you to gui screen.

ENter the elements you need to handle.

regards,

keerthi

Re: reports

Former Member — Mon, 05 Mar 2007 02:59:10 GMT

Murthy,

Use SET PF-STATUS 'XXX'.

Double click on XXX.

For more information...

Setting the GUI Status

To assign a GUI status to a screen, use the ABAP statement

SET PF-STATUS <stat> [OF PROGRAM <prog>]

[EXCLUDING <f>|<itab>].

This statement defines the user interface for all subsequent screens of a screen sequence until another is set using a new SET PF-STATUS statement. The GUI status <stat> must be a component of the current ABAP program, unless you use the OF PROGRAM addition in the SET PF-STATUS statement to set a GUI status of another program <prog>.

The EXCLUDING function allows you to change the appearance and function of a GUI status dynamically. This is useful if the individual user interfaces for a range of screens are very similar. You can define a single global status, and then just deactivate the functions you do not need using EXCLUDING. Specify <f> to deactivate the function code stored in field <f>. Specify <itab> to deactivate all function codes stored in the internal table <itab>. Field <f> and the lines of table <itab> should be of type C, and have length 20.

You should set the GUI status for a screen in the PBO event. If you do not specify a GUI status for a screen, it is displayed with the interface of the previous screen. If you do not specify a GUI status for the first screen of a program, it has no user interface, and the user may not be able to leave the screen.

Pls. mark if useful.

Re: reports

Former Member — Mon, 05 Mar 2007 04:14:58 GMT

You should copy the 'STANDARD' GUI status from program SAPLKKBL using transaction SE90 ~~>Programming SubObjects~~> Gui Status.

Execute this transaction to get to next screen. select status using checkbox. click on GUI Status --> Copy.

Enter your Z program name and the name you what for this status - you can keep it as 'STANDARD' to be simple.

Then you can edit the new status to add or delete buttons.

Write set pf-status 'TEST' in your report.

Best Regards,

Vibha

*Please mark all the helpful answers