Track User Changes Using a Change Log in Integrated Planning

  • by Pranab Parhi, Senior Associate SAP BI and Planning, Bluefin Solutions, UK
  • February 8, 2012
Learn how to create a change log in a planning application using SAP NetWeaver BW Integrated Planning (IP). This process helps track the changes made in an IP application, creating data that you can use for audit purposes and performance assessment. Sample code in included.
Key Concept

If you use SAP NetWeaver BW Integrated Planning (IP) as your planning tool, a final version of the plan data is normally visible, but you can’t see the changes made by different users to the plan data due to technical restrictions. However, you can use characteristic derivation techniques in your planning application to trace the changes made by different users. These techniques derive and populate different values to the plan InfoCube in the background while a user saves the plan data.

If you have the SAP NetWeaver BW Integrated Planning (IP) application, multiple users can be responsible for the same plan data. For example, a sales plan for the year can be developed by multiple sales managers responsible for individual sales areas. Senior sales team members can review and change the plan. In a scenario like this in which plan data can change, and you can only see the final version of the plan data, it is difficult to trace the changes made by different users, creating an obstacle to proper auditing.

However, a solution exists to help you record changes to planning data by multiple users. This method involves using a few additional fields in the planning InfoCube and implementing characteristic derivation techniques to populate them. The result records the time of changes and the users making the changes. I give a step-by-step guide to implementing the solution in your environment. You can use this guide in an SAP NetWeaver BW 7.x IP environment, or alternatively in an SAP NetWeaver BW 3.x Business Planning and Simulation (BPS) environment. Authorization aspects of standard users are not affected by this implementation.

To understand the benefits of the proposed solution, I first demonstrate a typical planning solution in a planning environment. I then explain how to implement the proposed solution. The configuration involved requires knowledge of SAP NetWeaver BW 7.x, IP, and object-oriented ABAP.

Described below is a basic sales planning scenario, in which planning is performed for each month at the sales organization level with multiple divisions:

Pranab Parhi

Pranab Parhi is a senior SAP NetWeaver BW and planning consultant who has been involved with multiple full-life cycle SAP NetWeaver BW reporting and planning implementations. He has 10 years of SAP consulting experience in various industries, including pharmaceutical, oil, public sector, aviation, consumer packaged goods, services, and retail in multinational environments. He is currently working as a senior associate for Bluefin Solutions. Pranab is an SAP-certified SAP NetWeaver BW 7.0 and SAP NetWeaver BW 3.5 consultant with six years of BI experience. In addition, he is an SAP-certified ABAP consultant with more than four years of ABAP experience. He also holds a bachelor’s degree in engineering (computer science).

If you have comments about this article or BI Expert, or would like to submit an article idea, please contact the BI Expert editor.

See more by this author


Comments

2/19/2013 8:14:18 AM
Richard Wong

I like this solution for auditing.

If I were to implement though I would be concerned at the granularity of the data as the records can not be rolled up. I would be tempted to use an auditing cube to store this information, and move the data to a different cube for reporting if stored persistently.

Good work.

Please log in to post a comment.

To learn more about subscription access to premium content, click here.