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
-Assigning Transaction Codes-
 
Page 13 Of 13
 

Final Step – Assign Transaction Code and IT IS READY TO RUN

Our transaction is now ready. Generate and activate all the flow logics that we have written. Also generate and activate all the screens, pf-statuses and the module pool program itself. This ensures that all the changes done to the various objects during the writing of the transaction are active when we finish developing the transaction.

Invoke transaction SE93. Click the create button to create the new transaction ZTRY. Specify the name of the module pool program as SAPMZTRY and the first screen of the transaction as 0100.

Save the transaction code.

To test the transaction, give ZTRY in the command window and press ENTER. The first screen that we had developed should be displayed. Now you can play around with the transaction to see that all the functions that we have coded are working properly for both the screens.

Once the transaction is tested in development up to satisfaction level, transport it to test environment for another round of testing, and then finally to the Production environment to make it a working transaction.

We hope you have found this tutorial useful. Good luck designing your SAP Transactions!

 
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.