Restrict background jobs to immediate execution

Hello,
we have got a central jobmanagment and want to restrict background jobs to immediate execution.
Of course users should be able to send processes in the background, especially when creating a list needs a lot of performance. But users should not be able to plan these jobs to a time in future or perodically.
So, in authorization object S_BTCH_JOB I didn't find a solution - just JOB_ACTION can be restricted to "RELE", so that a user needs a release from another user. This is not what we want.
Is there a possibility to restrict the execution in background to the Option "immediate". The options "Date/Time", "After job", "After event", "at operation mode" should not be possible.
Regards,
Julia

Hello Julius,
with searchterm "BTCOPTIONS" I can't find suitable notes or anything else, even with a search machine.
But I found thread Restrict periodic scheduling in SM37 which describes exactly this problem.
So I will ask in that thread again, because there haven't been any news since may.
Regards,
Julia

Similar Messages

Background job with immediate start

Hi,
In my program, I have to create a background job with immediate start. I used function module 'BP_JOB_CREATE', but it does not start immediately.
Can anybody provide sample code for immediate job start.
Regards,
Nitin

Hi,
Use these function modules.
JOB_OPEN
JOB_SUBMIT
JOB_CLOSE
in JOB_SUBMIT function module u can pass to start the job immediately in export parameters PRIPARAMS structure field name PRIMM which has to be set to 'X' to start immediately.
regards,
Santosh Thorat

Restrict background Jobs thro' ABAP Program

Hello,
While I was working in one of the customer place , they restricted the background jobs thro' one ABAP program for customer reports . Unfortunately , I don't have the source code with me. As you are all aware that users fires the background jobs for different periods so that he/she can submit the reports to the higher up in time.
Scenario : I have 10 application servers and each application has 20 work processes ( 12-Dialog,4-Background,3-spool,1-Gateway). I would like to restrict 1 background process/per appl server for customer reports(Y OR Z programs) during the business hours .
It would be great help to Basis Consultants , if you can contribute to restrict the background jobs .
Thanks
Regards,
S.Srinivasan

Hi Daniel,
The program MEREP_DISTRIBUTOR(Client Data Distributor) determines delta data independent of a download request from the client.This is mainly used to reduce the load on the server and scheduling of this program is part of "SAP MI Administration" which is generally performed as part of OR after MI Post Installation steps that recommends you to Schedule Background Jobs for Generic and Smart Sync which you wanted to confirm in your post.So the programs
(1)WAF_MW_MAPPING
(2)WAF_DEPLOYMENT_FROM_ROLES &
(3)MEREP_RETRY_BP
are good enough for scheduling Generic & Smart Sync(in your case for MAM).Apart from these you may have to check up the Handler Settings that is mentioned in my previous post.
Hope this helps.
Thanks
Gisk

Restrict Periodic jobs scheduling from SM36 or any other t-code

HI,
We would like to restrict users from scheduling periodic background jobs. Immediate jobs will be fine.
And also one more concerns is that user should not be able to directly execute any report or transaction in background periodically.
In short immediate jobs will be fine but users should not be able to set periodic jobs by any T-code.
Thanks,
Chandresh Pranami

If you search for "btcoptions" you will find a comprehensive discussion about this, and a development suggestion in the wiki.
I attempted the same and ended up recreating the UI from scratch and scheduling the report + variant from a parameter transaction they are authorized for, but the user can navigate in many transactions showing this option.
A compensating control when retiring users and central batch administration with monitoring is easier.
Cheers,
Julius

How to restrict the job start conditions (only "Immediate" type) ?

Hi,
We allow our users to schedule and execute in background mode transactions (example IP19, IW38). We gave them for that authorizations (object S_BTCH_JOB with LIST, PROT, RELE and SHOW - objetct S_PROGRAM with BTCSUBMIT).
We would like that users can schedule and execute their jobs only with the u201CImmediateu201D job start condition (in the Start Time screen for the type of start condition : Immediate, Date/Time, After job, After event, or At operation mode).
Another solution: prohibit the scheduling and the execution background job in a certain time interval ...
How can restrict the job start conditions ?
Thank you.
Patrice.

