Limit user from submitting a background job

Hi,
Is there a parameter that would limit the user from submitting a background job?
Regards,
Raquel

Read about Authorization object S_BTCH_JOB
http://help.sap.com/saphelp_nw70/helpdata/en/86/f7f3393bef4604e10000000a11402f/content.htm
Regards
Juan

Similar Messages

User Name in a background job

Hello All,
I am running a report in background that creates data in IT0105. This table has a field "UNAME". When I run it in
foreground this field takes up the id from which I am logged in. The program doesn't complete in background because
it has a BDC which we complete forcefully in foreground due to some data issue.
So I need to know what will be the "UNAME" in IT0105 when the report runs in background?
Thanks,
Ritika Mathur

Hello Neal,
Actually I don't need to check any authority. The issue is that I need to track and give a proof that it is not the program putting in inconsistent data into the database. So in foreground I can run and test that the user name is the id I was logged into from. But in background I assume that the user name is set to "BATCH". (I see the data previously created in IT0105 and the username is either the ids of logged in users or "BATCH" as the report is actually meant to run as a background job).
Now I cannot test in background and hence need to know if the username is set to "BATCH" if a program runs in background.
Thanks,
Ritika

DYNPRO_SEND_IN_BACKGROUND when submitting a background job, when creating a

Hi.
We create sales orders via EDI. When certain sales orders are created, we execute user exists on the Sales Order save. During the User Exit, we submit/create (job_open_adk function, the submit command, and the job_close_adk function) a background job.
The background, is created and executed successfully, but we get 2
short dumps everytime.
The short dump is:
DYNPRO_SEND_IN_BACKGROUND
The description is:
Screen output without connection to user.
The short dump is for the user WF-BATCH.
I've used DEBUG and the shortdump occurs on the submit command.
submit zsd
to sap-spool
destination 'null'
immediately ''
keep in spool 'X'
without spool dynpro
and return
user l_user via job tbtcjob-jobname
number tbtcjob-jobcount
with p_vbeln = l_order
with p_ebeln = l_po
with p_uname = l_user.
Nothing should be displayed on the screen.
I used 'without spool dynpro' to prevent the 'Print Screen List' window
from appearing.
I've put this code into a TEST program. I ran the test program
myself. (under my ID) The program run perfectly. No
shortdump.
Similar code is used in other programs and it works perfectly - no shortdumps.
The short dump occurs when we use ALE/EDI to create a sales order.
The short dump has the ID WF-BATCH on it.
I'm guessing the problem is with the WF-BATCH ID. Are printer setting
missing on a Work Flow ID?
Any ideas why the 'without spool dynpro' parameter doesn't work for the
WF-BATCH ID?
I've tried searching OSS and I looked at the on-line help/documentation
on Submit. I saw a recommentation to use the
fuction 'GET_PRINT_PARAMETERS' to set all of the print parameters. I
tried this, but still got the short dumps.
Any suggestion on how I can run the Submit command and not get a short dump?
thanks,
Michelle

