Exception ( in Reporting Agent ) background job runs indefinitely

Hi
I created an Exception setting under reporting agent (to send out a mail in the SAP Office inbox, on a specific exception) and assigned it under a scheduling package.
I have assigned a proper query variant to the exception setting also.
When I exeucte the job, it goes indefinitely.
I highly appreciate if somebody can help what needs to be done to fix this.
Thanks
KC

Hi,
If you choose the Precalculate by User option, all the data and HTML pages for the Reporting Agent setting are precalculated for each of the selected users in a single job. This applies in both the cases: Roles or users. When you specify a role after selecting the option 'Precalculate by User', the precalculation will be done for all the users assigned to that role and not the role.
Roles/Users is just 2 different ways of giving the user restriction. If you specify the roles, the system will precalculate for all the users assigned to the role. If you have few users for whom you want the precalculation to be done, then you can specify the user IDs. If you have many users assigned to a particular role for whom you want the precalculation to be done, then you can specify the role.
Regards,
Shilpa

Similar Messages

Export of report/query to a file for background job runs

I have a requirement to automate the export of a report or query to a file so when a background job runs a new file is generated to the drive.
This cannot be a customized solution for 1 report, it must be able to adapt to other reports or queries as well.
Any help will be highly appreciated.
Thank you,
Thamina

Hi,
SAP have created a standard program RSTXPDFT4 to convert your Sapscripts spools into a PDF format.
Specify the spool number and you will be able to download the sapscripts spool into your local harddisk.
It look exactly like what you see during a spool display.
Please note that it is not restricted to sapsciprts spool only. Any reports in the spool can be converted using the program 'RSTXPDFT4'.
Regards,
Pavan

Background Job Run - Error Msg

Hi all,
When i run my report as background job it is failing.
In report i have checked one condition n if that do not satisfy it will give error. but in any situation the background job fails though condition satifies but the spool is getin created.
when i debug the report it gives no error in that report but after it gives System message '' Job cancelled after system exception ERROR_MESSAGE''.
any guidelines will be appreciated...
regards,
vikas.

