Transcript
Page 1: Why Doesn't the CompositeProvider Show Any Results?a248.g.akamai.net/n/248/.../sapasset.download.akamai.com/420835/sapcom/docs/2015/07/...SAP NetWeaver Business Warehouse 7.30 (BW7.30)

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 1

Why Doesn't the

Composite Provider Show Any

Results?

Applies to

SAP NetWeaver Business Warehouse 7.30 (BW7.30) SP05 with SAP NetWeaver Business Warehouse Accelerator 7.20 (BWA7.20) or HANA 1.0 running as a database for SAP NetWeaver BW 7.3 SP05

Summary

This article describes how the Join Analysis Methods of the BW Workspace Designer can help the Business Analyst to find out why the newly created data model does not return any values. As a prerequisite we recommend reading the article ‘What is a BW Workspace?’ and ‘How can Central and Local Provider easily be combined?’ from this article series.

Author: Silvia Bratz Company: SAP AG Created: October 2011 Version: 1.0

Author Biography

Silvia Bratz: Development Project Manager, TIP In-Memory Platform BW (SAP AG). Silvia Bratz joined SAP 12 years ago and began working as a technical SAP consultant for Business Intelligence. Today, she is a member of the BWA and Data Management team.

Page 2: Why Doesn't the CompositeProvider Show Any Results?a248.g.akamai.net/n/248/.../sapasset.download.akamai.com/420835/sapcom/docs/2015/07/...SAP NetWeaver Business Warehouse 7.30 (BW7.30)

Why Doesn't the CompositeProvider Show Any Results?

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 2

Table of Contents

1. Introduction ............................................................................................................................................................ 3

2. Check Types and Location ......................................................................................................................................... 3

2.1. Join Fields Analysis (Single Field Link) ......................................................................................................................... 3

2.2. Join Fields Analysis (Selected Provider) ....................................................................................................................... 5

2.3. Join Fields Analysis (All Providers) .............................................................................................................................. 6

2.4. Step-by-Step Provider Join Analysis ............................................................................................................................ 6

3. Scenario ‘No data displayed’ (Step-by-Step Provider Join Analysis) ................................................................................ 7

3.1. Provider Data ........................................................................................................................................................... 7

3.2. CompositeProvider ................................................................................................................................................... 8

3.3. Step-by-Step Provider Join Analysis ............................................................................................................................ 9

3.4. Explanation of Analysis Result ................................................................................................................................. 11

4. Scenario ‘No data displayed’ (Join Fields Analysis (All Providers)) ................................................................................ 27

4.1. Provider Data ......................................................................................................................................................... 27

4.2. CompositeProvider ................................................................................................................................................. 28

4.3. Join Fields Analysis (All Providers) ............................................................................................................................ 28

4.4. Explanation of Analysis Result ................................................................................................................................. 34

5. Scenario ‘Analysis not possible – Empty Provider’ ...................................................................................................... 38

5.1. Provider Data ......................................................................................................................................................... 38

5.2. CompositeProvider ................................................................................................................................................. 38

5.3. Join Analysis – Index created ................................................................................................................................... 39

5.4. Join Analysis – Index formerly filled .......................................................................................................................... 40

6. Scenario ‘Analysis not possible – Provider Inconsistent’ ............................................................................................. 42

6.1. Provider Data ......................................................................................................................................................... 42

6.2. CompositeProvider ................................................................................................................................................. 43

6.3. Explanation of Analysis Result ................................................................................................................................. 44

7. Scenario ‘Join does not operates as a filter’ .............................................................................................................. 45

7.1. Provider Data ......................................................................................................................................................... 45

7.2. CompositeProvider ................................................................................................................................................. 46

7.3. Explanation of Analysis Result ................................................................................................................................. 47

8. Scenario ‘Number of Evaluated Links’ ....................................................................................................................... 48

8.1. Provider Data ......................................................................................................................................................... 48

8.2. CompositeProvider ................................................................................................................................................. 49

8.3. Explanation of Analysis Result ................................................................................................................................. 49

9. Related Content ..................................................................................................................................................... 55 Copyright............................................................................................................................................................................ 56

Page 3: Why Doesn't the CompositeProvider Show Any Results?a248.g.akamai.net/n/248/.../sapasset.download.akamai.com/420835/sapcom/docs/2015/07/...SAP NetWeaver Business Warehouse 7.30 (BW7.30)

Why Doesn't the CompositeProvider Show Any Results?

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 3

1. Introduction

A BW Workspace is a kind of ‘small sandbox’ which IT defines. IT sets the boundaries, IT sets the amount of resources that a BW Workspace can consume and exposes some of the central data models to the BW Workspace (data of the models and their related semantics). The BW Workspace exposes the central data in a logical fashion only. The data is not copied over into the BW Workspace, which means that no data replication is needed. The goal is to enable the Key Business Users to use this functionality in a dedicated and separated environment, which is deeply embedded and integrated in the existing BW landscape. The BW Workspaces bridge the gap between the architected and the departmental data marts. Therefore, Workspaces are integrated, independent and, as the usage of the SAP Business Warehouse Accelerator is mandatory, they are completely in-memory.

2. Check Types and Location

There are different types of checks which can be used in order to find out why a CompositeProvider does not show any values or not the expected ones. There are checks which can be executed per join field or per combination of fields as well as you can execute checks for a single Provider or for all Providers. Finally there is a method which checks the Providers step-wise.

2.1. Join Fields Analysis (Single Field Link)

An analysis can be executed for a single field link. This type of analysis is possible in the mapping step where you link fields, as well as in the graphical and table view on step 2 (Model CompositeProvider). It is the same check as the Join Fields Analysis for a selected or all Providers but executed on basis of the selected field only.

Picture chapter 2.1.: Join Fields Analysis in Step 2a of the CompositeProvider creation

Page 4: Why Doesn't the CompositeProvider Show Any Results?a248.g.akamai.net/n/248/.../sapasset.download.akamai.com/420835/sapcom/docs/2015/07/...SAP NetWeaver Business Warehouse 7.30 (BW7.30)

