Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

What is PF-STATUS.

Former Member
0 Kudos
4,721

Hi,

1. What is PF-STATUS?

2. Maximum how many sub window we can create in smart forms?

3. Can we use Check Table and Value Table to Same field?

4. In BDC session method maximum how many records we can upload?

2 REPLIES 2

Former Member
0 Kudos
621

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 PFsee forignkey relationship.

BDC session method maximum

1 lack record

Former Member
0 Kudos
621

Hi

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.