Comment section is significant in planning scenario as it allows the planner or reviewer to enter the text to explain why he/she is entering a value or changing a specific value, which would help the readers to interpret the data efficiently. It also helps during auditing as it can say from where the data came from and why it is there.

In BPC Standard, the comment section can be enabled using EPM functions save/retrieve comment and we can have comments up to 4000 characters either on base level or parent level. But that is not going to be the case for BPC Embedded. The front end is also going to be different as SAP is recommending Analysis Office (AO) for BPC Embedded.

The comment section in SAP BPC Embedded can be enabled by creating a separate DSO (Direct Input) for it. Then this DSO is connected to the Multiprovider along with the other cubes (Actual and Planning) and an aggregation level on top of it. The main disadvantage with this comment section is that it allows only up to 250 characters and also as the planning is happening on the base level, the comments also can be entered only in the base level. However, performance wise this option is better than EPM, as the DSO is the part of the OLAP engine where as in EPM, comments can be enabled only by having the EPM comment function in each and every cell where the comment is required.

The following section details how to enable comment section in BPC embedded step by step.

Step 1: Create an Infoobject

 

An Infoobject ZCOMMENT is created with datatype CHAR and of length 250(Maximum allowed).

Step 2: Create a DSO

Drag and place the key fields as per your requirements. In the data field drag and place the ZCOMMENT infoobject. Then go to the settings section and enable the planning mode.

Once all the above steps are done, activate the DSO and now you could see a new section called characteristics as key figure. Enable it so that we can use it as a key figure.

Step 3: Connect it to the Multiprovider along with Actual and Planning cube.

Create a Multiprovider with the actual cube, planning cube and the comment DSO. Select/Identify the characteristics for the dimensions and the key figures.

Step 4: Create an aggregation level on top of the Multiprovider.

Step 5: Create BEx query

 

Restrict the Amount (Differs as per your requirement) key figure with the dimensions that are not part of comment DSO.

Restrict the Comment (Characteristic Keyfigure) with our DSO as the Infoprovider.

That’s it with the query, you can proceed with creating the model

Step 6: Create the model in BPC web client


Step 7: Analysis Office

You would able to enter the comments and save it as shown below.

Tested in my side and it is working fine. Try it and let me know if you face any issues with the above steps. You can modify the query to include the actual’s data also in the cube to compare it with the planning data and enter comments as required.

Thanks

To report this post you need to login first.

8 Comments

You must be Logged on to comment or reply to a post.

    1. Martin Hájek

      Hello Gregor,

      Is it possible in this scenario to connect a navigational attribute from Actuals ADSO to a corresponding characteristic (understand, the same char. is not used as attribute, but as full char.) in the Planning ADSO in the composite? We are facing some aggregation based errors, OSS says it is not supported… Is there any solution or workaround?

      Thank you very much,

      Martin

      (0) 
        1. Martin Hájek

          Hi Gregor,

          sorry I maybe did not write my question correctly. Let me clarify it because my issue occurs only with comments (direct update DSO and aDSO in composite provider).

          My scenario is that I have an aDSO with actuals and a planning cube (we are still on 7.4) for plan data. aDSO is FI-GL data. Our planning model is using 0SEM_POSIT because we do not plan on GL account level.

          Therefore the data model is like this:

           

          In composite provider 0SEM_POSIT is filled from 0GL_ACCOUNT__0SEM_POSIT for actuals and from 0SEM_POSIT for plan data.

          Up to now everything works ok.

          Now we add a direct update DSO which has the same structure as the planning cube and a planable keyfigure comment (as per the how to guide). We have only 0SEM_POSIT in the DSO.

          But because of the nav. attribute mapping for actuals we cannot activate the composite provider because of the NO2 aggregation. If we use a multiprovider this works fine.

          According to me, this must be addressed by SAP. Because currently composite provider does not have the same functionality as the multiprovider had. And this kind of mapping is done in 99% of planning projects.

           

          Please correct me if I am wrong.

           

          Best regards

           

          Martin

          (0) 

Leave a Reply