Back ground Jobs

[Former Member]

hi all

need some information or the steps for Background Jobs

Thank you

Swapna

[Former Member · Accepted solution]

hi

<b>Creating a Background Job Using the Job Wizard</b>

•From the main menu select System>Services>Jobs>Define Job (transaction SM36).

•Press the Job Wizard button and step through the screens as follows:

•1:Continue

•2: Enter a name for your job. Continue.

•3: Continue with ABAP Program Step selected

•4: Enter the ABAP Program Name and variant name.

Press the Print Parameters button, specify the required printer and set the "Time of Print" to "Send to Print Spooler for now".

Press green tick

Continue

•5: If more reports need to be added to the job tick the checkbox, press continue and repeat screens 3 and 4.

•6: Select how the job is to scheduled (eg Date and Time)

•7: Enter the required scheduling information ( eg Date and Time) and if required tick "Periodic Jobs"

•8: If "Periodic Job" was selected select the frequency (eg Monthly)

•9: Check the job details and press Complete

====

Viewing Background Jobs

•From the main menu select System>Services>Jobs>Job Overview (transaction SM37).

•Enter the required selection criteria and press Execute

•To view the job log, tick the required job and press the "Job Log" button.

•To view the output from the job, tick the required job and press the "Spool" button.

=====

Scheduling Background Job

http://help.sap.com/bp_lblv1500/LBL_UK/HTML/LBLUK_Solution_Map/5FF7FDF4F7734A2EA38EF7898AB3621D.htm

Background Processing

http://help.sap.com/saphelp_nw04s/helpdata/en/ed/a9bb3f8e236d3fe10000000a114084/frameset.htm

Debugging a Background Job

http://searchsap.techtarget.com/tip/0,289483,sid21_gci933590,00.html

Sample Screen Shots

http://www2.warwick.ac.uk/services/finance/sap/help/howtoguides/backgroundjobs/

Reward if Useful

Thanx & Regards

Naren..

[Former Member]

Thanks All

Swapna

[Former Member]

Hi Swapna,

Please follow these steps

...

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 job’s 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 job’s 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.

Hope this will be useful

award points if useful..

Cheerss!!!

Pankaj Sharma

[former_member227476]

dear swapna

SM36 Define Background Job

SM37 Background Job Overview

SM39 Job Analysis

to have an idea about the background scheduling let us take an example of a long report. Suppose we execute this report in interactive mode, it takes several minutes and during time the SAP System is blocked for any further input. As a result, you will not be able to interact with SAP sessions anymore.

However, when you run the report non-interactively, you can interact with the SAP sessions while processing the report in the background. For executing jobs in non-interactive mode, schedule the job for background processing. To create a background processing job you should specify:

• The name of the report

• The name of any variant it needs

• What to do with output

• When to start it

After this, the SAP system does not require user’s intervention and can proceed with the job even without you. It executes the report and prints the output using printer or output controller. While scheduling a job in background process, three parameters should be specified. These parameters are:

• Definition of programs

• Its start time

• The printing specification for getting the prints as required

After this, you can check whether your job was executed successfully and display a log of any system messages.

For scheduling background processing, you have to direct the system to process an ABAP/4 or external program in the background. This is a two-step process:

• Scheduling the program

• Releasing the job

This needs to have a special authorization for releasing and scheduling the job. Generally, the system administrator, who organizes and monitors background processing, supervises the release of these jobs. Many users are also authorized to schedule background processing of reports. You cannot schedule a job unless and until you have a release authorization. If a user is authorized and has specified a start date or selected "start immediately," he or she can release the job.

Authorized users can change start time. A program can be scheduled as a separate job or you can append it to an existing job, which has not yet been processed. Background process can be run while doing some other online work. However, this can adversely affect online operation and should be avoided. For example, if you run a program that locks the database, the work of online users will be hampered or stopped. Often, long-running reports are scheduled automatically or semi-automatically for background processing.

First Step

Initiate the job scheduling function. Standard job scheduling must be used in case of scheduling of an external command or external program as a background job and ABAP job¬ scheduling function can be used to schedule ABAP programs. For starting a standard job scheduling function choose the following:

Administration menu bar option à CCMS option à Jobs option à Definition option.

For starting ABAP job scheduling function, navigate to ABAP Editor and choose Program menu bar option execute option à Background option.

Second Step

now define a job. Using the Job Wizard you can define your job. From the Application toolbar, choose the wizard button. After this, the initial screen of the SAP Job Wizard appears. The Job Wizard is available only from the standard job scheduling function.