thankx for your reply..
it is not giving me any dump or something neither my report contains any popup window.
thing is that i am checking one error value at the event END-OF-SELECTION and giving some error mesg depending upon that.
when i check this in debug mode in background mode itself (thr' JDBG or SM50) the value of error mesg is empty...so idealy the report is executed fine but when after words i go for F8 it gives me that error message.
regards,
vikas

Background job running for a long time - trace is not capturing.

hi guys,
My background job runs for more thatn 4 hours. some times. (normally it completes withing one hour)
i tried to trace using st12 ....and executed this program. but not got complete trace report of 4 hours.
what is the best way to trace long running programs like this.
is there any alternative for this...???
regards
girish

Giri,
There is no need to trace a program for the full 4 hours. There is usually just one piece of rogue code causing the problem, and it can be identified quite quickly.
If I were you I would just watch the job run via SM50, to see if it lingers on any database tables. Also check if the memory is filling up - this is the sign of a memory leak.
You can also try stopping the program (via SM50 debugging) at random points, to see what piece of code it is stuck in.
The issue should reveal itself fairly quickly.
Tell us what you find!
cheers
Paul

What client is background job running in?

Hello all,
Is there a way to tell which client a background job listed in SM37 is running in? Can't seem to find that information in the job nor any tables. I thought that you could only see the jobs that are running in the client you are logged onto too but that's not the case.
Thanks,
Tom

Hi,
For checking the client for particular background job which is runnig can be cheked by.
Go to SM37- enter the particular job name and the details eg: username and the job start and end condition. Execute this.
Now on top go to Setting->Layout->Change Layout->
On right side u can find the hidden fields-select client from that and bring it to change layout ie. left part. and press copy.
This will change the layout of ur report and u can see the client number for that particular background job running.
U can do this by using * also while mentioning the jobname.This way you do not have to open every job to find out.
Hope this will be of some help.
Thanks
Ruchika
Edited by: Ruchika Kapoor on Jul 2, 2009 2:04 PM

RE: Report for Background jobs

Hi SAP Guru's,
I need to create a report on Background Job status , please tell me is there any standard reports ? or How to create a report on Background Jobs Status?
Thanks in Advance,
Krishna.

Dear Raja,
In std report this is not possible, talk to ur ABAPer to fetch the feild PLNUM from AFPO table with respect to the AUFNR field. This can be added to the std report itself. use this logic it will work
sree

Background Job running long time.

Hello All,
One of customer background job running for long time more than 11 hours, but usually this jobs get completed within 4 hrs.
I have checked in WP trace file, it shows "WP has reached abap/heaplimit=40000000".
This is the Value I can see in RZ11. Now it is not possible to change the value.
Frequently facing this problem, please guide me to solve this issue.
Regards
Vinay.

Hi
First of all, abap/heaplimit is the limit of memory usage by a WP.
Follwing is the documentation from help.sap.com
The value of the parameter should be between 10000000 (10 MB) and 2000000000 (2GB), the recommended default setting is 40000000 (40 MB).
The objective is to have the least number of work process restarts as possible, without a swap space bottleneck occurring. The heap memory allocated by the work processes has to be released again.
As shown in the graphic, the value of abap/heaplimit should be smaller than abap/heap_area_dia or abap/heap_area_nondia, so that the dialog step that is running can still be executed. This prevents the work process from working against the operating systemu2019s swap space limit if there is a programmed termination of the work process.
So,Do the above checks. And importantly check the memory utilizations at the time of running your job and check whether any other job was also running at the sametime.
Increasing the parametes is not a good idea.. If you continuously face this issue then only think of parametes. As u said ,this problem is not happenng too often.
Hope this is useful

ALV report in Background Job

Hi,
We have an report in which we are using FM :- REUSE_ALV_LIST_DISPLAY.
In forgroud the Report Header is getting displayed only Once.
When we run the report in background, we are getting in spool in which there are "Page Break and Header" in every page.
Downloading the report to MS Excel from Spool is creating setting problem.
Please tell me "how can we do so while running the report in background, "Page break and header dosen't create i.e only One Header and One Page"
Waiting for reply..
Saurabh Garg

Hi Saurabh ,
Use TOP-OF-LIST instead of TOP-OF-PAGE.
Please check this sample with different events in ALV-GRID.
report zbnstest.
* TABLES AND DATA DECLARATION.
*TABLES: mara,makt.",marc.
data syrepid like sy-repid.
data sydatum(10). " LIKE sy-datum.
data sypagno(3) type n.
* WHEN USING MORE THAN ONE TABLE IN ALV WE NEEED TO DECLARE THE TYPE
* GROUP (TYPE-POOLS--------->SLIS)
type-pools : slis.
* INTERNAL TABLE DECLARATION.
* INTERNAL TABLE TO HOLD THE VALUES FROM THE MARA TABLE
data: begin of t_mara occurs 0,
matnr like mara-matnr,
meins like mara-meins,
mtart like mara-mtart,
matkl like mara-matkl,
end of t_mara.
* INTERNAL TABLE TO HOLD THE CONTENTS FROM THE EKKO TABLE
data : begin of t_marc occurs 0,
matnr like mara-matnr,
werks like marc-werks,
minbe like marc-minbe.
data: end of t_marc.
* INTERNAL TABLE TO HOLD THE VALUES FROM MAKT TABLE.
data : begin of t_makt occurs 0,
matnr like mara-matnr,
maktx like makt-maktx,
spras like makt-spras,
end of t_makt.
* INTERNAL TABLE WHICH ACTUALLY MERGES ALL THE OTHER INTERNAL TABLES.
data: begin of itab1 occurs 0,
matnr like mara-matnr,
meins like mara-meins,
maktx like makt-maktx,
spras like makt-spras,
werks like marc-werks,
minbe like marc-minbe,
end of itab1.
* THE FOLLOWING DECLARATION IS USED FOR DEFINING THE FIELDCAT
* AND THE LAYOUT FOR THE ALV.
* HERE AS slis_t_fieldcat_alv IS A INTERNAL TABLE WITHOUT A HEADER LINE
* WE EXPLICITELY DEFINE AN INTERNAL TABLE OF THE SAME STRUCTURE AS THAT
* OF slis_t_fieldcat_alv BUT WITH A HEADER LINE IN THE DEFINITION.
* THIS IS DONE TO MAKE THE CODE SIMPLER.
* OTHERWISE WE MAY HAVE TO DEFINE THE STRUCTURE AS IN THE NORMAL SAP
* PROGRAMS.
* IN THE FIELDCATALOG TABLE WE ACTUALLY PASS THE FIELDS FROM ONE OR
* MORE TABLES AND CREATE A STRUCTURE
* IN THE LAYOUT STRUCTURE WE BASICALLY DEFINE THE FORMATTING OPTIONS
* LIKE DISPLAY IN THE ZEBRA PATTERN ,THE HOTSPOT OPTIONS ETC.
data: fieldcatalog type slis_t_fieldcat_alv with header line,
fieldlayout type slis_layout_alv.
* DECLARING THE EVENTTABLE INTERNL TABLE FOR USING EVENTS LIKE
* TOP-OF-PAGE ETC.
data : eventstab type slis_t_event with header line.
* DECLARING AN INTERNAL TABLE TO HOLD THE DATA FOR THE TOP-OF-PAGE
data : heading type slis_t_listheader with header line.
data : heading1 type slis_t_listheader with header line.
data : heading2 type slis_t_listheader with header line.
data : heading3 type slis_t_listheader with header line.
data : heading4 type slis_t_listheader with header line.
data : heading5 type slis_t_listheader with header line.
data : heading6 type slis_t_listheader with header line.
data : heading7 type slis_t_listheader with header line.
data : heading8 type slis_t_listheader with header line.
* STRUCTURE TO PASS THE COLOR ATTRIBUTES FOR DISPLAY.
data : colorstruct type slis_coltypes.
* INITIALIZATION. *
initialization.
syrepid = sy-repid.
sypagno = sy-pagno.
clear fieldcatalog.
* START-OF-SELECTION. *
start-of-selection.
* SUBROUTINE TO POPULATE THE COLORSTRUCT
perform fill_colorstruct using colorstruct.
* SUBROUTINE TO POPULATE THE FIELDS OF THE FIELD CATALOGUE
perform populate_fieldcatalog.
* SUBROUTINE TO SELECT DATA FROM VARIOUS TABLES AND POPULATE IT IN THE
* INTERNAL TABLE.
perform selectdata_and_sort.
* SUBROUTINE TO POPULATE THE LAYOUT STRUCTURE.
perform populate_layout using fieldlayout.
* SUBROUTINE TO CALL THE FUNCTION MERGE TO ENSURE PROPER DISPLAY.
perform merge_fieldcatalog.
* SUBROUTINE TO POPULATE THE EVENTSTAB.
perform fill_eventstab tables eventstab.
* SUBROUTINE TO POPULATE THE HEADING TABLES.
perform fill_headingtable tables heading using 'HEADING'.
perform fill_headingtable tables heading1 using 'HEADING1'.
perform fill_headingtable tables heading2 using 'HEADING2'.
perform fill_headingtable tables heading3 using 'HEADING3'.
perform fill_headingtable tables heading4 using 'HEADING4'.
perform fill_headingtable tables heading5 using 'HEADING5'.
perform fill_headingtable tables heading6 using 'HEADING6'.
perform fill_headingtable tables heading7 using 'HEADING7'.
perform fill_headingtable tables heading8 using 'HEADING8'.
* SUBROUTINE TO DISPLAY THE LIST.
perform display_alv_list.
* FORMS
* IN THIS SUBROUTINE WE POPULATE THE FIELDCATALOG TABLE WITH THE NAMES
* OF THE TABLE,FIELDNAME,WHETHER IT IS KEY FIELD OR NOT,HEADING AND
* COLUMN JUSTIFICATION.
form populate_fieldcatalog.
perform fill_fields_of_fieldcatalog tables fieldcatalog
using 'ITAB1' 'MATNR' 'X' .
perform fill_fields_of_fieldcatalog tables fieldcatalog
using 'ITAB1' 'MEINS' ' '.
perform fill_fields_of_fieldcatalog tables fieldcatalog
using 'ITAB1' 'MAKTX' ' ' .
perform fill_fields_of_fieldcatalog tables fieldcatalog
using 'ITAB1' 'MTART' ' ' .
perform fill_fields_of_fieldcatalog tables fieldcatalog
using 'ITAB1' 'MATKL' ' ' .
perform fill_fields_of_fieldcatalog tables fieldcatalog
using 'ITAB1' 'SPRAS' ' ' .
perform fill_fields_of_fieldcatalog tables fieldcatalog
using 'ITAB1' 'WERKS' ' ' .
perform fill_fields_of_fieldcatalog tables fieldcatalog
using 'ITAB1' 'MINBE' ' ' .
endform. " POPULATE_FIELDCATALOG
* FORM FILL_FIELDS_OF_FIELDCATALOG *
* --> FIELDCATALOG *
* --> P_TABNAME *
* --> P_FIELDNAME *
* --> P_KEY *
* --> P_KEY *
form fill_fields_of_fieldcatalog tables fieldcatalog
structure fieldcatalog
using p_tabname
p_fieldname
p_key.
* p_no_out.
fieldcatalog-tabname = p_tabname.
fieldcatalog-fieldname = p_fieldname.
fieldcatalog-key = p_key.
fieldcatalog-emphasize = '1234'.
*fieldcatalog-no_out = p_no_out.
append fieldcatalog.
endform. " FILL_FIELDSOFFIELDCATALOG
* FORM POPULATE_LAYOUT *
* --> FIELDLAYOUT *
form populate_layout using fieldlayout type slis_layout_alv.
fieldlayout-f2code = '&ETA' .
fieldlayout-zebra = 'X'.
* FOR THE WINDOW TITLE.
fieldlayout-window_titlebar = 'ALV with Events'.
fieldlayout-colwidth_optimize = 'X'.
fieldlayout-no_vline = ' '.
*fieldlayout-no_input = 'X'.
fieldlayout-confirmation_prompt = ''.
fieldlayout-key_hotspot = 'X'.
* This removes the column headings if the flag is set to 'X'
fieldlayout-no_colhead = ' '.
*fieldlayout-hotspot_fieldname = 'MAKTX'.
fieldlayout-detail_popup = 'X'.
* fieldlayout-coltab_fieldname = 'X'.
endform. " POPULATE_LAYOUT
* FORM SELECTDATA_AND_SORT *
form selectdata_and_sort.
select matnr meins mtart matkl from mara
into corresponding fields of t_mara
up to 500 rows .
select matnr maktx spras from makt
into corresponding fields of t_makt
where matnr = t_mara-matnr and
spras = sy-langu.
select matnr werks minbe from marc
into corresponding fields of t_marc
where matnr = t_mara-matnr.
append t_marc.
endselect.
append t_makt.
endselect.
append t_mara.
endselect.
perform populate_itab1.
sort itab1 by matnr.
endform. " SELECTDATA_AND_SORT
* FORM MERGE_FIELDCATALOG *
form merge_fieldcatalog.
call function 'REUSE_ALV_FIELDCATALOG_MERGE'
exporting
i_program_name = syrepid
i_internal_tabname = 'ITAB1'
* i_structure_name = 'COLORSTRUCT'
* I_CLIENT_NEVER_DISPLAY = 'X'
i_inclname = syrepid
changing
ct_fieldcat = fieldcatalog[]
exceptions
inconsistent_interface = 1
program_error = 2
others = 3.
endform. " MERGE_FIELDCATALOG
* IN THIS FUNCTION THE MINIMUM PARAMETERS THAT WE NEED TO PASS IS AS
* FOLLOWS:-
* i_callback_program --> CALLING PROGRAM NAME
* i_structure_name --> STRUCTURE NAME.
* is_layout --> LAYOUT NAME.
* it_fieldcat ---> BODY OF THE FIELD CATALOGUE INTERNAL TABLE
form display_alv_list.
call function 'REUSE_ALV_LIST_DISPLAY'
exporting
* I_INTERFACE_CHECK = ' '
i_callback_program = syrepid
* I_CALLBACK_PF_STATUS_SET = ' '
* I_CALLBACK_USER_COMMAND = ' '
i_structure_name = 'ITAB1'
is_layout = fieldlayout
it_fieldcat = fieldcatalog[]
* IT_EXCLUDING =
* IT_SPECIAL_GROUPS =
* IT_SORT =
* IT_FILTER =
* IS_SEL_HIDE =
* I_DEFAULT = 'X'
* THE FOLLOWING PARAMETER IS SET AS 'A' INORDER TO DISPLAY THE STANDARD
* TOOL BAR
i_save = 'A'
* IS_VARIANT = ' '
it_events = eventstab[]
* IT_EVENT_EXIT =
* IS_PRINT =
* I_SCREEN_START_COLUMN = 0
* I_SCREEN_START_LINE = 0
* I_SCREEN_END_COLUMN = 0
* I_SCREEN_END_LINE = 0
* IMPORTING
* E_EXIT_CAUSED_BY_CALLER =
* ES_EXIT_CAUSED_BY_USER =
tables
t_outtab = itab1
exceptions
program_error = 1
others = 2.
endform. " DISPLAY_ALV_LIST
*& Form POPULATE_ITAB1
* text
* --> p1 text
* <-- p2 text
form populate_itab1.
loop at t_mara.
loop at t_makt where matnr = t_mara-matnr.
loop at t_marc where matnr = t_mara-matnr.
move-corresponding t_mara to itab1.
move-corresponding t_makt to itab1.
move-corresponding t_marc to itab1.
append itab1.
endloop.
endloop.
endloop.
endform. " POPULATE_ITAB1
*& Form FILL_EVENTSTAB
* text
* -->P_EVENTSTAB text *
form fill_eventstab tables p_eventstab structure eventstab.
* WHEN THE FOLLOWING FUNCTION IS CALLED THE SYSTEM POPULATES THE
* INTERNAL TABLE EVENTSTAB WITH A LIST OF EVENTS NAME.
* AS SHOWN BELOW WHEN USING I_LIST_TYPE = 0 THE FUNCTION RETURNS 14
* EVENTS NAME.
call function 'REUSE_ALV_EVENTS_GET'
exporting
i_list_type = 0
importing
et_events = p_eventstab[]
exceptions
list_type_wrong = 1
others = 2.
* BY CALLING THE ABOVE FUNCTION WE FIRST POPULATE THE EVENTSTAB WITH
* THE PREDEFINED EVENTS AND THEN WE MOVE THE FORM NAME AS SHOWN BELOW.
* WE ASSIGN A FORM NAME TO THE EVENT AS REQUIRED BY THE USER.
* FORM NAME CAN BE ANYTHING.THE PERFORM STATEMENT FOR THIS FORM
* IS DYNAMICALY CALLED.
read table p_eventstab with key name = slis_ev_top_of_page.
if sy-subrc = 0 .
move 'TOP_OF_PAGE' to p_eventstab-form.
append p_eventstab.
endif.
read table p_eventstab with key name = slis_ev_top_of_coverpage.
if sy-subrc = 0 .
move 'TOP_OF_COVERPAGE' to p_eventstab-form.
append p_eventstab.
endif.
read table p_eventstab with key name = slis_ev_end_of_coverpage .
if sy-subrc = 0 .
move 'END_OF_COVERPAGE' to p_eventstab-form.
append p_eventstab.
endif.
read table p_eventstab with key name = slis_ev_foreign_top_of_page.
if sy-subrc = 0 .
move 'FOREIGN_TOP_OF_PAGE' to p_eventstab-form.
append p_eventstab.
endif.
read table p_eventstab with key name = slis_ev_foreign_end_of_page.
if sy-subrc = 0 .
move 'FOREIGN_END_OF_PAGE' to p_eventstab-form.
append p_eventstab.
endif.
read table p_eventstab with key name = slis_ev_list_modify.
if sy-subrc = 0 .
move 'LIST_MODIFY' to p_eventstab-form.
append p_eventstab.
endif.
read table p_eventstab with key name = slis_ev_top_of_list.
if sy-subrc = 0 .
move 'TOP_OF_LIST' to p_eventstab-form.
append p_eventstab.
endif.
read table p_eventstab with key name = slis_ev_end_of_page.
if sy-subrc = 0 .
move 'END_OF_PAGE' to p_eventstab-form.
append p_eventstab.
endif.
read table p_eventstab with key name = slis_ev_end_of_list .
if sy-subrc = 0 .
move 'END_OF_LIST' to p_eventstab-form.
append p_eventstab.
endif.
endform. " FILL_EVENTSTAB
*& Form FILL_HEADINGTABLE
* text
* -->P_HEADING text *
form fill_headingtable tables p_heading structure heading
using tablename.
case tablename.
when 'HEADING'.
p_heading-typ = 'H'.
concatenate
' REPORT NAME:-' syrepid
' ABB Industry Pte Ltd' into p_heading-info.
append p_heading.
write sy-datum using edit mask '__/__/____' to sydatum.
concatenate
' DATE:-' sydatum ' USER: ' sy-uname 'PAGE NO:' sypagno
into p_heading-info.
append p_heading.
when 'HEADING1'.
p_heading-typ = 'H'.
p_heading-info = 'TOP-OF-COVER-PAGE'.
append p_heading.
when 'HEADING2'.
p_heading-typ = 'H'.
p_heading-info = 'END-OF-COVER-PAGE'.
append p_heading.
when 'HEADING3'.
p_heading-typ = 'H'.
p_heading-info = 'FOREIGN-TOP-OF-PAGE'.
append p_heading.
when 'HEADING4'.
p_heading-typ = 'H'.
p_heading-info = 'FOREIGN-END-OF-PAGE'.
append p_heading.
* WHEN 'HEADING5'.
* P_HEADING-TYP = 'H'.
* P_HEADING-INFO = 'LIST-MODIFY'.
* APPEND P_HEADING.
when 'HEADING6'.
p_heading-typ = 'H'.
p_heading-info = 'END-OF-PAGE'.
append p_heading.
when 'HEADING7'.
p_heading-typ = 'H'.
p_heading-info = 'END-OF-LIST'.
append p_heading.
when 'HEADING8'.
p_heading-typ = 'H'.
p_heading-info = 'TOP-OF-LIST'.
append p_heading.
endcase.
endform. " FILL_HEADINGTABLE
* FORM TOP_OF_PAGE *
form top_of_page.
call function 'REUSE_ALV_COMMENTARY_WRITE'
exporting
it_list_commentary = heading[]
exceptions
others = 1.
endform.
*& Form FILL_COLORSTRUCT
* text
* -->P_COLORSTRUCT text *
form fill_colorstruct using p_colorstruct type slis_coltypes .
p_colorstruct-heacolfir-col = 6.
p_colorstruct-heacolfir-int = 1.
p_colorstruct-heacolfir-inv = 1.
endform. " FILL_COLORSTRUCT
* FORM TOP_OF_COVERPAGE *
form top_of_coverpage.
call function 'REUSE_ALV_COMMENTARY_WRITE'
exporting
it_list_commentary = heading1[]
exceptions
others = 1.
endform.
* FORM END_OF_COVERPAGE *
form end_of_coverpage.
call function 'REUSE_ALV_COMMENTARY_WRITE'
exporting
it_list_commentary = heading2[]
exceptions
others = 1.
endform.
* FORM FOREIGN_TOP_OF_PAGE *
form foreign_top_of_page.
call function 'REUSE_ALV_COMMENTARY_WRITE'
exporting
it_list_commentary = heading3[]
exceptions
others = 1.
endform.
* FORM FOREIGN_END_OF_PAGE *
form foreign_end_of_page.
call function 'REUSE_ALV_COMMENTARY_WRITE'
exporting
it_list_commentary = heading4[]
exceptions
others = 1.
endform.
* FORM LIST_MODIFY *
*FORM LIST_MODIFY.
* CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
* EXPORTING
* IT_LIST_COMMENTARY = HEADING5[]
* EXCEPTIONS
* OTHERS = 1.
*ENDFORM.
* FORM END_OF_PAGE *
form end_of_page.
call function 'REUSE_ALV_COMMENTARY_WRITE'
exporting
it_list_commentary = heading6[]
exceptions
others = 1.
endform.
* FORM END_OF_LIST *
form end_of_list.
call function 'REUSE_ALV_COMMENTARY_WRITE'
exporting
it_list_commentary = heading7[]
exceptions
others = 1.
endform.
* FORM TOP_OF_LIST *
form top_of_list.
call function 'REUSE_ALV_COMMENTARY_WRITE'
exporting
it_list_commentary = heading8[]
exceptions
others = 1.
endform.
*--- End of Program
Regards,
Raghav

Background job running

Hi Friends,
I need to run a standard program(report) in background immediately from my custom program(report) and I need to pick up the output report(standard) table values back to my custom program.
Is it possible? if so Can you pls suggest the solution for the same
I am trying with submit with job statement, but it is only scheduling the job and it is not running immediately. If it runs immediately also I need to pick the values of standard program to my custom program
Thanks in advance
pavan

Hi Pavan,
In this scenario where you want to run the standard report in background from the custom report,the only solution is to schedule the job(any method) with the custom report as the starting point and then use Submit with the values in it and then Use Return along wth it.
OR else use Exporting List to Memory with Submit and Return.
And then,use the Function Module "Importing From Memory" and pass the data from the standard report to the internal table.
In case you have any further clarifications,do let me know.
Regards,
Puneet Jhari.

Background job running slow

Hi,
Suppose any background job is taking much more time than required so how to speed up the job without chaning the master data.
Regards,
Prabhat Sahay

Hello,
If your job is a DP job, please refer to SAP note 864950 and follow the suggestions in the note.
Basically. there're following points:
1)If the job is relevant to planning book/data view, make sure only needful key figures are loaded in the data view.
2)Macros should only be executed on detailed level, except when aggregate level execution is also necessary.
3)Try not to use navigational attributes.
4)Make sure the consisteny of the planning area by:
   /sapapo/ts_lcm_reorg
   /sapapo/ts_lcm_cons_check
