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 | REBDPARTSEPARATOR |
| Short Description | AOID Code: Separator |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | REBDPARTSEPARATOR | |
| Data Type | CHAR | Character String |
| Length | 10 | |
| Decimal Places | 0 | |
| Output Length | 10 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | PART_SEPARATOR | |
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Separator |
| Medium | 15 | Separator |
| Long | 20 | Separator |
| Heading | 10 | Separator |
Documentation
Definition
You can specify a default a separator in Customizing or enter one on the architectural object. If the architectural object ID of an object is used for creating the architectural object IDs of objects below it in the architectural hierarchy, then the architectural object ID of the lower-level object would look like this
xxxxxxxxTyyy
where xxxxxxxx is the architectural object ID of the object, on which the separator was specified, T is the separator, and yyy is the AOID code of the object for which the architectural object ID is being created.
There is not a set number of places for xxxxxxxx, T and yyy. (However, you can define a maximum number of places in Customizing for yyy and therefore indirectly for xxxxxxxx.)
Use
Dependencies
Example
The following was specified in the Customizing table for automatic assignment of the architectural object ID (AOID):
Name of AO Type Max.Length DefLength Use Separator From AONR
Locality 3 X
Bldg complex 13
Building 2 X - X
Part of building 1 X X
Floor 2 1 X . X
Room 3 2 X X
The system assigns the following architectural object IDs based on these object numbers and codes:
Name of Arch. Object Type
AO Number AOID Code Generated AOID
Locality WALLDORF WDF (manual) WDF
Bldg complex 1 COM1 (manual) WDFCOM1
Building 2 02 (automatic) WDF02
Part of building A A (automatic) WDF02-A
Floor 4 4 (automatic) WDF02-A4
Room 56 56 WDF02-A4.56
Explanation:
- Where the Use in Subordinate Objects indicator is set, the codes are used as part of the AOID in the next level.
- If a separator was specified, then this is added after the AOID of the object on the previous level. If the indicator is not set (in the example this applies to the building complex), then the code is only used for assigning the AOID of the current object itself (WDFCOM1 in the example).
- If the From AONR indicator is set, then the AOID code is derived from the number. In this case, the system uses the number of places specified in the DefLength field to create the AOID code. In doing so, the system starts from right to left, and adds leading zeros if needed. If there is no value specified for this Def.Length, the system uses the value in the Max.Length field instead.
History
| Last changed by/on | SAP | 20031111 |
| SAP Release Created in | 200 |
