Different behavior when submiting and calling transaction vl10b

[naotoxxx]

Hello i'm calling my program rvv50r10c and passing some values but when i execute it i don't get any result but if i open a new mode and call tx vl10b with same parameters it shows results, look:

after execute : 

now, if i call trnasaction vl10b

after execute it, i get this:

Solution

I needed at leat a date in my parameter, with that is done

[Lakshmipathi]

VL10B calls program RVV50R10_PRESTEP, which in turn calls RVV50R10C. It skips the initial screen and uses predefined parameters or user profiles, whereas, program RVV50R10C displays the selection screen and processes deliveries based on input criteria. When run directly, it behaves like a standalone report.
Having said that, when you run the program, you get the full selection screen and can manually enter parameters. It doesn’t inherit the user role profile, default filters, or variant logic that VL10B applies automatically.

If you're seeing different delivery creation results, it's likely because VL10B applies filters or logic that aren't active when you run RVV50R10C directly. VL10B might exclude blocked orders or apply a specific delivery creation horizon, while RVV50R10C processes everything based on what you manually input.

[RaymondGiuseppi]

You should start by analyzing FM SHP_VL10_PRESTEP to build your code.