Hierarchy
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ GBSE (Package) FI-SL sets
Basic Data
Data Element | SETNR |
Short Description | Set ID |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | SETNR | |
Data Type | CHAR | Character String |
Length | 12 | |
Decimal Places | 0 | |
Output Length | 12 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | GSE | |
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Set |
Medium | 15 | Set ID |
Long | 20 | Set ID |
Heading | 12 | Set ID |
Documentation
Definition
A set is a flexible structure for depicting hierarchies and quantities.
The set ID is only unique when used in combination with the table name.
Set IDs can contain letters, numbers as well as the special characters '_' (underscore) and '-' (hyphen). Please note the following:
- The set ID should begin with a letter.
- The set ID must not contain any blank characters.
- You cannot use the names 'TRUE', 'T', 'FALSE', 'F', 'NOT', 'AND', 'NAND', ''OR' and 'NOR' as set IDs.
- The system does not differentiate between upper case and lower case letters.
Sets whose name begins with a number are delivered with the system or are created by special applications. In general set maintenance, you cannot create them, you can only display, change or delete them. If the first number is 0, you can only display the set.
Groups that were created in controlling are also stored technically as sets. They can however, not be displayed or changed in set maintenance. However, you can use groups, for example, in single and multiple sets as well as in Report Writer reports.
Supplementary Documentation - SETNR 2000
Use
Table GLU1 is always used in the planning parameters. This table contains all fields of the logical tables, so that the same parameter can be used for planning to ledgers from different tables.
Procedure
You thus only need to enter a set ID without a table in parameter maintenance.
Examples
Dependencies
History
Last changed by/on | SAP | 19981111 |
SAP Release Created in |