Output after the background job finished successfully

Hi All,
We executed a Dunning job in the background (sm37) and the job finished succesfully. How to check whether the job has created an output ? Where to look for the output ?
Regards
Shiva

You can check the spool request of your job via SM37 or SMX. Go to SM37 select your job and check the spool request.
Regards
Subhash

Similar Messages

How to check the ALV output for the background job

Hi Guru,
We are having a cutomized report which will display the result like a ALV report.
We configured it as an background job, after the completion of the background job, it will send the result to the SPOOL, and we can use SP02 to check the output,
But it is not easy for user to directly check the result easily, is there an method we can save it as an spreadsheet and send the output to a specific location or mailbox and then user can check it easily
thanks,

In SM37 ,select the Job > Spool > Select Spool No > Display Contents > Here it will show you the Output of the Report.Now select Ctrl +Shift + F12 , it will ask you to save the Spread sheet in specified location.
Best Regards,
Ankur

Not generating a spool output in the background job

Hi Team,
I have an alv report and If I schedule the program using SM36 transaction it is not generating the spool ouput.
If I run the same program in background mode when we use se38 and select execute in background in program menu and it works successfully and generates alv grid list in the spool output.
But, user wants to schedule the job in sm36 and check the same output in spool. Please advise why it is not generating.
Note:I am using the cl_salv_table=>factory method to generate the output.
Thanks in advance,
Sunil Kumar.

This is not really an ABAP question and you might want to ask your Basis admin for assistance. But I believe that spool will not be generated if you don't specify print parameters for a step. When you define the step in SM36, make sure to specify the print parameters.

Message when background Job is successful .. information

Dear All
I just want to give an information message when background job is successful.
I am starting a job using SUBMIT < > AND RETURN
if sy-subrc = 0
CALL FUNCTION 'JOB_CLOSE'
if sy-subrc <> 0
Do Nothing
else
message <>
end if.
end if.
Let me know if above code is correct and how to make a message information only in this.
Amol

Hi Amol,
I'm struggling to fully follow your requirements, but the job is not complete when you call the function 'JOB_CLOSE'.
You can check if the background job is successful using the method below...
Within a DO-ENDDO use the function module 'BDL_READ_JOB_STATUS' passing it job name and job number.
If the job status returned from 'BDL_READ_JOB_STATUS' = 'F' then the job is finished and exit the DO-ENDDO.
Kind Regards,
Richard.

Read Error logs after running the background jobs

Hi,
How to read the error logs after running the background jobs. In our scenarion we are running the COHV transaction to release the production orders in background. But we are not finding the error logs after background job. We would like to read the error logs and correct for further processing.
Kindly suggest.
Thanks & Regards,
N. Laxman

Hi
you can check the back ground jobs defined by any user in SM37 and where you can see the spool and job logs as well.
plz check in your case and revert back
Regards
Anupam Sharma

After upgrade the background jobs

Dear all,
We are Upgrading the PRD server.after after upgrade the background job (user specific ) jobs are mannully started are atuomatically started.I check the job btctrns2.
The user specfic jobs are not started.
Kindly advise us to start automatically.
regards
guna

Hello Guna,
Please find below a link to Background Jobs related information
(if click does not work, copy and paste it in your browser)
http://help.sap.com/erp2005_ehp_03/helpdata/EN/51/c0e07d569a11d189200000e8323d3a/frameset.htm
I hope this is useful to you in your work
Best Regards
Sitaraman

Actual Varaint Name used in the Background Job

Hi,
When a program is executed in Background made the selection screen variant selected is not the one that is shown in the Background Job Step information. There we see variant as &0000000000044.
I want to find the actual variant that was selected at the time of running the program in background mode.
Thanks.

Hi,
I also faced the same issue and after my R&D i found a workaround for this. Check this out.
Create a selection screen parameter and hide it.
PARAMETERS: po_varnt TYPE sy-slset NO-DISPLAY.
Now place below code in AT SELECTIO-SCREEN OUTPUT event.
AT SELECTION-SCREEN OUTPUT.
    CHECK sy-batch IS INITIAL.
    CLEAR po_varnt.
    MOVE sy-slset TO po_varnt.
If you are running in background by pressing F9 from selection screen, Use your hided parameter po_varnt for the variant name instead of sy-slset.
If you are running the report in foreground or through SM36 then you can use sy-slset to know the variant name.
Thanks,
Vinod.

The lotus mail about the Background Job status

Hi ,
I have a requirement where SAP users want the status of the background job in their lotus mail.The problem is job takes run for more than 15-20 hours and some times gets failed too.Whichever is the status , they want the update. The job is run daily in the night.So can not be done in the same program. Writng different program to check and send the mail can be an option.
But My question would be
1.Is there SAP standard funtionality /progarm to send the job log (not the spool) in the mail?
Thanks in advance.

