VL10 Debugging

[Former Member]

Hi,

I have problem with VL10 debug. Actually, I have implemented a BADI on save document. I want to debug that badi. I have break points at BADI but it doesnt work. It shows breakpoints in VL10 at runtime but doesnt stop there. I am assuming that there is parallel processing that is why it ignores that. That is why I tried to debug it step by step but it doesnt work. Anyone can help me to debug and stop at breakpoints anywhere in VL10.

Thanks,

SA

[Former Member]

Hi!

I've entered my modifications into the delivery save user-exit (in program MV50AFZ1). It stops both with VL01N and VL10A.

Check out, is your BADi working in VL01N? If not, then you might try out the user-exit...

Regards

Tamá

[Former Member]

Hi,

Yes, It works fine with VL01N, VL02N. But I want to check VL10 because there is a method which executes only during certain scenario that is created by VL10.

Thanks,

SA

[Former Member]

Try system debugginh(/hs) - In certain cases it will stop only if sytem debugginh is switched on

[Former Member]

Thanks Tamás  and Sam SS,

I tried System debugging also but it didnt work. But I got solution for it. I like to share with all of you that is:

With the source code corrections specified under Corrections, you create the prerequisites for an automatic branching to the debugging at the beginning of function modules RV_DELIVERY_CREATE and GN_DELIVERY_CREATE as well as in 'Save document' of the delivery.

In order to activate these breakpoints, user parameter 'LEDSP_DEBUG_MODE' must contain string VL10 (maintainable per user, for example, with Transaction SU3).

You must take into account that in case of improper application the usage of these breakpoints might lead to non-supply, to inconsistencies in the database or to excessive consumption of system resources.

Thanks,

SA

<moderator message: refer SAP Note 444078 for further details>

Message was edited by: Manish Kumar

[Former Member]

issue is resolved.