5)If you use fixed aggregates, they may affect the performance very much.
   Try to deactivate them and run /sapapo/ts_lcm_cons_check before the job (if the job changes relevant data).
   Then activate and fill the fixed aggregates afterwards.
Best Regards,
Ada

Setting layout to a report in background job

Hi.
Does anybody knows how I set layouts dynamically to a report output, given that such report is scheduled to run once a day in a background job?
It would work for me, either: through SM36 or coding JOB_OPEN / JOB_SUBMIT / JOB_CLOSE (or any other option, if available).
My requirement is to execute every night few reports, each with their corresponding variants and layouts.
Something like:
RUN <report1> VARIANT <variant1> LAYOUT <layout1> JOB <job>. (it would output and xls file).
RUN <report2> VARIANT <variant2> LAYOUT <layout1> JOB <job>. (it would output another xls file).
RUN <report3> VARIANT <variant3> LAYOUT <layout2> JOB <job>. (it would output a 3rd xls file).
How should I do to inform variant and layout parameters?
Thank you.
Rafael.

I think I didn't make myself clear in my explanation. Sorry about that.
My question is, I can create a new field in selection-screen specifically to layout and it would work. However, as I'm running it in background, the ALV will not be shown and the output file must be the export of the ALV with the layout (if in XLS, it'd be even better, but in .CSV would work as well). I just don't think it would work with a .TXT output, because there's no way to reflect the layout in a .TXT file.
Is there any way of having the ALV inside the output file (saved in the server, in background processing)?
Thank you so much!
Edited by: rvsilvax on Nov 30, 2011 3:45 PM