Why Doesn't the CompositeProvider Show Any Results?

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 4

Picture chapter 2.1.: Join Fields Analysis in Step 2a of the CompositeProvider creation under ‘Details’

Picture chapter 2.1.: Join Fields Analysis in the Graphical View in step 2 of the CompositeProvider creation

Page 5: Why Doesn't the CompositeProvider Show Any Results?a248.g.akamai.net/n/248/.../sapasset.download.akamai.com/420835/sapcom/docs/2015/07/...SAP NetWeaver Business Warehouse 7.30 (BW7.30)

Why Doesn't the CompositeProvider Show Any Results?

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 5

Picture chapter 2.1.: Join Fields Analysis in the Tabular View in step 2 of the CompositeProvider creation

2.2. Join Fields Analysis (Selected Provider)

An analysis can be executed for a single Provider. This type of analysis is possible in step 2 of the CompositeProvider creation and also in the graphical view on basis of a Provider. It is the same check as Join Fields Analysis (All Providers) but executed only for the selected Provider.

Picture chapter 2.2.: Join Fields Analysis (Selected Provider) in CompositeProvider creation

Picture chapter 2.2.: Join Fields Analysis (Selected Provider) in Graphical View

Page 6: Why Doesn't the CompositeProvider Show Any Results?a248.g.akamai.net/n/248/.../sapasset.download.akamai.com/420835/sapcom/docs/2015/07/...SAP NetWeaver Business Warehouse 7.30 (BW7.30)

Why Doesn't the CompositeProvider Show Any Results?

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 6

2.3. Join Fields Analysis (All Providers)

An analysis can be executed for all Providers. This type of analysis is possible in step 2 of the CompositeProvider creation.

Picture chapter 2.3.: Join Fields Analysis(All Providers)

2.4. Step-by-Step Provider Join Analysis

A Step-by-Step Provider Join Analysis can be executed for all Providers. This type of analysis is possible in step 2 of the CompositeProvider creation.

Picture chapter 2.4.: Step-by-Step Provider Join Analysis

Page 7: Why Doesn't the CompositeProvider Show Any Results?a248.g.akamai.net/n/248/.../sapasset.download.akamai.com/420835/sapcom/docs/2015/07/...SAP NetWeaver Business Warehouse 7.30 (BW7.30)

Why Doesn't the CompositeProvider Show Any Results?

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 7

3. Scenario ‘No data displayed’ (Step-by-Step Provider Join Analysis)

In this chapter the check type ‘Step-by-Step Provider Join Analysis’ is explained on the basis of an example with very simple data. It is an example where the CompositeProvider displays no data.

3.1. Provider Data

The CompositeProvider consists of five Local Providers which have been created in the Analysis Process Designer. These Providers contain the following fields and data.

Picture chapter 3.1.: Provider @3AINUNI1

Picture chapter 3.1.: Provider @3AIINJ1

Picture chapter 3.1.: Provider @3AIINJ2

Picture chapter 3.1.: Provider @3AIINJ3

Page 8: Why Doesn't the CompositeProvider Show Any Results?a248.g.akamai.net/n/248/.../sapasset.download.akamai.com/420835/sapcom/docs/2015/07/...SAP NetWeaver Business Warehouse 7.30 (BW7.30)

Why Doesn't the CompositeProvider Show Any Results?

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 8

Picture chapter 3.1.: Provider @3AIINJ4

3.2. CompositeProvider

Provider ‘AINUNI1’ is linked with connection type union to the CompositeProvider ‘JA_SCENI1A (Scenario 1a which Provider fields prevent a result)’. All other Providers are linked with connection type inner join. The blue lines show the fields which are joined to the CompositeProvider. Some fields and some fields are not linked at all (shown in light grey).

Picture chapter 3.2.: Graphical View of CompositeProvider JA_SCENI1A (Scenario 1a which Provider fields prevent a result)

Picture chapter 3.2.: Tabular View of CompositeProvider JA_SCENI1A (Scenario 1a which Provider fields prevent a result)

Picture chapter 3.2.: Display Data of CompositeProvider does not show any values

Page 9: Why Doesn't the CompositeProvider Show Any Results?a248.g.akamai.net/n/248/.../sapasset.download.akamai.com/420835/sapcom/docs/2015/07/...SAP NetWeaver Business Warehouse 7.30 (BW7.30)

Why Doesn't the CompositeProvider Show Any Results?

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 9

3.3. Step-by-Step Provider Join Analysis

Execute the analysis:

Picture chapter 3.3.: Step-by-Step Provider Join Analysis

Picture chapter 3.3.: Progress of the Step-by-Step Provider Join Analysis

Picture chapter 3.3.: Graphical View A Step-by-Step Provider Join Analysis leads to the following results:

Page 10: Why Doesn't the CompositeProvider Show Any Results?a248.g.akamai.net/n/248/.../sapasset.download.akamai.com/420835/sapcom/docs/2015/07/...SAP NetWeaver Business Warehouse 7.30 (BW7.30)

Why Doesn't the CompositeProvider Show Any Results?

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 10

Picture chapter 3.3.: Result of Step-by-Step Provider Join Analysis *The join with ‘aiinj3’ does not return any values.

Picture chapter 3.3.: Result of Step-by-Step Provider Join Analysis also displaying the last lines when scrolled-down. The yellow line shows if a join operates as a filter. *The join with ‘aiinj3’ does not return any values.

Yellow

Yellow

Yellow

Yellow

Join functions as a filter Join does not function as a filter (Left outer)

Join functions as a filter Join does not function as a filter (Left outer)

*

Provider ‚aiinj3‘ is responsible for the empty result set

* This field link (JACHA3) is responsible for the empty result set see chapter ‘3.4. Explanation of Analysis Result’

Page 11: Why Doesn't the CompositeProvider Show Any Results?a248.g.akamai.net/n/248/.../sapasset.download.akamai.com/420835/sapcom/docs/2015/07/...SAP NetWeaver Business Warehouse 7.30 (BW7.30)

