CC Management Reports background job- no results

I am conducting testing in CC and as part of that I have run the the background job to update Management Reports. The reports were already populated for September. I made changes to users in October and have run the job to populate the report today 4th October. The job is showing that it has completed successfully but when I go to run the risk Violation report for October, 10/2007 is not appearing in the month/year field. Does anybody know why October values are not displaying?

You need to run the Incremental Updates first, one at a time starting with Users and then roles & profiles.  Make sure that Users has completed before starting the Roles and profile jobs otherwise they can crash.
When these increments have completed, start running the Risk Analsysis increments jobs again 1 by 1, that way if you have any issues you do dnot lose the whole batch run, only one element.
Only after the risk analyses have completed do you start the Management Report job.
Please note that some of these jobs could take over 24hrs to complete.
Also it is best to log off anf on once the management report job has completed to see the updates.

Similar Messages

  • RA&R Management Reports displaying 1 day behind

    Hi forum guru's.
    I am having an issue with the Risk Violations Management view on RA&R (i.e. the default screen after you log into RA&R). On the management view on the right hand side, the date "Summary as of" is always a day behind.  I need this date to be current.
    The daily management report background jobs run at 5:00am each day and the jobs complete successfully with no errors.  The server date and time is correct as well.  Has anbody experienced something similar?
    We are on AC5.3, SP10.
    Rgds,
    Prevo.

    Hello Gurus,
    I am new to GRC, I have to create a background job for RA&R daily  Management Reports. I have created a background job by going to Risk Analysis>user level->Risk level>Critical>Report Format>Management summary>clicking on Background>setting the backgorund job for daily.
    But the background is failing to display the report. I ran in the foreground and it works fine.
    Please let me know if I am doing anything wrong in the steps..
    Thank you!
    Regard's,
    SA

  • 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

  • JOB_OPEN, SUBMIT REPORT VIA JOB, JOB_CLOSE, How to get result?

    Hi Friends,
    I am calling reports using jobs as calling job_open, submit report via job.., and job_close. But I want to the output/result of the report. How can I do this?
    Thanks.

    Hello nkara,
    Welcome to SDN!!!
    Check this thread:
    background grid
    REgards,
    Vasanth

  • SM:SELFDIAGNOSIS background job getting failed in Solution manager

    Hi All,
    SM:SELFDIAGNOSIS background job getting failed in Solution manger server :
    Job Log:
    2-22-2012 16:44:02 Job started                                                                                00           516          S
    2-22-2012 16:44:02 Step 001 started (program RDSWP_SELF_DIAGNOSIS, variant &0000000000324, user ID BASISUSER)      00           550          S
    2-22-2012 16:45:07 Internal session terminated with a runtime error (see ST22)                                     00           671          A
    2-22-2012 16:45:07 Job cancelled                                                                                00           518          A
    ST22: Dump:
    Runtime Errors         ITAB_DUPLICATE_KEY
    Date and Time          02-22-2012 16:45:07
    Short text
    A row with the same key already exists.
    What happened?
    Error in the ABAP Application Program
    The current ABAP program "CL_DSWP_SD_DIAGNOSE_CONSISTENTCP" had to be
    terminated because it has
    come across a statement that unfortunately cannot be executed.
    What can you do?
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
    Error analysis
    An entry was to be entered into the table
    "\CLASS=CL_DSWP_SD_DIAGNOSE_CONSISTENT\METHOD=CHECK_USERS_BP\DATA=LT_USCP"
    (which should have
    had a unique table key (UNIQUE KEY)).
    However, there already existed a line with an identical key.
    The insert-operation could have ocurred as a result of an INSERT- or
    MOVE command, or in conjunction with a SELECT ... INTO.
    The statement "INSERT INITIAL LINE ..." cannot be used to insert several
    initial lines into a table with a unique key.
    How to correct the error
    Probably the only way to eliminate the error is to correct the program.
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "ITAB_DUPLICATE_KEY" " "
    "CL_DSWP_SD_DIAGNOSE_CONSISTENTCP" or "CL_DSWP_SD_DIAGNOSE_CONSISTENTCM00M"
    "CHECK_USERS_BP"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
    To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
    Display the system log by calling transaction SM21.
    Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
    In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
    4. Details about the conditions under which the error occurred or which
    actions and input led to the error.
    KIndly Suggest to resolve the above issue
    Thanks
    Nekkalapu

    HI,
    Deatils:
    SAP EHP 1 for SAP Solution Manager 7.0
    SAP_ABA                701          0006    SAPKA70106
    SAP_BASIS              701          0006    SAPKB70106
    PI_BASIS               701          0006    SAPK-70106INPIBASI
    ST-PI                  2008_1_700   0002    SAPKITLRD2
    CRMUIF                 500          0004    SAPK-50004INCRMUIF
    SAP_BW                 701          0006    SAPKW70106
    SAP_AP                 700          0019    SAPKNA7019
    BBPCRM                 500          0016    SAPKU50016
    BI_CONT                704          0007    SAPK-70407INBICONT
    CPRXRPM                400          0016    SAPK-40016INCPRXRP
    ST                     400          0024    SAPKITL434
    ST-A/PI                01M_CRM570   0000         -
    ST-ICO                 150_700      0009    SAPK-15079INSTPL
    ST-SER                 701_2010_1   0002    SAPKITLOS2
    Thanks
    Nekkalapu

  • Background Job result output should be displayed in Email body

    Hi Friends,
    One of our user is scheduling background job, He need the output to his external Email ID.
    user required that Job result output should be displayed in Email body, Not in attachment.
    We have tried but job result received in email as HTML (or) PDF file attachment, But he wants output  in Email body itself.
    Please help.
    Regards,
    Karthickbabu G.G

    Hi,
    Displaying report output in email body is not available as a standard feature. Also doing a custom development would be very cumbersome .
    Regards,
    Deepak Kori

  • Background job failing - ECC 6.0, Solution Manager 7.0

    Dear All,
    Four days back, I have installed the Solution Manager 7.0 and ECC 6.0 on
    HPUX IA64 hardware with database as Oracle 10.2.0.2.0 (Unicode).
    In both server, latest kernel patch has been applied.
    The Support package versions are (both server):
    KERNEL (Release 700)      146
    SAP_BASIS           0014
    SAP_ABA           0014
    PI_BASIS(2005_1_700)      0014
    ST-PI                0005
    SAP_BW                0016
    While checking the the jobs from SM37, in both the server,
    I am observing that following jobs are always failing with
    same reason:
    SAP_COLLECTOR_FOR_PERFMONITOR
    =============================
    Date       Time     Message text                                                           Message class Message no. Message type
    ========== ======== ====================================================================== ============= =========== ============
    15.05.2008 06:25:12 Job started                                                                 00           516          S
    15.05.2008 06:25:12 Step 001 started (program RSCOLL00, variant , user ID BGDUSER)              00           550          S
    15.05.2008 06:25:18 Clean_Plan:Cleanup of DB13 Plannings                                       DB6PM         000          S
    15.05.2008 06:25:18 Clean_Plan:started by RSDBPREV                       on server gcbeccd     DB6PM         000          S
    15.05.2008 06:25:18 Clean_Plan:Cleaning up jobs of system RD3                                  DB6PM         000          S
    15.05.2008 06:25:18 Clean_Plan:finished                                                        DB6PM         000          S
    15.05.2008 06:25:18 Database system not supported                                               S1           101          S
    15.05.2008 06:25:36 ABAP/4 processor: DBIF_DSQL2_SQL_ERROR                                      00           671          A
    15.05.2008 06:25:36 Job cancelled                                                               00           518          A
    SAP_REORG_UPDATERECORDS
    =======================
    Date       Time     Message text                                                          Message class Message no. Message type
    ========== ======== ===================================================================== ============= =========== ============
    14.05.2008 00:31:01 Job started                                                                00           516          S
    14.05.2008 00:31:01 Step 001 started (program RSM13002, variant SAP&001, user ID BGDUSER)      00           550          S
    14.05.2008 00:31:01 Reorganization of update date not allowed in batch                         15           100          A
    14.05.2008 00:31:02 Job cancelled                                                              00           518          A
    SAP_WP_CACHE_RELOAD_FULL
    ========================
    Date       Time     Message text                                                                                Message class Message no. Message type
    ========== ======== ============================================================================================ ============= =========== ============
    15.05.2008 00:30:11 Job started                                                                                00           516          S
    15.05.2008 00:30:11 Step 001 started (program RWP_RUNTIME_CACHE_RELOAD, variant SAP&RELOAD_ALL, user ID BGDUSER)      00           550          S
    15.05.2008 00:30:11 No component system chosen                                                                   URL_GEN_MSGS      031          E
    15.05.2008 00:30:11 Job cancelled after system exception ERROR_MESSAGE                                                00           564          A
    Please help to resolve this issue.
    Thanks in advance.
    Regards
    Sudip Ghosh

    Hi Markus,
    Thanks for the reply.
    Below is the dump:
    ======
    ======
    Runtime Errors         DBIF_DSQL2_SQL_ERROR
    Date and Time          15.05.2008 06:25:36
    Short text
    An SQL error occurred when executing Native SQL.
    What happened?
    The error 3113 occurred in the current database connection "DEFAULT".
    What can you do?
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
    How to correct the error
    Database error text........: "ORA-03113: end-of-file on communication channel"
    Database error code........: 3113
    Triggering SQL statement...: "FETCH NEXT "
    Internal call code.........: "[DBDS/NEW DSQL]"
    Please check the entries in the system log (Transaction SM21).
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "DBIF_DSQL2_SQL_ERROR" " "
    "RSORAVSH" or "RSORAVSH"
    "FILL_DBVSE"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
    To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
    Display the system log by calling transaction SM21.
    Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
    In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
    4. Details about the conditions under which the error occurred or which
    actions and input led to the error.
    System environment
    SAP-Release 700
    Application server... "gcbeccd"
    Network address...... "10.10.4.158"
    Operating system..... "HP-UX"
    Release.............. "B.11.23"
    Hardware type........ "ia64"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 15
    Shortdump setting.... "full"
    Database server... "gcbeccd"
    Database type..... "ORACLE"
    Database name..... "RD3"
    Database user ID.. "SAPSR3"
    Char.set.... "C"
    SAP kernel....... 700
    created (date)... "Apr 5 2008 00:55:24"
    create on........ "HP-UX B.11.23 U ia64"
    Database version. "OCI_102 (10.2.0.1.0) "
    Patch level. 146
    Patch text.. " "
    Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
    SAP database version. 700
    Operating system..... "HP-UX B.11"
    Memory consumption
    Roll.... 1117216
    EM...... 0
    Heap.... 0
    Page.... 32768
    MM Used. 695792
    MM Free. 400816
    User and Transaction
    Client.............. 000
    User................ "BGDUSER"
    Language key........ "E"
    Transaction......... " "
    Transactions ID..... "482B8A4C89F0442BE10000000A0A049E"
    Program............. "RSORAVSH"
    Screen.............. "SAPMSSY0 1000"
    Screen line......... 6
    Information on where terminated
    Termination occurred in the ABAP program "RSORAVSH" - in "FILL_DBVSE".
    The main program was "RSORAVSH ".
    In the source code you have the termination point in line 48
    of the (Include) program "RSORAVSH".
    The program "RSORAVSH" was started as a background job.
    Job Name....... "SAP_COLLECTOR_FOR_PERFMONITOR"
    Job Initiator.. "BGDUSER"
    Job Number..... 05251100
    Source Code Extract
    Line
    SourceCde
    18
    INCLUDE STRUCTURE v_system_event_struc.
    19
    DATA:  END OF v_system_event_tab .
    20
    21
    check sy-dbsys(3) = 'ORA' .
    22
    23
    Get the new snapshots
    24
    25
    PERFORM fill_dbvse TABLES v_system_event_tab.
    26
    27
    28
    Get the old snapshots from database table MONI
    29
    30
    startday = sy-datum - days_to_keep .
    31
    32
    33
    Save new data now (otherwise these data will be selected twice)
    34
    35
    CONCATENATE 'SYSEVENT' sy-datum sy-uzeit INTO   monikey .
    36
    37
    EXPORT sy-datum
    38
    sy-uzeit
    39
    v_system_event_tab
    40
    TO DATABASE moni(db) ID monikey .
    41
    42
    *&      Form  FILL_DBVSE
    43
    44
    FORM fill_dbvse TABLES v_system_event_tab.
    45
    date =  sy-datum .
    46
    time =  sy-uzeit .
    47
    EXEC sql performing append_v_system_event .
    >>>>>
    select event,
    49
    total_waits,
    50
    total_timeouts,
    51
    time_waited * 10,
    52
    average_wait * 10
    53
    into :v_system_event_struc
    54
    from v$system_event
    55
    ENDEXEC .
    56
    ENDFORM.                               " FILL_DBVSE
    57
    58
    59
    *&      Form  APPEND_V_SYSTEM_EVENT
    60
    61
    FORM append_v_system_event.
    62
    v_system_event_tab-date  = date .
    63
    v_system_event_tab-time  = time .
    64
    65
    MOVE-CORRESPONDING v_system_event_struc TO v_system_event_tab.
    66
    APPEND v_system_event_tab .
    67
    ENDFORM.                               " APPEND_V_SYSTEM_EVENT
    Contents of system fields
    Name
    Val.
    SY-SUBRC
    0
    SY-INDEX
    0
    SY-TABIX
    16
    SY-DBCNT
    0
    SY-FDPOS
    0
    SY-LSIND
    0
    SY-PAGNO
    0
    SY-LINNO
    1
    SY-COLNO
    1
    SY-PFKEY
    SY-UCOMM
    SY-TITLE
    Report for Collecting Data from V$SYSTEM_EVENT Hourly
    SY-MSGTY
    SY-MSGID
    SY-MSGNO
    000
    SY-MSGV1
    SY-MSGV2
    SY-MSGV3
    SY-MSGV4
    SY-MODNO
    0
    SY-DATUM
    20080515
    SY-UZEIT
    062520
    SY-XPROG
    RSDBRUNT
    SY-XFORM
    %_INIT_PBO_FIRST
    Active Calls/Events
    No.   Ty.          Program                             Include                             Line
    Name
    2 FORM         RSORAVSH                            RSORAVSH                               48
    FILL_DBVSE
    1 EVENT        RSORAVSH                            RSORAVSH                               25
    START-OF-SELECTION
    Chosen variables
    Name
    Val.
    No.       2 Ty.          FORM
    Name  FILL_DBVSE
    SY-REPID
    RSORAVSH
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    5545455422222222222222222222222222222222
    23F2163800000000000000000000000000000000
    V_SYSTEM_EVENT_STRUC
    00000000000000000000000000000000000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000000000000000000000000000000000
    22222222222222222222222222222222222222222222222222222222222222220000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000C000C000C000C
    %_SPACE
    0
    0
    2
    0
    SY
    ###############################################################################T########  ####
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000004000000
    000000000000000000000000000000000000000100000000000000000000000000000000000000000000000D000400
    000001000000000000000000000000000000000F000000000000000000000000000000000000010500000005220000
    000000000000000000000000010001000000000E00000000000000000000000000000000000006040000000800000C
    No.       1 Ty.          EVENT
    Name  START-OF-SELECTION
    SY-LDBPG
    SAPDB__S
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    5454455522222222222222222222222222222222
    31042FF300000000000000000000000000000000
    %_DUMMY$$
    0000
    0000
    2222
    0000
    SY-DBSYS+0(6)
    ORA
    000
    000
    454
    F21
    SYST
    ###############################################################################T########  ####
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000004000000
    000000000000000000000000000000000000000100000000000000000000000000000000000000000000000D000400
    000001000000000000000000000000000000000F000000000000000000000000000000000000010500000005220000
    000000000000000000000000010001000000000E00000000000000000000000000000000000006040000000800000C
    V_SYSTEM_EVENT_TAB[]
    Table[initial]
    V_SYSTEM_EVENT_TAB
    00000000000000                                                                ################
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    3333333333333322222222222222222222222222222222222222222222222222222222222222220000000000000000
    000000000000000000000000000000000000000000000000000000000000000000000000000000000C000C000C000C
    SY-DATUM
    20080515
    00000000
    00000000
    33333333
    20080515
    DAYS_TO_KEEP
    30
    0001
    000E
    STARTDAY
    00000000
    00000000
    00000000
    33333333
    00000000
    MONIKEY
    0000000000000000000000
    0000000000000000000000
    2222222222222222222222
    0000000000000000000000
    SY-UZEIT
    062520
    000000
    000000
    333333
    062520
    SYST-REPID
    RSORAVSH
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    5545455422222222222222222222222222222222
    23F2163800000000000000000000000000000000
    MONI-CLUSTR
    0
    00
    00
    MONI
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    2222222222222222222222220022000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    Internal notes
    The termination was triggered in function "ExecuteCall"
    of the SAP kernel, in line 1190 of the module
    "//bas/700_REL/src/krn/runt/abexsql.c#2".
    The internal operation just processed is "DSQL".
    Internal mode was started at 20080515062520.
    Internal call code.........: "[DBDS/NEW DSQL]"
    Active Calls in SAP Kernel
    Lines of C Stack in Kernel (Structure Differs on Each Platform)
    (0)  0x4000000003b2b450  CTrcStack + 0x1b0 at dptstack.c:227 [dw.sapRD3_DVEBMGS00]
    (1)  0x4000000004d2c470  Z16rabaxCStackSavev + 0x1d0 [dw.sapRD3_DVEBMGS00]
    (2)  0x4000000004d32160  ab_rabax + 0x3570 [dw.sapRD3_DVEBMGS00]
    (3)  0x40000000047b51e0  Z10abdbdserriPKtiS0_P9DS_HEADERS0_iPv + 0x470 [dw.sapRD3_DVEBMGS00]
    (4)  0x4000000003d777f0  Z11ExecuteCallv + 0x11f0 [dw.sapRD3DVEBMGS00]
    (5)  0x4000000003d7e7b0  Z8abjdsqlv + 0x1b0 [dw.sapRD3_DVEBMGS00]
    (6)  0x400000000402f190  Z8abextriv + 0x440 [dw.sapRD3_DVEBMGS00]
    (7)  0x4000000003f53bc0  Z9abxeventPKt + 0x3c0 at abrunt1.c:339 [dw.sapRD3_DVEBMGS00]
    (8)  0x4000000003d9f210  Z8abtriggv + 0x110 at abrunt1.c:58 [dw.sapRD3_DVEBMGS00]
    (9)  0x4000000003d9ebe0  ab_run + 0xc0 [dw.sapRD3_DVEBMGS00]
    (10) 0x4000000001caa820  N_ab_run + 0x20 at dymainstp.c:4739 [dw.sapRD3_DVEBMGS00]
    (11) 0x4000000001cb40f0  dynpmcal + 0x3f0 at dymainstp.c:2281 [dw.sapRD3_DVEBMGS00]
    (12) 0x4000000001caf260  dynppai0 + 0xcb0 at dymainstp.c:1107 [dw.sapRD3_DVEBMGS00]
    (13) 0x4000000001cb1ec0  dynprctl + 0x340 at dymainstp.c:358 [dw.sapRD3_DVEBMGS00]
    (14) 0x4000000001c9dff0  dynpen00 + 0xac0 at dymain.c:1628 [dw.sapRD3_DVEBMGS00]
    (15) 0x4000000001fea460  Thdynpen00 + 0x510 at thxxhead.c:4830 [dw.sapRD3_DVEBMGS00]
    (16) 0x4000000001fb54e0  TskhLoop + 0x5520 at thxxhead.c:3945 [dw.sapRD3_DVEBMGS00]
    (17) 0x4000000001faae40  ThStart + 0x460 at thxxhead.c:1164 [dw.sapRD3_DVEBMGS00]
    (18) 0x4000000001569ec0  DpMain + 0x5f0 at dpxxdisp.c:1088 [dw.sapRD3_DVEBMGS00]
    (19) 0x4000000002c10630  nlsui_main + 0x30 [dw.sapRD3_DVEBMGS00]
    (20) 0x4000000002c105c0  main + 0x60 [dw.sapRD3_DVEBMGS00]
    (21) 0xc00000000002be30  main_opd_entry + 0x50 [/usr/lib/hpux64/dld.so]
    List of ABAP programs affected
    Index
    Typ
    Program
    Group
    Date
    Time
    Size
    Lang.
    0
    Prg
    RSORAVSH
    0
    30.03.2005
    10:21:59
    19456
    E
    1
    Prg
    SAPMSSY0
    1
    17.12.2007
    15:41:05
    92160
    E
    2
    Prg
    SAPMSSYD
    1
    12.09.2006
    11:33:31
    21504
    E
    3
    Prg
    SAPFSYSCALLS
    1
    09.09.2004
    14:18:32
    8192
    E
    4
    Prg
    RSDBRUNT
    0
    17.12.2007
    16:04:40
    254976
    E
    5
    Typ
    RSSCR
    0
    30.03.2005
    10:21:45
    5120
    6
    Prg
    RSDBSPBL
    0
    30.03.2005
    10:21:58
    72704
    E
    7
    Prg
    SAPDB__S
    0
    30.03.2005
    10:22:01
    19456
    E
    8
    Prg
    RSDBSPMC
    0
    12.09.2006
    11:25:01
    79872
    E
    9
    Typ
    DDSHDESCR
    0
    03.09.1997
    03:05:16
    4096
    10
    Typ
    SPPARAMS
    0
    07.05.1997
    13:10:38
    2048
    11
    Prg
    SAPLSABE
    11
    09.09.2004
    14:18:36
    13312
    E
    12
    Prg
    SAPLSECU
    12
    17.12.2007
    15:31:45
    87040
    E
    13
    Typ
    RSSUBINFO
    0
    14.10.1999
    22:01:03
    3072
    14
    Prg
    SAPLSTUP
    14
    17.12.2007
    15:29:58
    74752
    E
    15
    Prg
    SAPLCNDP
    15
    11.09.2007
    15:24:45
    195584
    E
    16
    Prg
    SAPLSCNT
    16
    18.02.2005
    14:16:06
    30720
    E
    17
    Prg
    SAPSHDTV
    16
    05.01.2005
    16:26:16
    33792
    E
    18
    Prg
    SAPFGUICNTL
    1
    18.02.2005
    14:15:08
    24576
    E
    19
    Prg
    SAPLOLEA
    19
    11.09.2007
    11:17:30
    96256
    E
    20
    Prg
    SAPLSGUI
    20
    17.12.2007
    15:41:05
    84992
    E
    21
    Prg
    SAPLSTTM
    21
    05.07.2005
    13:10:18
    69632
    E
    22
    Prg
    SAPLSBDC
    22
    17.12.2007
    15:30:54
    44032
    E
    23
    Prg
    SAPLSFES
    23
    17.12.2007
    16:04:40
    260096
    E
    24
    Prg
    SAPLTHFB
    24
    17.12.2007
    15:41:05
    394240
    E
    25
    Typ
    WPINFO
    0
    26.02.1999
    14:49:01
    6144
    26
    Prg
    SAPLURFC
    26
    17.12.2007
    15:37:35
    22528
    E
    27
    Prg
    SAPLSPLUGIN
    27
    09.09.2004
    14:18:36
    8192
    E
    28
    Typ
    SWCBCONT
    0
    15.11.2000
    17:55:11
    3072
    29
    Typ
    OLE_VERBS
    0
    04.04.1995
    16:02:20
    2048
    30
    Typ
    OLE_PA
    0
    04.04.1995
    16:02:19
    2048
    31
    Typ
    SYST
    0
    09.09.2004
    14:18:12
    31744
    32
    Typ
    MONI
    0
    31.03.2004
    16:41:21
    5120
    Directory of Application Tables
    Name                                     Date       Time       Lngth
    Val.
    Program  RSORAVSH
    SYST                                     09.09.2004 14:18:12   00004612
    \0\0\0\0\0\x0010\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0
    MONI                                       .  .       :  :     00002944
    \0\0  \0\0\0\0\0\0\0\0\0\0\0\0\0\0
    ABAP Control Blocks (CONT)
    Index
    Name
    Fl
    PAR0
    PAR1
    PAR2
    PAR3
    PAR4
    PAR5
    PAR6
    Source Code
    Line
    71
    PAR2
    03
    0000
    0014
    002B
    RSORAVSH
    37
    73
    PAR2
    03
    0000
    0015
    002D
    RSORAVSH
    37
    75
    PAR2
    03
    0000
    0016
    0026
    RSORAVSH
    37
    77
    00
    0000
    RSORAVSH
    37
    78
    PERP
    00
    0002
    RSORAVSH
    44
    79
    PERP
    1C
    0000
    RSORAVSH
    44
    80
    PERP
    04
    0000
    RSORAVSH
    44
    81
    mvqk
    10
    0005
    0044
    04EC
    RSORAVSH
    45
    83
    mvqk
    0C
    0005
    0054
    052E
    RSORAVSH
    46
    85
    DSQL
    00
    0017
    RSORAVSH
    48
    86
    DSQL
    01
    0018
    RSORAVSH
    48
    87
    DSQL
    04
    0025
    RSORAVSH
    48
    >>>>>
    DSQL
    16
    0025
    RSORAVSH
    48
    89
    BRAN
    05
    0004
    RSORAVSH
    48
    90
    perf
    00
    000A
    RSORAVSH
    48
    91
    PERP
    80
    0000
    RSORAVSH
    48
    92
    BRAX
    00
    FFFC
    RSORAVSH
    48
    93
    DSQL
    23
    0000
    RSORAVSH
    48
    94
    ENDF
    00
    0000
    RSORAVSH
    56
    95
    00
    0000
    RSORAVSH
    56
    ===========
    ===========
    Please check and advise.
    Also, I am trying to search for the note 6083 in market place, but not getting the same.
    Please advise.
    Thanks & Regards
    Sudip

  • ALV reports emailed in background job

    Hi,
    we have a background job that emails a report to some users. So far so good but the emailed result is a (not very nicely formated) txt file. Is there any way to specify the format of the output so that the report is emailed as a pdf or an html or and excel spreadsheet? Any would do.
    Thanks in advance
    Tania

    hi tania,
    check this code mailing with XLS attachment.
    report zxxx.
    tables: ekko.
    parameters: p_email   type somlreci1-receiver
                                      default '[email protected]'.
    types: begin of t_ekpo,
      ebeln type ekpo-ebeln,
      ebelp type ekpo-ebelp,
      aedat type ekpo-aedat,
      matnr type ekpo-matnr,
    end of t_ekpo.
    data: it_ekpo type standard table of t_ekpo initial size 0,
          wa_ekpo type t_ekpo.
    types: begin of t_charekpo,
      ebeln(10) type c,
      ebelp(5)  type c,
      aedat(8)  type c,
      matnr(18) type c,
    end of t_charekpo.
    data: wa_charekpo type t_charekpo.
    data:   it_message type standard table of solisti1 initial size 0
                    with header line.
    data:   it_attach type standard table of solisti1 initial size 0
                    with header line.
    data:   t_packing_list like sopcklsti1 occurs 0 with header line,
            t_contents like solisti1 occurs 0 with header line,
            t_receivers like somlreci1 occurs 0 with header line,
            t_attachment like solisti1 occurs 0 with header line,
            t_object_header like solisti1 occurs 0 with header line,
            w_cnt type i,
            w_sent_all(1) type c,
            w_doc_data like sodocchgi1,
            gd_error    type sy-subrc,
            gd_reciever type sy-subrc.
    *START_OF_SELECTION
    start-of-selection.
      Retrieve sample data from table ekpo
      perform data_retrieval.
      Populate table with detaisl to be entered into .xls file
      perform build_xls_data_table.
    *END-OF-SELECTION
    end-of-selection.
    Populate message body text
      perform populate_email_message_body.
    Send file by email as .xls speadsheet
      perform send_file_as_email_attachment
                                   tables it_message
                                          it_attach
                                    using p_email
                                          'Example .xls documnet attachment'
                                          'XLS'
                                          'filename'
                                 changing gd_error
                                          gd_reciever.
      Instructs mail send program for SAPCONNECT to send email(rsconn01)
      perform initiate_mail_execute_program.
    *&      Form  DATA_RETRIEVAL
          Retrieve data form EKPO table and populate itab it_ekko
    form data_retrieval.
      select ebeln ebelp aedat matnr
       up to 10 rows
        from ekpo
        into table it_ekpo.
    endform.                    " DATA_RETRIEVAL
    *&      Form  BUILD_XLS_DATA_TABLE
          Build data table for .xls document
    form build_xls_data_table.
    CONSTANTS: con_cret TYPE x VALUE '0D',  "OK for non Unicode
                con_tab TYPE x VALUE '09'.   "OK for non Unicode
    *If you have Unicode check active in program attributes thnen you will
    *need to declare constants as follows
    *class cl_abap_char_utilities definition load.
    constants:
        con_tab  type c value cl_abap_char_utilities=>horizontal_tab,
        con_cret type c value cl_abap_char_utilities=>cr_lf.
      concatenate 'EBELN' 'EBELP' 'AEDAT' 'MATNR'
             into it_attach separated by con_tab.
      concatenate con_cret it_attach  into it_attach.
      append  it_attach.
      loop at it_ekpo into wa_charekpo.
        concatenate wa_charekpo-ebeln wa_charekpo-ebelp
                    wa_charekpo-aedat wa_charekpo-matnr
               into it_attach separated by con_tab.
        concatenate con_cret it_attach  into it_attach.
        append  it_attach.
      endloop.
    endform.                    " BUILD_XLS_DATA_TABLE
    *&      Form  SEND_FILE_AS_EMAIL_ATTACHMENT
          Send email
    form send_file_as_email_attachment tables pit_message
                                              pit_attach
                                        using p_email
                                              p_mtitle
                                              p_format
                                              p_filename
                                              p_attdescription
                                              p_sender_address
                                              p_sender_addres_type
                                     changing p_error
                                              p_reciever.
      data: ld_error    type sy-subrc,
            ld_reciever type sy-subrc,
            ld_mtitle like sodocchgi1-obj_descr,
            ld_email like  somlreci1-receiver,
            ld_format type  so_obj_tp ,
            ld_attdescription type  so_obj_nam ,
            ld_attfilename type  so_obj_des ,
            ld_sender_address like  soextreci1-receiver,
            ld_sender_address_type like  soextreci1-adr_typ,
            ld_receiver like  sy-subrc.
      ld_email   = p_email.
      ld_mtitle = p_mtitle.
      ld_format              = p_format.
      ld_attdescription      = p_attdescription.
      ld_attfilename         = p_filename.
      ld_sender_address      = p_sender_address.
      ld_sender_address_type = p_sender_addres_type.
    Fill the document data.
      w_doc_data-doc_size = 1.
    Populate the subject/generic message attributes
      w_doc_data-obj_langu = sy-langu.
      w_doc_data-obj_name  = 'SAPRPT'.
      w_doc_data-obj_descr = ld_mtitle .
      w_doc_data-sensitivty = 'F'.
    Fill the document data and get size of attachment
      clear w_doc_data.
      read table it_attach index w_cnt.
      w_doc_data-doc_size =
         ( w_cnt - 1 ) * 255 + strlen( it_attach ).
      w_doc_data-obj_langu  = sy-langu.
      w_doc_data-obj_name   = 'SAPRPT'.
      w_doc_data-obj_descr  = ld_mtitle.
      w_doc_data-sensitivty = 'F'.
      clear t_attachment.
      refresh t_attachment.
      t_attachment[] = pit_attach[].
    Describe the body of the message
      clear t_packing_list.
      refresh t_packing_list.
      t_packing_list-transf_bin = space.
      t_packing_list-head_start = 1.
      t_packing_list-head_num = 0.
      t_packing_list-body_start = 1.
      describe table it_message lines t_packing_list-body_num.
      t_packing_list-doc_type = 'RAW'.
      append t_packing_list.
    Create attachment notification
      t_packing_list-transf_bin = 'X'.
      t_packing_list-head_start = 1.
      t_packing_list-head_num   = 1.
      t_packing_list-body_start = 1.
      describe table t_attachment lines t_packing_list-body_num.
      t_packing_list-doc_type   =  ld_format.
      t_packing_list-obj_descr  =  ld_attdescription.
      t_packing_list-obj_name   =  ld_attfilename.
      t_packing_list-doc_size   =  t_packing_list-body_num * 255.
      append t_packing_list.
    Add the recipients email address
      clear t_receivers.
      refresh t_receivers.
      t_receivers-receiver = ld_email.
      t_receivers-rec_type = 'U'.
      t_receivers-com_type = 'INT'.
      t_receivers-notif_del = 'X'.
      t_receivers-notif_ndel = 'X'.
      append t_receivers.
      call function 'SO_DOCUMENT_SEND_API1'
           exporting
                document_data              = w_doc_data
                put_in_outbox              = 'X'
                sender_address             = ld_sender_address
                sender_address_type        = ld_sender_address_type
                commit_work                = 'X'
           importing
                sent_to_all                = w_sent_all
           tables
                packing_list               = t_packing_list
                contents_bin               = t_attachment
                contents_txt               = it_message
                receivers                  = t_receivers
           exceptions
                too_many_receivers         = 1
                document_not_sent          = 2
                document_type_not_exist    = 3
                operation_no_authorization = 4
                parameter_error            = 5
                x_error                    = 6
                enqueue_error              = 7
                others                     = 8.
    Populate zerror return code
      ld_error = sy-subrc.
    Populate zreceiver return code
      loop at t_receivers.
        ld_receiver = t_receivers-retrn_code.
      endloop.
    endform.
    *&      Form  INITIATE_MAIL_EXECUTE_PROGRAM
          Instructs mail send program for SAPCONNECT to send email.
    form initiate_mail_execute_program.
      wait up to 2 seconds.
      submit rsconn01 with mode = 'INT'
                    with output = 'X'
                    and return.
    endform.                    " INITIATE_MAIL_EXECUTE_PROGRAM
    *&      Form  POPULATE_EMAIL_MESSAGE_BODY
           Populate message body text
    form populate_email_message_body.
      refresh it_message.
      it_message = 'Please find attached a list test ekpo records'.
      append it_message.
    endform.                    " POPULATE_EMAIL_MESSAGE_BODY

  • Spool report line width in background jobs

    Hi All,
    I wrote a report and specified the line size in the report header:
    REPORT /sappssrm/option_handler
    NO STANDARD PAGE HEADING
    LINE-SIZE 185.
    I want to run this report as background job and get a spool list with results of the report. I expected the width of the spool output to be well defined and it works in one system. However, in another systen, the line / page width is much smaller, and the system inserts line breaks in the output splitting my lines into two which causes very ugly results.
    It seems that the LINE-SIZE specified in the report header doesn't affect the output width in every system.
    Can anyone advice?
    Regards
    Wolfgang

    Hi Siggi,
    thanks for your reply. Actually I changed that already yesterday...
    But I found out what it was:
    It seems, the background job keeps old versions of the program, even if you import a new program version. I created a new job with the same program and it worked.
    Thanks again and best regards
    Wolfgang

  • Download ALV result list as excel-file in background job

    Dear Experts,
    I am looking for a possibily to download the result of an ALV based report as excel-file in a background job. Surely there is a standard function which can be used or at least some hints how to implement this. I searched the forum but couldn't find a thread which was covering this problem exactly.
    Thanks in advance
    Benjamin

    Dear Mr. Krapf,
    it is possible to output an ALV list to an Excel file in the background but there are some limitations.
    Please consider the following notes:
    #7925  Graphics, Upload, Download do not work in backgrnd
    #65050 Data types and file formats in files (DATASET) 
    #145073 - FAQ Report Writer: Excel download 
    #569537 - Incorrect data during import into Excel
    #590126  Sending CSV documents up to Release 4.6
    Please be aware that they are all Basis notes. So for more information you might ask in the Basis SDN Forum.
    Best regards, Christin Angus

  • Background Job Result to my Internal ID

    Hi Everyone,
                im Defining a Background job in SM36 and scheduling it. After the completion of that job that particular job result has to come to my Internal ID.is it possible?
       Now, ii is generating a Spool request number and going to a Printer.Instead of that SPOOL , i want that Result/Report has to come to my SAP Id.
        what & Where can i do this?
    Regards,
    Siva

    Siva,
    Just a thought.
    Is the job creator (you) and the User name of the person running the program (defined in Step in SM36) the same in this case ?
    What Im hinting at is, the program inside the job may be run with a different username and HE might not have the authorization. So if you run SU53 from your account, it will not throw up an authorization error, since you are logged in as the you and not the person.
    I would check the following if I were you.
    1. Is the username of the person running the report/program the same as the one running the job.
    2. If they are different, either log in as the user or run a trace on him and find out what he/she is missing.
    This sounds like an authorization problem to me too. Also check authorization for S_OC_SEND object.

  • USMM report showing some Background job, which not in SAP

    Sir,
    I took USMM report from SAP PRD system for audit purpose.  Everything is fine , expect some background job. There showing some background job finish on 01.04.2013. But I don't find any background job in SM37 which showing finish in USMM report. Please suggest what to do. Following are the background Job..
    0000 Measurement Extensions Finished on 01.04.2013 at 12:55:30
    0001 ABAP Workbench Finished on 01.04.2013 at 12:55:44
    0002 Mobile Engine Finished on 01.04.2013 at 12:55:24
    0009 Activity Checks Finished on 01.04.2013 at 12:56:55
    0100 mySAP Human Resources Finished on 01.04.2013 at 12:55:26
    0101 SAP HR e-recruitment Finished on 01.04.2013 at 12:55:24
    0200 mySAP Banking Finished on 01.04.2013 at 12:55:25
    0250 Financial Services Loan Management Finished on 01.04.2013 at 12:55:25
    0300 mySAP Healthcare Finished on 01.04.2013 at 12:55:25
    0400 mySAP Utilities Finished on 01.04.2013 at 12:55:26
    0500 mySAP Telecommunications Finished on 01.04.2013 at 12:55:26
    0600 mySAP Insurance Finished on 01.04.2013 at 12:55:26
    0700 mySAP Public Sector Finished on 01.04.2013 at 12:55:26
    0730 mySAP Public Sector Campus Finished on 01.04.2013 at 12:55:26
    0800 mySAP Oil & Gas Finished on 01.04.2013 at 12:55:26
    0900 mySAP Engineering & Construction Finished on 01.04.2013 at 12:55:27
    1000 mySAP Aerospace & Defense Finished on 01.04.2013 at 12:55:28
    1100 mySAP Automotive Finished on 01.04.2013 at 12:55:28
    1201 SAP Financial Supply Chain Management Finished on 01.04.2013 at 12:55:26
    1215 SAP FSCM Credit Management Finished on 01.04.2013 at 12:55:27
    1500 mySAP Retail Finished on 01.04.2013 at 12:55:26
    1550 BI Accelerator Finished on 01.04.2013 at 12:55:27
    2100 SAP Records Management Finished on 01.04.2013 at 12:55:28
    2200 ICM Incentive and Commissions
    Management
    Finished on 01.04.2013 at 12:55:27
    2320 SAP Exchange Infrastructure Finished on 01.04.2013 at 12:55:29
    2600 SAP Exchange Infrastructure Adapter Finished on 01.04.2013 at 12:55:29
    6000 mySAP Financials Real Estate Finished on 01.04.2013 at 12:55:28
    7100 mySAP Financials Corporate Finance
    Mgmt
    Finished on 01.04.2013 at 12:55:28
    7500 Third-Party CAD Integration Finished on 01.04.2013 at 12:55:29
    7550 SAP Learning Solution Finished on 01.04.2013 at 12:55:30
    8020 Recipe Management Finished on 01.04.2013 at 12:55:29
    8030 Catch Weight Management Finished on 01.04.2013 at 12:55:28
    8040 RBD Tool Finished on 01.04.2013 at 12:55:29
    8050 Bex Broadcaster Finished on 01.04.2013 at 12:55:28
    Thanks & Regards,
    Nabin Chatterjee

    Hi,
    You will get the list of background jobs in SM37.
    It seems that these jobs are not being scheduled by your user ID.
    In username field use * and check on the desired job statuses and use the date from and to on which you want to see the jobs.
    Screen shot is also attached for your reference.
    Regards,
    Siddharth Khandelwal

  • HOw to find out a report name when you know only the name of background job

    Hi experts ,
    my question is i need to find out teh report name for which i knew only the background job name of the report .
    thanx
    Venky.

    Go to tcode SM37->Give job name and execute->choose tool bar button STEPS (Disply Steps list) ->Then you will get program or command

  • 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

  • Job failure ( report RFFDKU00 scheduled for background job)

    Hi Experts,
        When iam scheduling the report RFFDKU00 for background job. Job is getting cancelled with status "ABAP/4 processor: DBIF_RSQL_SQL_ERROR" . when iam obesrving this job it is going to dump at this select query
    "     select ausbk belnr gjahr bzkey buzei
    033370                  from vbsegs into table t_vbsegsfields
    033380            where bukrs in r_bukrs
    033390            and not ( fdlev = space
    033400                  and fdgrp = space
    033410                  and fdtag = init_date
    033420                  and fdwbt = 0 )
    033430            and not saknr in r_cm_sk   "
    Can anyone helpme to deal with this issues ,
    thanks in advance,
    Kranthi

    note 167301 might help.

Maybe you are looking for