SAP ABAP Data Element T3130GPUSHX (Function code that should be executed on an RF screen)
Hierarchy
☛
SAP_APPL (Software Component) Logistics and Accounting
⤷ LE-MOB (Application Component) Mobile data entry
⤷ LMOB (Package) Mobile Computing in warehouse logistics
⤷ LE-MOB (Application Component) Mobile data entry
⤷ LMOB (Package) Mobile Computing in warehouse logistics
Basic Data
Data Element | T3130GPUSHX |
Short Description | Function code that should be executed on an RF screen |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | SYCHAR70 | |
Data Type | CHAR | Character String |
Length | 70 | |
Decimal Places | 0 | |
Output Length | 70 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Func. code |
Medium | 15 | Function code |
Long | 20 | Function code |
Heading | 5 | FCode |
Documentation
Definition
This field is used to control screen navigation in RF transactions.
You can set up the ENTER key in such a way that it replaces a sequence of up to five pushbuttons. In the relevant fields, you enter the function codes and the sequence in which they should be executed on the RF screens. After you do this, you no longer need to choose the pushbuttons on the screen.
When you define the ENTER key, use the actual function code of the screen pushbuttons. For example:
PGDN Page down
SAVE Save
CMPL Save and display next screen
History
Last changed by/on | SAP | 20011120 |
SAP Release Created in |