Skip to Content

Business Planning and Simulation version for Netweaver successfully leverages the Netweaver infrastructure and we can use many tools and techniques that are available to us in the Netweaver platform. Debugging is one of the powerful tools that one can effectively use for issue resolution. However debugging in BPC7NW is different than debugging other usual SAP transactions. In this blog let us talk about why it is different and what we need to do to enable us to debug with BPC7NW.

Why debugging is different in BPC7NW:

In a regular SAP transaction, if an end user is executing a transaction and we want to debug it, one of the usual ways might be to set up a break point for that user so that the debugger will prompt us when the underlying program encounters the transaction executed by that user. It is little bit different in BPC7NW. To understand the difference, let us look at the architecture of BPC7NW. The following diagram shows the high level architecture of BPC7NW.

 image

 The end user of BPC7NW does not use SAP GUI. He/she uses BPC front end. BPC users as well as their authorizations are maintained on the BPC front end. When a BPC user takes an action, for example – modify a property or edit a dimension member, the corresponding BW infoobject in the BPC namespace is automatically modified. (You can read more about the automatic generation of infoobjects in the BPC namespace at A reservation of a different kind – why, what and how of BPC namespace) The BPC front end, which is on the .NET layer, communicates with the ABAP layer by means of service users. If we want to debug any BPC activity, we need to map a valid debug user in the ABAP layer to the BPC user so that the debugging can be done with that debug user instead of anonymous service user.  This step of mapping a debug user is generally not necessary for debugging a usual SAP transaction. In this regard, debugging in BPC7NW is different. Now the next question is what do we have to do to take care of this difference. Let us discuss that.

How to enable a BPC user to debug in BPC7NW:

In order for us to map debug user to BPC user, we need to access the BPC Server Manager. Within the BPC Server Manager, we have the option to maintain debug users as shown below.

image

Here we can maintain debug user and password for each BPC user as shown below. Many BPC users can share the same debug user if necessary. If a BPC user is not maintained here, that BPC user may not be able to debug.

image

Once we maintain the debug user, we have made the necessary set up required for debugging in BPC7NW. The next question is how to know what program, API, function module etc to debug for a specific BPC action. For example, if someone is having an issue in say modifying an application, then how can he/she know which API/program/function module that ‘modify application’ task is using.

Identifying the development objects germane to a specific BPC task:

Fortunately BPC7NW provides us a very simple way to identify all the development objects pertinent to the BPC task or action that we want to debug.  Just go to the Object Navigator (transaction se80) and select package UJ as illustrated below.

 

image

image

Here we get a list of all APIS for BPC7NW as shown below. We can easily select the program appropriate for the BPC task that we want to debug.

image

We can set an external breakpoint in this session. Whenever that BPC user linked to the debug user executes that BPC action, the debugger screen will open. For example, if we are facing an issue in modifying an application, then we would select the API for modifying application and set a breakpoint there. Next time our BPC user (linked to the debug user) clicks on modify application; it would stop at the breakpoint set by us.

Ability to debug in this way is a feature that becomes very useful – especially while troubleshooting. Though we still can’t easily debug the issues in .NET layer of BPC7NW, we can definitely take advantage of this powerful debugging feature for any issues in the ABAP layer where majority of processing occurs.

To report this post you need to login first.

4 Comments

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

  1. Ethan Jewett
    I believe you can also use transaction code ST05 to set up an RFC trace on the debug user to track down the exact function modules and class methods being invoked by an BPC for Netweaver user action.  This only works, of course, after setting up the debug user.
    (0) 
  2. Jay Roble
    Most of our BPC users do NOT have a BW user ID.

    So what BW baclemd ID would we Use?
    – Not the BPCxxxx service id’s, these are not dialog & have too much access.

    What access/BW roles would the Debug User ID need?
    – Same as the BPCxxxxx service user?
    – We can’t do that, cause that role gives way too much BW back end access.

    (0) 
  3. Manoj Damle
    Hi Pravin:
    Really thanks for the help on Debugging in SAP BPC NW.

    I have followed all the steps as mentioned in the blog. But, It didn’t click.
    The only doubt, I am having over here is whether I have used the correct id as BPC user id. I have tried with BPC_USER id ( std id hiven by SAP – BPC), but it didn’t work.
    Can you please let us kbow which among three ids mentioned below, we can use as BPC user for debugging:
    1. BPC_SYSADMIN
    2. BPC_ADMIN
    3. BPC_USER

    I want to understand this faciltiy to debug the following activity :
    When, I use BPC Web browser to chnage the Current View (CV), table “UJA_USER_CV” gets populated correctly.
    When, I am doing same activity through BPC Excel Client, this table is not getting updated with latest changes in the CV.

    Really appreciate your help on this blog again.

    Thanks.

    With regards,
    Manoj Damle |Capgemini India| Mumbai
    Senior Consultant | Technology Services – SAP
    Extn: 221 3914|VoIP: 221 3906
    Mobile: +91 9920200248
    Email:manoj.damle@capgemini.com

    (0) 

Leave a Reply