Job Overview

Hi BW Experts,
I have some doubts in data loading.
We run the jobs through Process Chains and InfoPackages.
What is difference between Dialogue Process and Background Process?
When we run the Process Chains, it will show User Name: ALEREMOTE
When we run the Infopackage manually, it will show our User Name.
What is difference between these 2 Users.
Regards
Anjali

Hi,
Background Processing: Concepts and Features
http://help.sap.com/saphelp_nw04/helpdata/en/c4/3a7ed1505211d189550000e829fbbd/frameset.htm
Background Processing
http://help.sap.com/saphelp_nw04/helpdata/en/73/69ef3d55bb11d189680000e829fbbd/frameset.htm
Features of Background Processing
Running a report in the background does not tie up the SAP sessions you are currently working with.
When you start a report interactively, your current SAP session is blocked for further input for as long as the report runs.
When you start the report in the background, running the report does not influence your interactive work with the SAP System.
You can shift the execution of reports to the evening or other periods of low load on the SAP System.
You can schedule a report or external program to run at any time that the SAP System is active. You can also set up reports to run automatically on a regular basis (for example, on the last day of each month).
Background processing is the only way you can execute long-running jobs.
To prevent tying up system resources with interactive sessions for long reports, the SAP System has a built-in time limit on interactive sessions. If a single ABAP report runs for more than 5 minutes continuously in an interactive session, the SAP System terminates the report automatically.
The background processing system executes long-running ABAP reports more efficiently. Often, such reports are automatically scheduled for execution in the background. In this case, you do not need to schedule them for background processing yourself.
A few more.
http://help.sap.com/saphelp_nw04/helpdata/en/c4/3a8016505211d189550000e829fbbd/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/8f/c08b3baaa59649e10000000a11402f/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/e1/b7463c32a3fe13e10000000a114084/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/4a/2d513897110872e10000009b38f889/frameset.htm
SPPFP: Different processing in dialog mode or background
SAP Note Number: 589836
Hope this helps.
Thanks,
JituK

Similar Messages

Is it possible to have Multiple Spool requests in one batch job overview?

Hi,
While running one of my z program in back ground, there are two spools generated (one by write statement and one by OPEN_FORM statement and both the spools are available in SP01 Transaction), but when i see the job overview in transaction SM37, I only see one spool request (that of the last spool request). Can any body in the group please tell me is it possible to see multiple spool requests in the job overview of one Abap program and if yes, how?
Thank you.
Abinash

Hi Jayanthi,
Thank you for the link. But probably that discussion was also an unsolved one.
Anyway, does any one in the group think that display of multiple spools per one step job is dependent on client / SAP Server setting? Because as evident from the chain of mails in the link provided by Jayanthi, some people say that they see multiple spool requests for one program in batch mode job overview (SM37)? If yes, can some body tell me the required configuration?

Question about job overview

Hello Gurus,
for RSM37, I found some job record with me as the user, for example " SAP_CCMS_MONI_BATCH_DP", "BI_PROCESS_COMPRESS". but I did not do anything on this system , so I wonder why those jobs are sticking on me? , and what does this user column really refer to?
Many thanks

HI,
Chk this help link, it will give some idea:
http://help.sap.com/saphelp_nw04/helpdata/en/c3/0dec3b6e011341e10000000a114084/content.htm
Hope this helps.
thanks,
rahul

Cancelled job still visible in Job Overview as active

Hello Peers
I am loading the data from One Cube to other and had given selection wrongly,
I tried checking the PID number for the Job and Cancelled it with Core in SM50.
then i made the Traffic light Red and deleted the request from the Infocube Manage.
But in SM37 i see that job is in Active state.
Can anyone tell what could be the reason, even i tried selecting that and cancelling it from menu it shows Cancellation not possible as job is not in active state.
Suggest me why it is showing the job in active state

Hi there,
That's because the job is already cancelled but transaction sm37 is not automatically refreshed.
Go to transaction sm37 mark your job and choose Check Status (CtrlShiftF12).
This will update your job status to cancelled.
Diogo.

Transaction SM37 - Job overview

In this transaction, i can see Jobs status as
- Scheduled
- Released
- Ready
- Active
- Finished
- Canceled
Is there a sequence which has to be followed ie, first will be active, released ...... finished.
ALso what is scheduled Job do.

