Scribd
Upload
95 views

How To Debug NW BPC

This document provides instructions for debugging Business Planning and Consolidation (BPC) 10 for SAP NetWeaver. It explains that the .NET tier has been removed, so accounts no longer need to be mapped for debugging. It describes how to set up a debug user in BW with the required roles and set breakpoints in transactions SE80 to debug EPM Add-In and administration functions or data manager packages. The debugging process is outlined for both scenarios.

Uploaded by

adybaddyus7573
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
95 views

How To Debug NW BPC

This document provides instructions for debugging Business Planning and Consolidation (BPC) 10 for SAP NetWeaver. It explains that the .NET tier has been removed, so accounts no longer need to be mapped for debugging. It describes how to set up a debug user in BW with the required roles and set breakpoints in transactions SE80 to debug EPM Add-In and administration functions or data manager packages. The debugging process is outlined for both scenarios.

Uploaded by

adybaddyus7573
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

http://www.linkedin.com/groups/BPC-10-NW-BADIsList-3919710.S.

225242291

Debugging BPC 10 for NetWeaver


Posted by Daniel Settanni in daniel.settanni on Jul 13, 2011 7:14:42 AM
inShare1

Debugging in BPC 10

1.
2.

In my opinion the ability to debug is one of the biggest advantages in the BPC for NetWeaver platform.
It has proven to be a huge asset when writing custom logic (BAdis and custom integration scenarios)
in addition to general troubleshooting tasks.
The good news is that the latest release of BPC for NetWeaver (BPC 10) also allows you to debug the
BW tier but there have been a couple of changes that you need to be aware of:
The .NET tier has been removed from the 10.0 release of BPC for NetWeaver. This means you
dont have to map accounts on the .NET tier to enable debugging anymore.
The entry point for debugging has changed
After reading this (short) blog you will be prepared to debug BPC 10 for NetWeaver to your hearts
content.
Lets get started
Setting up your debug user
The only thing you need to start debugging BPC 10 is a valid BW user account with the same access as
the BPC BW System Account. You can find the required roles in section 4.1 of the Installation guide.
Once that is complete, grant the user the appropriate rights to the environment / model (application
set / application) and set your breakpoints.
Where do I set my breakpoints?
There has been a pretty good amount of rework in the UJ package for BPC 10 and this has also
impacted where you need to set your breakpoints. Ill cover two different scenarios below, debugging
EPM Add-In and Administration functions and debugging data manager packages.

1.
2.
3.
4.
5.
6.

7.

Debugging EPM Add-In and Administration functions


Log into the BPC client you want to debug (EPM Add-In or Web Administration console) with
your BW debug user account.
Go to the portion of the use case you want to debug, but dont execute the action yet.
Log into SAPGUI with your BW debug user.
Go to transaction SE80
Navigate to the class CL_BPC_REST_RES (under package UJX,
embedded package UJX0).
Go to line 56 of the HANDLE_REQUEST method and set
an external breakpoint.
Note If you know the specific location you want to debug you
can set theexternal breakpoint there and skip the breakpoint mentioned above.
Switch to the BPC client and execute the action you want to debug.

8.
9.

This will launch a SAPGUI debugging session


The case statement on line 60 will get you to the code you need to evaluate.

Debugging Data Manager Packages


1.
2.
3.
4.
5.
6.
7.
8.

Log into SAPGUI with your BW debug user.


Go to transaction SE80
Navigate to the class CL_UJXD_PACKAGES_RES (under package UJX,
embedded package UJXD).
Go to line 179 of the DO_POST method and set an external breakpoint.
Switch to the BPC client and execute the data manager package you want
to debug.
This will launch a SAPGUI debugger
Double click on the ls_package_run-if_debug exporting parameter and
set its value to true (represented by the character X).
You can then continue to any downstream external breakpoints you already set (for instance, in
your BAdi) or can step through the code line by line.

Happy Debugging!

You might also like