Dear Readers,
I would like to share brief information on the possibility of forecasting in transaction currency in SAP commercial Project Management (CPM). CPM standard supports forecasting in Plan Currency (CPM specific currency). However, there could be business needs to perform forecasting in transaction currency.
In my recent CPM implementation, I have implemented the forecasting in transaction currency.
This blog post is divided into four sections:
1. Business Scenario
Master project is created and multiple PS projects are assigned to the master project. Project Finance Manager performs the Financial Planning at the start of the project. During the project execution, planned data from the financial planning (CPM), Approved change request (CPM), Actuals and Commitments in transaction currencies act as an input for the forecasting.
During each month, resources from various departments performs the forecasting in transaction currency for their individual scope. The below picture depicts typical business flow:
2. Challenges
In CPM standard, key figures Actual Cost in transaction currency and Total Commitments in transaction currency are stored on different currency key figure definition as shown below:
Actual Cost in Transaction Currency
Total Commitments in Transaction Currency
These currencies are displayed in the financial Forecasting Workbook/Lumira dashboard based on the key figure definition. Since the key figures are coming from different underlying cubes, they are represented separately in the financial Forecasting Workbook/Lumira dashboard.
The below picture shows how key figures are represented in the forecasting workbook when the key figures are associated with the different currency figures definition.
It is practically impossible to perform forecasting using three different currency types. Further, it is not possible to use standard or any Z planning functions and sequences in the forecasting workbook/Lumira dashboard. Hence the expectation was to have a single currency key (Transaction Currency)
3. Solution Design
The solution presented here may differ based on customer specific requirements and business scenarios. The below solution was designed for very specific business requirements. However, with this solution, you may find a good foundation to make relevant enhancements for your customers.
4. Final Outcome
All the key figures (EAC, Actuals & Commitments) are now represented with single currency key (Transaction Currency) enabling all the standard and Z planning functions/sequences to work as expected.
Thanks a lot!
Best Regards,
Akash Ghulghule
I would like to share brief information on the possibility of forecasting in transaction currency in SAP commercial Project Management (CPM). CPM standard supports forecasting in Plan Currency (CPM specific currency). However, there could be business needs to perform forecasting in transaction currency.
In my recent CPM implementation, I have implemented the forecasting in transaction currency.
This blog post is divided into four sections:
- Business Scenario
- Challenges
- Solution Design
- Final Outcome
1. Business Scenario
Master project is created and multiple PS projects are assigned to the master project. Project Finance Manager performs the Financial Planning at the start of the project. During the project execution, planned data from the financial planning (CPM), Approved change request (CPM), Actuals and Commitments in transaction currencies act as an input for the forecasting.
During each month, resources from various departments performs the forecasting in transaction currency for their individual scope. The below picture depicts typical business flow:
2. Challenges
In CPM standard, key figures Actual Cost in transaction currency and Total Commitments in transaction currency are stored on different currency key figure definition as shown below:
Actual Cost in Transaction Currency
Total Commitments in Transaction Currency
These currencies are displayed in the financial Forecasting Workbook/Lumira dashboard based on the key figure definition. Since the key figures are coming from different underlying cubes, they are represented separately in the financial Forecasting Workbook/Lumira dashboard.
The below picture shows how key figures are represented in the forecasting workbook when the key figures are associated with the different currency figures definition.
It is practically impossible to perform forecasting using three different currency types. Further, it is not possible to use standard or any Z planning functions and sequences in the forecasting workbook/Lumira dashboard. Hence the expectation was to have a single currency key (Transaction Currency)
3. Solution Design
The solution presented here may differ based on customer specific requirements and business scenarios. The below solution was designed for very specific business requirements. However, with this solution, you may find a good foundation to make relevant enhancements for your customers.
New Z key figures for storing ETC and EAC values in the transaction currency.
New Z query for forecasting with all the key figures in transaction currency. The standard CPM queries deliver all the key figures in the plan currency.
The existing key figures for ETC and EAC can also be used for storing the values in plan currency if needed for reporting. However, the currency conversion between the transaction currency to plan currency needs to be developed. It is possible to enhance method ‘PERFORM_CURR_TRANSLATION’ in the class /CPD/CL_PFP_PO_SERVICES
Implementation of enhancement in the BADI ‘RSROA_OLAP_BADI’. The new Z enhancement is created to achieve the merging of Actual Cost and Total committemnt currency keys into one common transaction currency key. The enhancement is restricted to the two info providers /CPD/AVR_MP02 and /CPD/PFP_M_A1
4. Final Outcome
All the key figures (EAC, Actuals & Commitments) are now represented with single currency key (Transaction Currency) enabling all the standard and Z planning functions/sequences to work as expected.
Thanks a lot!
Best Regards,
Akash Ghulghule
- SAP Managed Tags:
2 Comments
