Hierarchy
EA-FIN (Software Component) EA-FIN⤷
RE-FX (Application Component) Flexible Real Estate Management⤷
RE_LD_LD (Package) RE: Logical Databases
Basic Data
| Data Element | RELDISTOPDOWN |
| Short Description | Top-Down Search |
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 | Top-Down? |
| Medium | 15 | Top-Down Search |
| Long | 20 | Top-Down Search? |
| Heading | 4 | TpDw |
Documentation
Definition
- Indicator is set (
'X')
The search in the logical database should be performed from the top down in any case.
- Indicator is not set (
' ')
The search in the logical database should be performed from the bottom up if selection criteria were entered for a hierarchically lower table (this is the default).
In the standard system (the indicator is not set), the search via the logical database is optimized. If selection criteria were entered for a table that is lower in the hierachy, then the system first searches for entries in that table. The higher-level nodes are processed only for those objects, for which hits were found in the lower-level table.
Example
BUSENTITY
BUILDING
RENTALOBJ
In logical database REBD, the user selected (for example, using dynamic selections) rental objects with usage type 1, and did not make any other limitations. The following rental objects exist:
Business Entity Building Rental Object Usage Type
1 10 100 1
1 20 200 5
2 30 300 5
2 30 400 5
3 50 500 1
If the indicator is not set, then the system first selects all rental objects that have usage type 1. Then it checks which buildings and business entities these rental objects belong to. Only these business entities and buildings are supplied in the GET events:
Business entity: 1
->Building: 10
-> -> Rental object 100
Business entity: 3
-> Building: 50
-> -> Rental object: 500
If the indicator is set, then the selection is always top-down. Since no selections are entered for buildings and business entities in the example, then each existing business entity and each existing building is provided in the GET event, even if it does not have a rental object that meets the selection criteria:
Business entity: 1
-> Building: 10
-> -> Rental object: 100
-> Building: 20
Business entity: 2
-> Building: 30
Business entity: 3
-> Building: 50
-> -> Rental object: 500
If the program using the logical database is a report or processing program for rental objects, probably you want to use bottom-up selection. In this case, it can make sense to set the indicator under certain circumstances, if the report itself carries out complex checks on a superior hierarchical level, and these checks cannot be performed by the logical database, and it is to be expected that these checks are more selective than the limitations of the rental object. If needed, the using program can check, at ... late event, if rental objects were selected, and thereby re-create the behavior of the program in the bottom-up case. If this is not done, and the result of the program differs for this reason from the bottom-up search, this should be made clear to the end user in any case.
You can specify the nodes for which a bottom-up search can be started in the STARTNODEBOTTUP field.
History
| Last changed by/on | SAP | 20011002 |
| SAP Release Created in | 110 |