Hi,
You can run another job in background which can monitor this original program. I would die and schedule itself in an hour for next status. the logic goes this way.
1) The original Z program call the Z job monitor prog with jobname.
2) The Z job monitor prog checks the status of job and will send a status mail on finished or cancelled.
3) if the job is still active, the z job monitor prog will schedule itself for after an hour to check the status again.
thus steps 2 & 3 would be in loop till the original z prog finishes or gets cancelled.
Regards,
Nirmal

Alv show in report but when see in spool (after run background job) there i

my program have some error when i run result alv show in report but when see in spool (after run background job) there is no data, (other program can see result in spool)
Please help
here is some example of my program
********************************declare internal table*****************************
internal table output for BDC
data : begin of t_output occurs 0,
bukrs type anla-bukrs,
anln1 type anla-anln1,
anln2 type anla-anln2,
zugdt type anla-zugdt,
result(70) type c,
end of t_output.
*****get data from loop********************************
loop at t_anla.
    CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
         EXPORTING
              INPUT = t_anla-anln1
         IMPORTING
              OUTPUT = t_anla-anln1.
    CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
         EXPORTING
              INPUT = t_anla-anln2
         IMPORTING
              OUTPUT = t_anla-anln2.
check record is correct or not
    select single bukrs anln1 anln2 zugdt
    into w_output
    from anla
    where bukrs = t_anla-bukrs and
    anln1 = t_anla-anln1 and
    anln2 = t_anla-anln2
   zugdt = '00000000'
if record is correct
    if sy-subrc = 0 and w_output-zugdt = '00000000'.
      w_output-bukrs = t_anla-bukrs.
      w_output-anln1 = t_anla-anln1.
      w_output-anln2 = t_anla-anln2.
      w_output-result = 'Yes : this asset can delete'.
      append w_output to t_output.
if record is not correct
    elseif sy-subrc = 0 and w_output-zugdt <> '00000000'.
there is error record this asset have value already
      v_have_error = 'X'.
      w_output-bukrs = t_anla-bukrs.
      w_output-anln1 = t_anla-anln1.
      w_output-anln2 = t_anla-anln2.
      w_output-result = 'Error : this asset have value already'.
      append w_output to t_output.
    else.
there is error record this asset donot exist in table anla
      v_have_error = 'X'.
      w_output-bukrs = t_anla-bukrs.
      w_output-anln1 = t_anla-anln1.
      w_output-anln2 = t_anla-anln2.
      w_output-result = 'Error : this asset doest not exist'.
      append w_output to t_output.
    endif.
*end of check record is correct or not
    clear w_output.
endloop.
******************************show data in ALV***************************************************
show data from file in ALV
perform display_report_ALV.
*&      Form display_report_ALV
form display_report_ALV.
DATA: LT_FIELD_CAT TYPE SLIS_T_FIELDCAT_ALV,
      LT_EVENTS TYPE SLIS_T_EVENT,
      LV_REPID LIKE SY-REPID.
PERFORM ALV_DEFINE_FIELD_CAT USING LT_FIELD_CAT.
PERFORM ALV_HEADER_BUILD USING T_LIST_TOP_OF_PAGE[].
PERFORM ALV_EVENTTAB_BUILD USING LT_EVENTS[].
LV_REPID = SY-REPID.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
       EXPORTING
            I_CALLBACK_PROGRAM = LV_REPID
            IT_FIELDCAT        = LT_FIELD_CAT
            I_SAVE             = 'A'
            IT_EVENTS          = LT_EVENTS[]
       TABLES
            T_OUTTAB           = t_output
       EXCEPTIONS
            PROGRAM_ERROR      = 1
            OTHERS             = 2.
IF SY-SUBRC NE 0.
    WRITE: / 'Return Code : ', SY-SUBRC,
      'from FUNCTION REUSE_ALV_GRID_DISPLAY'.
ENDIF.
endform.
*&      Form alv_define_field_cat
      text
     -->P_LT_FIELD_CAT text
FORM ALV_DEFINE_FIELD_CAT USING TB_FCAT TYPE SLIS_T_FIELDCAT_ALV.
DATA: WA_FIELDCAT LIKE LINE OF TB_FCAT,
    LV_COL_POS TYPE I.
DEFINE FIELD_CAT.
    CLEAR WA_FIELDCAT.
    ADD 1 TO LV_COL_POS.
    WA_FIELDCAT-FIELDNAME = &1.
    WA_FIELDCAT-REF_TABNAME = &2.
    WA_FIELDCAT-COL_POS = LV_COL_POS.
    WA_FIELDCAT-KEY = &3.
    WA_FIELDCAT-NO_OUT = &4.
    WA_FIELDCAT-REF_FIELDNAME = &5.
    WA_FIELDCAT-DDICTXT = 'M'.
    IF NOT &6 IS INITIAL.
      WA_FIELDCAT-SELTEXT_L = &6.
      WA_FIELDCAT-SELTEXT_M = &6.
      WA_FIELDCAT-SELTEXT_S = &6.
    ENDIF.
    WA_FIELDCAT-DO_SUM = &7.
    WA_FIELDCAT-OUTPUTLEN = &8.
    APPEND WA_FIELDCAT TO TB_FCAT.