Why Doesn't the CompositeProvider Show Any Results?

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 11

3.4. Explanation of Analysis Result

What is that analysis result supposed to mean? The following explanations describe the contents of each line of the analysis result.

1. Union part versus Join of Provider AIINJ1

Picture chapter 3.4.: Union part versus Join of Provider AIINJ1

Picture chapter 3.4./1: Union part versus Join of Provider AIINJ1

Line 1: Only the union part (Provider AINUNI1) is investigated without any joined Provider. The distinct values of the linked fields (from union part to the CompositeProvider) are taken into account (see Picture chapter 3.4./1). In the Result line the number of distinct values is shown. This value is determined by the calculation engine.

Picture chapter 3.4.: Union part

Line 1

Line 2

Line 3

Line 1

Line 2

Page 12: Why Doesn't the CompositeProvider Show Any Results?a248.g.akamai.net/n/248/.../sapasset.download.akamai.com/420835/sapcom/docs/2015/07/...SAP NetWeaver Business Warehouse 7.30 (BW7.30)

Why Doesn't the CompositeProvider Show Any Results?

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 12

Picture chapter 3.4.: Distinct Characteristic Values of Provider AINUNI1 for fields JACHA1, JACHA3 and JACHA6 Line 2: Provider AIINJ1 is investigated ‘stand-alone’ without the union part or any other joined Provider (see Picture chapter 3.4./1). The distinct values of the joined fields of Provider AIINJ1 are taken into account. This result value is determined by the calculation engine.

Picture chapter 3.4.: Provider AIINJ1

Page 13: Why Doesn't the CompositeProvider Show Any Results?a248.g.akamai.net/n/248/.../sapasset.download.akamai.com/420835/sapcom/docs/2015/07/...SAP NetWeaver Business Warehouse 7.30 (BW7.30)

Why Doesn't the CompositeProvider Show Any Results?

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 13

Picture chapter 3.4.: Distinct Characteristic Values of Provider AIINJ1 for fields JACHA1, JACHA3 and JACHA6

Line 3:

Picture chapter 3.4.: Intersection

The intersection of Line 1 and Line 2 is executed by the calculation engine. The result set are the matching distinct values.

Page 14: Why Doesn't the CompositeProvider Show Any Results?a248.g.akamai.net/n/248/.../sapasset.download.akamai.com/420835/sapcom/docs/2015/07/...SAP NetWeaver Business Warehouse 7.30 (BW7.30)

Why Doesn't the CompositeProvider Show Any Results?

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 14

Picture chapter 3.4.: Matching Distinct Characteristic Values (intersection) when AIINJ1 has been joined to the union part AINUNI1 with regards to fields JACHA1, JACHA3 and JACHA6

2. Union part and Join of Provider AIINJ1 versus Provider AIINJ2

Picture chapter 3.4.: Union part and Join of Provider AIINJ1 versus Provider AIINJ2

Line 1

Line 2

Line 3

Page 15: Why Doesn't the CompositeProvider Show Any Results?a248.g.akamai.net/n/248/.../sapasset.download.akamai.com/420835/sapcom/docs/2015/07/...SAP NetWeaver Business Warehouse 7.30 (BW7.30)

Why Doesn't the CompositeProvider Show Any Results?

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 15

Picture chapter 3.4./2: Union part and Join of Provider AIINJ1 versus Provider AIINJ2

Line 1: Now the union part and the Provider checked under ‘1. Union part and Join of Provider AIINJ1’, are investigated (AINUNI1 + AIINJ1) see Picture chapter 3.4./2. The distinct values of ’AINUNI1 + AIINJ1’ are determined with regards to the joined fields (JACHA1, JACHA3) with ‘AIINJ2’. In the Result line the number of distinct values is shown (determined by the calculation engine).

Picture chapter 3.4.: Union part and Join of Provider AIINJ1

Line 1

Line 2

Page 16: Why Doesn't the CompositeProvider Show Any Results?a248.g.akamai.net/n/248/.../sapasset.download.akamai.com/420835/sapcom/docs/2015/07/...SAP NetWeaver Business Warehouse 7.30 (BW7.30)

Why Doesn't the CompositeProvider Show Any Results?

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 16

Picture chapter 3.4.: Distinct Characteristic Values of Provider AINUNI1 + AIINJ1 for fields JACHA1 and JACHA3

Line 2:

Picture chapter 3.4.: Provider AIINJ2

Provider ‘AIINJ2' is investigated stand-alone without the union part or other joined parts (Picture chapter 3.4./2). The distinct values are determined by the calculation engine with regards to the joined fields ‘JACHA1, JACHA3’ of Provider ‘AIINJ2'.

Page 17: Why Doesn't the CompositeProvider Show Any Results?a248.g.akamai.net/n/248/.../sapasset.download.akamai.com/420835/sapcom/docs/2015/07/...SAP NetWeaver Business Warehouse 7.30 (BW7.30)

Why Doesn't the CompositeProvider Show Any Results?

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 17

Picture chapter 3.4.: Distinct Characteristic Values of Provider AIINJ2 for fields JACHA1 and JACHA3

Line 3:

Picture chapter 3.4.: Intersection

The intersection of Line 1 and Line 2 is executed by the calculation engine. These six values remain when Provider ‘AIINJ2’ has been joined in addition.

Page 18: Why Doesn't the CompositeProvider Show Any Results?a248.g.akamai.net/n/248/.../sapasset.download.akamai.com/420835/sapcom/docs/2015/07/...SAP NetWeaver Business Warehouse 7.30 (BW7.30)

Why Doesn't the CompositeProvider Show Any Results?

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 18

Picture chapter 3.4.: Matching Distinct Values (intersection) of union part + AIINJ1 + AIINJ2 with regards to joined fields JACHA1 and JACHA3

This procedure is done until all joined Providers have been added or until the first intersection (Line 3) shows the value 0 which is an indicator which added Provider is responsible that no data can be retrieved. 3. Union part and Join of Provider AIINJ1 + AIINJ2 versus Provider AIINJ3

