topic Re: Background execution - VL06O in Application Development and Automation Discussions

Background execution - VL06O

Former Member — Fri, 19 Jun 2009 10:30:35 GMT

Hi All,

We have a peculiar problem. User is able to view data for VL06O in foreground but when the report is run with the same parameters in the background the values do not show up. The batch job shows status "complete" and no errors appear.

Thanks in advance for your responses

Regards

Vijaya

Re: Background execution - VL06O

Former Member — Fri, 19 Jun 2009 10:50:58 GMT

Hi,

While running the transaction in the back ground run a trace report via ST01 and check whether you get any entry with RC=4 related to s_btch* and let us know.

Regards

Aveek.

Re: Background execution - VL06O

Former Member — Fri, 19 Jun 2009 10:58:05 GMT

Per the error , S_BTCH_ADM = Y is required. But per our security policy this cannot be enabled for end users (non-Basis team members)

Re: Background execution - VL06O

Former Member — Fri, 19 Jun 2009 11:58:08 GMT

Hi,

In this case you need to give this authorization to certain users who will deal with Back ground activities. Then these users will be able to view the data when vl06O is ran in Back ground.

Please let me know if any further info needed.

Regards

Aveek.

Re: Background execution - VL06O

sdipanjan — Fri, 19 Jun 2009 14:06:36 GMT

What is the user id you used to use in Production to execute the steps of the Batch Job? Is this same as the Job scheduler? Or is there any SYSTEM ID used... (check your SOP)

You should create a system id in Prod and use this for all Job execution.. for this system id you can put S_BTCH_ADM 's filed value = Y... there will be no issues from Security point of view..

So in your case.. use this type of system id to define the steps of the Job and run it again.. then check the spool list...

Regards,

Dipanjan

Re: Background execution - VL06O

Former Member — Fri, 19 Jun 2009 21:56:59 GMT

> Per the error , S_BTCH_ADM = Y is required.

This is a famous "red herring"... If you are seeing this in the trace, double-click the object before the S_BTCH_ADM check and take a look in the top left corner for the "Jump to code" button to see the context.

Also when you check the background job, check in SU24 whether there is a check indicator set to "No check" for the transaction code.

--> When run in the forground, sy-tcode is known.

--> When you submit a report in the background (e.g. from SA38 - which makes no sense to deactivate a context sensitive check as it is generic...) then sy-tcode is often not known.

This might explain the difference...

Cheers,

Julius