Third Step

Now, you have to save the job. When it displays the message "Job saved" it means the job has been successfully scheduled. We know that a job must be released before it is scheduled. Only authorized users can release the job, otherwise your system administrator will release your job.

Fourth Step

this is the last step of scheduling. In this step you have to check the status of your job. For this you need to choose System menu bar option à Own jobs option.

In SAP System, the background processing runs according to your instructions. In case a list is generated by the report, the report either prints directly or waits for you in the SAP output controller. The status of background processing can be checked for its correctness.

rewards if it helps

siva

[Former Member]

Hi Swapna Latha,

BACKGROUND JOB PROCESS

If its a custom program, your should talk to the programmer who wrote the program by finding out what is the program running behing the job.

Aslo, if you want to find out on your own, you can try to run the SQL trace on it using ST05 and then analyze the trace for the expensive statements. Check the trace wherevere it shows the fetch time marked in RED and then, you can try to analyze the SQL statement running in the backgroung, to see if the programmer is doing an unnecessary select/fetch, reading too many records etc.

Hope that helps..

You can try the following:

go to SM36 and create background job by giving

job name,job class and job steps (JOB SCHEDULING)

BATCH

If the user forgets to opt for keep session then the session will be automatically removed from the session queue(log remains). However if session is processed we may delete it manually.

ii)if session processing fails data will not be transferred to SAP database table.

Direct Input.

Without calling the screens but all the validations should be done and only for master datas upload.

Direct Input method:

1. Only for error free datas and also master data

updation.

2. It will directly updates the database table. No

screens involved.

3. Transaction BMVO or Program RBMVSHOW has been

used.

BDC(Batch Input Session):

1. Screens will be called programmatically.

2. First sessions will be created then we'll run the seesions in SM35 transaction.

3. Synchronous database update. After the processing the session only database update will occur.

Batch Data Communication (BDC) is the process of transferring data from one SAP System to another SAP system or from a

non-SAP system to SAP System.

Features:

BDC is an automatic procedure.

This method is used to transfer large amount of data that is available in electronic medium.

BDC can be used primarily when installing the SAP system and when transferring data from a legacy system (external

system).

BDC uses normal transaction codes to transfer data.

Types of BDC:

CLASSICAL BATCH INPUT (Session Method)

CALL TRANSACTION

BATCH INPUT METHOD:

This method is also called as ‘CLASSICAL METHOD’.

Features:

Asynchronous processing.

Synchronous Processing in database update.

Transfer data for more than one transaction.

Batch input processing log will be generated.

During processing, no transaction is started until the previous transaction has been written to the database.

CALL TRANSACTION METHOD :

This is another method to transfer data from the legacy system.

Features:

Synchronous processing. The system performs a database commit immediately before and after the CALL TRANSACTION USING

statement.

Updating the database can be either synchronous or asynchronous. The program specifies the update type.

Transfer data for a single transaction.

Transfers data for a sequence of dialog screens.

No batch input processing log is generated.

Differences between Call Transaction and Sessions Method:

Session method.

1) Synchronous processing.

2) Can transfer large amount of data.

3) Processing is slower.

4) Error log is created

5) data is not updated until session is processed.

6) Generally used for back ground jobs.

7) At a time we can update to more than one screens.

Call transaction.

1) Asynchronous processing

2) can transfer small amount of data

3) processing is faster.

4) Errors need to be handled explicitly

5) data is updated automatically

6) for background n fore ground jobs.

7) At a time we can update to a single screen.

Direct Input method:

Without calling the screens but all the validations should be done and only for master datas upload.

1. Only for error free datas and also master data updation.

2. It will directly updates the database table. No screens involved.

3. Transaction BMVO or Program RBMVSHOW has been used.

For BDC:

http://myweb.dal.ca/hchinni/sap/bdc_home.htm

https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/bdc&;

http://www.sap-img.com/abap/learning-bdc-programming.htm

http://www.sapdevelopment.co.uk/bdc/bdchome.htm

http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm

http://help.sap.com/saphelp_47x200/helpdata/en/69/c250684ba111d189750000e8322d00/frameset.htm

http://www.sapbrain.com/TUTORIALS/TECHNICAL/BDC_tutorial.html

Check these link:

http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm

http://www.sap-img.com/abap/question-about-bdc-program.htm

http://www.itcserver.com/blog/2006/06/30/batch-input-vs-call-transaction/

http://www.planetsap.com/bdc_main_page.htm

Please Reward If Really Helpful,

Thanks and Regards,

Sateesh.Kandula