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 - Define Screens-
 
Page 6 Of 13
 

Define the Screen Layout

Use the various options of the screen painter to place the text fields, input/output fields, pushbuttons required for the 2 screens.

Define the Screen Element Attributes

As far as possible, use dictionary data elements for the input/output fields so that the required attributes will be automatically set by SAP and the basic automatic validations checks will also be done by SAP.

To set the attributes of each field, select the field and double click on it to open the Attributes Screen.

Define the ok code field in the field list for the Screens

Whenever user does any interaction with the screens, a field is required to trap the action that the user is trying to perform. To do this, define 4 character variable by the name v_okcode_screennumber.

Assign function codes to the various buttons on the screen that the user is likely to press.

These function codes are then transferred via the variable to the flow logic of the screen, to decide the path to be taken by the flow of the transaction.

 
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.