END-OF-DEFINITION.
FIELD_CAT 'BUKRS' 'ANLA'     'X' '' 'BUKRS' 'Company Code' '' ''.
FIELD_CAT 'ANLN1' 'ANLA'     'X' '' 'ANLN1' 'Asset Number' '' ''.
FIELD_CAT 'ANLN2' 'ANLA'     'X' '' 'ANLN2' 'Asset Sub Number' '' ''.
FIELD_CAT 'ATEXT'   'T5EAE'     'X' '' 'ATEXT' 'Result' '' ''.
FIELD_CAT 'RESULT' ''     'X' '' 'RESULT' 'RESULT' '' ''.
ENDFORM.                    " alv_define_field_cat

Hi,
Check this code..
FORM display_report_alv.
DATA: lt_field_cat TYPE slis_t_fieldcat_alv,
lt_events TYPE slis_t_event,
lv_repid LIKE sy-repid.
PERFORM alv_define_field_cat USING lt_field_cat.
PERFORM alv_header_build USING t_list_top_of_page[].
PERFORM alv_eventtab_build USING lt_events[].
lv_repid = sy-repid.
IF sy-batch EQ 'X'. ----> " System Field for Backgroud..if Background use list display
    CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'
      EXPORTING
        i_callback_program = lv_repid
        it_fieldcat        = lt_field_cat
        i_save             = 'A'
        it_events          = lt_events[]
      TABLES
        t_outtab           = t_output
      EXCEPTIONS
        program_error      = 1
        OTHERS             = 2.
ELSE.
    CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
      EXPORTING
        i_callback_program = lv_repid
        it_fieldcat        = lt_field_cat
        i_save             = 'A'
        it_events          = lt_events[]
      TABLES
        t_outtab           = t_output
      EXCEPTIONS
        program_error      = 1
        OTHERS             = 2.
ENDIF.
IF sy-subrc NE 0.
    WRITE: / 'Return Code : ', sy-subrc,
    'from FUNCTION REUSE_ALV_GRID_DISPLAY'.
ENDIF.
ENDFORM.                    "display_report_ALV

How to schedule the background job using current selection screen field val

Hello Friends,
How to schedule the background job using current selection screen field values.
after completion of the job the spool should be sent as a mail to SAP Inbox.
Is there any way to create the variant dynamically by reading the current selection screen values.
Thanks,
Ravi

Hi,
To get the variant details you can use teh following FM.
'RS_VARIANT_CONTENTS'.
Regards,
Ankur Parab

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.

Send/export the background job spool in Excel (in MHTML format) in ECC 6.0.

Hello All,
I have a requirement to send/export the background job spool in Excel (in MHTML format) in ECC 6.0. Please help.
Thank you.
Nalini

Hi Jigar,
Thanks for your response.
Anything is like download to desktop or email is fine. But in MHTML format.
We can download the ALV report in MHTML spreadsheet format when we run the program online. But the program is running for long time and going to dump.
So i scheduled it as background job and downloading the output in .HTML format. But user wants the spool/report output in .MHTML spreadsheet format.
I can write the code. Instead of changing the existing program I would like to know is there any way (from standard SAP) that I can get the background spool in MHTML spreadsheet format.
Thanks,
Nalini

Copying the background job

Hi,
I have a background job with has a start condition after execution of a particular event.
Now i need to copy this background job to another name and execute it. I tried using the function module BP_JOB_COPY, but that copied the background job without the job start conditions. How can i copy the background job along with start conditions.
Thank you in anticipation.

Hi Nikhil,
the follwoing code schedules 2 jobs from a source job (which is maintaned in the system).
data: s_tbtcjob1 like tbtcjob,         "target job #1"
      s_tbtcjob2 like tbtcjob.         "target job #1"
data: h_1 like tbtco-jobcount,         "jobcount"
      h_2 like tbtco-jobcount,         "jobcount"
      h_1s like tbtco-jobname,         "jobname source"
      h_2s like tbtco-jobname,         "jobname source"
      h_1t like tbtco-jobname,         "jobname target"
      h_2t like tbtco-jobname.         "jobname target"
