Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

VOFM Custom Routine not getting triggered while creating Outbound Deliveries in Background Mode

0 Likes
6,962

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

7 REPLIES 7
Read only

vijay_hariharan
Contributor
6,782

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

Read only

Sandra_Rossi
Active Contributor
0 Likes
6,782

It's very strange. Are you sure you run "custom program 2" below exactly the same way in the two cases? (same parameters, etc.)

  • "background" case: SE38 Custom program 1 ---run job---> custom program 2 which does VA02 or VL10C
  • "foreground" case: SE38 custom program 2 which does VA02 or VL10C

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?

Read only

0 Likes
6,782

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?

Read only

Sandra_Rossi
Active Contributor
0 Likes
6,782

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.com

I see this question/answer: Copy control routine is not getting triggered when executing using VL10G tcode in background mode | ...

Read only

0 Likes
6,782

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?

Read only

stephanysonos
Newcomer
0 Likes
5,335

Someone found a solution for this?

Read only

0 Likes
5,282

Please create a new discussion detailing your issue with the related screen shots so that members will assist you.  This discussion has been originally created by someone in 2021