Picture chapter 3.4.: Union part and Join of Provider AIINJ1 + AIINJ2 versus Provider AIINJ3

Line 1

Line 2

Line 3

Line 4

Page 19: Why Doesn't the CompositeProvider Show Any Results?a248.g.akamai.net/n/248/.../sapasset.download.akamai.com/420835/sapcom/docs/2015/07/...SAP NetWeaver Business Warehouse 7.30 (BW7.30)

Why Doesn't the CompositeProvider Show Any Results?

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 19

Picture chapter 3.4./3: Union part and Join of Provider AIINJ1 + AIINJ2 versus Provider AIINJ3 Line 1: Now the union part and the Providers checked before, are investigated (AINUNI1 + AIINJ1 + AIINJ2) see Picture chapter 3.4./3.The distinct values of the joined fields with AIINJ3 are taken into account. In the Result line the number of distinct values is shown (determined by the calculation engine).

Picture chapter 3.4.: Union part and Join of Provider AIINJ1 + AIINJ2

Line 1

Line 2

Page 20: Why Doesn't the CompositeProvider Show Any Results?a248.g.akamai.net/n/248/.../sapasset.download.akamai.com/420835/sapcom/docs/2015/07/...SAP NetWeaver Business Warehouse 7.30 (BW7.30)

Why Doesn't the CompositeProvider Show Any Results?

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 20

Picture chapter 3.4.: Distinct Characteristic Values of Provider AINUNI1 + AIINJ1+ AIINJ2 for fields JACHA1 and JACHA3

Line 2:

Picture chapter 3.4.: Provider AIINJ3

Provider ‘AIINJ3' is investigated stand-alone without the union part or other joined parts (Picture chapter 3.4./3). The number of distinct values of Provider ’AIINJ3’ is determined with regards to the joined fields ‘JACHA1 and JACHA3’ (determined by the calculation engine).

Page 21: Why Doesn't the CompositeProvider Show Any Results?a248.g.akamai.net/n/248/.../sapasset.download.akamai.com/420835/sapcom/docs/2015/07/...SAP NetWeaver Business Warehouse 7.30 (BW7.30)

Why Doesn't the CompositeProvider Show Any Results?

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 21

Picture chapter 3.4.: Distinct Characteristic Values of Provider AIINJ3 for fields JACHA1 and JACHA3

Line 3:

Picture chapter 3.4.: Intersection; *The join with ‘aiinj3’ does not return any values. The intersection of Line 1 and Line 2 is executed by the calculation engine.

There are no matching values anymore when Provider ‘AIINJ3’ is joined.

*

Page 22: Why Doesn't the CompositeProvider Show Any Results?a248.g.akamai.net/n/248/.../sapasset.download.akamai.com/420835/sapcom/docs/2015/07/...SAP NetWeaver Business Warehouse 7.30 (BW7.30)

Why Doesn't the CompositeProvider Show Any Results?

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 22

Picture chapter 3.4.: No Matching Distinct Values (intersection) of union part + AIINJ1 + AIINJ2 + AIINJ3 with regards to joined fields JACHA1 and JACHA3

Line 4: Line 4 shows the information that the join with Provider ‘AIINJ3’ supplies no values.

Which join field actually is responsible that no values show up?

Picture chapter 3.4.: Responsible Field

The final finding is that field JACHA3 is responsible that no data is displayed at all. Remark: It could be that each single joined field has matching values but not the combination of fields. Therefore also the join combinations are investigated.

Page 23: Why Doesn't the CompositeProvider Show Any Results?a248.g.akamai.net/n/248/.../sapasset.download.akamai.com/420835/sapcom/docs/2015/07/...SAP NetWeaver Business Warehouse 7.30 (BW7.30)

Why Doesn't the CompositeProvider Show Any Results?

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 23

Remove the link for field JACHA3 for Provider ‘AIINJ3’:

Picture chapter 3.4.: Removal of field link

Execute ‘Display Data’ after removing the field link of JACHA3:

Picture chapter 3.4.: Display Data; The table does not contain any data

Why does no data show up? Let us execute the Step-by-Step Provider Join Analysis again after having removed the link of field JACHA3 of Provider ‘AIINJ3’.

Page 24: Why Doesn't the CompositeProvider Show Any Results?a248.g.akamai.net/n/248/.../sapasset.download.akamai.com/420835/sapcom/docs/2015/07/...SAP NetWeaver Business Warehouse 7.30 (BW7.30)

Why Doesn't the CompositeProvider Show Any Results?

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 24

Picture chapter 3.4.: Result of Step-by-Step Provider Join Analysis after Link removal

Picture chapter 3.4.: Result of Step-by-Step Provider Join Analysis after Link removal; Result of Step-by-Step Provider Join Analysis also displaying the last line when scrolled-down; The yellow line shows if a join operates as a filter. *The join with ‘aiinj4’ does not return any values.

Yellow

Yellow

Yellow

Yellow

Join functions as a filter Join does not function as a filter (Left outer)

Join functions as a filter Join does not function as a filter (Left outer)

*

Page 25: Why Doesn't the CompositeProvider Show Any Results?a248.g.akamai.net/n/248/.../sapasset.download.akamai.com/420835/sapcom/docs/2015/07/...SAP NetWeaver Business Warehouse 7.30 (BW7.30)

Why Doesn't the CompositeProvider Show Any Results?

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 25

Picture chapter 3.4.: *The join with ‘aiinj4’ does not return any values.

Picture chapter 3.4./4: Union part and Join of Provider AIINJ1 + AIINJ2 + AIINJ3 versus Provider AIINJ4 Now we can see that in case field ‘JACHA3’ of Provider ‘AIINJ3’ is removed, 2 values match. But: There is a forth Provider (AIINJ4) which we attached to the data model via inner join. But none of its characteristic values would lead to a result.

Yellow

*

Line 1

Line 2

