SAP ABAP Data Element SWD_TPDOWN (Top-down modeling)
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷ BC-BMT-WFM (Application Component) SAP Business Workflow
⤷ SWD (Package) Business Workflow: Process Definition
⤷ BC-BMT-WFM (Application Component) SAP Business Workflow
⤷ SWD (Package) Business Workflow: Process Definition
Basic Data
Data Element | SWD_TPDOWN |
Short Description | Top-down modeling |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | XFELD | |
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 | 0 | |
Medium | 0 | |
Long | 31 | Use Top-Down Modeling |
Heading | 31 | Use Top-Down Modeling |
Documentation
Definition
If this indicator is set, you can model a workflow in the workflow builder without having already defined any tasks. When you insert a step into the workflow definition you are not taken to the step definition screen. The step is only added in the graphic.
Use
You model a workflow from the available step types in the subject with the same name, by using drag&drop. There is also an outcome icon that you can use to model additional outcomes to activities and multiple conditions, as well as new branches in forks.
To use the workflow that you have modeled, you must complete the step definition. A syntax check for the workflow will show all the specifications you still need to enter (step labels, tasks, and so on).
Dependencies
Example
History
Last changed by/on | SAP | 20110908 |
SAP Release Created in | 630 |