Hi,
you no need to follow any sequence in SM37.
Once u create a job via SM36 or via some programs, the jobs will be coming under Scheduled job.
If you submit a job via program, the job will be released automatically. but if u schedule a job theu SM36 , it'll be under scheduled and u have to release that job to run--u can see release button
Once u release that job , it'll go to active state and then finished or if any issues come , it'll be under cancelled..
Scheduled
- Released
- Ready
- Active
- Finished
- Canceled
These are all for users to see the job, I mean the Job status. This whole cycle will be run automatically. U need to release the Job that's it.
Edited by: Selva M on Aug 19, 2009 2:52 PM

SM37 - Job overview

In this transaction, i can see Jobs status as
- Scheduled
- Released
- Ready
- Active
- Finished
- Canceled
Is there a sequence which has to be followed ie, first will be active, released ...... finished.
ALso what is scheduled Job do.

Hello Rajesh,
Any background job goes through the following states 'in that sequence':
1. Scheduled (the job has been planned, it will execute at some point of time in future, but you may still edit the job steps at this stage)
2. Released (the job steps cannot be edited, any job scheduled in 'immediate' mode will be in released state directly)
3. Ready (the job is in execution queue and is about to be executed depending upon availability of background work process and the job priority)
4. Active (the job is being executed by a background work process, you may monitor this in sm37 and sm50/51)
5. Finished (all the job steps completed successfully) OR Cancelled (there was a error and job has been terminated, as mentioned in the job log)
Coming to your second question, scheduled job will go through the states mentioned above before its finished or cancelled.
This may clarify your doubts.
Regards,
Saurabh.

Job cancelled While loading data from DSO to CUBE using DTP

Hi All,
while i am loading data frm DSO to CUBE the job load is getting cancelled.
in the job overview i got the following messages
SYST: Date 00/01/0000 not expected.
Job cancelled after system exception ERROR_MESSAGE
wt can be the reason for this error as i have successfully loaded data into 2 layers of DSO before loading the data into the CUBE

hi,
Are u loading the flat file to DSO?
then check the data in the PSA in the date field and replace with the correct date.
i think u r using write optimised DSO which is similar to PSA it will take all the data from PSA to DSO.
so clear the data in PSA and then load to DSO and then to CUBE.
If u dont need a date field in CUBE then remove the mapping in transformation in cube and activate and make DTP activate and trigger it it will work.

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 not run properly

Hi,
When an infopackage is triggred through process chain in BI a background job will be exeuted at R/3 to fetch data from R/3.
But the bakground job did not execute properly hat is it did not fetch any data but ot finished.
But when the infopackage is executed manually the background job fetches the data from R/3.
Why the job is not fetching data when triggered through process chain.
Please help me to sole this issue.
Regards,
Indhu

Hi Induja,
In your case, you will have to debug the background job that is activated through BI. Check if proper data is coming from BI.
You can only debug a background job if it is created under your user id. Thus, to debug the job you first have to own it and then debug by selecting it and either typing 'JDBG' in the command field or through menus available on the top.
Job overview transaction code - SM37.
Hopefully the issue is in Development/Test/Quality system and not in Production.
Hope that helps!.
Regards,
Saba

Job was cancelled in source sytem.

Hi,
One job was in cancelled state in source system itself.How can i correct the error?how can i get the data from source sytem.could please anybody help me out on this issue please.In RSMO,in that statu tab its stating as JOB OVERVIEW,by clicking onto this its leads to,r/3.by executing this one it shows as job cancelle.update method is delta.
Thanks & Regards,
Praveena.

Hi anil,
one ODS is getting nearly 500000 of records,it is loading master data,here the problem is that in details tab processing process is well all the datapackets are getting fine data,but at transfer tab after processing of infoidocs,dataidocs should be filled,but there it self problem is getting.in status tab its is in yellow status i cant forcibly make it into green.how can i solve this issue.And please give me reply more detaily about RSODSACT tbale details,what are changes can be done by using this table.
Thanks & Regards,
Mano.

DTP Background job in sm37?

Hi Gurus,
When I see the dtp status from the monitoring screen of dtp thru Job Overview, the below screen comes.
                                                           Status              then other tabs for timings and other.....
BI_Process_dtp_load                         Finished
BIDTPR_123456_1                             Active
BIDTPR_123456_1                             Active
BIDTPR_123456_1                             Active
BIDTPR_123456_1                             Active
BIDTPR_123456_1                            Finished
What these middle jobs are for and why then it always shows Finished in last BIDTPR_123456_1 status.
And what does the RELEASE JOB means in the same screen
Thanks,
SDPSDN
Edited by: SDPSAP on Feb 29, 2012 5:09 PM
Edited by: SDPSAP on Feb 29, 2012 5:10 PM