Hi,
Try this notes:
0100915 RSBDCREO: System hangs or parameters not effective
0377038 HR-CA-ALE: DYNPRO_SEND_IN_BACKGROUND for HR doc. d
0105165 Dump "DYNPRO_SEND_IN_BACKGROUND" in prog.SAPMSSY0
0169303 Warning messages displayed for settlement mass pro
0428489 VL10: Dump 'DYNPRO_SEND_IN_BACKGROUND' with backgr
[[http://forums.sdn.sap.com/thread.jspa?threadID=14875|http://forums.sdn.sap.com/thread.jspa?threadID=14875]]
Regards
HM

Is it possible to prevent users from changing iPad background?

I am currently helping deploy 130 iPads for a school using Apple Configurator. I have set the desired wallpaper and lockscreen text via Apple Configurator, however this can easily be removed if a user decides to change the lockscreen wallpaper. Is there any way to set a restriction that would prevent a user from changing the lockscreen wallpaper? Any ideas would be greatly appreciated! Thanks for the help in advance!

I heard that with iOS6 MDMs could have the ability to remotely change the wallpaper and lockscreen OTA. So far Airwatch is the only one I've heard of that claims to be able to do it:
http://www.air-watch.com/company/news-room/press-releases/2012/09/airwatch-offer s-same-day-comprehensive-support-for-apple-ios-6
(scroll down to "New MDM Capabilities")
I hope other MDM's adopt this. It sure would be nice to be able to do this from an MDM.
Hope this helps!
~Joe

Submitting a updates in a prog to a background job

Hello everyone,
I am generating a alv report with production orders.In the toolbar i created a button for updating data.When i select some production orders in the alv list and select the button then transaction co02 is called and some updates are done.I done that the updating by using bdc recording and the updates are working fine.
But my problem is
1. when the user selects the updates button in the toolbar these updates should take place via. a background job.
2. Before submitting the background job the program needs to check if a version of a prog is running,the check should look for the prog name and the triggering user, if a match is found the user should receive a error message.
3. If a match is not found then the background job should be scheduled immediately and should be created with a name of prog name and the triggering user.
I need to these steps,can anyone please give me a sample code for this.
Thank you.
dp.

The approach I would probably take for this would be:
1. Write the records that need processing to a "Z" table from the ALV, and delete these back out (or mark as "done") once processed by the batch job.
2. It is possible to check for a batch job name and its status, but I've usually found an easier and more reliable way is to use a lock object to check this e.g. you could use and existing object such as ESRDIRE with a dummy lock argument such as 'CO02_IS_LOCKED' . The batch job should contain code to set the enqueue... if this enqueue fails it means another job / program is already processing the requests so this instance can stop, otherwise the batch program can continue the CO02 processing. In other words, you are creating a doorway through which only one instance of the job can pass at a time.
3. A couple of easy ways to do this are (a) event triggered jobs, wherein you define the job and have it fire up when an event is raised (e.g. by calling function BP_EVENT_RAISE) or (b) use the SIMPLE_BATCH_JOB_SUBMIT (which calls the JOB_OPEN, JOB_SUBMIT, JOB_CLOSE functions for you).
Jonathan

Submitting a update in a porg to a background job?

Hello everyone,
I am generating a alv report with production orders.In the toolbar i created a button for updating data.When i select some production orders in the alv list and select the button then transaction co02 is called and some updates are done.I done that the updating by using bdc recording and the updates are working fine.
But my problem is
1. when the user selects the updates button in the toolbar these updates should take place via. a background job.
2. Before submitting the background job the program needs to check if a version of a prog is running,the check should look for the prog name and the triggering user, if a match is found the user should receive a error message.
3. If a match is not found then the background job should be scheduled immediately and should be created with a name of prog name and the triggering user.
I need to these steps,can anyone please give me a sample code for this.
Thank you.
dp.

The approach I would probably take for this would be:
1. Write the records that need processing to a "Z" table from the ALV, and delete these back out (or mark as "done") once processed by the batch job.
2. It is possible to check for a batch job name and its status, but I've usually found an easier and more reliable way is to use a lock object to check this e.g. you could use and existing object such as ESRDIRE with a dummy lock argument such as 'CO02_IS_LOCKED' . The batch job should contain code to set the enqueue... if this enqueue fails it means another job / program is already processing the requests so this instance can stop, otherwise the batch program can continue the CO02 processing. In other words, you are creating a doorway through which only one instance of the job can pass at a time.
3. A couple of easy ways to do this are (a) event triggered jobs, wherein you define the job and have it fire up when an event is raised (e.g. by calling function BP_EVENT_RAISE) or (b) use the SIMPLE_BATCH_JOB_SUBMIT (which calls the JOB_OPEN, JOB_SUBMIT, JOB_CLOSE functions for you).
Jonathan

Problem with background job using SUBMIT under different user

Hi All,
I am submitting a background job under different user name. I am submitting this job by using JOB_OPEN , SUBMIT report and JOB_CLOSE. But submit statement is returning sy-subrc 8, becuase of this the job_close is failed. Can you please help me to solve this problem.
Thanks in advance.
Tjgupta

Hi,
The user is having all authorizations. is there any difference with user types?
This user is having user type " as communication data".
Thanks,
Tjgupta

E-Mailing Background Job Log from SM36

Friends,
Is there a way that you can set up automatic emailing of the log from a periodic background job set in SM36? I want this log to be sent to few external E-mail IDs.
Let me know.
Thanks
Jagadish

Dear Jagadish,
In my previous project we have achieved the same requirement,like sending the mail to particular User Id's
for a background run job.
Check with these steps,
Go to T code S023 > create>enter some name and Title->Folder ->private or shared one>Save->
back button->select name & change then recipient name mail address-->recipient type --->internet
address and then save.
In SM36 before scheduling the job click on spool list recipient and assign the one which you have
created,then you schedule the job ,give some job name and then save.
Before doing the above steps ask your BASIS consultant whether sending mails is active,the same can be
checked in T code SCOT.
Check and revert back whether you are successfful or not.
Regards
Mangalraj.S

Pass parameter to background job from report

Hi All,
I have following requirement.
I am executing a Report. At end of report I am executing an event.
On the bases of event a background job runs.
Problem is that, I want to pass one field data from report to background job.
I already tested SET PARAMETER/GET PARAMETER is not working.
Is there any way any one can suggest, without using Tables.
Regards

Hi,
If you submit via job it will not be executing the program ..After SUBMIT statement the control will come to the program immediately..
Check this example..
DATA: p_jobcnt LIKE tbtcjob-jobcount,
      l_release(1) TYPE c.
Open the job
CALL FUNCTION 'JOB_OPEN'
     EXPORTING
          jobname          = 'ZMY_OBJ'
     IMPORTING
          jobcount         = p_jobcnt
     EXCEPTIONS
          cant_create_job = 1
          invalid_job_data = 2
          jobname_missing = 3
          OTHERS           = 4.
Submit the job.
SUBMIT ztest_program VIA JOB 'ZMY_OBJ' NUMBER p_jobcnt
       TO SAP-SPOOL WITHOUT SPOOL DYNPRO
       WITH destination = 'LOCL'
       WITH immediately = space
       WITH keep_in_spool = 'X' AND RETURN.
Close the job.
CALL FUNCTION 'JOB_CLOSE'
     EXPORTING
          jobcount             = p_jobcnt
          jobname              = 'ZMY_OBJ'
          strtimmed            = 'X'
          prdmins              = 15
     IMPORTING
          job_was_released     = l_release.
Thanks,
Naren

How to limit end user from creating grid

Can I limit the end user's ability of creating new grids? What is the best practice for managing grids?
Thanks!

The best practice is to allow end user to create and save their own grids. There is no need to limit users from a potentially useful feature. If you have grids which you don't want users to change, assign a class to those grids which they should change, and give them View access to that class.
If you still don't want users to save their own grids, you might try giving them View access to the [Default] class, though any user smart enough to assign a class to the grid for which the user has All access to can still save the grid. Such users should be recruited to the application administration team and given a raise :-)
--Chris

Background Job Scheduling

Hi,
I am scheduling a report to run in background.
In this report it is creating background jobs automatically for different company codes.
It submits the 1st background job and waits until it finishes.
Then 2nd job starts in background and continues with other jobs.
At end it finishes all the jobs and closes.
Now my problem is.
1.       Whether is it possible for us to submit all the jobs at 1 time. And execute at same time. Ie., 1st, 2nd job will start at same time.
2.       If possible how can we do that.
What I have written is
loop at companycode.
Create job name.
call fun 'Job_Open'.
submit xxxx user sy-uname via job job_name numer job_count
to sap-spool
spool parameters l_spool_parameter
without spool dynpro
with companycode
with ......
and return.
endloop.
Please help ASAP, urgent.

hi praveen,
Job Scheduling Explained
Definition
Before any background processing can actually begin, background jobs must be defined and scheduled. The scheduled time for when a job runs is one part of the jobs definition. There are several ways to schedule jobs:
From Transaction SM36 (Define Background Job)
With the "start program in the background" option of either Transaction SA38 (ABAP: Execute Program) or Transaction SE38 (the ABAP editor)
Through the background processing systems own programming interface. (Many SAP applications use the internal programming interface to schedule long-running reports for background processing.)
Through an external interface.
Scheduling Background Jobs
Use
You can define and schedule background jobs in two ways from the Job Overview:
·         Directly from Transaction SM36. This is best for users already familiar with background job scheduling.
·         The Job Scheduling Wizard. This is best for users unfamiliar with SAP background job scheduling. To use the Job Wizard, start from Transaction SM36, and either select Goto ® Wizard version or simply use the Job Wizard button.
Procedure
       1.      Call Transaction SM36 or choose CCMS ® Jobs ® Definition.
       2.      Assign a job name. Decide on a name for the job you are defining and enter it in the Job Name field.
       3.      Set the jobs priority, or Job Class:
·         High priority:      Class A
·         Medium priority: Class B
·         Low priority: Class C
       4.      In the Target server field, indicate whether to use system load balancing.
·         For the system to use system load balancing to automatically select the most efficient application server to use at the moment, leave this field empty.
·         To use a particular application server to run the job, enter a specific target server.
       5.      If spool requests generated by this job are to be sent to someone as email, specify the email address. Choose the Spool list recipient button.
       6.      Define when the job is to start by choosing Start Condition and completing the appropriate selections. If the job is to repeat, or be periodic, check the box at the bottom of this screen.
       7.      Define the jobs steps by choosing Step, then specify the ABAP program, external command, or external program to be used for each step.
       8.      Save the fully defined job to submit it to the background processing system.
       9.      When you need to modify, reschedule, or otherwise manipulate a job after you've scheduled it the first time, you'll manage jobs from the Job Overview.
Note: Release the job so that it can run. No job, even those scheduled for immediate processing, can run without first being released.
Specifying Job Start Conditions
Use
When scheduling a background job (either from Transaction SM36, Define Background Job or CCMS ® Jobs ® Definition), you must specify conditions that will trigger the job to start.
Procedure
Choose the Start condition button at the top of the Define Background Job screen.
Choose the button at the top of the Start Time screen for the type of start condition you want to use (Immediate, Date/Time, After job, After event, or At operation mode) and complete the start time definition in the screen that appears.
For the job to repeat, check the Periodic job box at the bottom of the Start Time screen and choose the Period values button below it to define the frequency of repetition (hourly, daily, weekly, monthly, or another specific time-related period). Then choose the Save button in the Period values screen to accept the periodicity and return to the Start Time screen.
Once youve completed specifying the job start conditions, choose the Save button at the bottom of the Start Time screen to return to the Define Background Job screen.
No job can be started until it is released, including jobs scheduled to start immediately. Since releasing jobs can be done only by a system administrator from the job management screen (Transaction SM37) or by other users who have been granted the appropriate Authorizations for Background Processing, no unauthorized user can start a job without explicit permission
Managing Jobs from the Job Overview
Use
The Job Overview, or Job Maintenance, screen is the single, central area for completing a wide range of tasks related to monitoring and managing jobs, including defining jobs; scheduling, rescheduling, and copying existing jobs; rescheduling and editing jobs and job steps; repeating a job; debugging an active job; reviewing information about a job; canceling a job's release status; canceling and deleting jobs; comparing the specifications of several jobs; checking the status of jobs; reviewing job logs; and releasing a job so it can run.
Procedures
To display the Job Overview screen, choose CCMS ® Jobs ® Maintenance or call Transaction SM37. Before entering the Job Overview screen, the system first displays the Select Background Jobs screen. You'll need to complete this Job Selection screen to define the criteria for the jobs you want to manage. Once you've selected jobs to manage, you can choose from a wide range of management tasks:
To copy a single existing job, choose Job ® Copy.
To reschedule or edit job steps or attributes of a single job, choose Job ® Change. A job step is an independent unit of work within a background job. Each job step can execute an ABAP or external program. Other variants or authorizations may be used for each job step. The system allows you to display ABAP programs and variants. You can scan a program for syntax errors. You can also display the authorizations for an authorized user of an ABAP job step.
To repeat a single job, choose Job ® Repeat scheduling.
To debug an active job, choose Job ® Capture: active job. Only a single selection is allowed. If an active job seems to be running incorrectly (e.g., running for an excessively long time), you can interrupt and analyze it in debugging mode in a background process, and then either release it again or stop it altogether.
You will be able to capture a background job only if you are logged on to the SAP server on which the job is running. To find server information in the Job Overview, select and mark the job, then choose Job ® Job details.
To review information about a job, choose Job ® Job details. Details displayed can include:
current job status
periodicity, or the repetition interval
other jobs linked to the current job, either as previous or subsequent jobs
defined job steps
spool requests generated by the current job
To cancel a job's "Released" status, select the job or jobs from the Job Overview list and choose Job ® Release -> Scheduled.
To cancel a job from running but keep the job definition available, select the job or jobs from the Job Overview list and choose Job ® Cancel active job.
To delete a job entirely, select the job or jobs from the Job Overview list and choose Job ® Delete. Jobs with the status of Ready or Running cannot be deleted.
To compare the specifications of more than one job, select the jobs from the Job Overview list and choose Job ® Compare jobs.
To check the status of jobs, select the job or jobs from the Overview Job list and choose Job ® Check status. This allows you to either change the job status back to Planned or cancel the job altogether. This is especially useful when a job has malfunctioned.
To review job logs, select a job or jobs with the status Completed or Canceled from the Job Overview list and
regards
karthik
reward me points if helpfull

Background job- getting printed automatically

In my BDC Program i have submitted Session for Background Processing using
Submit RSBDCSUB..........
my code is also given below..The problem is after the user executes the program, background job is automatically going to his Local printer and getting printed. HOw to avoid this?
CALL FUNCTION 'JOB_OPEN'
       EXPORTING
            jobname          = gf_jobname
       IMPORTING
            jobcount         = gf_jobcount
       EXCEPTIONS
            cant_create_job = 1
            invalid_job_data = 2
            jobname_missing = 3
            OTHERS           = 4.
*-Submit the selected sales orders for changes.
SUBMIT rsbdcsub AND RETURN
         WITH mappe = v_sess
         WITH von = sy-datum
         WITH bis = sy-datum
         WITH z_verarb = 'X'
         WITH fehler = space
         WITH batchsys = space
         WITH logall = space
         USER sy-uname VIA JOB gf_jobname NUMBER gf_jobcount.
IF sy-subrc NE 0.
    MESSAGE i999 WITH text-013.
    EXIT.
ENDIF.
*-Close job and start immediately.
CALL FUNCTION 'JOB_CLOSE'
       EXPORTING
            jobcount             = gf_jobcount
            jobname              = gf_jobname
            strtimmed            = 'X'
       IMPORTING
            job_was_released     = gf_release
       EXCEPTIONS
            cant_start_immediate = 1
            invalid_startdate    = 2
            jobname_missing      = 3
            job_close_failed     = 4
            job_nosteps          = 5
            job_notex            = 6
            lock_failed          = 7
            OTHERS               = 8.

On SUBMIT use
SUBMIT zxxxxxx TO SAP-SPOOL
                    WITHOUT SPOOL DYNPRO
                    IMMEDIATELY ' '
                    KEEP IN SPOOL 'X'
                    DESTINATION printer
                     NUMBER number
                    AND RETURN

Background Job cancellation-Alert config in Solman

Team,
We would like to send an alert to the distribution list or the user whenever a particular background job is getting cancelled.
Could you please let me know the steps how it can be done in solution manager.
Regds,
Satyanarayana N

Hello,
I recommend to setup the Job Monitoring of Business Process Montoring from a Job Documentation. The alerts can either generate notifications (E-Mail, SMS) or workflow documents (messages in Support Desk).
This is demonstrated in a RKT tutorial:
http://service.sap.com/~sapidb/011000358700001911422008E.sim
The process is also documented:
http://help.sap.com/saphelp_smehp1/helpdata/en/8e/3ad6f807e147669036d2a6aed597aa/frameset.htm
Please also visit our Service Markteplace representation: http://service.sap.com/jsm
Kind regards,
Martin

Reg : Background job

Hi Guru's
I am sending IDOC from R/3 System to APO System.when idoc reached APO system.its triggers immediately and creating one file in application server(APO).sometimes this process makes more than 10 to 15 hours so user dont know whether is executing or failed. so i gave one soltion to user that is creating background job while idoc is executing when its idoc is processed then the background job also shows that finished..i dont know how to write this background job code in IDOC function module and also i dont know its possible in IDOC. i dont have knowledge in IDOC..Please helpme on this issue.
anybody helpme on this issue.????
Regards
P.Senthil Kumar

Hi,
You have not to write Back Ground Code in FM of IDOC.
To Process Idoc in Back Ground do following Step
Go to T-CODE We20
Select Partner
Double Click on any IDOC Message type in Outbound Parameter like INVOIC
In Outbound Options Tab, at Output Mode select Collect Idoc Radio Button.
For Inbound parameterDouble Click on any Message type.
Select Trigger by BackGround Program Radio Button
Please use T-code SM36 to schedule program which process Idoc.
The Program used is,
RSEOUT00 : For Processing 30 Status IDocs For outbound Idoc
RBDAPP01 : For Processing 64 Status IDocs For Inbound Idocs
T-code BD87
To Refer more about IDOC,
https://wiki.sdn.sap.com/wiki/display/ABAP/ALE%2CIDOC
https://wiki.sdn.sap.com/wiki/display/ABAP/ALE+IDOCS
Thanks & Regards,
ShreeMohan
Thanks & Regards,
ShreeMohan

GUI_UPLOAD in Background jobs

Hi,
I have a requirement where in the a text file is received from an external application at the end of each day. This text file has to be picked up by the SAP system and SAP transaction MFBF has to be updated. The customer wants this entire process to be done without any user intervention. A background job needs to be scheduled at the end of the day. However the problem is GUI_UPLOAD cannot be used to pick up the text file, because of the Background job. Any suggestions are welcome.

You cant use GUI UPLOAD or DOWNLOAD function in backgroun jıb.
U can use DATASETS
DATA:
dsn(20) VALUE '/usr/test.dat',
rec(80).
OPEN DATASET dsn.
IF sy-subrc = 0.
DO.
    READ DATASET dsn INTO rec.
    IF sy-subrc <> 0.
      EXIT.
    ELSE.
      WRITE / rec.
    ENDIF.
ENDDO.
ENDIF.
CLOSE DATASET dsn.
ibrahim

Limit user from submitting a background job

Similar Messages

Maybe you are looking for