Background job "EU_REORG" scheduled to run daily is taking lot of time.....

1) My BTC work processes always in run state.due to this my server is very slow.can i stop these processes?is there any harm in stopping these processes?
due to this my server is very slow... how to speed up this job execution?
i'm searching some threads.i have got SM50 . in that i got some info about background program which is long running and slowing down
This is part of EU_REORG job that is scheduled to run daily.
Report / Spool action : SAPLSEU_COMPONENT
Main Program : RS_APPL_REFRESH
Action Table
Sequential Read TADIR
Database Number Time (usec) Recs.
Direct Read 0 0 0
Sequential Read 0 0,000000000000000E+ 0
Insert 0 0 0
Update 0 0 0
Delete 0 0 0
Sources 3.229.092 (Bytes)
RSQL 367870216 (Bytes)
Commit 4.349.042
DB Procedure Calls 0 0
Roles / Memory Number Time (usec)
Roll In 3 1.583
Roll Out 4 34.970
Roll 286.720 (Bytes)
Page 24.576 (Bytes)
Memory (Total) 144.252.304 (Bytes)
Memory(Total Private) 0 (Bytes)
Memory (used) 137.970.624 (Bytes)
Memory (Max. Transaction) 144.242.016 (Bytes)
Memory (Max. Dialog Step) 144.242.016 (Bytes)
this is what i got. Please resolve....
2) how to speed up the start of my sap instance ? it is taking nearly 20 mins to get all the work processes in wait mode..except this back ground job which is not coming into wait mode....
Thanks & regards
Will

Hi,
EU_REORG is scheduled to run every night (quiet time etc.) so as to refresh the 'where-used' index for the Development Workbench tools. Note 18023 will give you more information about the job.
Check Note 1353707 if it applies to your case.

Similar Messages

Background job is taking lot of time for processing the job.

One background job - which is processing Idocs is processing a job for more than 2000+ seconds.. and completed tho.
But this is happening for the past few days.. is there any way to trouble shoot, or find from any logs of this completed job, to find out why it was taking lot of time for processing.
Can you please tell me the steps of analyzing / trouble shooting why it was taking lot of time daily.
Regards,
Satish.

Hi Satish,
Run DB stat from db13 it will improve the performance.
Check number of idocs. You can send part by part, instead of sending huge data.
Check SM58 logs
Suman

Background jobs are scheduled in future date

Hi
A system which is used by a customer test system was installed and scheduled the jobs in 2010( in future date).
Now we have changed the date to current date. But still all the background jobs are in future date.
There are around 500 jobs are scheduled. And it not possible to reschedule one by one.
Is there any way workaround to change it back to current date format.
Best Regards,
Jai

Dear Jai,
The jobs scheduler should have this dates changed to current. If its a third party system which are running these batches, then be careful to convey the same message to the 3rd party.
If its in SAP, then the schedule change date should execute your jobs. At the same time, ensure that the transports between the test systems match to the destination.
Do let me know for any clarification.
Thanks
Madhu

Schedule to run twice a day at different times.

Hi
I am trying to write a schedule to run twice a day, 7 days a week at 11.30am and 0.01am (i.e one minute after midnight).
I have tried setting the repeat_interval = 'FREQ=DAILY;BYDAY=MON,TUE,WED,THU,FRI,SAT,SUN;BYHOUR = 11,0;BYMINUTE=30,1';
However, this causes the job to run at 11:01; 11:30, 00:01 and 00:30. Can some please show me how to get it to run only at 11:30 and 00:01?
Thanks.
jov

Hi Joe
Thanks for your reply.
Unfortunately, your suggestion still causes the app to run 4 times a day, 11:01; 11:30, 00:01 and 00:30. I am trying to avoid writing two schedules but it looks like I'm going to have to.
jov

Charms : Background job not scheduled (normal correction) ?

Hi,
I am trying to run a dry cycle for normal correction but when i go to task plan in any ticket to release a request. When i schedule this job " release a request" , i dont see any job running in background in SM37. I think job is not gettin sceduled properly.
Please help me out

Hi,
All right. We need to dig this one
I guess you schedule the import by going the the tasklist
and you get a red flag for this activity in the calendar ? do you have any error message ?
If the messagein the task-list is not self-explanatory you can check the SLG1 log in SOLMAN. Which error message do you get there. (select the correct time frame, the log could be big)
My guess is that some S_RFC authorisation is still missing there
This authorisation is outside SAP_ALL and is often the cause of this kind of issue
Tell me the error message and we will hopefully fix this (I had the same kind of issue when I started last year)
best regards Xavier

