SAP ABAP Data Element MEMOLONG (Set/Get Parameter ID for Drag&Relate)
Hierarchy
☛
PI_BASIS (Software Component) Basis Plug-In
⤷
CA (Application Component) Cross-Application Components
⤷
PORX (Package) Drag & Relate (Workplace Plugin)

⤷

⤷

Basic Data
Data Element | MEMOLONG |
Short Description | Set/Get Parameter ID for Drag&Relate |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | CHAR20 | |
Data Type | CHAR | Character String |
Length | 20 | |
Decimal Places | 0 | |
Output Length | 20 | |
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 | 0 | |
Medium | 20 | Parameter ID |
Long | 0 | |
Heading | 0 |
Documentation
Definition
You can use set/get parameters to predefine values in screen fields. In the Drag&Relate environment, set/get parameters fulfill two tasks:
- Completion of keys
- If the business object key consists of more than one field, the non- identifying key fields must be supplemented by set/get parameters. The prerequisite for this is that the application has set these parameters, otherwise the system cannot generate the link.
- Setting parameters for services
- When you start a service (for example, a transaction), the system sets the set/get parameters that were assigned to the key fields. If the start screen of the transaction that is started contains these parameters as get parameters, no further parameters need to be defined. If you can set enough parameters for the transaction using set/get parameters, you should give preference to this procedure, instead of explicitly linking key fields to input fields, since, in this case, the system can start the transaction using a simple call transaction (without batch input).
History
Last changed by/on | SAP | 20080415 |
SAP Release Created in |