SAP ABAP Data Element BU_MAXJOIN (Maximum number of tables in a view)
Hierarchy
☛
SAP_ABA (Software Component) Cross-Application Component
⤷
AP-MD-BP (Application Component) SAP Business Partner
⤷
BUPA (Package) SAP Business Partner
SAP_ABA (Software Component) Cross-Application Component⤷
AP-MD-BP (Application Component) SAP Business Partner⤷
BUPA (Package) SAP Business Partner
Basic Data
| Data Element | BU_MAXJOIN |
| Short Description | Maximum number of tables in a view |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | NUMC2 | |
| Data Type | NUMC | Character string with only digits |
| Length | 2 | |
| Decimal Places | 0 | |
| Output Length | 2 | |
| 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 | maxjoin |
| Medium | 15 | maxjoin |
| Long | 20 | maxjoin |
| Heading | 7 | maxjoin |
Documentation
Definition
The BDT search tool generates code with selects in the tables involved. Several tables can be grouped into views for this purpose (with the JOIN command in the FROM clause). This can improve performance in the selection. On the other hand, if too many tables are connected with joins, extremely complex database queries will arise that should then be processed using smaller views to improve performance.
We recommend allowing views of a maximum of 3 tables.
History
| Last changed by/on | SAP | 20010216 |
| SAP Release Created in |
