Hierarchy
EA-FIN (Software Component) EA-FIN⤷
RE-FX-BD (Application Component) Basic Data⤷
RE_BD_AO (Package) RE: Arch. Object (Master Data of Architectural Object)
Basic Data
| Data Element | REBDISGLOBAL |
| Short Description | Number Assignment Is Global |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | RECABOOL | |
| 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 | Global NA |
| Medium | 15 | Global No.Asgn. |
| Long | 20 | Global No. Assgnmt |
| Heading | 10 | Global NA |
Documentation
Definition
Specifies if number assignment for an object type is unique for the whole client, that is, global. Numbers are then assigned uniquely for this object type, regardless of its hierarchical level.
Example
You define the Locality object type as the top level of an architectural hierarchy. Number assignment is automatically global for this object type. If you now create a building for this locality, the number of the building only has to be unique within the given locality. If you have two localities, A1 and A2, then each of these localities can contain a building called B1.
If you set this indicator for the Building object type, however, then the system also assigns the building numbers uniquely. The system ensures in this case that each building number exists only once throughout the client and for all localities.
History
| Last changed by/on | SAP | 20030326 |
| SAP Release Created in | 46C |