CRYSTAL REPORTS AS BACKGROUND JOBS

Hi Experts,
We are running some Crystal reports that extract data from our SAP BI System. These Crystal report jobs run on a regular basis to populate the crystal reports.
The Problem is that whenever these jobs run in the BI system, they block most of the DIALOG processes available ( 5 out of 7 available) leading to very LOW system performance in terms of response and execution.
The Solution what we are seeking is whether we can somehow set these Crystal jobs as BACKGROUND processes, so that the overall system performance is improved. So kindly suggest any means by which we can set these crystal report jobs as BACKGROUND processes in SAP BI when they are executed from crystal server.
Thanks in Advance,
Uday

Hi,
Crystal Reports is NOT an ETL tool. For those kind of activities we have a product called Data Integrator.
ingo

How to submit the report in Background job.

Hello Friends,
In the selection screen I have 2 radio buttons one for background Process & other for foreground processing. if the user selects the background processing the program should execute in background and output need to be sent to SAP Inbox.
Issues:
1) If I am using the JOB_Submit FM or Report Submit the program is going to infinite loop and many continiously jobs are are being scheduled. How to avoid.
2) Is there any best possible way to send the mail to SAP Inbox.
Note: I am using OOALV in my program....
Thanks,
Ravi

Hi,
the first problem looks like you have an infinite recursion. You just need to avoid background scheduling again. There is a system field sy-batch. So if this field is equal to 'X' then you are already in background mode and you don't need to schedule your background job again. Another way is to split your program in two programs. The first will be responsible for scheduling or executing the second one.
You can use FM SO_NEW_DOCUMENT_SEND_API1 to send message to workflow inbox. You need to user receiver type B. There are so many posts on this forum about sending emails from ABAP which may help you with implementing this requirement.
Cheers

