cancel
Showing results for 
Search instead for 
Did you mean: 

Debugger not stopping in Z*classes in BSP_WD_CMPWB

ricky_shaw
Contributor
0 Kudos

Hi Experts,

I am rephrasing my question for CRM 7.0 to make it simple.

I used the Comp Workbench tool (BSP_WD_CMPWB) to create an enhancement for BP_ADDR component on the StandardAddress view.

It created a Z* Impl class, Z*CTXT class & Z* CN01 Context Node class. I happened to put my code inside the methods of all the above Z*I classes & also in the Page attributes in View Layout Z* context class.

I placed break points in the Z*classes. When I am trying to create a new BP, the program is not all stopping in any of these break-points.

I can see that the transaction is stopping at the Std Context classes(CL_BP_ADDR_STANDARDADDRES_IMPL).

Can anyone pls help me?

Thanks

ricky_shaw
Contributor
0 Kudos

Hi, To put in simple terms none of my Z** classes are getting triggered.

Can anyone help me please.

Sandra_Rossi
Active Contributor
0 Kudos

Hint: when this happens to Z code within an application/framework you don't know very well, it's difficult to know whether it's related to the debugger options or if your code is simply not called. So, the first thing to do is to make sure whether your code is called by adding a MESSAGE x001(00) => it will short dump if it executes (go to ST22). Then you can ask your question related to either the debugger or to the framework.

ricky_shaw
Contributor
0 Kudos

No..its not dumping.

Sandra_Rossi
Active Contributor

Thanks. Title of the question is misleading to me, it's not a matter of debugger at all, it's just code which is not executed and you probably want to ask how to achieve your requirement "create an enhancement for BP_ADDR component on the StandardAddress view", which you should probably describe a little bit more. I don't get why you are implementing "everything" instead of just what is needed...

ricky_shaw
Contributor
0 Kudos

No.Its crystal clear..

I used open dataset stmts to AL11 file in my Z** classes & its writing to Al11 .

matt
Active Contributor

No, it's misleading. The title implies the code is being called, but the debugger isn't stopping.

You've demonstrated that the real issue is nothing to do with the debugger - the real issue is that your code isn't being called at all.

(This reminds me of the support call where the user complains they can't see the cursor on the screen ... and it turns out they're in the middle of a power cut. The symptom is true, but not really the cause of the issue!)

I suggest you edit the title to "My code isn't being called" or something similar.

ricky_shaw
Contributor
0 Kudos

Why i am seeing -2 votes here.

it can be 0 instead.

Accepted Solutions (0)

Answers (2)

Answers (2)

thalesvb
Active Contributor
0 Kudos

Hi,

Enhancement Set is probably not "active" on client.

Can you check if that Enhancement Set is the one registered on BSPWDV_EHSET_ASG maintenance view? The average guide for enhancing BSP Components is having only one enhancement set per landscape, so only one entry should exists on that table.

You can also try to see/debug near where COMPONENT_HANDLING BAdI is invoked, since it is responsible to define the active enhancement set for user session, and someone may have implemented a different behavior on your system.

Regards

ricky_shaw
Contributor
0 Kudos

Hi Thales, Yes it is added in the view BSPWDV_EHSET_ASG .

Questions:

1) You said "The average guide for enhancing BSP Components is having only one enhancement set per landscape".what exactly does it mean? I am trying to add another enhancement of a different view & also different component altogether but its not allowing me.

2) In assignment defn: I made the development in dev client say 100, Do i need to change the client # when i am testing my component in testing client(say 200)?

thalesvb
Active Contributor
0 Kudos

#1: I should have used the term "common" instead of "average". "Enhancement Set" conceptually is a grouping for BSP enhancements to be used altogether at runtime, and unless some very specific cases, there is no reason to have multiple Enhancement Sets defined on a system. The first time someone enhance a standard component under a Enhancement Set, a shadow BSP application is created to store all modifications done to it. The next person that wants to do more modifications to that same standard component under same Enhancement Set (any kind of modification allowed on BSP_WD_CMPWB), the same shadow BSP application will be reused (system understands that you are further enhancing that component). If another BSP component must be enhanced, even on same Enhancement Set, a new shadow BSP application will be created to store changes for that component.

#2: You can and should create a second assignment entry for that client, that may be the cause.

Another possibility is the (User) parameter WCF_IGNORE_ENHANCEMT enabled to ignore enhancements. If is not that, Other than that I recommend to debug the mechanism itself to investigate what happens on your system (it is on CL_BSP_WD_COMPONENT_FACTORY constructor).

ricky_shaw
Contributor
0 Kudos

Great explanation Thames.

ricky_shaw
Contributor
0 Kudos

Now the debugger is stopping..for some reason which i dont know.

matt
Active Contributor

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details