Hierarchy
SAP_BS_FND (Software Component) SAP Business Suite Foundation⤷
CA-EPT-BCV (Application Component) Business Context Viewer⤷
/BCV/QRM (Package) BCV Query Management Layer
Basic Data
| Data Element | /BCV/QRM_JOIN_TYPE |
| Short Description | Query Join Type |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | /BCV/QRM_JOIN_TYPE | |
| 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 | JType |
| Medium | 15 | Join Type |
| Long | 20 | Query Join Type |
| Heading | 40 | JT |
Documentation
Definition
Use
In this field, you specify how the system combines the data retrieved from the primary and the secondary search connector. The following values are available:
- Inner Join
The system creates a result record for each data record of the primary search connector and each data record of the secondary search connector that match according to the join criteria you defined. Usually, this type of join is used if the data provided by the secondary search connector is essential for the query results.
- Left Outer Join
The system creates the same result records as in the case of the Inner Join case described above. Additionally, it creates a result record for each data record of the primary search connector for which there is no matching data record of the secondary search connector. Usually, this type of join is used if the data provided by the secondary search connector only provides auxiliary information for the query results.
Dependencies
Example
Assume the primary search connector SCONN1 provides the following data:
SALES_ORDER CUSTOMER DATE
0007 CUST_01 01.01.2009
0012 CUST_01 01.06.2009
0023 CUST_02 01.09.2009
Assume the second search connector SCONN2 provides the following data:
SALES_ORDER ITEM_NUMBER MATERIAL QUANTITY
0007 10 PROD_01 5
0007 20 PROD_02 23
0015 10 PROD_01 2
0023 10 PROD_03 100
Assume further that the join criterion is SCONN1-SALES_ORDER = SCONN2-SALES_ORDER.
In the Inner Join case, the system returns the following result data:
SALES_ORDER CUSTOMER DATE ITEM_NUMBER MATERIAL QUANTITY
0007 CUST_01 01.01.2009 10 PROD_01 5
0007 CUST_01 01.01.2009 20 PROD_02 23
0023 CUST_02 01.09.2009 10 PROD_03 100
In the Left Outer Join case, the system would return the following result data:
SALES_ORDER CUSTOMER DATE ITEM_NUMBER MATERIAL QUANTITY
0007 CUST_01 01.01.2009 10 PROD_01 5
0007 CUST_01 01.01.2009 20 PROD_02 23
0012 CUST_01 01.06.2009
0023 CUST_02 01.09.2009 10 PROD_03 100
History
| Last changed by/on | SAP | 20130604 |
| SAP Release Created in | 702 |
