SAP ABAP Data Element HISKZ (Indicator: Process plan with or without history)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷
CRM (Application Component) Customer Relationship Management
⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ CP (Package) R/3 Application development: PP Task Lists
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
CP (Package) R/3 Application development: PP Task Lists
Basic Data
| Data Element | HISKZ |
| Short Description | Indicator: Process plan with or without history |
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 | 10 | Hist. ind. |
| Medium | 15 | History ind. |
| Long | 20 | History indicator |
| Heading | 8 | History |
Documentation
Definition
Specifies whether changes in the requirements plan are to be stored in a history.
Supplementary Documentation - HISKZ 0001
Dependencies
If an original plan is to be created, you must set the indicator for the creation of a history.
Supplementary Documentation - HISKZ_ABBAU0001
Use
Procedure
Examples
Dependencies
If an original plan is to be generated, the history creation indicator must also be selected.
History
| Last changed by/on | SAP | 20011120 |
| SAP Release Created in |
