SAP ABAP Data Element R_MULCHAR_U (Multiple usage: Uniqueness check when saving)
Hierarchy
☛
SAP_FIN (Software Component) SAP_FIN
⤷
FI-SL-IS (Application Component) Information System
⤷
GRWT (Package) Report Painter / Report Writer
⤷
⤷
Basic Data
| Data Element | R_MULCHAR_U |
| Short Description | Multiple usage: Uniqueness check when saving |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | RW_RADIO | |
| 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 | Uniq.sav. |
| Medium | 15 | Unique saving |
| Long | 30 | Uniqueness when saving |
| Heading | 0 |
Documentation
Definition
In the report definition you can use a characteristic in the row, column, or general selection of a report. In the header of the report, you can set up how the usage is to be checked:
- Uniqueness for each entry (default parameters)
The use of a characteristic has to be unique. This means, that a characteristic within a report may only be used in columns, rows, or the general selection. When defining a report, the system checks each entry or change of a set for uniqueness, and an error message is output if it is not unique. - Uniqueness when saving
The use of a characteristic also has to be unique in rows, columns, or the general selection. The system first checks for uniqueness however, when you save the report or explicitly request a check of the report. - Multiple use is allowed
The use of a characteristic does not have this limitation.
History
| Last changed by/on | SAP | 20010607 |
| SAP Release Created in |