Page 26: Why Doesn't the CompositeProvider Show Any Results?a248.g.akamai.net/n/248/.../sapasset.download.akamai.com/420835/sapcom/docs/2015/07/...SAP NetWeaver Business Warehouse 7.30 (BW7.30)

Why Doesn't the CompositeProvider Show Any Results?

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 26

So let us also remove Provider ‘AIINJ4’:

Picture chapter 3.4.: Removal of Provider AIINJ4

With these join combinations a result is displayed:

Picture chapter 3.4.: Display Data

Page 27: Why Doesn't the CompositeProvider Show Any Results?a248.g.akamai.net/n/248/.../sapasset.download.akamai.com/420835/sapcom/docs/2015/07/...SAP NetWeaver Business Warehouse 7.30 (BW7.30)

Why Doesn't the CompositeProvider Show Any Results?

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 27

4. Scenario ‘No data displayed’ (Join Fields Analysis (All Providers))

The Join Fields Analysis (All Providers) delivers results quickly when only one Provider is responsible that no data is displayed. In the scenario chapter 3 one complete Provider and one field of another Provider were responsible that no values showed up. In that case the Join Fields Analysis (All Providers) would not have been of great help in contrast to the Step-by-Step method. If only one Provider causes an empty result is quite obvious when the Join Fields Analysis (All Providers) is executed see the following scenario 4.1./4.2. Therefore we slightly changed the data contents of the scenario above (see green lines in the tables below). Then we show the execution of the Join Fields Analysis for all Providers. The Join Field Analysis is especially recommended to be executed on one single Provider linked with inner join when a scenario contains e.g. only one Provider connected with inner join and all other Providers connected with union or left outer join. As only the inner join can act as a filter the Join Fields Analysis (Selected Provider) will help you to save analysis time which would be necessary to execute the Join Fields Analysis for all connected Providers or the Step-by-Step Analysis for all connected Providers.

4.1. Provider Data

Picture chapter 4.1.: Provider @3AINUNI1 - changed

Picture chapter 4.1.: Provider @3AIINJ1 - changed

Page 28: Why Doesn't the CompositeProvider Show Any Results?a248.g.akamai.net/n/248/.../sapasset.download.akamai.com/420835/sapcom/docs/2015/07/...SAP NetWeaver Business Warehouse 7.30 (BW7.30)

Why Doesn't the CompositeProvider Show Any Results?

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 28

Picture chapter 4.1.: Provider @3AIINJ2 - changed

Picture chapter 4.1.: Provider @3AIINJ3

Picture chapter 4.1.: Provider @3AIINJ4

4.2. CompositeProvider

We are using the same CompositeProvider model see chapter 3.2 above. The additional data (green lines in table above) has been loaded to the Providers. No data is displayed when you go to ‘Display Data’.

4.3. Join Fields Analysis (All Providers)

Execute the Join Fields Analysis (All Providers):

Picture chapter 4.2.: Execution of Join Fields Analysis (All Providers)

The Join Fields Analysis (All Providers) investigates the Composite Provider by always excluding the one Provider which is displayed in the result in column 1 (Provider). The Join Fields Analysis (All Providers) approach shows the following results. The following screenshots show the investigated Provider combinations and the corresponding detailed check results.

Page 29: Why Doesn't the CompositeProvider Show Any Results?a248.g.akamai.net/n/248/.../sapasset.download.akamai.com/420835/sapcom/docs/2015/07/...SAP NetWeaver Business Warehouse 7.30 (BW7.30)

Why Doesn't the CompositeProvider Show Any Results?

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 29

Picture chapter 4.3./1: Link combinations without Provider AIINJ1

Picture chapter 4.3./1: Link combinations without Provider AIINJ1

Evaluation of all link combinations without AIINJ1

Page 30: Why Doesn't the CompositeProvider Show Any Results?a248.g.akamai.net/n/248/.../sapasset.download.akamai.com/420835/sapcom/docs/2015/07/...SAP NetWeaver Business Warehouse 7.30 (BW7.30)

Why Doesn't the CompositeProvider Show Any Results?

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 30

Picture chapter 4.3./1: Link combinations without Provider AIINJ1

Picture chapter 4.3./1: Link combinations without Provider AIINJ1

Page 31: Why Doesn't the CompositeProvider Show Any Results?a248.g.akamai.net/n/248/.../sapasset.download.akamai.com/420835/sapcom/docs/2015/07/...SAP NetWeaver Business Warehouse 7.30 (BW7.30)

Why Doesn't the CompositeProvider Show Any Results?

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 31

Picture chapter 4.3./2: Link combinations without Provider AIINJ2

Picture chapter 4.3./2: Link combinations without Provider AIINJ2

Picture chapter 4.3./2: Link combinations without Provider AIINJ2

Evaluation of all link combinations without AIINJ2

Page 32: Why Doesn't the CompositeProvider Show Any Results?a248.g.akamai.net/n/248/.../sapasset.download.akamai.com/420835/sapcom/docs/2015/07/...SAP NetWeaver Business Warehouse 7.30 (BW7.30)

Why Doesn't the CompositeProvider Show Any Results?

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 32

Picture chapter 4.3./3: Link combinations without Provider AIINJ3

Picture chapter 4.3./3: Link combinations without Provider AIINJ3

Evaluation of all link combinations without AIINJ3

Page 33: Why Doesn't the CompositeProvider Show Any Results?a248.g.akamai.net/n/248/.../sapasset.download.akamai.com/420835/sapcom/docs/2015/07/...SAP NetWeaver Business Warehouse 7.30 (BW7.30)

Why Doesn't the CompositeProvider Show Any Results?

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 33

Picture chapter 4.3./4: Link combinations without Provider AIINJ4

Picture chapter 4.3./4: Link combinations without Provider AIINJ4

Evaluation of all link combinations without AIINJ4

Page 34: Why Doesn't the CompositeProvider Show Any Results?a248.g.akamai.net/n/248/.../sapasset.download.akamai.com/420835/sapcom/docs/2015/07/...SAP NetWeaver Business Warehouse 7.30 (BW7.30)

