Advanced Customizing for Planning Layouts in
BI
After customizing the planning layouts in BPS0, perform advanced Customizing for downloading historical data using the UPX_MNTN transaction in SAP NetWeaver BI.
Only One Key Figure in the Virtual Layout
Since a different planning profile is intended to be used, create the customizing entry called MSA_PROF in BPS advanced Customizing in row 50 of the 4TPM9910 layout.
Parameter Name |
Value |
AREA |
4TPM9000 |
PLEVEL |
4TPM9911 |
MSA_PROF |
4TPM991A |
Identical Selection Criteria Across Planning Levels
If several virtual planning levels that are used in the SEM advanced layout have identical selection characteristics, you can use the following optimization mechanism.
This is an option supported by the mobile application; it is not a mandatory approach.
Group all key figures with identical selection characteristics in a single layout and download this layout. This approach reduces the data volume since the header and lead-column downloads are not repeated. In addition, the number of planning manager instances in the clients is reduced.
If you adopt this approach, you must specify additional information about the key figures (to be shown in that particular row) in the MSA_KF parameter.
● If you want several key figures in a layout to be summed up, include the key figures in the MSA_KF parameter, separated by semicolons.
If, for example, row 30 of the 4TPM9930 layout contains the following values, the variable promotion spends are summed up.
Parameter Name |
Value |
AREA |
4TPM9000 |
PLEVEL |
4TPM9931 |
MSA_PROF |
4TPM992A |
MSA_KF |
0BONUS_SCAN;0BONUS_SHIP;0FRGO_DSCNT;0OFFR_DSCNT |
● If you do not want the key figures to be summed up, specifying the key figure name in the MSA_KF parameter.
The Customizing is as follows (row 50 of the 4TPM9920 layout):
Parameter Name |
Value |
AREA |
4TPM9000 |
PLEVEL |
4TPM9921 |
MSA_PROF |
4TPM992A |
MSA_KF |
0OFFR_DSCNT |
The same Virtual Planning Profile (4TPM992A) is used for the 0FRGO_DSCNT key figure.
Common Planning Level for Different Leading Objects
There would be a common profile for Business Partners (BP) and BP Hierarchy Nodes (BPHN). The leading object (BP or BPHN) is determined based on the application type (ACB or ACH) defined in Customizing for CRM.
· If the application type is ACB, then BP variable values are read.
· If the application type is ACH, then BPHN variable values are read.
For each profile, perform Customizing twice in CRM – once each for BP and BPHN – by choosing Account Planning à Key Figure Planning à Define Planning Profiles for Mobile Client.