This is simply an extension of the header form, where you install trigger functions for the current mask, these additional attributes are also master attributes.
Pre-Mask Userexit | name of a userexit attached to the Pre_Mask trigger |
Post-Mask Userexit | name of a userexit attached to the Post_Mask trigger |
Sel-Action Userexit | name of a userexit attached to the Sel_Action trigger |
Edit-Action Userexit |
name of a userexit attached to the Edit_Action trigger |
Pre-Action Userexit | name of a userexit attached to the Pre_Action trigger |
Post-Action Userexit |
name of a userexit attached to the Post_Action trigger |
Join Definition | link to other table data |
Comments | comments about a mask record |
The Pre_Mask userexit is executed before the mask appears on the screen.
You should use it to prepare the mask for viewing, for example by hiding fields from certain users, blocking certain operations or precalculating some field values.
The most often-used userexit here is wdh_upd_lis, which queries the records and automatically fills the mask before it is displayed on screen. Users no longer need to use the Rebuild function.
Post-Mask Userexit
The Post_Mask userexit is executed after the mask has been removed from the screen.
This function could determine the next dialog. other masks could be activated, or you could delete the old mask's temporary objects.
Sel-Action Userexit
A single mouseclick (select or deselect) on records causes the Sel_Action userexit to execute.
A function on the Sel_Action trigger generally responds to mouse events or browsing. For example, the standard userexit cch_set_tit can be used to display graphics in forms dependent on the selected record.
The trigger operates differently in lists and forms:
The Sel_Action trigger passes a parameter to the attached userexit, containing the action which was carried out and the record(s) affected:
Example: parameters passed in lists:
Example: parameters passed in forms:
Edit-Action Userexit
The Edit_Action userexit is executed before the mask enters the Edit state. This is always the case when records are edited, queried or deleted (e.g. with standard functions).
Pre-Action Userexit
The Pre_Action userexit is executed before a transaction takes place. This is always the case when Edit, Query or Delete operations are confirmed (e.g. saving, fetching,....).
Post-Action Userexit
The Post_Action userexit is executed after changes to the mask's content have been confirmed and DataView has completed the transaction. This is always the case when Edit, Query or Delete operations are finally completed.
Join Definition
attribute
master attribute for mask (T_MASK)
type, entry
string, entry optional
max. no. of characters
2000
selection tool
no
multilingual field
no
More information:
-> Join Conitions
Comments
attribute
master attribute for mask (T_MASK)
type, entry
string, entry optional
max. no. of characters
243
selection tool
no
multilingual field
no