Why Doesn't the CompositeProvider Show Any Results?

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 34

4.4. Explanation of Analysis Result

In order to explain the result lines we use the last five lines of the analysis result for Provider ‘AIINJ4’. Nevertheless the same applies to all five lines per Provider/Field(s) combination.

Picture chapter 4.4.: Analysis Result

Line 1: This line represents the number of distinct values for field combination JACHA1 and JACHA3 of the union part and all joined Providers when Provider ‘AIINJ4’ is excluded (see Picture chapter 4.3./4). This value is determined by the calculation engine.

Picture chapter 4.4.: Provider @3AINUNI1 - changed

Picture chapter 4.4.: Provider @3AIINJ1 - changed

Line 1

Line 2

Line 3

Line 4

Line 5

Distinct values A AA A AB A AC B BA B BB B BC C CA C CB C CC A AAA

Distinct values A AA A AB A AC B BA B BB B BC C CA C CB C CC A AAA

Page 35: Why Doesn't the CompositeProvider Show Any Results?a248.g.akamai.net/n/248/.../sapasset.download.akamai.com/420835/sapcom/docs/2015/07/...SAP NetWeaver Business Warehouse 7.30 (BW7.30)

Why Doesn't the CompositeProvider Show Any Results?

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 35

Picture chapter 4.4.: Provider @3AIINJ2 - changed

Picture chapter 4.4.: Provider @3AIINJ3

Picture chapter 4.4.: Provider @3AIINJ4

Picture chapter 4.4.: Distinct Characteristic Value in Line 1

Line 2: Line 2 displays the number of distinct values for field combination JACHA1 and JACHA3 in Provider ‘AIINJ4’. This value is determined by the calculation engine.

Picture chapter 4.4.: Provider @3AIINJ4

Distinct values A AA A AB A AC B BA B BB B BC A AAA

Distinct values A AAA B AAA

Distinct values Z AAA

Distinct values Z AAA

Page 36: Why Doesn't the CompositeProvider Show Any Results?a248.g.akamai.net/n/248/.../sapasset.download.akamai.com/420835/sapcom/docs/2015/07/...SAP NetWeaver Business Warehouse 7.30 (BW7.30)

Why Doesn't the CompositeProvider Show Any Results?

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 36

Picture chapter 4.4.: Distinct Characteristic Value in Line 2

Line 3: No values match for intersection of Line 1 and Line 2. This value is determined by the calculation engine. Line 4: Line 4 represents the subtraction of Line 1 and Line 3 (1-3). Line 5: Line 5 represents the subtraction of Line 2 and Line 3 (2-3).

Page 37: Why Doesn't the CompositeProvider Show Any Results?a248.g.akamai.net/n/248/.../sapasset.download.akamai.com/420835/sapcom/docs/2015/07/...SAP NetWeaver Business Warehouse 7.30 (BW7.30)

Why Doesn't the CompositeProvider Show Any Results?

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 37

How could I proceed and find out which values prevent a result? Step 1: Scan the output first for the field combinations (concatenation) where the lines are marked in yellow and where the result is Zero for ‘Matching Values. Step 2: Then have a look which field(s) of the field combination has (have) a Zero for ‘Matching Values’ in the line marked in yellow. Step 3: In this part of the analysis go to Line 5 (Non-Matching Values in Provider ‘AIINJ4’). Here you will find out which field(s) and characteristic value(s) is (are) responsible that no values are displayed. In this scenario you will find out that field JACHA1 with characteristic value ‘Z’ is the responsible field that no values are shown in ‘Display Data’:

Picture chapter 4.4.: Distinct Characteristic Value in Line 5

Line 1

Line 2

Line 3

Line 4

Line 5

Step 2

Step 3

Step 1

Yellow

Yellow

Page 38: Why Doesn't the CompositeProvider Show Any Results?a248.g.akamai.net/n/248/.../sapasset.download.akamai.com/420835/sapcom/docs/2015/07/...SAP NetWeaver Business Warehouse 7.30 (BW7.30)

Why Doesn't the CompositeProvider Show Any Results?

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 38

5. Scenario ‘Analysis not possible – Empty Provider’

5.1. Provider Data

See chapter 4.1., but Provider ‘AIINJ4’ has been exchanged with Provider ‘AIINJ4_EMPTY’ with same field definition.

5.2. CompositeProvider

Picture chapter 5.2.: Graphical View of CompositeProvider JA_SCEN1B (Scenario 1b with empty Provider)

Page 39: Why Doesn't the CompositeProvider Show Any Results?a248.g.akamai.net/n/248/.../sapasset.download.akamai.com/420835/sapcom/docs/2015/07/...SAP NetWeaver Business Warehouse 7.30 (BW7.30)

Why Doesn't the CompositeProvider Show Any Results?

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 39

5.3. Join Analysis – Index created

The Provider ‘AIINJ4_EMPTY’ has been created but not filled. The system makes you aware that the Provider does not contain any data as a special error code from the aggregation engine can be retrieved in this case.

Picture chapter 5.3.: Step-by-Step Join Fields Analysis of CompositeProvider JA_SCEN1B (Scenario 1b with empty Provider)

Picture chapter 5.3.: Join Fields Analysis (All Providers) of CompositeProvider JA_SCEN1B (Scenario 1b with empty Provider)

Join functions as a filter Join does not function as a filter (Left outer)

Page 40: Why Doesn't the CompositeProvider Show Any Results?a248.g.akamai.net/n/248/.../sapasset.download.akamai.com/420835/sapcom/docs/2015/07/...SAP NetWeaver Business Warehouse 7.30 (BW7.30)

Why Doesn't the CompositeProvider Show Any Results?

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 40

5.4. Join Analysis – Index formerly filled

The Provider ‘AIINJ4_EMPTY’ has been filled with data first. The data then has been deleted in transaction RSDD_LTIP at a later point in time. After the deletion of data the analysis is called again. In this case the system is not aware anymore that the Provider does not contain any data as no special error code is sent from the aggregation engine. Anyhow the ‘Zero’ in Line 2 of the Provider analysis shows that it does not contain any data.