Hi SDNSAP
For example you have triggered a DTP which is having parallel processing as 10 with serial and immediate parallel processing as processing mode, then you can see maximum of 9 data packets are running.
All these 9 data packets will with job BIDTPR_1236023_1 individually, i mean that each packet will have one job with BIDTPR_1236023_1. whenever few packets are finished their respective job status will be finished.
Thanks,
Prashanth

Error after scheduling a job in background....

Hi All,
I'm trying to schedule background job and i m using code for scheduling that job for ex-
CALL FUNCTION 'JOB_OPEN'
 EXPORTING
 jobname = g_name
 IMPORTING
 jobcount = number
 EXCEPTIONS
 cant_create_job = 1
 invalid_job_data = 2
 jobname_missing = 3
 OTHERS = 4.
 IF sy-subrc <> 0.
 MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
 WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
 ENDIF.
 IF sy-subrc EQ 0.
 SUBMIT zrb_cc_clc_n_copy VIA JOB g_name NUMBER number TO SAP-SPOOL WITHOUT SPOOL DYNPRO
WITH DESTINATION = 'HPMISPRT'
WITH IMMEDIATELY = SPACE
WITH KEEP_IN_SPOOL = 'X' AND RETURN.
CALL FUNCTION 'JOB_CLOSE'
 EXPORTING
 jobcount = number
 jobname = g_name
 sdlstrtdt = sdate
 sdlstrttm = stime
 strtimmed = 'X'
IMPORTING
JOB_WAS_RELEASED =
CHANGING
RET =
 EXCEPTIONS
 cant_start_immediate = 1
 invalid_startdate = 2
 jobname_missing = 3
 job_close_failed = 4
 job_nosteps = 5
 job_notex = 6
 lock_failed = 7
 invalid_target = 8
 OTHERS = 9
 IF sy-subrc <> 0.
 MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
 WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
 ENDIF.
Still i am getting error message in job overview status cancelled
Thanx in advance
N.s

check in transaction SM37 why this particular job was cancelled

Batch job creation for sales order

Hi,
How to create a job and schedule it so that it assigns reason of rejection to sales order line items for a particular sales org which are not delivered and after doing so, the status of the sales order is set to complete.
regards
sachin

Hi,
Execute transaction SM36
Define Job name, Job class, Target server
Click on 'START CONDITION' button
Click on 'Date/Time' button
Enter Scheduled start DATE & TIME. Check mark 'Periodic Job' field. Click on 'Period values' button and select 'Hourly' or 'Dialy' or 'Weekly' or 'Monthly' or Other period and SAVE. Go back to main screen.
Click on 'STEPS' button and enter Program name and Variant under box 'ABAP Program'. Click on 'Print Specification' button and enter Printer name under 'Output device' and SAVE
Click on SAVE button until you get message on bottom of the screen that describes 'Job XYZ saved with status: Scheduled'.
Click on 'Job overview' button or execute SM37 transaction.
Select the appropriate 'Job name', 'User name', 'Job Status' & Schedule date under 'Job start condition' and click on 'Execute' button or press F8.
You will now see all your scheduled JOBS.
regards,
mahantesh

Issue regarding job SAP_CCMS_MONI_BATCH_STARTUP_DP

Hi,
We are facing an issue regarding an event triggered job SAP_CCMS_MONI_BATCH_STARTUP_DP.
Details of the job
ABAP Program -> RSAL_BATCH_TOOL_STARTUPDISP
User -> DDIC
Job Frequency -> Event Periodic
Event -> SAP_MONITORING_STARTUP_DISPATCH
We performed Database Refresh and this job has come from Source System. We have deleted the job in Target System but after that also we are getting continuous error message in SM21.
Error message is as follows:
14:33:36 DIA 001 000 SAPSYS EA S Failed to reschedule a periodic job
14:33:36 DIA 001 000 SAPSYS EB C > Job SAP_CCMS_MONI_BATCH_STARTUP_DP
On digging down we got the below information in SM21 regarding the error:
Documentation for system log message EA S :
This message is output by one of the job schedulers active in the
system (e.g. time or event-based scheduler). It indicates a problem
related to the database. An attempt was made to reschedule a periodic
job and write the respective control data in the database. This error
occurred for one of the associated database operations (for example,
INSERT or UPDATE).
Another cause of the error is failure to generate a new job ID number.
A subsequent message will point this out.
The following courses of action are possible:
Check whether there are any other notes on this problem next to this
message in the system log, for example direct messages from the
database interface. These details generally bring you closer to the
actual cause of the problem.
The additional information for this message contains the name of the
database table for which the error occurred.
If you determine that the error occurred during the SELECT access to
table TBTCI, the internal report belonging to this background job has
been deleted. In this case, there is normally a background job in the
'terminated' status, which ended due to runtime error
'LOAD_PROGRAM_NOT_FOUND'. Delete this job to prevent further
unnecessary scheduling on the part of the background processing
scheduler. You must then reschedule the job concerned.
As rescheduling of the periodic job could not be completed
successfully, this job is not executed at first. The background
processing scheduler takes this job and attempts to schedule it again.
Depending on the repetition period, gaps in running the background jobs
can occur for successful scheduling (i.e. the background jobs that were
unsuccessfully scheduled will be missing in the job overview if their
execution date elapsed in the meantime).
Since the next start of the periodic job could not be scheduled
correctly, there is no entry in the job overview for the planned start
date.
If the system failed to generate the job ID number, you will find notes
on what to do next in the long text of the respective system log
message.
We have fixed also Background Object in SM61.
Kindly help to fix this issue. Looking forward for reply.
Thanks,
Soumya

