Gui Xt Presentation for SAP
-
Upload
peterhbrown -
Category
Documents
-
view
2.861 -
download
5
description
Transcript of Gui Xt Presentation for SAP
GuiXT Technology
SAPGUIUser Request MM01
R/3 ProcessesRequest
R/3 Responds withMM01 Screen
GUIXTScreen Modification
Are applied
SAPGUIDraws screen
Steps to finish a project
VA01 – Order Entry
1. Design screens
• What to display
• How to display
What to display
• User involved
• Kaizen
• Balance simplicity and coverage
VA01 Screen Design
How to display
• Programmer involved
• Decide templates for each GuiXT screen – find real SAP screen/tab to modify on
• Selected screens/tabs should be easily jumped between
• Try not to create new table in GuiXT but use existing table in SAP
Screen Mapping – Initial screen
Screen Mapping – Header
Screen Mapping – Items
Screen Mapping – Item detail
2. Develop scripts
• 2 different types of GuiXT scripts– GuiXT script, display all SAP/GuiXT
components on the template screen– Input script, process GuiXT components and
run SAP screens
GuiXT Script for initial screen
Input script to 2nd screen
3. Improve performance
• Use function code to go to a screen.– tab or menu might be hidden/displayed by different order type or
item, like ‘billing plan’ shows for some order type only
• Use most efficient path to read all screens/tabs– There are many ways to get to the same screen, choose the
fastest one.
• Bypass unnecessary screens and tabs– Accessing a screen/tab would use some time, bypass those
screen/tab you don’t need to read/write.
• Error handling on all modified screens– Unless all modified fields in the screen are 100% free form,
always have error handling when leaving a screen.
We learned
• Screen should be independent, can be run by itself– Screen could be brought in from different
Tcode– Variable on the screen should be refreshed
when the screen is loaded
• Add error handling for all ‘Enter …’ screens with user input– Error happens when screen didn’t go as
designed