Picture chapter 5.4.: Deletion of all Provider Data (AIINJ4_EMPTY) in transaction RSDD_LTIP

Picture chapter 5.4.: Step-by-Step Provider Join Analysis of CompositeProvider JA_SCEN1B (Scenario 1b with empty Provider)

Line 2

Join functions as a filter Join does not function as a filter (Left outer)

Page 41: Why Doesn't the CompositeProvider Show Any Results?a248.g.akamai.net/n/248/.../sapasset.download.akamai.com/420835/sapcom/docs/2015/07/...SAP NetWeaver Business Warehouse 7.30 (BW7.30)

Why Doesn't the CompositeProvider Show Any Results?

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 41

Picture chapter 5.4.: Join Fields Analysis (All Providers) of CompositeProvider JA_SCEN1B (Scenario 1b with empty Provider)

Join functions as a filter Join does not function as a filter (Left outer)

Page 42: Why Doesn't the CompositeProvider Show Any Results?a248.g.akamai.net/n/248/.../sapasset.download.akamai.com/420835/sapcom/docs/2015/07/...SAP NetWeaver Business Warehouse 7.30 (BW7.30)

Why Doesn't the CompositeProvider Show Any Results?

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 42

6. Scenario ‘Analysis not possible – Provider Inconsistent’

6.1. Provider Data

Picture chapter 6.1.: Provider @3ORDER_HEADER

Picture chapter 6.1.: Provider @3INVOICE_HEADER

Picture chapter 6.1.: Provider @3INVOICE_ITEM

Page 43: Why Doesn't the CompositeProvider Show Any Results?a248.g.akamai.net/n/248/.../sapasset.download.akamai.com/420835/sapcom/docs/2015/07/...SAP NetWeaver Business Warehouse 7.30 (BW7.30)

Why Doesn't the CompositeProvider Show Any Results?

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 43

6.2. CompositeProvider

Picture chapter 6.2.: Graphical view of CompositeProvider JA_IMP1A (Join analysis impossible - inconsistent Provider) – Display CompositeProvider

Picture chapter 6.2.: Graphical view of CompositeProvider JA_IMP1A (Join analysis impossible - inconsistent Provider) – Display Join only

The field ‘ITEM’ of Provider ‘Invoice_Item’ is mapped to the CompositeProvider via Provider ‘Invoice_Header’. Fields OHEADER and IHEADER are mapped directly.

Picture chapter 6.2.: Header Field Link

Picture chapter 6.2.: Item Field Link

Page 44: Why Doesn't the CompositeProvider Show Any Results?a248.g.akamai.net/n/248/.../sapasset.download.akamai.com/420835/sapcom/docs/2015/07/...SAP NetWeaver Business Warehouse 7.30 (BW7.30)

Why Doesn't the CompositeProvider Show Any Results?

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 44

6.3. Explanation of Analysis Result

The Step-by-Step Provider Join Analysis can be executed as usual as the Providers which are directly mapped to the CompositeProvider are added first in the analysis. Therefore it cannot happen that the CompositeProvider gets inconsistent.

Picture chapter 6.3.: Step-by-Step Provider Join Analysis

This is different when the Join Fields Analysis (All Providers) is executed where always one Provider is excluded for the analysis of the rest of the CompositeProvider. Excluding the Provider ‘invoice_header’ (which is done when the Join Fields Analysis is executed) brings the CompositeProvider into an inconsistent state. Provider ‘invoice_item’ is not connected anymore to the CompositeProvider when Provider ‘invoice_header’ has been removed. The system makes you aware of this behaviour.

Join functions as a filter Join does not function as a filter (Left outer)

Page 45: Why Doesn't the CompositeProvider Show Any Results?a248.g.akamai.net/n/248/.../sapasset.download.akamai.com/420835/sapcom/docs/2015/07/...SAP NetWeaver Business Warehouse 7.30 (BW7.30)

Why Doesn't the CompositeProvider Show Any Results?

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 45

Picture chapter 6.3.: Join Fields Analysis (All Providers)

7. Scenario ‘Join does not operates as a filter’

This example shows under which conditions a joined Provider operates as a filter and where it does not.

7.1. Provider Data

Picture chapter 7.1.: Provider @3AIUNI5

Picture chapter 7.1.: Provider @3AIINJ5

Picture chapter 7.1.: Provider @3AIINJ6

Join functions as a filter Join does not function as a filter (Left outer)

Page 46: Why Doesn't the CompositeProvider Show Any Results?a248.g.akamai.net/n/248/.../sapasset.download.akamai.com/420835/sapcom/docs/2015/07/...SAP NetWeaver Business Warehouse 7.30 (BW7.30)

Why Doesn't the CompositeProvider Show Any Results?

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 46

Picture chapter 7.1.: Provider @3AILOJ6

Picture chapter 7.1.: Provider @3AILOJ7

7.2. CompositeProvider

In this scenario the Providers ‘AILOJ6’ and ‘AILOJ7’ are linked with connection type ‘Left outer join’.

Picture chapter 7.2.: Table View of CompositeProvider JA_FILTER (Does the join operate as a filter?)

Picture chapter 7.2.: Graphical View of CompositeProvider JA_FILTER (Does the join operate as a filter?)

Page 47: Why Doesn't the CompositeProvider Show Any Results?a248.g.akamai.net/n/248/.../sapasset.download.akamai.com/420835/sapcom/docs/2015/07/...SAP NetWeaver Business Warehouse 7.30 (BW7.30)

Why Doesn't the CompositeProvider Show Any Results?

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 47

7.3. Explanation of Analysis Result

Picture chapter 7.3.: When does a join operate as a filter?

The lines highlighted in yellow show up when a join operates as a filter. When a join is defined as a left outer join it never filters any values and is therefore highlighted in another colour (green). A join operates as a filter, when:

