SAPMV45A -Program
MV45AF01 -Form include
MV45AO01 -PBO include
MV45AI01 -PAI include
MV45ATOP -Data declaration
SAPZNAME -User defined Program
ZNAMEF01 -User defined Form include
... Types of screen
List
Selection
Dialog
Normal
Selection screen
Function Codes
Function Type:
' ' Normal
'E' Exit
'S' System
'T' Transaction
'P' Tabst. Control
'H' Help request
Text type:
Static (used on menu + app button if no icon assined.
Dynamic
Static function texts:
Function text |_____|
Icon name |_____| - Used on app button
Icon text |_____| - Used on app button
Info. text |_____| - Used when user holds cursor over button.
Fastpath |_____|
Key Assignments.
Reserved function keys
Recommended function keys
Freely assigned function keys
Application tool bar
App toolbar can have up to 35 push buttons
Functions on app toolbar must be assigned to and Fkey.
If you use the fixed posistion attribute (pad lock icon) inactive function are grey out rather than
removed.
Menu
A menu can contain up to 15 entries
Menus can be up to 3 levels.
The menubar can contain up tp 8 different menus (including 2 standard ones, system and help)
Activate or Deactivate functions
Active/inactive button
SET pf-status 'STATUS' EXCLUDING <fcode> <itab>
Set defaults GUI Status values
To provide appropriate default function codes, depending on type of status/screen goto the following menu
path within the gui staus creation screen.
Extras -> Adjust template
List status
Selection screen
List viewer
Tree status
Template status (copy status)
Program |_____________|
Status |_____________|
GET CURSOR
FIELD fieldname
[LINE] fieldname or structure(store rep line)
Screen numbers
Numbers greater than 9000 are reserved for SAP customers
Numbers 1000 through 1010 are reserved for maintenance screen of ABAP dictionary tables and the
standard selection screen report.
TABLES Statement
If you create screen fields based on DATABASE table fields (I.e. EKKO-EBELN) remember the TABLES:
statement. This creates a WA with the same name and structure as the DB table.
BUT
TABLES: makes and interface between the Program(ABAP) and the screen:
TABLES: SFLIGHT Does NOT work the same as DATA: SFLIGHT TYPE SFLIGHT
Note: The TABLES: statement will populate the screen fields the DATA: statement will not.
TABLES: VBAK, "Creates WA based on VBAK
*VBAK. "Creates second WA based on VBAK
CALL Screen
CALL SCREEN 100
STARTING AT
ENDING AT
Get / SET PArameter ID
Get Parameter "Get value stored in Parameter ID
Set Parameter "Store entered value in Parameter ID
Flow Logic
FIELD SPFLI-CARRID MODULE validate_carrid.
"If the module 'validate_carrid' produces and Error message, it returns to screen making field SPFLICARRID ready for INPUT. Without this all fields would be output only.
CHAIN.
FIELD: SPFLI-CARRID,
SPFLI-CONNID. MODULE 'validate_carrid_connid'.
ENDCHAIN.
"Returns to screen making multiple field ready for INPUT.
FIELD SPFLI-CARRID MODULE validate_carrid ON INPUT
"Has the contents of the field changed from its initial value.
CHAIN.
FIELD: SPFLI-CARRID,
SPFLI-CONNID.
MODULE 'validate_carrid_connid' ON CHAIN-INPUT
ENDCHAIN.
"Has the contents of any of the fields changed from its initial value.
ON REQUEST and ON CHAIN-REQUEST
"Similar to ON INPUT but checksif contents of field has changed since the last time the screen was
displayed.