I want to provide an overview about possible decimal issues in BPS Planning used in the CRM Marketing scenario. There are some known issues related to decimal settings in PBS planning. This blog should provide information about the design of the decimal validation and how to set up the planning layout correctly. Furthermore this should contain a collection of solutions for known issues.
When looking the the planning layout created for a trade promotion in CRM we can see a key figure in the plannning layout defined with 2 decimals.
I will take these example to explain the design.
When setting up the planning layout the following 4 level dependencies need to be considered.
1. UPX Layout Definition
2. BPS0 Customizing
3. Key Figure
4. Data Element
When the planning layout is rendered the first level that is considered is the UPX Layout Definition. In transaction UPX_MNTN the number of decimals can be defined:
The decimals places set in the UPX layout defines the number of decimals displayed in the planning layout. This number is for display reasons only.
On the second level there is the BPS0 Customizing. This is the first level that defines how the key figures are stored. That means key figures are rounded to the number of decimals defined in BPS0 and stored as the rounded value.
For data consistency reasons the number of decimals defined in UPX_MNTN must be smaller or equal to the number of decimals defined in BPS0. Otherwise an error will be raised.
If there are no decimals defined in BPS0 the same rule is valid for the key figure definition in RSD1.
If there are no decimals defined in the key figure details the data element for the key figure is considered.
The decimals defined in the UPX_MNTN are considered for displaying the key figures, whereas the decimals defined in the levels below BPS0 are considered for calculations and storing the values. You should not have more decimals in layout than what you can actually save in the database. The general rule is the following:
No of display decimals <= No of decimals used for calculation
Please refer to the following KBA for further information about the dependencies between the different levels:
Percentage based key figures
What needs to be considered for percentage based key figures?
The number of displayed decimals is taken from the UPX_MNTN settings as well.
This is similar to any other key figure definition. The difference is the way the system stores the percentage values. Depending on the parameter UPX_KPI_KFVAL_PERC_CONV_TO_BW the percentage value is stored as divided by 100. A value of 10% is therefore stored as 0,01. This requires the settings for the percentage key figure to have 2 more decimals defined in BPS0 than in UPX_MNTN not to lose precission.
This is documented in the following SAP note:
With the parameter UPX_KPI_KFVAL_PERC_CONV_TO_BW set the percentage key figure values is stored in BW as 10 for 10%. If the parameter is set the above decimal setting is not required. Information about the UPX_KPI_KFVAL_PERC_CONV_TO_BW parameter in UPC_DARK2 table is available in the following SAP note:
There are some known issues for percentage key figures, those are solved with the following SAP notes:
Currency key figures
Since most currencies use 2 decimals per design there should not be any issues for the most currencies. However there are some known issues for exceptional currencies, so currencies with other than 2 decimal places such as JPY. In case of issues with those currencies the following SAP notes are required in the system:
Using master and dependent profiles
When using master and dependent profiles the decimal settings need to be exactly the same for the key figures in the master and the dependent profiles. It is the master profile that is synchronized and that is rendered for calculating the key figures. Therefore the key figures hold the values with decimals from the master profile. However for display reasons the rendering happens for the displayed profile, so for the depending profile. Therefore the decimal settings need to be in sync in the master and the dependent profiles.
There are some known issues that are corrected with the following SAP notes:
The blog will be updated on a regulary basis. If you find any information missing please let me know.