Querying on an Infoset return multiple of the actual key figure value Part1
I have stumbled across a few posts on SDN, which describe the problem that the Key figures in an Infoset are duplicates / triplicates / n times the actual or correct value.
This typically happens in a scenario where you adjoin infoproviders, which could result in 1:n or m:n cardinality of the records, in the joining infoproviders.
Example:
Header and Item infoproviders
Sales and delivery infoproviders
Purchase and Goods receipt infoproviders.
SAP Note:- 592785 provides more insight on the limitation
SDN: Infoset.
Elaboration of the multiplicity of key figures:-
This befalls, when for a single record in one infoprovider(say A) you have multiple records in another infoprovider(say B), the join then ordains that one record in A is redundant for the multiple records of B and on an aggregated level the key figures from the A then are ostensibly multiple of the original value.
The multiple = number of corresponding records in B.
I will try to illustrate with example to clarify the issue.
Case I
Say we were trying to find out the preferred vendor through a report.
Demand planning data has indicated that there is a requirement of a particular material in one planning area.
We browse through, different quotations from different vendors to find our preferred Vendor.
Infoprovider A |
Demand plan Area | Material | Req Qty(in 1000units) |
DP1 | Mat1 | 3 |
Infoprovider B |
Material | Vendor | Price in Eur/1000 unit |
Mat1 | A | 200 |
Mat1 | B | 195 |
Mat1 | C | 190 |
Infoset |
Demand Plan Area | Material | Vendor | Req Qty | Price/Unit |
DP1 | Mat1 | A | 3 | 200 |
DP1 | Mat1 | B | 3 | 195 |
DP1 | Mat1 | C | 3 | 190 |
| Total | | 9 | |
Querying on the Infoset above with Demand planning in rows will display the required quantity as 9 (i.e. 3*3 = 9). While the actual required quantity would be 3.
To tackle this, the conventional approach was to use exception aggregation and average the value of the key figure as per the reference characteristic: Material.
In our case, since Material Mat1 has occurred thrice so the sum of the required quantity (9 here) is divided by 3 to get the actual required quantity. (i.e. 9/3 = 3).
However, this reference aggregation falters if there is a requirement for the same material in other demand planning area. (As illustrated in the example below)
Infoprovider A |
Demand plan Area | Material | Req Qty(in 1000units) |
DP1 | Mat1 | 3 |
DP2 | Mat1 | 9 |
Infoprovider B |
Material | Vendor | Price in Eur/1000 unit |
Mat1 | A | 200 |
Mat1 | B | 195 |
Mat1 | C | 190 |
Infoset |
Demand Plan Area | Material | Vendor | Req Qty | Price/Unit |
DP1 | Mat1 | A | 3 | 200 |
DP1 | Mat1 | B | 3 | 195 |
DP1 | Mat1 | C | 3 | 190 |
| Total | | 9 | |
DP2 | Mat1 | A | 9 | 200 |
DP2 | Mat1 | B | 9 | 195 |
DP2 | Mat1 | C | 9 | 190 |
| Total | | 27 | |
Querying on the Infoset above with Demand planning in rows will display the required quantity as 9 and 27 (i.e. 3*3 = 9 & 9*3 = 27). The total would then show that 36 units of material Mat1 is required.
However, the correct result is 12 units of Mat1 are required, 3 in DP1 and 9 in DP2.
Now, if exception aggregation as average was used with reference characteristic material then the result would be displayed as 1.5 and 4.5 (i.e. 9/6 = 1.5 and 27/6 = 4.5). This is because material Mat1 occurs 6 times in this data set
Continued in querying on an Infoset return multiple of the actual key figure value Part2
Infoset Keyfigure multiplicity Part 2
