Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-BMT-OM (Application Component) Organizational Management⤷
SP0E (Package) HR-OM: Organizational Management Enhancements
Basic Data
| Data Element | OMSEANODE |
| Short Description | Object Manager: Search Node in Search Area |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | OMSEANODE | |
| 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 | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Key |
| Medium | 15 | Node Key |
| Long | 20 | Search Node Key |
| Heading | 20 | Search Node Key |
Documentation
Definition
Search nodes group together search tools in the search area of the object manager.
Dependencies
A search node can be based on an object type in table T7780 (in the example below on the object type 'O'), or it can be independent of object type, for example it would be possible to create a search node Search for Last-Used Objects with corresponding search tools. A search node can refer to an object type, it has a name and an icon. The name and the icon are displayed in the object manager search area. If the search node refers to an object type, the object manager displays the search node using the name and the icon stored for the object type in the table T778O, unless another name or icon is entered in the search node definition table (T77FSEAN).
Example
An example of a search node is Organizational Unit. Under this search node you can group together search tools such as Search Term, Free Search und Structure Search, which are all used to search for organizational units.
History
| Last changed by/on | SAP | 20010130 |
| SAP Release Created in |
