Professional Documents
Culture Documents
Calculation Examples
Calculation Examples
PUBLIC
Original content:
https://help.sap.com/docs/SAP_INTEGRATED_BUSINESS_PLANNING/feae3cea3cc549aaa9d9de7d363a83e6?locale=en-
US&state=PRODUCTION&version=2205
Warning
This document has been generated from the SAP Help Portal and is an incomplete version of the official SAP product
documentation. The information included in custom documentation may not re ect the arrangement of topics in the SAP Help
Portal, and may be missing important aspects and/or correlations to other topics. For this reason, it is not for productive use.
This is custom documentation. For more information, please visit the SAP Help Portal 1
5/7/2022
Calculation Examples
The calculation of ABC/XYZ segments depends on the segmentation measure, on the calculation level, and on the calculation
method. However, the way that the resulting segments are stored in the system depends on the master data type of the target
attribute.
In the following examples, different calculation levels are used and the results are stored in different master data types. All
examples are based on the same input key gure and on the same ABC segmentation method, (5) by segmentation measure
(single values).
Input Values
In the examples below, the base planning level of the input key gure contains the following master data attributes (with the
root attributes marked by asterisks):
Product ID*
Product Group
Location ID*
Region ID
Sales Representative
The input key gure and the attributes of its base planning level have the following values:
This is custom documentation. For more information, please visit the SAP Help Portal 2
5/7/2022
As shown in the rst table on this page, the following key gure values belong to the various product-location combinations:
Product 20 Location 7 50
Since the calculation level is Product ID - Location ID, the segments are calculated for each of these calculations based on the
following thresholds:
This is custom documentation. For more information, please visit the SAP Help Portal 3
5/7/2022
Segment A >= 1000
To save the results for each combination separately, we can choose Product Location as the target master data type. Tthis
master data type contains the following attributes:
Product ID*
Location ID*
Sales Representative
Segment
After the calculation is run, the attributes of the target master data type will store the following values:
This is custom documentation. For more information, please visit the SAP Help Portal 4
5/7/2022
In this example, we want to classify the locations based on the key gure values they produced. First we will save the results for
each Product ID - Location ID combination, then for each location.
As shown in the rst table, the following key gure values belong to the various Location IDs:
Location 7 Product 20 50
Since the calculation level is Location ID, the key gure values are aggregated for each location. Then the segments are
calculated based on the following thresholds:
Location 1 1300 C
Location 2 1050 C
This is custom documentation. For more information, please visit the SAP Help Portal 5
5/7/2022
Location 3 1700 C
Location 4 5500 A
Location 5 2200 B
Location 6 1320 C
Location 7 2050 A
To save the results for each Product ID - Location ID combination separately, we can choose Product Location as the target
master data type. As we have seen in the previous example, this master data type contains the following attributes:
Product ID*
Location ID*
Sales Representative
Segment
After the calculation is run, the attributes of the target master data type will store the following values:
This is custom documentation. For more information, please visit the SAP Help Portal 6
5/7/2022
The segments calculated for the locations determine the segments that the various product-location combinations are
assigned to, regardless of the key gure values of the individual products. For example, Product 1 would be in segment B
according to the calculation on Product - Location level (see the 2nd table on this page), but it's produced at location Location 1,
which has been classi ed into segment C. Therefore, Product 1 is now also stored as an item belonging to segment C.
Now we want to classify the locations based on the key gure values they produced. For this, we need to choose Location ID as
the target master data type, which contains the following attributes:
Location ID*
Region ID
Segment
After the calculation is run, this target master data type will contain the following values:
Europe Location 1 C
Europe Location 2 C
Asia Location 3 C
Asia Location 4 A
America Location 5 B
America Location 6 C
America Location 7 A
As shown in the rst table on this page, the following key gure values belong to the various products belonging to various
product groups:
This is custom documentation. For more information, please visit the SAP Help Portal 7
5/7/2022
Since the calculation level in this case is Product Group, the key gure values are aggregated for each product group and the
segments are recalculated based on the following thresholds:
To save the results for each product-location combination separately, we can choose Product Location as the target master
data type. As we have seen in the previous example, this master data type contains the following attributes:
Product ID*
Location ID*
Sales Representative
Segment
The Product Group attribute is not included but it is included in Product, the simple master data type that Product ID belongs
to, so it can be used for saving the segmentation results.
After the calculation is run, the target master data type will contain the following values:
This is custom documentation. For more information, please visit the SAP Help Portal 8
5/7/2022
Similarly to the previous example, the results calculated for the product groups determine the segments that the various
products are assigned to, regardless of the key gure values of the individual products. For example, Product 8 would be in
segment B according to the calculation on Product - Location level (see the 2nd table on this page), but it belongs to the
product group Product Group 1, which has been classi ed into segment A. Therefore, Product 8 is now also classi ed into
segment A.
If we want to want to save the results for each product separately, we can use a simple target master data type, Product, which
contains the following attributes:
Product ID*
Product Group
Segment
After the calculation is run, this target master data type will contain the following values:
This is custom documentation. For more information, please visit the SAP Help Portal 9
5/7/2022
Again, the segments calculated for the product groups determine the segments that the various products are assigned to,
regardless of the key gure values of the individual products.
Finally, we can also classify the product groups based on the key gure values they produce. For this, we can choose Product
Group as the target master data type. After the calculation is run, this target master data type will contain the following values:
Product Group 1 A
Product Group 2 B
Product Group 3 C
As shown in the rst table on this page, the following key gure values belong to the various products belonging to various
locations and sales representatives:
This is custom documentation. For more information, please visit the SAP Help Portal 10
5/7/2022
Location 7 George 50
Since the calculation level in this case is Location ID - Sales Representative, the key gure values are aggregated for each
representative and location, and the segments are recalculated based on the following thresholds:
This is custom documentation. For more information, please visit the SAP Help Portal 11
5/7/2022
For example, the Stephan-Location 1 combination has been classi ed into segment B because Stephan produced 1100 at
Location 1 from Product 1 and Product 2. George only produced 200 at the same location so the George - Location 1
combination has been classi ed as C.
To save the results for each product-location combination separately, we can choose Product Location as the target master
data type. As we have seen in the previous example, this master data type contains the following attributes:
Product ID*
Location ID*
Sales Representative
Segment
Sales Representative is included but not as a key attribute in this compound master data type.
The target master data type will include the following values:
This is custom documentation. For more information, please visit the SAP Help Portal 12
5/7/2022
Although Sales Representative is not a key attribute in the target master data type, the segments calculated for it determine
the segments that the various product-location combinations are assigned to. For example, Product 2 would be in segment A
according to the calculation on Product - Location level (see the 2nd table on this page), but it belongs to the location Location 1
and the sales representative Stephan, the combination of which has been classi ed into segment B. Therefore, Product 2 is now
also classi ed into segment B.
In the next step, we want to save the results for each location-sales representative combination separately. For this, we can
choose Location ID - Sales Representative as the target master data type. It will contain the following values:
Location 1 George C
Location 1 Stephan B
Location 2 George C
Location 2 Stephan C
Location 3 Anna B
Location 3 George C
Location 3 Stephan C
Location 4 Anna A
Location 4 Stephan C
Location 5 Anna C
Location 5 George B
Location 6 Anna B
Location 6 George C
Location 7 George B
This is custom documentation. For more information, please visit the SAP Help Portal 13
5/7/2022
As shown in the rst table on this page, the following key gure values belong to the various product groups and regions:
Since the calculation level in this case is Product Group - Region ID, the key gure values are aggregated for each product group
and region, and the segments are recalculated based on the following thresholds:
This is custom documentation. For more information, please visit the SAP Help Portal 14
5/7/2022
For example, the Product Group 1-Asia combination has been classi ed into segment A because Product Group 1 produced 3700
from all products that belong to that group and were manufactured in Asia. The same product group only produced 2350 in
Europe, so the Product Group 1 - Europe combination has been classi ed as B.
To classify the product-location combinations based on the key gure values produced by each product group manufactured in a
region, we can choose Product Location as the target master data type. This target master data type will include the following
attributes and values:
Although the attributes of the calculation level (Product Group and Region ID) are not part of the target master data type, the
segments calculated for the combinations of those attributes determine the segments that the various product-location
combinations are assigned to. For example, Product 2-Location 1 would be in segment A according to the calculation on Product
- Location level (see the 2nd table on this page), but Product 2 belongs to Product Group 1 and Location 1 belongs to the Europe
region, and the combination of these two items has been classi ed into segment B. Therefore, Product 2 is now also classi ed
into segment B.
Finally, we want to save the results for each product group - region combination. For this, we can choose Product Group Region
as the target master data type. This simple master data type will contain the following values:
This is custom documentation. For more information, please visit the SAP Help Portal 15
5/7/2022
This is custom documentation. For more information, please visit the SAP Help Portal 16