Hi Jan,
Yes, sa38 makes it possible indeed to execute in background into immediate mode a job but
the user have to know the name of the program to be carried out ...
The user knows only the name of these transactions trade. For example, IW38.
In the menu of this transaction, SAP gives the possibility to execute in background :
Program --> Execute in Background --> display of Start Time screen for the type of start condition :
Immediate, Date/Time, After job, After event, or At operation mode).
It is at this time there that we want that the user can only choose the "immediate" mode.
We must thus prohibit the other choices (Date/Time, After job, After event, or At operation mode) ... and
and we don't know how to restrict these other options in this screen "Start Time screen for the type of start condition".
Thank you.
By.

Scheduling function module execution in background jobs

Hi,
I have requirement where in after obtaining all the required inputs from the user we will call an function module to execute it.
The requirement is that the execution of fm shld happen in background and a log must be created showing the user whther it was successful or if it failed with the list of errors.
Can you kindly give some input on how to schedule the execution of function module in background job and if scheduled how to create the logs to display the success or error message.
Warm Regards,
Naveen M

Hi,
Just create a simple program where you have to call this FM.
Pass the values to FM either by declaring some internal table of selection screen and execute the program in background.
For Message Log, you can use structurre BDCMSGCOLL
DATA: MESSTAB LIKE BDCMSGCOLL OCCURS 0 WITH HEADER LINE.
After Call to FM, read from this internal table as follows
READ TABLE MESSTAB WITH KEY MSGTYP = <Message Type>
MSGNR = <Message Number>.
regds,
Anil

Long time for execution for scheduled CIF background jobs

Hi,
we hv schedlued CIF background job to be run daily around 10.30 PST.
there is large variation for the time required for execution of this job.
on 26 Dec, it took approx 48000 seconds while regular average is 120 seconds only.
today, despite past of 6000 seconds, the job is still in ACTIVE stage.
can anyone know why such long delay for such jobs?
how can i reduce its execution time (as one of case in a week)?
rgds/Jay

Hi Jay,
A few obvious things to look for:
1. Multiple CIF activation jobs running at the same time
2. Large change in the master data, eg new plant, new Material Masters, new customers, etc etc.
3. Conflicts with other non CIF programs that may be going after the same data
4. Communication degradation between the OLTP and SCM clients
Normally you refer such questions to someone on your Basis team, or perhaps your DBA. They can turn on tracing tools that can track the changes in your environment that may be contributing to the changes in run time.
Regards,
DB49

Background Job execution enabled via pro-active monitoring

Hi community,
We're interested in CPS Redwood to help us in proactive monitoring of background jobs (Ad Hoc and Periodic) and impacts in system performance.
The idea would be to have somehow a tool that monitor the number of available working process and system performance. When the system workload reaches a certain level, ex: 95%, this tool would intercept new jobs execution. After this, when the system workload goes down and the resources are free, the system would release all jobs to normal run again.
Is it possible via CPS Redwood?
Is there any other way to have something automatic like this?
Thanks,
Jose Antonio.

Hi Jose,
This is possible indeed using CPS. CPS can monitor various load metrics of your system, then adapt the scheduling logic if thresholds are exceeded.
In your scenario, you would basically always intercept all jobs, but normally not enforce any limits so effectively that means all jobs still run immediately. If the load is too high, CPS would enforce a limit, so then jobs will be delayed until the load is lower again.
Regards,
Anton.

Execution of Macro in Background job

We have created a macro in APO DP that uses 4 characteristics and a key figure. As part of the macro we are executing a Z-function that we have created. The problem occurs when executing the macro in a background job. When the background job is executed the macro processes correctly (performs the correct calculations) for the first CVC that is processes, but it is not able to process the rest of the CVCs.
ERROR: "There are no plannable characteristic combinations",
The function copies data from the CVC that is being processed (source CVC) to another CVC (target CVC). The values for the target CVC to which the data has to be copied for a particular key figure are determined from the paramaters that are given to the function in the macro.
The steps followed in the function are the following:
1- Determine the relation between source and target CVC, ie, from the source CVC that is being processes in the macro, the function determines the target CVC to which the data has to be copied.
2- Call BAPI "BAPI_PBSRVAPS_GETDETAIL2" to retrieve the valuesthat are in the Planning Book for the source CVC.
3- Perform the addition of data (value retrieved from the source CVC is added to the target CVC).
4- Write value to the target CVC using BAPI "BAPI_PBSRVAPS_CHANGEKEYFIGVAL2".
When using the BAPIs the aggregation level used is the same aggregation as the one specified in the Background job used for the execution of the macro.
This macro is executed in a background job, and the copy/calculation is performed correctly for the first CVC (first CVC contained in the data selection used in the background job) processed, but then it does not do anything else for the rest of CVC's. The error message given by the log of the background job is "There are no plannable characteristic combinations", when in fact, the characteristic combinations do exist in the Planning Object Structure.

