SAP ABAP Data Element SWD_PERSID (Type of Persistence Profile)
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_PERSID |
Short Description | Type of Persistence Profile |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | SWD_PERSID | |
Data Type | NUMC | Character string with only digits |
Length | 4 | |
Decimal Places | 0 | |
Output Length | 4 | |
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 | Persistence Profile |
Long | 0 | |
Heading | 0 |
Documentation
Definition
This determines how the container data is saved at runtime.
The settings have the following effects:
- Structure persistence
The data is saved in the conventional container tables. Only use this setting if you have developed your own programs, which expicitly require the conventional tables.
- XML persistence
The data is saved in an XML table. Use this setting to enable use of the properties of the new container.
When you create a new workflow, the container is saved in an XML table as standard.
When you open a workflow created in an earlier release, this field contains the entry Compatibility mode. This corresponds to the entry Structure persistence. If you do not choose an entry, the data is always saved in the conventional tables.
History
Last changed by/on | SAP | 20110908 |
SAP Release Created in | 610 |