selection-screen begin of line.
selection-screen position 2.
parameters ra radiobutton group rad1.
selection-screen comment 4(70) text-001.
selection-screen end of line.
selection-screen begin of block block1 with frame.
parameters: p_a1 like h_1,
            p_a1s like h_1s,
            p_a1t like h_1t,
            p_a2 like h_2,
            p_a2s like h_2s,
            p_a2t like h_2t.
selection-screen end of block block1.
start-of-selection.
perform create_jobs using p_a1 p_a1s p_a1t p_a2 p_a2s p_a2t.
*       FORM CREATE_JOBS                                              *
form create_jobs using h_1 h_1s h_1t h_2 h_2s h_2t.
call function 'BP_JOB_COPY'
       exporting
            dialog                  = 'N'
            source_jobcount         = h_1
            source_jobname          = h_1s
            target_jobname          = h_1t
       importing
            new_jobhead             = s_tbtcjob1
       exceptions
            cant_create_new_job     = 1
            cant_enq_job            = 2
            cant_read_sourcedata    = 3
            invalid_opcode          = 4
            jobname_missing         = 5
            job_copy_canceled       = 6
            no_copy_privilege_given = 7
            no_plan_privilege_given = 8
            others                  = 9.
call function 'BP_JOB_COPY'
       exporting
            dialog                  = 'N'
            source_jobcount         = h_2
            source_jobname          = h_2s
            target_jobname          = h_2t
       importing
            new_jobhead             = s_tbtcjob2
       exceptions
            cant_create_new_job     = 1
            cant_enq_job            = 2
            cant_read_sourcedata    = 3
            invalid_opcode          = 4
            jobname_missing         = 5
            job_copy_canceled       = 6
            no_copy_privilege_given = 7
            no_plan_privilege_given = 8
            others                  = 9.
call function 'JOB_CLOSE'
       exporting
            jobcount                    = s_tbtcjob2-jobcount
            jobname                     = s_tbtcjob2-jobname
            pred_jobcount               = s_tbtcjob1-jobcount
            pred_jobname                = s_tbtcjob1-jobname
          targetsystem                = '<<SYSTEM IN CASE OF MULTIPLE SERVERS>>'
       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.
call function 'JOB_CLOSE'
       exporting
            jobcount                    = s_tbtcjob1-jobcount
            jobname                     = s_tbtcjob1-jobname
            strtimmed                   = 'X'
          targetsystem                = '<<SYSTEM IN CASE OF MULTIPLE SERVERS>>'
       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.
endform.

The background job "SM:EXEC SERVICES" is ending Green in Just 0 seconds

Solution Manager 4.0
In our customer system the background job "SM:EXEC SERVICES" is ending Green in Just 0 seconds or just 1 second.
Here is the log:
Job log overview for job:    SM:EXEC SERVICES 000000046740000 / 12193100
Date       Time     Message text                                                                               Message class Message no. Message type
28.04.2009 12:19:31 Job started                                                                                00           516          S
28.04.2009 12:19:31 Step 001 started (program RDSMOPBACK_AUTOSESSIONS, variant &0000000001054, user ID BJ8099)      00           550          S
28.04.2009 12:19:32 RDSMOPBACK_AUTOSESSIONS : MemSize Begin = 1374064                                              DSWP          000          I
28.04.2009 12:19:32 Solution Enterprice Portal(GGP) is being edited (Operations)                                   DSWP          438          I
28.04.2009 12:19:32 RDSMOPBACK_AUTOSESSIONS : MemSize End = 20902480                                               DSWP          000          I
28.04.2009 12:19:32 Job finished                                                                                00           517          S
Due to this EWA reports are not being generated.
What could be the reason that the Job ends immediately with no significant warnings or error in the log?
Many thanks in advance,
Manoj

Hi Manoj
Following Notes will be helpful to you to analyze the problem
Note 894279 - Background processing in SAP Solution Manager
Note 1246329 - RDSMOPBACK_AUTOSESSIONS: Additional displays
Note 1163920 - SM:Scheduler: Improved display in job log
Note 946607 - Automatic diagnosis in SAP Solution Manager
SAP Note 727998 "Complete Replacement of Service Definitions for SDCC/SDCCN"
Note 986973 - How to analyze problems with EarlyWatch Alerts in SolMan
however, is this problem occurring for sessions of ALL the systems today, if yes, then something wrong only in solman, last note of the above shows you to manually run the job interactively, may be will help in analyzing and i hope SDCCN settings in Solman are already fine..
thanks
Bhudev

Afer background job finished, spool was not generated

hi all
Afer background job finished, spool was not generated but all background jobs is not
soem background jobs was created spool.
even if same user and same backgorund job, sometime generated spool or not.
how can I solve??
thanks

Hi,
Spool will be generated only spool specification wil be defined for that job.
Select the job go to steps spool specification you can see the device assigned to it.
Regards
Ashok

Output after the background job finished successfully

Similar Messages

Maybe you are looking for