Hi Ian
There are not any other macros in the planning book.
In addition, if we execute the macro in interactive mode we have another error at the end of the execution (after doing all the combinations):
Invalid data status.
and we don't know why.
Regards

Background job restriction

Hi,
Where can I find detailed description about the restriction options of background jobs:
Always execute job
Do not execute job on Sundays or holidays
Move job to previous day
Move job to next workday
I need to schedule a job to run only on Sunday - Friday (without Saturday).
I have created a factory calendar and choosed it in the factory calendar ID but I don't know which of the above to choose.
Thanks,
Hagit.

PLEASSE VISIT THIS LINK
http://help.sap.com/saphelp_47x200/helpdata/en/73/69ef5755bb11d189680000e829fbbd/frameset.htm
in the left pane navigate in this way
find the node Scheduling Background Jobs
then
Scheduling Background Jobs>Scheduling Standard Jobs>Choosing a Start Time
Reward points if it helps you
Thanks,
Anid
Message was edited by: Anid

Reg Background job execution

Hi gurus,
I have a doubt in back ground job processing...We have a job which runs for very long time (archiving job). I want that job to run from Sunday morning to evening 6PM again I need to run the same job next sunday morning to evening continuing from previous week stop point.
My question , there is a option in SM37 to STOP the job. If I stop the job and then resume back the same job, will it continue from the point where it stopped?
Is there any way to execute the background job like above scenario. I know it can be done by 3rd party tool, but I want to do the same from R/3
Vinodh

Hi Vinodh,
In later versions of SAP (from Enterprise version if iam not wrong), you can interrupt the archive job and continue later. This is not the feature of background processing, but the archiving job itself.
Interruption is possible on basis of duration of the job and size of archive file. See the following link which details the mentioned feature; go to The Archive Development Kit and see the topic Interrupting and Continuing Archive Sessions:
http://help.sap.com/saphelp_47x200/helpdata/en/6d/56a06a463411d189000000e8323d3a/frameset.htm
Hope this helps to work towards the solution of your problem.
Regards,
Naveen

Restrict the background jobs to perticular server

Hi
I have ECC6 with 3 app servers. To balance the load i would like the users to schedule their background jobs on a perticular server only. Is it possible?
If most of the users using sap for reports only, in this case how can i balance the load?
UR suggestions are highly appreciable.

Go to SM37
Search for all released jobs.
Select the job you want to move to other server.
Rightclick on the job and select option "Move to different Server"
Assign server to your job.
Note: There must be least one BG process available on the server.
Regards,
Yogesh
Edited by: Yogesh Patel on Jun 14, 2011 9:10 AM

Background Job processing

After writing a report, I used this Function Module LIST_TO_ASCI to copy my report to an internal table (DOWNTAB) because Ill use that internal table to download a text file on the server using dataset.
Here is my code:
FORM DL_REP_SERVER.
 DATA: ABAP_LIST LIKE ABAPLIST OCCURS 1,
 MV_FILE2 LIKE RLGRAP-FILENAME.
DATA: BEGIN OF DOWNTAB OCCURS 1,
 LINE(150),
 END OF DOWNTAB.
CLEAR: MV_FILE2.
MV_FILE2 = J:/Downloads/Report.txt.
CALL FUNCTION 'LIST_TO_ASCI'
 EXPORTING
 LIST_INDEX = SY-LSIND
 TABLES
 LISTASCI = DOWNTAB
 LISTOBJECT = ABAP_LIST
 EXCEPTIONS
 LIST_INDEX_INVALID = 1
 OTHERS = 2.
