Hierarchy
SAP_BW (Software Component) SAP Business Warehouse⤷
BW-EI-APD (Application Component) Analysis Process Designer⤷
RSAN_WB (Package) APD - Tool - User Interface
Basic Data
| Data Element | RSAN_WB_DST_JOIN |
| Short Description | Transformation "Join" |
Data Type
| Category of Dictionary Type | Direct Type Entry | |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | ||
| Data Type | STRG | Character String of Variable Length |
| Length | 0 | |
| Decimal Places | 0 | |
| Output Length | 0 | |
| 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 | Text |
| Medium | 20 | Description |
| Long | 40 | Description |
| Heading | 60 | Description |
Documentation
Use
With this transformation you can join two data sources with one or more common fields (database function Join).
Three types of join are supported:
- INNER JOIN: Join data records with identical values in the join fields.
- LEFT OUTER JOIN: In contrast to the INNER JOIN, all data records of the left table occur in the result, even if no corresponding data record is found in the right table.
- FULL OUTER JOIN: This join does more than the LEFT OUTER JOIN; all data records of the right side occur in the result, even if there is no corresponding data record on the left side.
Activities
- Select the fields that you want to pass on to subsequent nodes using the indicator in front of each field. Result structure
- Create a join condition between the fields for the various data sources that are to be joined by drawing a connecting line between the fields with the mouse.
- With the right mouse key, open a context menu on the connecting line and define the type of join (INNER, LEFT OUTER, or FULL OUTER JOIN). We suggest you use an INNER JOIN, which is relevant in the majority of cases.
The INNER JOIN is represented by a solid line, the LEFT OUTER JOIN by an arrow pointing to the right, and the FULL OUTER JOIN by a broken line.
The table to the left is the data source that was joined first with the join node. To swap the left and right tables, select the appropriate option in the context menu.
Example
Data on business partners in an InfoProvider is to be enhanced with attributes from the master data for the Business Partner (0BPARTNER) characteristic. To do this, you join the InfoProvider and the characteristic 0BPARTNER with an inner join with a join condition via the field 0BPARTNER. The required attributes from the master data and the selected fields from the InfoProvider form the output structure of the node. At runtime, the master data from the characteristic is added to each record in the InfoProvider.
Runtime Behavior
The join is performed in ABAP with a sort-merge-join logic. First, the data from the first data source is read and then sorted according to the fields in the join condition. The data from the second data source is then read and in turn is sorted according to the fields in the join condition. Finally, the data from the two tables is merged (merge).
If you have used Goto -> Performance Settings to set the indicator Process Data in Memory, all the data is kept in the main memory when it is sorted. If this indicator is not set, the data is stored in temporary database tables.
If large amounts of master data and DataStore objects are joined in the analysis process, you can improve the performance by moving the join to an InfoSet. Fewer temporary tables will then be required and the join will be performed directly on the database.
History
| Last changed by/on | SAP | 20130604 |
| SAP Release Created in | 30B |