While running Interface it is taking lot of time.

Hi,
I created a interface using join condition with two tables in each table it has 2,46,405 rows. while running the job it was loading work table quickly, but while inserting table to target it was taking long time.
I am using IKM sql to sql append in changed flow control to No.
could you please let me know how to improve performance.

What technologies are you using and where have you put the staging area?

How to schedule the background job daily twice?

Hi,
How to schedule the background job daily twice? any conditions?
Regards,
Srihitha

see the step by step procedure.
Scheduling Background Jobs:
1. Background jobs are scheduled by Basis administrators using transaction SM36.
2. To run a report in a background, a job needs to be created with a step using the report name
and a variant for selection parameters. It is recommended to create a separate variant for each
scheduled job to produce results for specific dates (e.g. previous month) or organizational units (e.g.
company codes).
3. While defining the step, the spool parameters needs to be specified
(Step-> Print Specifications->Properties) to secure the output of the report and help authorized users
to find the spool request. The following parameters needs to be maintained:
a. Time of printing: set to Send to SAP spooler Only for now
b. Name abbreviated name to identify the job output
c. Title free form description for the report output
d. Authorization a value defined by Security in user profiles to allow those users to access
this spool request (authorization object S_SPO_ACT, value SPOAUTH). Only users with matching
authorization value in their profiles will be able to see the output.
e. Department set to appropriate department/functional area name. This field can be used in
a search later.
f. Retention period set to Do not delete if the report output needs to be retained for more
than 8 days. Once the archiving/document repository solution is in place the spool requests could
be automatically moved to the archive/repository. Storage Mode parameter on the same screen
could be used to immediately send the output to archive instead of creating a spool request.
Configuring user access:
1. To access a report output created by a background job, a user must have at
least access to SP01 (Spool requests) transaction without restriction on the user
name (however by itself it will not let the user to see all spool requests). To have
that access the user must have S_ADMI_FCD authorization object in the profile with
SPOR (or SP01) value of S_ADMI_FCD parameter (maintained by Security).
2. To access a particular jobs output in the spool, the user must have
S_SPO_ACT object in the profile with SPOAUTH parameter matching the value used
in the Print Specifications of the job (see p. 3.d above).
3. Levels of access to the spool (display, print once, reprint, download, etc) are
controlled by SPOACTION parameter of S_SPO_ACT. The user must have at least
BASE access (display).
On-line reports:
1. Exactly the same configuration can be maintained for any output produced
from R/3. If a user clicks Parameters button on a SAP Printer selection dialog, it
allows to specify all the parameters as described in p. 3 of
Scheduling background jobs section. Thus any output created by an online report
can be saved and accessed by any user authorized to access that spool request
(access restriction provided by the Authorization field of the spool request
attributes, see p. 3.d of Scheduling background jobs section).
Access to reports output:
1. A user that had proper access (see Configuring user access above) can
retrieve a job/report output through transaction SP01.
2. The selection screen can be configured by clicking Further selection
criteria button (e.g. to bring Spool request name (suffix 2) field or hide other
fields).
3. The following fields can be used to search for a specific output (Note that
Created By must be blank when searching for scheduled jobs outputs)
a. Spool request name (suffix 2) corresponds to a spool name in p. 3.b in
Scheduling background jobs section above).
b. Date created to find an output of a job that ran within a certain date range.
c. Title corresponds to spool Title in p. 3.c in Scheduling background jobs
section above).
d. Department - corresponds to spool Department in p. 3.e in Scheduling
background jobs section above).
4. Upon entering selection criteria, the user clicks the Execute button to
retrieve the list of matching spool requests.
5. From the spool list the user can use several function such as view the
content of a spool request, print the spool request, view attributed of the spool
request, etc. (some functions may need special authorization, see p.3 in
Configuring user access)
a. Click the Print button to print the spool request with the default attributes
(usually defined with the job definition). It will print it on a printer that was
specified when a job was created.
b. Click the Print with changed attributed button to print the spool request
with the different attributes (e.g. changing the printer name).
c. Click the Display contents button to preview the spool request contents. A
Print and Download functions are available from the preview mode.

Certain Maintenance Plan not getting scheduled in the background job

Hi Gurus,
I am facing an issue here.
A weekly background job (RISTRA20) runs every weekend and schedules the maintenance plans.
But we have noticed that some maintenance plans are not getting scheduled. i.e no orders or schedule is getting generated.
When I run IP30 manually for these plans then the schedule gets generated and orders get called.
I have checked up the background job and it is running fine.
Also, i have noticed a similarity in all these plans which are not getting scheduled. There schedule has been restarted (through IP10) at somepoint or the other.
But i don't see any direct impact of this?
Can any of you provide some help on this?? Points will be rewarded.
Thanks and regards,
Nitin Saini