OPEN DATASET MV_FILE2 FOR OUTPUT IN TEXT MODE.
IF SY-SUBRC <> 0.
 IF SY-SUBRC = 8.
 MESSAGE E037 WITH 'File could not be opened'.
 ELSE.
 MESSAGE E037 WITH 'Error occurs in downloading the file'.
 ENDIF.
ENDIF.
LOOP AT DOWNTAB.
 TRANSFER DOWNTAB TO MV_FILE2.
ENDLOOP.
CLOSE DATASET MV_FILE2.
ENDFORM. " DL_REP_SERVER
My big problem is this, when Im running my program ordinarily (not as background job), Im getting all the pages downloaded correctly but when I run it as background job (using SM36), Im only getting the last page of my report being downloaded. Definitely, I cant debug it because its in background. I cant figure out why. Hope that I stated my problem clearly. Any help would be greatly appreciated. Thanks.

You can debug batch jobs by going to 'SM37', type in 'JDBG' in the
command line ( no '/' ), put the cursor on the job and press enter - will
take you to the job in debug mode.
You can do this only after the job has finished execution. This will simulate the exact background scenario with the same selection screen values as used in the job also sy-batch will set to 'X'.
So type in the transaction code 'JDBG' and place your cursor on the job after It has finished. It will take you to a SAP program in debug mode. Step through this program which is about 10 lines, after this your program will be executed in the debug mode.
Steps
1. Create variant called BACKGROUND for program to be debugged.
2. Execute ZDEBUGBG (pgm code below) in background for immediate processing.
3. Execute transaction SM50.
4. Select process that runs ZDEBUGBG.
5. Goto 'Program/Session' 'Program' 'Debugging'.
A se80 debug session will open.
6. Change variable W_EXIT to 'E'.
7. Step thru (F6) until ZWBTEST comes up.
1. Go to Transaction SM66 and find your work porocess.
Select the line work process is on and click on the Debugging button.
If this is a custom program, you can put a wait statement in the code to buy yourself sometime.
2. Go to Transaction SM50. From the tool bar "Program/session"->Program->Debugging.
goto SM37 and from Program menu(not sure.. try other menu's)
-->Catchjob . it will goto the active job in debugging mode.

How to Prevent the Executing a Program but Allow to Run as Background Job?

Hi All,
I have an ABAB List Program. I need to restrict this program from executing. This has to always run as a Background Job. How do I check this condition in the program?
Thanks,
Kishan

Check for the system variable SY-BATCH. If this field is 'X', then allow the execution of the program. If not then exit. Do this coding in the initialization event or start of selection.
INITIALIZATION.
IF sy-batch IS INITIAL.
STOP.
ENDIF.
Manoj

Regarding background job.

Hi All,
I have to debug background job which is currently running.
I know how to get the job in debug mode, that is through SM51 transaction...But once i m done with seeing some values in debug mode. I need to put this job back again in the background. Becasue since this is long running job i can not run it in forground.
Plase guide me in this regards.
-Sanjay

Hi,
You can debug batch jobs by going to 'SM37', type in 'JDBG' in the
command line ( no '/' ), put the cursor on the job and press enter - will
take you to the job in debug mode.
You can do this only after the job has finished execution. This will simulate the exact background scenario with the same selection screen values as used in the job also sy-batch will set to 'X'.
So type in the transaction code 'JDBG' and place your cursor on the job after It has finished. It will take you to a SAP program in debug mode. Step through this program which is about 10 lines, after this your program will be executed in the debug mode.
Steps
1. Create variant called BACKGROUND for program to be debugged.
2. Execute ZDEBUGBG (pgm code below) in background for immediate processing.
3. Execute transaction SM50.
4. Select process that runs ZDEBUGBG.
5. Goto 'Program/Session' 'Program' 'Debugging'.
A se80 debug session will open.
6. Change variable W_EXIT to 'E'.
7. Step thru (F6) until ZWBTEST comes up.
1. Go to Transaction SM66 and find your work porocess.
Select the line work process is on and click on the Debugging button.
If this is a custom program, you can put a wait statement in the code to buy yourself sometime.
2. Go to Transaction SM50. From the tool bar "Program/session"->Program->Debugging.
goto SM37 and from Program menu(not sure.. try other menu's)
-->Catchjob . it will goto the active job in debugging mode.
Regards,
Raj.

Restrict background jobs to immediate execution

Similar Messages

Maybe you are looking for