Home > ABAP, UI > SAP Screen Sequence Control

SAP Screen Sequence Control

January 26th, 2010 Leave a comment Go to comments

Transaction Code:

VFBS – Next screen control.
VOVB – Screen Sequence Group Maintenance.
VOV8 - Document Type Maintenance. You can assign the standard screen sequence group to sales document type in this transaction.

Function Module: SCREEN_SEQUENCE_CONTROL

Function: SCREEN_SEQUENCE_CONTROL
Function group: V00F

Summary
Determination of the next screen from the function code

1. General description
The components contained in the function group V00F serve the determination of the further processing after input of a function code over key or menu. By three tables, those is steered to the definition by functions (T185F) and processing places (T185V), as well as the definition of ways between the places (T185) to be used.

Beyond that the possibility exists of merging the safety dialogues, which are realized in the function group SPO1. The control been made by T185F and T185D, the texts which can be spent are deposit able in T185T, all texts can however also at any time only be handed over at run-time dynamically.

A detailed description of the flow control and its extensive functionality is to be found in the project system under AS4 02,405,315 15. The here following description serves the documentation of the call and/or as guidance for the implementation of the functional modules for the flow control (function group V00F).

2. Use
The functional module FOLGEBILD (NEXT SCREEN) serves the controlling of the further processing at expiration of all single steps in the PAI of a Dynpros (screen control). It obtain not only the branch of a subsequent Dynpro (screen control), but also the control of menus, transactions, dialogue and functional modules, as well as report, whereby the interface is not yet accurately defined to the reporting.

It finished only functions of the type 0, that is the pre-emption of the field T185F-FCINT. A call with another type causes an error. It is to be made certain further that the static subsequent Dynpro (screen control) is not indicated in the head of the respective picture, since otherwise no windows can be sent.

3. Call
The functional module requires the sphere of activity with 5 digits that means usually the last 5 places of the module pool name of the calls, as input the head and group of positions, as well as naturally the function code.

The expenditure contains the CUA parameters for status and title, as well as the type of activity and the indication whether the next picture is to be processed darkly. In connection with the call of transactions etc.

  1. Jitendra
    August 9th, 2010 at 13:03 | #1

    Hi,

    I wanted to know that
    ‘How to know the hidden fields & frames in master transaction screen sequence’

    Regards
    Jitendra

  1. No trackbacks yet.