o The join type is inner AND o (Line 1 minus Line 3) > 0 (= not all values match; therefore the join operates as filter)

A join does not operate as a filter, when:

o The join type is left outer OR o (Line 1 minus Line 3) = 0 (= all values match; therefore the join does not operate as

filter)

Picture chapter 7.3.: Display Data (2 Matching Values)

Join functions as a filter Join does not function as a filter (Left outer)

Yellow

Green

Green

Line 1

Line 2

Line 3

Line 1

Line 2

Line 3

Line 1

Line 2

Line 3

Line 1

Line 2

Line 3

No filter as 4-4 = 0, although it is an inner join

Filter as inner join AND 4-2 > 0

No filter as left outer join, also 2-2 = 0

No filter as left outer join

Page 48: Why Doesn't the CompositeProvider Show Any Results?a248.g.akamai.net/n/248/.../sapasset.download.akamai.com/420835/sapcom/docs/2015/07/...SAP NetWeaver Business Warehouse 7.30 (BW7.30)

Why Doesn't the CompositeProvider Show Any Results?

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 48

8. Scenario ‘Number of Evaluated Links’

When a joined Provider is connected with up to 5 field links all join combinations of these field links are investigated. In case a joined Provider is linked with more than 5 field links the field combinations (concatenations) are not taken into account anymore due to performance reasons.

8.1. Provider Data

Picture chapter 8.1.: Provider @3AIUNI8

Picture chapter 8.1.: Provider @3AIINJ8

Picture chapter 8.1.: Provider @3AIINJ9

Page 49: Why Doesn't the CompositeProvider Show Any Results?a248.g.akamai.net/n/248/.../sapasset.download.akamai.com/420835/sapcom/docs/2015/07/...SAP NetWeaver Business Warehouse 7.30 (BW7.30)

Why Doesn't the CompositeProvider Show Any Results?

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 49

8.2. CompositeProvider

Picture chapter 8.2.: Graphical View of CompositeProvider JA_SCEN1C (Scenario 1c with more than 5 links for Provider ‘AIINJ9’)

8.3. Explanation of Analysis Result

When the Step-by-Step Provider Join Analysis is executed all fields per Provider are taken into account.

Picture chapter 8.3.: Step-by-Step Join Analysis When the Join Fields Analysis (All Providers) is executed for a Provider with <= 5 field links, all single fields and all combinations of fields per Provider are taken into account.

6 field links defined for ‚AIINJ9‘

Join functions as a filter Join does not function as a filter (Left outer)

Page 50: Why Doesn't the CompositeProvider Show Any Results?a248.g.akamai.net/n/248/.../sapasset.download.akamai.com/420835/sapcom/docs/2015/07/...SAP NetWeaver Business Warehouse 7.30 (BW7.30)

Why Doesn't the CompositeProvider Show Any Results?

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 50

Picture chapter 8.3.: Join Fields Analysis (All Providers)

Check of all 5 single fields

Page 51: Why Doesn't the CompositeProvider Show Any Results?a248.g.akamai.net/n/248/.../sapasset.download.akamai.com/420835/sapcom/docs/2015/07/...SAP NetWeaver Business Warehouse 7.30 (BW7.30)

Why Doesn't the CompositeProvider Show Any Results?

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 51

Picture chapter 8.3.: Join Fields Analysis (All Providers)

Check of two concatenated fields = 10 combi-nations

Page 52: Why Doesn't the CompositeProvider Show Any Results?a248.g.akamai.net/n/248/.../sapasset.download.akamai.com/420835/sapcom/docs/2015/07/...SAP NetWeaver Business Warehouse 7.30 (BW7.30)

Why Doesn't the CompositeProvider Show Any Results?

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 52

Picture chapter 8.3.: Join Fields Analysis (All Providers)

Check of three concatenated fields = 10 combina- tions

Page 53: Why Doesn't the CompositeProvider Show Any Results?a248.g.akamai.net/n/248/.../sapasset.download.akamai.com/420835/sapcom/docs/2015/07/...SAP NetWeaver Business Warehouse 7.30 (BW7.30)

Why Doesn't the CompositeProvider Show Any Results?

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 53

Picture chapter 8.3.: Join Fields Analysis (All Providers)

Picture chapter 8.3.: Join Fields Analysis (All Providers) When the Join Fields Analysis (All Providers) is executed for a Provider with > 5 field links, the single fields per Provider are taken into account. As the analysis of more field concatenations would lead to high analysis runtimes, this part of the check is not executed.

Check of four concate-nated fields = 5 combina-tions

Check of all five concatenated fields

Page 54: Why Doesn't the CompositeProvider Show Any Results?a248.g.akamai.net/n/248/.../sapasset.download.akamai.com/420835/sapcom/docs/2015/07/...SAP NetWeaver Business Warehouse 7.30 (BW7.30)

Why Doesn't the CompositeProvider Show Any Results?

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 54

Picture chapter 8.3.: Join Fields Analysis (All Providers)

When > 5 Links are defined for a Provider, the check is executed for all single fields but not for their concatenation as the number of possible combinations will lead to a high analysis runtime.

Page 55: Why Doesn't the CompositeProvider Show Any Results?a248.g.akamai.net/n/248/.../sapasset.download.akamai.com/420835/sapcom/docs/2015/07/...SAP NetWeaver Business Warehouse 7.30 (BW7.30)

Why Doesn't the CompositeProvider Show Any Results?

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 55

9. Related Content

http://www.sdn.sap.com/irj/sdn/bwa

http://www.sdn.sap.com/irj/sdn/edw

The help.sap.com Link to the BW Workspaces will be updated here when available!

Page 56: Why Doesn't the CompositeProvider Show Any Results?a248.g.akamai.net/n/248/.../sapasset.download.akamai.com/420835/sapcom/docs/2015/07/...SAP NetWeaver Business Warehouse 7.30 (BW7.30)

Why Doesn't the CompositeProvider Show Any Results?

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2011 SAP AG 56

Copyright

© Copyright 2011 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies (‘SAP Group’) for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.


Recommended