Designing SAP Transactions
Content
Introduction
SAP Dynpros
Screen Elements, Fields and Layouts
Flow Logic
Example Transaction Code
Example - Define Screens
Example - Write Flow Logic
Example - PBO
Example - PAI
Example - Forms
Example - Validating Fields
Example - Variable Declarations
Assigning Transaction Codes
  Designing SAP Transactions
-Example - Write Flow Logic-
 
Page 7 Of 13
 

Write the Flow Logic

Now let us write the flow logic for both the screens.

            Screen 100 

Process before output.

                Module status_0100.

*

Process after inout.

                Module User_Command_0100.

 

Screen 200 

Process before output.

                Module status_0200.

*

Process after inout.

                Module exitscreen at exit-command.

                Field ztryemp-name module check_name.

                Field ztryemp-phone module check_phone.

                Field ztryemp-basic module check_basic.

                Module User_Command_0200.

To add the code to each module, double click on the module. This will bring up a screen asking you to select the proper sub program from the module pool to place the code in it. Select the proper PBO, PAI and Form program to include the respective code. 

We will first see the PBO sub-program for both screens.

PBO modules are used for initializing variables, assigning the pf-statuses and titlebars for dynpros, and other screen processing to be done before the screen is displayed and re-displayed.

 
Stats Box
Vendor Listings (9)
Jobs (3)
Resumes (3)
Tutorials (18)
Articles (22)
Code Snippets (1)
CBTs (17)
Books (4)
Online Training (15)
Latest 5 Tutorial
SAPscript
SAP Mobile Engine
Integrating XML into SAP Business Connector
Lotus Notes Integration
SAP Data Archiving
 
Copyright © 2007 SapDox.com. All rights Reserved.