Hi Narender,
Thanks for replying.
The message number for 'Groups don't match' is ME303.
I think this does not have anything to do with the restart as i have done further investigation.
Whenever I run IP30 with sortfield input as AS02*, i get the error as mentioned above for a certain number of maintenance plans while the remaining plans get scheduled.
If i run IP30 for any other sort fields, it runs fine and i don't encounter the error
mentioned above.
If you send me ur email address, i could forward you screen-shots of the issue.

Periodic background job scheduling

Hello fellow SDNers,
I have a background job which has to run periodically. So I schedule it in SM36 to run after every 10 minutes and it executes without a problem. However, I have a scenario which requires that the next execution of the job should happen only after ensuring that the first one is not active (either it should have finished execution or aborted with error).
I need to understand the options available to handle this. Of course there is an option of writing another program to handle these jobs dynamically using JOB_OPEN, JOB_SUBMIT etc. or to create an event and trigerring it through another program and setting the job to run after this.
Is there any other option/setting available which can save me from the programming effort (which i wish to keep as my last resort to handle this)?
Any pointers are appreciated!!
-Priyank

`hi,
u hav after event in dat select--> sap_end_of_job
in job start conditons or esle u can check start condition in extended job selection.
read the usage tip there..

What is the spool, what is its role in background job scheduling

Hi,
I want to know what is meant by Spool request and spool number generated.
Tell about transaction SP01.
How it is linked to Background job scheduling.
thanks.
sam.

Hi,
Refer this link.
https://www.sdn.sap.com/irj/sdn/inf?rid=/library/uuid/7a5f4061-0a01-0010-c9bc-a4e4cb100438
About SP01.
Printing does not work in SAP. There is a printer definition for your local printer, but it does not work. Presuming that you use the program SAPLPD on your computer.
Boot your computer and start only the SAPLogon and the SAPLpd program.
Delete all of your old print jobs in the SAP system (Transaction SP01).Generate only one new print job.
Check that there is enough resource in your computer. Check the free memory (Win 3.1x) and the free disk space (The lists are temporarily saved on your disk).
Open the SAPLPD and read the print log in the window. The printer definition must correspond with the parameters shown here.
Check that the standard printer is on the same lpt (Win 3.1: Control panel, Printer) as defined for the printer (usually lpt1).
In Transaction SP01 read the protocol of your print job. Do not generate new print jobs! Wait till the SAP system changes the status of the print job.
If you can not find the print job in SP01 anymore, then the print job was successfully printed out. If it didn't come out on your printer and the SAPLpd didn't indicate an incoming print job, then the connection was realised with another PC. Then SAP printer definition you used, does not correspond with your computer.
Scheduling Background Jobs:
1.        Background jobs are scheduled by Basis administrators using transaction SM36.
2.        To run a report in a background, a job needs to be created with a step using the report name
and a variant for selection parameters. It is recommended to create a separate variant for each
scheduled job to produce results for specific dates (e.g. previous month) or organizational units (e.g.
company codes).
3.        While defining the step, the spool parameters needs to be specified
(Step-> Print Specifications->Properties) to secure the output of the report and help authorized users
to find the spool request. The following parameters needs to be maintained:
a.        Time of printing: set to u201CSend to SAP spooler Only for nowu201D
b.        Name u2013 abbreviated name to identify the job output
c.        Title u2013 free form description for the report output
d.        Authorization u2013 a value defined by Security in user profiles to allow those users to access
this spool request (authorization object S_SPO_ACT, value SPOAUTH). Only users with matching
authorization value in their profiles will be able to see the output.
e.        Department u2013 set to appropriate department/functional area name. This field can be used in
a search later.
f.        Retention period u2013 set to u201CDo not deleteu201D if the report output needs to be retained for more
than 8 days. Once the archiving/document repository solution is in place the spool requests could
be automatically moved to the archive/repository. Storage Mode parameter on the same screen
could be used to immediately send the output to archive instead of creating a spool request.
Configuring user access:
1.        To access a report output created by a background job, a user must have at
least access to SP01 (Spool requests) transaction without restriction on the user
name (however by itself it will not let the user to see all spool requests). To have
that access the user must have S_ADMI_FCD authorization object in the profile with
SPOR (or SP01) value of S_ADMI_FCD parameter (maintained by Security).
2.        To access a particular jobu2019s output in the spool, the user must have
S_SPO_ACT object in the profile with SPOAUTH parameter matching the value used
in the Print Specifications of the job (see p. 3.d above).
3.        Levels of access to the spool (display, print once, reprint, download, etc) are
controlled by SPOACTION parameter of S_SPO_ACT. The user must have at least
BASE access (display).
On-line reports:
1.        Exactly the same configuration can be maintained for any output produced
from R/3. If a user clicks u201CParametersu201D button on a SAP Printer selection dialog, it
allows to specify all the parameters as described in p. 3 of
u201CScheduling background jobsu201D section. Thus any output created by an online report
can be saved and accessed by any user authorized to access that spool request
(access restriction provided by the Authorization field of the spool request
attributes, see p. 3.d of u201CScheduling background jobsu201D section).
Access to reportu2019s output:
1.        A user that had proper access (see Configuring user access above) can
retrieve a job/report output through transaction SP01.
2.        The selection screen can be configured by clicking u201CFurther selection
criteriau2026u201D button (e.g. to bring u201CSpool request name (suffix 2)u201D field or hide other
fields).
3.        The following fields can be used to search for a specific output (Note that
Created By must be blank when searching for scheduled jobu2019s outputs)
a.        Spool request name (suffix 2) u2013 corresponds to a spool name in p. 3.b in
u201CScheduling background jobsu201D section above).
b.        Date created u2013 to find an output of a job that ran within a certain date range.
c.        Title u2013 corresponds to spool Title in p. 3.c in u201CScheduling background jobsu201D
section above).
d.        Department - corresponds to spool Department in p. 3.e in u201CScheduling
background jobsu201D section above).
4.        Upon entering selection criteria, the user clicks the Execute button   to
retrieve the list of matching spool requests.
5.        From the spool list the user can use several function such as view the
content of a spool request, print the spool request, view attributed of the spool
request, etc. (some functions may need special authorization, see p.3 in
Configuring user access)
a.        Click the Print button   to print the spool request with the default attributes
(usually defined with the job definition). It will print it on a printer that was
specified when a job was created.
b.        Click the u201CPrint with changed attributedu201D button   to print the spool request
with the different attributes (e.g. changing the printer name).
c.        Click the u201CDisplay contentsu201D button   to preview the spool request contents. A
Print    and Download   functions are available from the preview mode.
Exporting the Contents of a Spool Request
Use
You want to export the contents of a spool request as a text file to the SAP GUI working directory or to a directory of your choice. The content of the spool request is downloaded as plain text without, for example, graphics, images, or specific fonts.
The following procedures are irrelevant for the PDF-based form printing integrated as of SAP Web Application Server 6.40, since the print data can be opened and stored as a PDF. See also Displaying and Printing PDF-Based Forms.
Procedure
Exporting to the SAP GUI Working Directory:
Choose Spool Request ® Forward® Export as Text.
The entire text is stored in your SAP GUI working directory in ASCII format.
A file of this type is named using the following pattern:
.txt
Example: ABC0000004327.txt
You require appropriate authorization for this function.
Exporting to a Directory of Your Choice:
With this method of exporting a spool request, the content of the spool request is first displayed and you then download the screen list as a text file to the directory of your choice.
       1.      Select the spool request to be exported and choose Display Contents.
       2.      In the case of SAPScript/Smart Forms documents, activate list display by choosing Goto.
       3.      Choose System ® List ® Save ® Local File.
       4.      Choose one of the available formats and confirm your choice.
       5.      Choose a directory and save the spool request.
By default, only the first 10 pages of a spool request are saved in a file. You can increase the number of pages to be saved by choosing Goto ® Display Requests ® Settings and making the desired entries in the Display Area group box.

How to run the program in background job,program should run in 3 days.

Dear Gurus,
i have a program , that program should run approximately 3 days to get the result.
i scheduled this program as a background job.
how can i run sto5 t-code for this same program.
i that case how we can trace the output.
Experts please help me out.
Thank u very much.
Regards
sudheer

Hello Sudheer,
The trace can be set on background jobs by using ST12 transaction. Please make sure that the trace is activated for only few minutes in production environment.
Contact your basis team to activate trace on background job and the transaction used is ST12.
Thanks

Standard background job is running after deleting a user also

Hi Gurus,
in my production system environment i observed below thing.
1)Default standard background jobs were scheduled by earlier basis admin after some days he left and his id also deleted but still some jobs are running with his id and finishing also, how is it possible without having his ID in system?
2) what is the standard procedure to schedule default standard bg jobs in SAP? either from sap* or DDIC or basis admin?
one more question regarding Audit logs:
1)can we activate audit log for selective ids and selective period?
2)if we activate audit log is there any performance issues will come?
Thanks in advance
Venkat

Hello Venkat,
1)Default standard background jobs were scheduled by earlier basis admin after some days he left and his id also deleted but still some jobs are running with his id and finishing also, how is it possible without having his ID in system?
- Please cross check whether multiple jobs are scheduled with that user in different time period. If that user is defined in step then only that job fails otherwise it runs without any issues.
2) what is the standard procedure to schedule default standard bg jobs in SAP? either from sap* or DDIC or basis admin?
- Please go through the note suggested by Juan. I recommend to schedule with DDIC or Basis Admin.
Thanks,
Siva Kumar

Background job - programs all running at the same time...

Hi experts,
i have an issue regarding background job.i have to run multple programs in background one after another in one program.so i am using function modules job_open,submit and job_close.
my problem all the jobs are statrting at same time .but i want to run after completion of first job second job should start.
please guide me
Thanks
sai
Edited by: Julius Bussche on Feb 19, 2009 9:36 AM
Please use meaningfull subject titles

Try something like
LOOP AT it_filenames INTO ts_filenames.
CALL FUNCTION 'JOB_OPEN'
       EXPORTING
            jobname = jobname
       IMPORTING
            jobcount = jobcount.
SUBMIT program
    WITH p_file1 = ts_filenames-zzfname
    VIA JOB jobname NUMBER jobcount
    AND RETURN.
IF sy-tabix EQ 1.
    CLEAR: pred_jobcount,
           pred_jobname.
    GET TIME.
    IF sy-uzeit LT '235950'.
      sdlsstrttm = sy-uzeit + 10.
      sdlstrtdt = sy-datum.
    ELSE.
      sdlsstrttm = '000010'.
      sdlstrtdt = sy-datum + 1.
    ENDIF.
ELSE.
    sdlsstrttm = '      '. " no_time from LBTCHTOP
    sdlstrtdt = '        '. " no_date from LBTCHTOP
ENDIF.
CALL FUNCTION 'JOB_CLOSE'
       EXPORTING
            jobcount             = jobcount
            jobname              = jobname
            predjob_checkstat    = ' '
            pred_jobcount        = pred_jobcount
            pred_jobname         = pred_jobname
            sdlstrtdt            = sdlstrtdt
            sdlstrttm            = sdlstrttm
       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.
pred_jobcount = jobcount.
pred_jobname = jobname.
ENDLOOP.
I removed the checkstat, cause if you want to check the status you only have to submit one job with multiple steps. (Put JOB_OPEN and JOB_CLOSE out of the loop)
CALL FUNCTION 'JOB_OPEN'
     EXPORTING
          jobname = jobname
     IMPORTING
          jobcount = jobcount.
LOOP AT it_filenames INTO ts_filenames.
SUBMIT program
    WITH p_file1 = ts_filenames-zzfname
    VIA JOB jobname NUMBER jobcount
    AND RETURN.
ENDLOOP.
CALL FUNCTION 'JOB_CLOSE'
     EXPORTING
          jobcount = jobcount
          jobname   = jobname
          strtimmed = 'X'.
Regards

Rule set import - Background job did not run

Hi,
I am setting up my CC 5.2 production system. I have downloaded from ruleset from the dev CC and imported it into production. However the background job generated did not run. I am implementing SAP note 999785 to fix this, but am wondering what should I do about the rule set? Do I need to delete the rule set and reimport it? As this background job did not run I notice that the permission rules did not generate.
Any advice is welcome.
Thanks

Hi,
as the backgorund job never ran and no rules were created, I can just reimport the ruleset and let the job run. I have tried this and the rules were created successfully

Background job finished but flat file not created in the Background

Dear all,
ZHR_CSD program is scheduled to run daily at 00:01:00. This program is generating the flat file in the folder CSD/HR.
when i schedule this program to run immediately it is generating the flat file.
But when i schedule this program in Background it is not generating flat file .
Regards

Hi,
As suggested by Eric, your Z Program is probably using GUI_DOWNLOAD Function Module.
GUI_DOWNLOAD or any other GUI function modules (FM) will only run in foreground, not in Background.
Ask your developer to code that Z Program with OPEN DATASET logic, if its possible.
The Reverse situation is well described in [this thread|Background Job assigment with variant in SM37 , for Textfile uploading], please refer it to get some relative information for the same.
Regards,
Bhavik G. Shroff

Background job "EU_REORG" scheduled to run daily is taking lot of time.....

Similar Messages

Maybe you are looking for