SAP ABAP Data Element SRMRGUNIQ (Uniqueness of Record Numbers in Records Management)
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷ BC-SRV-RM (Application Component) SAP Records Management
⤷ SRM_RECORD_FACILITIES (Package) Tools and Add-Ons for Records Management
⤷ BC-SRV-RM (Application Component) SAP Records Management
⤷ SRM_RECORD_FACILITIES (Package) Tools and Add-Ons for Records Management
Basic Data
Data Element | SRMRGUNIQ |
Short Description | Uniqueness of Record Numbers in Records Management |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | SRMRGUNIQ | |
Data Type | CHAR | Character String |
Length | 32 | |
Decimal Places | 0 | |
Output Length | 32 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | CHECK_UNIQUE | |
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Uniqueness |
Medium | 15 | Uniqueness |
Long | 40 | Uniqueness of Record Numbers |
Heading | 40 | Uniqueness of Record Numbers |
Documentation
Definition
Use
You use this setting to influence the check of unique record numbers (or unique indicators in general) by using the record number generator in Records Management.
- Choose the value RULE if you want record numbers to be unique for each generation rule.
The uniqueness of record numbers is then guaranteed for each generation rule if you activate the uniqueness check in transaction SRMREFRULE when you define a rule.
- Choose the value RULETYPE, if you want record numbers to be unique for each rule type (record number, document number, and so on).
Uniqueness is guaranteed for all record numbers that are based on the rules of a rule type (for all record numbers or for all document numbers, for example).
In this case, the uniqueness check is globally activated, which means that the setting "Uniqueness Check" is then irrelevant for individual generation rules.
Dependencies
Example
History
Last changed by/on | SAP | 20040312 |
SAP Release Created in | 620 |