Hierarchy
PI_BASIS (Software Component) Basis Plug-In⤷
CA (Application Component) Cross-Application Components⤷
PORX (Package) Drag & Relate (Workplace Plugin)
Basic Data
| Data Element | DR_EXECMOD |
| Short Description | Drag&Relate: Function Module Instead of Transaction |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | DR_EXECMOD | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| 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 | FM Call |
| Medium | 15 | Call up FM |
| Long | 30 | Call function module |
| Heading | 0 |
Documentation
Definition
If this indicator has been set, a function module is called in the target system instead of a service (a transaction or ABAP report, for example).
This makes sense particularly when the transaction is not batch input-enabled or when it does not have any suitable input fields on the initial screen.
If the screen entered in table TSTC is not started at runtime, you can specify a different screen that is given the batch input data. You should only select the function module method if this is successful. You cannot combine the two methods.
In Basis Release 4.6 and higher, there is an improved version of call transaction in which setting the system field SY-BINPT can be suppressed. This means that transactions that are not batch input-enabled can also be used.
History
| Last changed by/on | SAP | 20080415 |
| SAP Release Created in |