I am also facing similar issue . I found below SM21 entries daily . becoz of this my system performance becomes slows down. no idea which tables are getting filled up due to this .
> Job SAP_CCMS_MONI_BATCH_STARTUP_DP
Failed to reschedule a periodic job
For temporary fix we have changed the below memory parameters when system performance is poor .
EM/TOTAL_SIZE_MB = 16384
ES/SHM_SEGS_VERSION = 2
ES/TABLE = SHM_SEGS
But we need to fix these system log entries as still we are getting these errors. If anybody knows the permanent fix of this error that will be great for us.
Regards
Krishna

How to display more than 255 chars in background job with ALV Grid ????

Hi All,
I am using ALV grid with OO.
I have used call screen for ALV grid display. I have to display more than 255 characters in width. While running it, I can see the list perfectly.
But in background mode, the list is truncated after 255 chars.
Can anybody help how to send complete list(width more than 255 chars) to spool.
Thanks and Regards,
Neha

Hi SAP fan,
YES you can run the ALV report in background mode.
To run the report in background do F9 instead of F8, then give immediate and save.
Now goto Sm35 goto job overview and view the job listed
Choose the job and press the spool button. It will show the list created on the next page. When u clcik the list u can see the ALV output.
To see this the job should be in the finished status.
How to define Periodic Jobs
1.Execute transaction SM36
2.Define Job name, Job class, Target server
3.Click on 'START CONDITION' button
4.Click on 'Date/Time' button
5.Enter Scheduled start DATE & TIME. Check mark 'Periodic Job' field. Click on 'Period values' button and select 'Hourly' or 'Dialy' or 'Weekly' or 'Monthly' or Other period and SAVE. Go back to main screen.
6.Click on 'STEPS' button and enter Program name and Variant under box 'ABAP Program'. Click on 'Print Specification' button and enter Printer name under 'Output device' and SAVE
7.Click on SAVE button until you get message on bottom of the screen that describes 'Job XYZ saved with status: Scheduled'.
8.Click on 'Job overview' button or execute SM37 transaction.
9.Select the appropriate 'Job name', 'User name', 'Job Status' & Schedule date under 'Job start condition' and click on 'Execute' button or press F8.
10.You will now see all your scheduled JOBS.
Case: 2
You can Run in Background but make sure it is alv list, not alv Grid FM. if you are uisng alv list not problem , but if you are using alv grid then you can code like this..
if sy-batch = ' '.
call 'REUSE_ALV_GRID_DISPLAY'.
else.
call 'REUSE_ALV_LIST_DISPLAY'.
endif.
if you are using OO alv then write this code..
CALL METHOD cl_gui_alv_grid=>offline
 RECEIVING e_offline = off.
 IF off IS INITIAL.
 CREATE OBJECT g_custom_container
 EXPORTING container_name = g_container.
 ENDIF.
Case: 3
if you are using OO ALV.
Just before creating the custom container check for the following condition.
Batch or Web Reporting
IF cl_gui_alv_grid=>offline( ) IS INITIAL.
CREATE OBJECT o_custcontainer
EXPORTING
container_name = lc_custcontrol
EXCEPTIONS
cntl_error = 1
cntl_system_error = 2
create_error = 3
lifetime_error = 4
lifetime_dynpro_dynpro_link = 5
OTHERS = 6
ENDIF.
You can see the output in Spool in transaction SP01.
Good Luck and thanks
AK

Job Overview

Similar Messages

Maybe you are looking for