How to get spool from background job run?

Hello,
I have this situation and need help on how to resolve:
I have RFC FM which called from another system, in that FM I am submitting BDC section as a batch job by report RSBDCSUB. The problem is that this job may run for 1 or 2 hours and my RFC call will be close by that time. How can I bring the result of my batch job run back to the calling system in this case? Will appreciate any hints.
Thank you,
Glenn

Hi
After you the Job completes. Use the spool ID and fetch the Spool list using the report RSPOLST2.
You can download the spool job using the Function module RSPO_DOWNLOAD_SPOOLJOB.
Thanks
Dev

SAP R/3 Enterprise : Background job run on application servers

Hello All,
For our SAP system (SAP_BASIS 620, SAP_ABA 620,SAP_APPL 470), there are 5 application servers and one central instance.
We have a Background job that connects to external non sap system for data delivery via RFC of Type "G" i.e.HTTP Connection to Ext. Server with port 443 . RFC works fine.
In transaction STRUST, SSL certificates are also installed to enable the https connectivity from R3 system.
Our current issue is that background jon runs on one of the application server correctly and is able to transfer that data to external system. However if same job runs on other 4 application server, it fails to connect to external server and throws error:
RFC Destination XXXX not defined
407 Unknown error
Failed to store the XML content
Error in the XML document: 1301540.xml
407 Unknown error
This is very starnge for us .RFC is working correctly every time but background job works on one AS and not on other AS.
Where and What can be the difference in application servers.
Please help to send in ur replies. Thanks
Edited by: Chetna Verma on Apr 27, 2011 1:46 PM

Hi,
Is there a firewall between the non SAP system and the SAP system ? It could be that firewall rules have only been set for one only of the SAP application servers ?
Did you check the HTTP connections from each application server ?
Did you check that the ICM is running on each SAP application server ?
Regards,
Olivier

Exception ( in Reporting Agent ) background job runs indefinitely

Similar Messages

Maybe you are looking for