Debugging BPC Package

[former_member756719]

Hi Team,

We wanted to debug one of the BPC package directly in production. We have access restrictions so we will not have access to debug and replace X value in CL_UJXD_PACKAGES_RES.

Please let us know if there are any other ways to debug it directly.

Thanks,

Mahesh

[former_member756719]

Hi Team,

Please let us know if there is any way to debug.

Thanks,
Mahesh.

[former_member186338]

Please provide details about package! data load? custom logic?..

[former_member756719]

Hi Vadim,

It's a push package from one model to another model with custom logic.

We are using the run logic to call the default script of other model.

Thanks,

Mahesh

[former_member186338]

OK, you are using RUNLOGIC_PH badi in the script?

And what do you want to debug?

[former_member756719]

Hi Vadim,

We are using RUNLOGIC not RUNLOGIC_PH.

Our logic is to Push the data from source model to target model and do the calculations in the target model using source model data.

The logic is to clear the data in the target system first, then push the data to target system. Then we are calling default logic in target system using RUN_LOGIC to do the calculations

We have observed that some of the calculations are not happening properly in the target model so we wanted to debug it directly in production, but we have very limited access.

I am looking for any solution to debug the package directly in production without replacing the value as X. I am yet to try UJKT

Thanks,

Mahesh.

[former_member186338]

"The logic is to clear the data in the target system first, then push the data to target system. Then we are calling default logic in target system using RUN_LOGIC to do the calculations"

Sorry, but you don't need ABAP debug to check the mentioned process.

Simply check logs!

P.S. RUNLOGIC is an old version of RUNLOGIC_PH badi, use the recent version!

[former_member756719]

Hi Deepak,

I tried the below steps but it didn't stop at the break point.

1. Go to transaction SE80
2. Navigate to the class CL_BPC_REST_RES (under package UJX, embedded package UJX0).
3. 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 the external breakpoint there and skip the breakpoint mentioned above.
4. Switch to the BPC client and execute the action you want to debug.

Thanks,

Mahesh.

[deepak-kalra]

Hi maheshreddy1274,

In the production environment, you can create a custom logic to debug
Here is the link
https://blogs.sap.com/2011/07/13/debugging-bpc-10-for-netweaver/

I hope it helps.

Regards
Deepak