2021 Dec 24 12:47 PM
Hi Everyone,
The requirement is to create Outbound Deliveries in Background Mode. To execute in background mode, I have a custom program through which a background job is created. If I try to debug that job then it is not triggering the custom VOFM routine and directly coming out of debugger. Can anyone give any solutions why the routine is not getting triggered?
But in Foreground Mode, if I try to create an Outbound Delivery through VA02 or VL10C, then the VOFM custom routine is getting triggered while debugging and it is working as expected.
I also tried executing standard SAP program 'RV80HGEN' to execute all routines but it is not working.
Also, I tried SU3 transaction to set parameter id 'LEDSP_DEBUG_MODE' and parameter value as VL10C and setting breakpoints at subroutine but it the custom routine is not getting triggered while debugging.
Any Solutions?
Thanks,
Abhishek
Hi Everyone,
The requirement is to create Outbound Deliveries in Background Mode. To execute in background mode, I have a custom program through which a background job is created. If I try to debug that job then it is not triggering the custom VOFM routine and directly coming out of debugger. Can anyone give any solutions why the routine is not getting triggered?
But in Foreground Mode, if I try to create an Outbound Delivery through VA02 or VL10C, then the VOFM custom routine is getting triggered while debugging and it is working as expected.
I also tried executing standard SAP program 'RV80HGEN' to execute all routines but it is not working.
Also, I tried SU3 transaction to set parameter id 'LEDSP_DEBUG_MODE' and parameter value as VL10C and setting breakpoints at subroutine but it the custom routine is not getting triggered while debugging.
Any Solutions?
Thanks,
Abhishek
2021 Dec 24 3:46 PM
Interesting.. though it shouldn't be the case.. pricing should be generally independent of Foreground or Background.. since you mention Custom program.. there may be certain parameters that may be different.. Is the requisite condition(for which the routine is assigned) triggered OR seen in the resultant Background job delivery? you may also check the relevant condition records..
Regards,
Vijay
2021 Dec 24 4:51 PM
It's very strange. Are you sure you run "custom program 2" below exactly the same way in the two cases? (same parameters, etc.)
I don't know how you debug "custom program2" in background but if you go to SM37 and run the job with the command JDBG, without debugging, do you stop at the break-point at the beginning of the VOFM routine?
2021 Dec 27 11:44 AM
We have only 1 custom program for background job and in that custom program we are calling the standard program "RVV50R10C" to create deliveries. We are debugging the background job with "JDBG" but it is not stopping at the breakpoint of the VOFM custom routine.
In foreground, we creating deliveries through transaction VA02 and not through any custom program and there the VOFM routine is triggered at the breakpoint and it is working as expected.
Only issue is in the background mode as the routine is not triggered at breakpoint. Any solutions?
2021 Dec 30 2:09 PM
Okay, it explains why it behaves differently, it's because you don't execute the same code, so the problem is not about "background mode", it's about VA02 stops at break point, and RVV50R10C (VL10C) doesn't stop at break point. Or maybe, VA02 calls VOFM routines and VL10C doesn't call them.
I would look at the forum:
"VL10c" "vofm" site:sap.comI see this question/answer: Copy control routine is not getting triggered when executing using VL10G tcode in background mode | ...
2022 Jan 03 1:42 PM
Yes, whenever we are using VL10C transaction code it is not calling the VOFM routines. So is there any solution to call the VOFM routines from VL10C transaction code or RVV50R10C?
2025 Sep 08 2:04 PM
2025 Sep 08 3:01 PM
| User | Count |
|---|---|
| 3 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |