GuiXT Technology SAPGUI User Request MM01 R/3 Processes Request R/3 Responds with MM01 Screen GUIXT Screen Modification Ar...
Steps to finish a project VA01 – Order Entry
1. Design screens <ul><li>What to display </li></ul><ul><li>How to display </li></ul>
What to display <ul><li>User involved </li></ul><ul><li>Kaizen </li></ul><ul><li>Balance simplicity and coverage </li></ul>
VA01 Screen Design
How to display <ul><li>Programmer involved </li></ul><ul><li>Decide templates for each GuiXT screen – find real SAP screen...
Screen Mapping – Initial screen
Screen Mapping – Header
Screen Mapping – Items
Screen Mapping – Item detail
2. Develop scripts <ul><li>2 different types of GuiXT scripts </li></ul><ul><ul><li>GuiXT script, display all SAP/GuiXT co...
GuiXT Script for initial screen
Input script to 2 nd  screen
3. Improve performance <ul><li>Use function code to go to a screen. </li></ul><ul><ul><li>tab or menu might be hidden/disp...
We learned <ul><li>Screen should be independent, can be run by itself </li></ul><ul><ul><li>Screen could be brought in fro...
Upcoming SlideShare
Loading in …5
×

Gui Xt Presentation for SAP

2,595 views

Published on

GuiXT for SAP SD

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
2,595
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
61
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Gui Xt Presentation for SAP

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

×