Is it possible to run alv grid in background

Can any one tell me about it?

Hi Avinash,
Yes, we can schedule ALV but OO ALV we need some piece of code.
Please see the below link.
http://scn.sap.com/message/15071173
Regards,
Vadamalai A

Similar Messages

Is it possible to run ALV report in background if Yes how?

is it possible to run ALV report in background if Yes how?

Hi,
Why not?Through se38 only you create ALV report. there you can give your report name and go to program on menu bar - click - execute buton- click-Background . You will get new screen there you can choose Execute immediate or schedule.
<REMOVED BY MODERATOR>
Cheers,
Chandra Sekhar.
Edited by: Alvaro Tejada Galindo on Mar 4, 2008 2:12 PM

Can we run alv reports in background

hi all
can we run alv reports in background

Hi
Yes You can
see this
Many a times there is a requirement to display ALV Grid (not ALV List) in the background Job. I have checked the SDN Forum for the same and it has been mentioned that ALV Grid cannot be displayed in Background, but the list output of ALV is possible. So user wont have the actual Grid interface but the List interface.
There is a workaround to display ALV Grid in Background Job. The only restriction is you cant schedule the job through SM36. You need to execute the transaction of the report program, fill in the selection screen data and hit Execute.
The job would be executed in background. User will be able to see the Job Log and Job Status after executing the program. User doesnt have to go to SM37 to view the job status/log. Once the Job Status is changed to COMPLETED, user can click on DISPLAY SPOOL to view the ALV Grid.
Limitations:
Cant schedulea background job
The session should be active until the background job is completed. If the session is closed, then user wont be able to check the output in ALV Grid. User would be able to check the output through spool or SM37
Advantages:
If the spool width is greater than 255 characters, then the entire width could be seen in the output because the output is directed to an ALV Grid and not to spool
Interface of ALV Grid is available instead of ALV List even though its a background job.
Program wont give the TIME OUT error
Steps Required:
1. Once you execute the program, the following screen would be displayed
2. Click Display Job Status to check the Status of the Background Job
3. Click on Display the Job Log to check the Log
4. Click on Display Job Status to check the Job Status
5. Click on DISPLAY SPOOL to check the spool content once the Job Status is changed to COMPLETED. Output is displayed in ALV Grid
Programs:
1. Two different programs needs to be created
ZPROGRAM_ONE: This is the 1st program, where the selection screen and all the data validations would be done. Error handling for invalid data should be done in this program.
Once the data validation is done, this program would call the 2nd program ZPROGEAM_TWO. Build the logic to display ALV Grid in this program. The logic will only display ALV in foreground and it wont be reflected in the spool.
ZPROGRAM_TWO: This program would fetch all the data and do all the processing. If you want the spool output along with ALV Grid output, then build the logic in this program to display ALV Grid.
*& Report ZPROGRAM_ONE                                                *
REPORT zprogram_one                            .
PRASHANT PATIL
TABLES : mara,
         tsp01.
type-pools:slis.
TYPES : BEGIN OF t_mara,
          matnr   TYPE mara-matnr,
          ersda   TYPE mara-ersda,
          ernam   TYPE mara-ernam,
          laeda   TYPE mara-laeda,
        END OF t_mara.
DATA : i_mara       TYPE STANDARD TABLE OF t_mara,
       wa_mara      TYPE t_mara,
       wa_index     TYPE indx,        " For Index details
       wa_index_key TYPE indx-srtfd VALUE 'PRG_ONE',
       i_jobsteplist     TYPE STANDARD TABLE OF tbtcstep, " For spool number
       wa_params         TYPE pri_params, " To Get Print Parameters
       wa_jobhead        TYPE tbtcjob,     " To know the status of job
       wa_jobsteplist    TYPE tbtcstep,    " To know the spool
       w_jobname         TYPE tbtco-jobname, " Job name for bckgrnd job
       w_jobcount        TYPE tbtco-jobcount, " Unique id for bckgrd job
       w_path            TYPE string,         " Upload path
       w_lsind           TYPE sy-lsind,       " Index
       wa_seltab         TYPE rsparams,
       i_seltab          TYPE STANDARD TABLE OF rsparams,
       wa_index1         TYPE indx,        " For Index details
       wa_index_key1     TYPE indx-srtfd VALUE 'PRG_TWO',
       i_fieldcat        TYPE slis_t_fieldcat_alv,
       wa_fieldcat       LIKE LINE OF i_fieldcat.
        CONSTANTS DECLARATION                                        *
CONSTANTS :
         c_a(1) TYPE c VALUE 'A',
         c_m(1) TYPE c VALUE 'M',
         c_l(1) TYPE c VALUE 'L',
         c_c(1) TYPE c VALUE 'C',
         c_zfdr(4) TYPE c VALUE 'ZFDR',
         c_x(1)    TYPE c VALUE 'X',
         c_locl(4) TYPE c VALUE 'LOCL', " Destination is LOCAL
         c_f(1)    TYPE c VALUE 'F',   " Job Status - Failed
         c_s(1)    TYPE c VALUE 'S',
         c_p(1)    TYPE c VALUE 'P'.
SELECTION SCREEN PARAMETERS
SELECT-OPTIONS : s_matnr FOR mara-matnr.
START-OF-SELECTION.
Before the export, fill the data fields before CLUSTR
wa_index-aedat = sy-datum.
wa_index-usera = sy-uname.
EXPORT s_matnr
       TO DATABASE indx(st) FROM wa_index ID wa_index_key.
To Open the Job for background processing
PERFORM open_job.
To get the print parameters
PERFORM get_print_parameters.
Submit the job in background
PERFORM job_submit.
Close the background job
PERFORM job_close.
This is the output screen with the buttons ********
Create 3 buttons DISPLAY SPOOL, STATUS, JOBLOG
SET PF-STATUS 'ZS001'.
WRITE: / 'The program is submitted in Background'.
WRITE: / 'Press DISPLAY SPOOL to see the spool'.
WRITE: / 'Press STATUS to see the status of the background'.
AT USER-COMMAND.
If user presses the 'BACK' button
IF sy-ucomm = 'BAK'.
    IF wa_jobhead-status = c_f OR
        wa_jobhead-status = c_a.
      LEAVE TO SCREEN 0.
    ENDIF.
ENDIF.
If the user presses the 'DISPLAY SPOOL' Button
IF sy-ucomm = 'DISPLAY'.
    PERFORM display_spool.
ENDIF.
If the user presses the 'JOB STATUS' Button
IF sy-ucomm = 'STATUS'.
    PERFORM display_status.
ENDIF.
If the user presses the 'JOB LOG' Button
IF sy-ucomm = 'JOBLOG'.
    PERFORM display_job_log.
ENDIF.
*&      Form open_job
      text
--> p1        text
<-- p2        text
FORM open_job .
This is to Create a new job which is to be submitted in background to
process sales order/delivery/invoice
Here we would get a unique id ( Jobcount ) which identifies our job
along with the job name which we have assigned to our job
CONCATENATE sy-uname
              sy-datum
              sy-uzeit
                      INTO w_jobname . " Assign unique jobname
CALL FUNCTION 'JOB_OPEN'
   EXPORTING
DELANFREP              = ' '
JOBGROUP               = ' '
    jobname                = w_jobname
SDLSTRTDT              = NO_DATE
SDLSTRTTM              = NO_TIME
JOBCLASS               =
IMPORTING
   jobcount                = w_jobcount
CHANGING
RET                    =
EXCEPTIONS
   cant_create_job        = 1
   invalid_job_data       = 2
   jobname_missing        = 3
   OTHERS                 = 4
IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
            WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
ENDFORM.                    " open_job
*&      Form get_print_parameters
      text
--> p1        text
<-- p2        text
FORM get_print_parameters .
DATA : l_valid TYPE c.
This is to get the Print Parameters for the job which is to be
submitted in background to process sales order/delivery/invoice
CALL FUNCTION 'GET_PRINT_PARAMETERS'
   EXPORTING
ARCHIVE_ID                   = C_CHAR_UNKNOWN
ARCHIVE_INFO                 = C_CHAR_UNKNOWN
ARCHIVE_MODE                 = C_CHAR_UNKNOWN
ARCHIVE_TEXT                 = C_CHAR_UNKNOWN
AR_OBJECT                    = C_CHAR_UNKNOWN
ARCHIVE_REPORT               = C_CHAR_UNKNOWN
AUTHORITY                    = C_CHAR_UNKNOWN
COPIES                       = C_NUM3_UNKNOWN
COVER_PAGE                   = C_CHAR_UNKNOWN
DATA_SET                     = C_CHAR_UNKNOWN
DEPARTMENT                   = C_CHAR_UNKNOWN
      destination                  = c_locl " LOCL
EXPIRATION                   = C_NUM1_UNKNOWN
      immediately                  = space
IN_ARCHIVE_PARAMETERS        = ' '
IN_PARAMETERS                = ' '
LAYOUT                       = C_CHAR_UNKNOWN
LINE_COUNT                   = C_INT_UNKNOWN
LINE_SIZE                    = C_INT_UNKNOWN
LIST_NAME                    = C_CHAR_UNKNOWN
LIST_TEXT                    = C_CHAR_UNKNOWN
MODE                         = ' '
      new_list_id                  = c_x
PROTECT_LIST                 = C_CHAR_UNKNOWN
      no_dialog                    = c_x
RECEIVER                     = C_CHAR_UNKNOWN
RELEASE                      = C_CHAR_UNKNOWN
REPORT                       = C_CHAR_UNKNOWN
SAP_COVER_PAGE               = C_CHAR_UNKNOWN
HOST_COVER_PAGE              = C_CHAR_UNKNOWN
PRIORITY                     = C_NUM1_UNKNOWN
SAP_OBJECT                   = C_CHAR_UNKNOWN
TYPE                         = C_CHAR_UNKNOWN
      user                         = sy-uname
USE_OLD_LAYOUT               = ' '
UC_DISPLAY_MODE              = C_CHAR_UNKNOWN
DRAFT                        = C_CHAR_UNKNOWN
ABAP_LIST                    = ' '
USE_ARCHIVENAME_DEF          = ' '
DEFAULT_SPOOL_SIZE           = C_CHAR_UNKNOWN
PO_FAX_STORE                 = ' '
NO_FRAMES                    = C_CHAR_UNKNOWN
   IMPORTING
OUT_ARCHIVE_PARAMETERS       =
      out_parameters               = wa_params
   valid                        = l_valid
   EXCEPTIONS
     archive_info_not_found       = 1
     invalid_print_params         = 2
     invalid_archive_params       = 3
     OTHERS                       = 4
IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
            WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
ENDFORM.                    " get_print_parameters
*&      Form job_submit
      text
--> p1        text
<-- p2        text
FORM job_submit .
The job which we have created & the unique id ( jobcount ) which we
have got identifies our job. Hence those parameters are passed along
with the name of the background program "ZPROGRAM_TWO"
The job is submitted in background.
CALL FUNCTION 'JOB_SUBMIT'
    EXPORTING
ARCPARAMS                         =
    authcknam                         = sy-uname
COMMANDNAME                       = ' '
OPERATINGSYSTEM                   = ' '
EXTPGM_NAME                       = ' '
EXTPGM_PARAM                      = ' '
EXTPGM_SET_TRACE_ON               = ' '
EXTPGM_STDERR_IN_JOBLOG           = 'X'
EXTPGM_STDOUT_IN_JOBLOG           = 'X'
EXTPGM_SYSTEM                     = ' '
EXTPGM_RFCDEST                    = ' '
EXTPGM_WAIT_FOR_TERMINATION       = 'X'
    jobcount                          = w_jobcount
    jobname                           = w_jobname
LANGUAGE                          = SY-LANGU
    priparams                         = wa_params
    report                            = 'ZPROGRAM_TWO'
VARIANT                           = ' '
IMPORTING
STEP_NUMBER                       =
   EXCEPTIONS
     bad_priparams                     = 1
     bad_xpgflags                      = 2
     invalid_jobdata                   = 3
     jobname_missing                   = 4
     job_notex                         = 5
     job_submit_failed                 = 6
     lock_failed                       = 7
     program_missing                   = 8
     prog_abap_and_extpg_set           = 9
     OTHERS                            = 10
IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
            WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
ENDFORM.                    " job_submit
*&      Form job_close
      text
--> p1        text
<-- p2        text
FORM job_close .
Once the job is submitted in background then the job is closed
CALL FUNCTION 'JOB_CLOSE'
    EXPORTING
AT_OPMODE                         = ' '
AT_OPMODE_PERIODIC                = ' '
CALENDAR_ID                       = ' '
EVENT_ID                          = ' '
EVENT_PARAM                       = ' '
EVENT_PERIODIC                    = ' '
    jobcount                          = w_jobcount
    jobname                           = w_jobname
LASTSTRTDT                        = NO_DATE
LASTSTRTTM                        = NO_TIME
PRDDAYS                           = 0
PRDHOURS                          = 0
PRDMINS                           = 0
PRDMONTHS                         = 0
PRDWEEKS                          = 0
PREDJOB_CHECKSTAT                 = ' '
PRED_JOBCOUNT                     = ' '
PRED_JOBNAME                      = ' '
SDLSTRTDT                         = NO_DATE
SDLSTRTTM                         = NO_TIME
STARTDATE_RESTRICTION             = BTC_PROCESS_ALWAYS
    strtimmed                         = c_x
TARGETSYSTEM                      = ' '
START_ON_WORKDAY_NOT_BEFORE       = SY-DATUM
START_ON_WORKDAY_NR               = 0
WORKDAY_COUNT_DIRECTION           = 0
RECIPIENT_OBJ                     =
TARGETSERVER                      = ' '
DONT_RELEASE                      = ' '
TARGETGROUP                       = ' '
DIRECT_START                      =
IMPORTING
JOB_WAS_RELEASED                  =
CHANGING
RET                               =
   EXCEPTIONS
     cant_start_immediate              = 1
     invalid_startdate                 = 2
     jobname_missing                   = 3
     job_close_failed                  = 4
     job_nosteps                       = 5
     job_notex                         = 6
     lock_failed                       = 7
     invalid_target                    = 8
     OTHERS                            = 9
IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
            WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
ENDFORM.                    " job_close
*&      Form display_spool
      text
--> p1        text
<-- p2        text
FORM display_spool .
To Read the Job to get the spool details
DATA : l_rqident TYPE tsp01-rqident, " Spool Number
         l_spoolno TYPE tsp01_sp0r-rqid_char.
CLEAR : l_rqident,
          w_lsind,
          wa_jobsteplist.
REFRESH : i_jobsteplist.
SET PF-STATUS 'ZAR02'.
Get the Spool Number
CALL FUNCTION 'BP_JOB_READ'
    EXPORTING
      job_read_jobcount           = w_jobcount
      job_read_jobname            = w_jobname
      job_read_opcode             = '20'
    JOB_STEP_NUMBER             =
   IMPORTING
     job_read_jobhead            = wa_jobhead
   TABLES
     job_read_steplist           = i_jobsteplist
CHANGING
   RET                         =
   EXCEPTIONS
     invalid_opcode              = 1
     job_doesnt_exist            = 2
     job_doesnt_have_steps       = 3
     OTHERS                      = 4
IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
            WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
Read the Job Step list to get the spool number
READ TABLE i_jobsteplist INTO wa_jobsteplist INDEX 1.
CHECK wa_jobsteplist-listident <> space.
Spool Number
l_rqident = wa_jobsteplist-listident.
MOVE l_rqident TO l_spoolno.
Check the spool in TSP01
SELECT SINGLE * FROM tsp01 WHERE rqident = l_rqident.
IF sy-subrc = 0.
    LEAVE TO LIST-PROCESSING.
    CALL FUNCTION 'RSPO_R_RDELETE_SPOOLREQ'
      EXPORTING
        spoolid       = l_spoolno
    IMPORTING
      RC            =
      STATUS        =
    PERFORM show_alv.
ENDIF.
w_lsind = sy-lsind.
IF sy-lsind GE 19.
    sy-lsind = 1.
ENDIF.
ENDFORM.                    " display_spool
*&      Form show_alv
      text
--> p1        text
<-- p2        text
FORM show_alv .
Before the import, fill the data fields before CLUSTR.
wa_index1-aedat = sy-datum.
wa_index1-usera = sy-uname.
To Import the selection screen data from Calling Program
IMPORT i_mara
FROM DATABASE indx(st) ID wa_index_key1 TO wa_index1.
FREE MEMORY ID wa_index_key1.
This prepares the field-catalog for ALV.
PERFORM prepare_fieldcatalog.
This displays the output in ALV format .
PERFORM display_alv.
ENDFORM.                    " show_alv
*&      Form display_status
      text
--> p1        text
<-- p2        text
FORM display_status .
To Display the STATUS of the JOB which is exectued in background
CLEAR : wa_jobsteplist.
REFRESH : i_jobsteplist.
WRITE:/ 'DISPLAYING JOB STATUS'.
CALL FUNCTION 'BP_JOB_READ'
    EXPORTING
      job_read_jobcount           = w_jobcount
      job_read_jobname            = w_jobname
      job_read_opcode             = '20'
    JOB_STEP_NUMBER             =
   IMPORTING
     job_read_jobhead            = wa_jobhead
   TABLES
     job_read_steplist           = i_jobsteplist
CHANGING
   RET                         =
   EXCEPTIONS
     invalid_opcode              = 1
     job_doesnt_exist            = 2
     job_doesnt_have_steps       = 3
     OTHERS                      = 4
IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
            WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
To Display the status text as per the status type
CASE wa_jobhead-status.
    WHEN 'S'. WRITE: / 'Scheduled'.
    WHEN 'R'. WRITE: / 'Released'.
    WHEN 'F'. WRITE: / 'Completed'.
    WHEN 'A'. WRITE: / 'Cancelled'.
    WHEN OTHERS.
ENDCASE.
IF sy-lsind GE 19.
    sy-lsind = 1.
ENDIF.
ENDFORM.                    " display_status
*&      Form display_job_log
      text
--> p1        text
<-- p2        text
FORM display_job_log .
To display the log of the background program
LEAVE TO LIST-PROCESSING.
CALL FUNCTION 'BP_JOBLOG_SHOW_SM37B'
    EXPORTING
      client                    = sy-mandt
      jobcount                  = w_jobcount
      joblogid                  = ' '
      jobname                   = w_jobname
    EXCEPTIONS
      error_reading_jobdata     = 1
      error_reading_joblog_data = 2
      jobcount_missing          = 3
      joblog_does_not_exist     = 4
      joblog_is_empty           = 5
      joblog_show_canceled      = 6
      jobname_missing           = 7
      job_does_not_exist        = 8
      no_joblog_there_yet       = 9
      no_show_privilege_given   = 10
      OTHERS                    = 11.
IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
            WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
ENDFORM.                    " display_job_log
*&      Form prepare_fieldcatalog
      text
--> p1        text
<-- p2        text
FORM prepare_fieldcatalog .
CLEAR wa_fieldcat.
wa_fieldcat-fieldname    = 'MATNR'.
wa_fieldcat-tabname      = 'I_MARA'.
wa_fieldcat-reptext_ddic = 'Material no.'.
wa_fieldcat-outputlen    = '18'.
APPEND wa_fieldcat TO i_fieldcat.
CLEAR wa_fieldcat.
wa_fieldcat-fieldname    = 'ERSDA'.
wa_fieldcat-tabname      = 'I_MARA'.
wa_fieldcat-reptext_ddic = 'Creation date'.
wa_fieldcat-outputlen    = '10'.
APPEND wa_fieldcat TO i_fieldcat.
CLEAR wa_fieldcat.
wa_fieldcat-fieldname    = 'ERNAM'.
wa_fieldcat-tabname      = 'I_MARA'.
wa_fieldcat-reptext_ddic = 'Name of Person'.
wa_fieldcat-outputlen    = '10'.
APPEND wa_fieldcat TO i_fieldcat.
CLEAR wa_fieldcat.
wa_fieldcat-fieldname    = 'LAEDA'.
wa_fieldcat-tabname      = 'I_MARA'.
wa_fieldcat-reptext_ddic = ' Last Change'.
wa_fieldcat-outputlen    = '10'.
APPEND wa_fieldcat TO i_fieldcat.
ENDFORM.                    " prepare_fieldcatalog
*&      Form display_alv
      text
--> p1        text
<-- p2        text
FORM display_alv .
Call ABAP List Viewer (ALV)
call function 'REUSE_ALV_GRID_DISPLAY'
    exporting
      it_fieldcat = i_fieldcat
    tables
      t_outtab     = i_mara.
ENDFORM.                    " display_alv
     ZPROGRAM_TWO: This is the 2nd program which would be called from program ZPROGRAM_ONE.
*& Report ZPROGRAM_TWO                                                *
REPORT zprogram_two                            .
PRASHANT PATIL
TABLES : mara.
TYPE-POOLS:slis.
TYPES : BEGIN OF t_mara,
          matnr   TYPE mara-matnr,
          ersda   TYPE mara-ersda,
          ernam   TYPE mara-ernam,
          laeda   TYPE mara-laeda,
        END OF t_mara.
DATA : i_mara        TYPE STANDARD TABLE OF t_mara,
       wa_mara       TYPE t_mara,
       wa_index      TYPE indx,        " For Index details
       wa_index_key TYPE indx-srtfd VALUE 'PRG_ONE',
       wa_index1     TYPE indx,        " For Index details
       wa_index_key1 TYPE indx-srtfd VALUE 'PRG_TWO',
       i_fieldcat        TYPE slis_t_fieldcat_alv,
       wa_fieldcat       LIKE LINE OF i_fieldcat.
SELECT-OPTIONS : s_matnr FOR mara-matnr.
Before the import, fill the data fields before CLUSTR.
wa_index-aedat = sy-datum.
wa_index-usera = sy-uname.
To Import the selection screen data from Calling Program
IMPORT s_matnr
FROM DATABASE indx(st) ID wa_index_key TO wa_index.
FREE MEMORY ID wa_index_key.
SELECT matnr
       ersda
       ernam
       laeda
       FROM mara
       INTO TABLE i_mara
       WHERE matnr IN s_matnr.
PERFORM prepare_fieldcatalog.
PERFORM display_alv.
Before the export, fill the data fields before CLUSTR
wa_index1-aedat = sy-datum.
wa_index1-usera = sy-uname.
EXPORT i_mara
TO DATABASE indx(st) FROM wa_index1 ID wa_index_key1.
*&      Form prepare_fieldcatalog
      text
--> p1        text
<-- p2        text
FORM prepare_fieldcatalog .
CLEAR wa_fieldcat.
wa_fieldcat-fieldname    = 'MATNR'.
wa_fieldcat-tabname      = 'I_MARA'.
wa_fieldcat-outputlen    = '18'.
APPEND wa_fieldcat TO i_fieldcat.
CLEAR wa_fieldcat.
wa_fieldcat-fieldname    = 'ERSDA'.
wa_fieldcat-tabname      = 'I_MARA'.
wa_fieldcat-outputlen    = '10'.
APPEND wa_fieldcat TO i_fieldcat.
CLEAR wa_fieldcat.
wa_fieldcat-fieldname    = 'ERNAM'.
wa_fieldcat-tabname      = 'I_MARA'.
wa_fieldcat-outputlen    = '10'.
APPEND wa_fieldcat TO i_fieldcat.
CLEAR wa_fieldcat.
wa_fieldcat-fieldname    = 'LAEDA'.
wa_fieldcat-tabname      = 'I_MARA'.
wa_fieldcat-outputlen    = '10'.
APPEND wa_fieldcat TO i_fieldcat.
ENDFORM.                    " prepare_fieldcatalog
*&      Form display_alv
      text
--> p1        text
<-- p2        text
FORM display_alv .
Call ABAP List Viewer (ALV)
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
    EXPORTING
      it_fieldcat = i_fieldcat
    TABLES
      t_outtab    = i_mara.
ENDFORM.                    " display_alv
its possible to display ALV Grid using OO ALV. Following code can be used instead of FM.
In the PBO, add following code
SET PF-STATUS 'ZSTAT'.
If program is executed in background
CALL METHOD cl_gui_alv_grid=>offline
RECEIVING
e_offline = off.
IF off IS INITIAL.
IF container1 IS INITIAL.
CREATE OBJECT container1
EXPORTING
container_name = 'CC_ALV1' .
ENDIF.
ENDIF.
CREATE OBJECT g_grid1
EXPORTING
i_parent = container1.
CALL METHOD g_grid1->set_table_for_first_display
EXPORTING
I_BUFFER_ACTIVE =
I_BYPASSING_BUFFER =
I_CONSISTENCY_CHECK =
I_STRUCTURE_NAME =
IS_VARIANT =
i_save = 'A'
i_default = ' '
is_layout =
is_print =
IT_SPECIAL_GROUPS =
it_toolbar_excluding =
IT_HYPERLINK =
IT_ALV_GRAPHICS =
IT_EXCEPT_QINFO =
CHANGING
it_outtab = i_output
it_fieldcatalog = i_fieldcatalog
IT_SORT =
IT_FILTER =
EXCEPTIONS
invalid_parameter_combination = 1
program_error = 2
too_many_lines = 3
OTHERS = 4
IF sy-subrc <> 0.
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
Reward points if useful
Regards
Anji

To display output of ALV GRID in background.

Hi,
I have a report which is giving TIMEOUT error .This report is interactive( it calls a standard transaction based on user action ) If i run this report in background then I can see the output through spool in basic list .
Whether it is possible to run this report in BACKGROUND and after it gets executed , display the output in foreground so that it does not looses the functionality of intractableness.

hi Tushar,
one idea : you can save the output (which is an internal table in fact) to a Z table. Than in another program you read this Z table to internal table and display with ALV.
ec

Will it be possible to run several jobs in background at the same time?

Hi!
The new release looks promising. Look forward to hear more in Birmingham.
Just now we have a problem. It have to do with functionality In Toad compared to SQL Developer.
Will it be possible to run several jobs in background at the same time. Toad allows that.
If yes: How can we make that happen?

"Jobs" are always background.
But I take you mean queries. Yes, since v1.5.x you can open an Unshared SQL Worksheet (ctrl-shift-n or the toolbar button).
Have fun,
K.

Running report with alv grid in background and exporting to excel

Hi Guys,
              I've created a report program that uses the alv grid. When I run the report in foreground, I can easily export it to excel. However, if I run it in background, then display the spooled report and try to export to excel, it does not put it in excel format (seems to go over as one big column rather than individual columns that are defined in the report). Is there a way to run it in background ,export to excel properly and i have to email also in Excel sheet format.?
Thanks,
Gopi.

In background u cannot do a download to excel. you can do is create CSV format file
or
write a report for output with tabs then call that report using
submit yXXXX exporting list to memory
           and return.
call function 'LIST_FROM_MEMORY'
    tables
      listobject = report_list
    exceptions
      not_found = 1
      others     = 2.
and send the report_list to email users
a®

Running ALV REPORT in background

Hi Experts ,
Before writing this query , i went through all the threads related to ALV report in background . But found none of them satisfactory .
I am running a alv report in background . I am not using OO ALV . I am using " REUSE_ALV_GRID_DISPLAY" .
This report is schedules through a background job . It is creating a spool .
But I am getting a error message : *" FRONT END NOT AVIALABLE "*
What i have found so far :
I am planning to use sy-batch variable to check whether it is running in background or not , Then I am planning to read the spool and if the spool is created , i will display the ALV .
Is this the correct approach or some other way to generate the ALV REPORT .
Also by this way will the error message *" FRONT END NOT AVIALABLE "* go .
Please advice .
Regards,
Abhishek

Hello Everyone ,
Thanks for your replies .
I have the spool generated . But it is waiting status .
The issue here is how I am going to say that the spool is in " Completed " status . Because only after when my spool is in completed status , I want to display the status .
Is there way for this ?
Regards ,
Abhishek

Run ALV report in background

Hi All,
We have a customised report whose output is in ALV format as it takes long time to run in foreground we schedule it as background job. When we go to spool and view the output each row appears in 4 to 5 lines. Now how can we download to excel file? Thanks a lot
Note : Report has 20 columns output where each row/line is close to 1000 chars
Regards

Hi,
Yes ,in background you cannot download your data into Excel or in any format
ALL the FM which are used for file processing on presentation server will not work in background.
Another way u can try is
1. Download it in UNCONVERTED format
to a TXT file.
2. Then open that file in EXCEL.
regards,
Shiva kUmar

Is it possible to run WF_DOC.CREATE in background?

Hi gurus,
In my workflow there's the step 'Document from Template' to generate a WF_DOC and it's working fine. However the user wants to have the step done in background and the document generated automatically.
To meet this requirement, I tried to copy the WF_DOC and modify it into a background version, but it seems as if the underlying CL_SWF_DOCUMENT is designed to run with frontend and many GUI functions such as POPUP_TO_SELECT are used. So my question is: Is it even possible to do the WF_DOC.CREATE in background or is there any work around?
Thanks in advance for any hints.
Best regards
Luis

Hello Luis,
I have looked through the coding and the answer to your question is: No.
The WF_Doc uses the frontend components (Word, etc.) to create those documents where the frontend isn't available in background tasks.
A workaround to your requirement could be some kind of report output or SAPscript-output (converted to PDF or something similar), then create from this binary data an Office-document and append this one to ADHOCOBJECTS container element.
This workaround is only an idea and there are several others to do so, as well.
Best wishes,
Florin

Possible to run something in the background?

This is my situation: I have a Student class and a Clazz class. A student can belong to only 1 clazz and a clazz can have many students. These 2 classes are mapped to 2 database tables. In the following code, I remove all the JPA annotations.
class Student {
    private Clazz clazz;
    public void setClazz(Clazz clazz) {
        this.clazz = clazz;
        clazz.getStudents().add(this);
class Clazz {
    private List<Student> students;
}So to add a new student to an existing class, I do something like:
Student student = new Student();
Clazz clazz = entityManager.find(Clazz.class, clazzId);
student.setClazz(clazz);
entityManager.persist(student);Because of the line clazz.getStudents().add(this); in the Student.setClazz method, the application has to go to the DB and load all the existing students for that clazz (which takes a long time).
The Student and Clazz codes are very difficult for me to change (somebody wrote them and they don't wanna change). So I have to think of some way to load the clazz and all its student when I have the clazzId information. The duration from when I have the clazzId info until the student is saved to the db is about 1min.
This is what I did:
- I created a stateful session bean with an EXTENDED entity manager which has a method to return a clazz when we feed it a clazzId. So the returned clazz is persisted.
- I created a stateless session bean which has a timer. When I have the clazzId, I start the timer, give the timer a ClazzHolder instance.
class ClazzHolder {
    private Long clazzId;
    private Clazz clazz;
    private boolean done;
}- The timer gets the clazzId from the ClazzHolder instance, feeds that clazzId to the stateful bean, receives a persisted Clazz instance back, saves that Clazz instance in the ClazzHolder instance and turns the flag "done" to true.
It seems to me that the ClazzHolder instance the stateless session bean has is not the ClazzHolder instance that I pass to it (but the content is the same). I think it's because the ClazzHolder instance I pass to the session bean is serialized first, and then de-serialized to build an object and give to a method in the session bean.
Summary: my idea of using timer to load something before hand doesn't work.
My question is: is there any way to load something from the database and keep it persisted before hand?

Hi Naimesh,
thx for explanation. I am not sure, if I understood everything in the right way.
Where do you write the code for building the selection-screen? (PARAMETERS, SELECT-OPTIONS etc.)
If you write these commands in a class method, you will get a syntax error ( because it's forbidden per definition of ABAP objects). So, am I right assuming that you put the coding just at the beginning of the ABAP report ? And after START-OF-SELECTION-event you start the processing... ?
Furthermore, I don't really understand why you create an separate class for ALV. I found your "SAP abap help"-blog, where you explained the concept of MVC ((By the way, well done!), but you didn't mention an "ALV class" there..
Mh.. another question - have you ever combined MVC with object services?
At the moment I'm working on a software project where I use object services. I created 2 persistent classes via SE24 and one local class in my ABAP Report.
I don't really see possibility to implement MVC in this project without change very much of coding and class structure...
In my opinion the M (data&business logic) are my existing global classes and my local class is kind of Controller class?!
Thx in advance,
Anne

Is there a possibility to run RSRV fix in background?

Hello,
Is there a possibility to schedule/run the "error correction" part of the RSRV result as a background job and not dialog.
Thank you

Hi Blue005,
there is no standard report provided as standard to do the 'Repair' tasks within a BGD job.
The reason for this is that some repairs have to be executed in a certain order or a certain time (when no other jobs can interfere). Furthermore these repairs should be supervised by an administrator.
The system is not supposed to do this automatically.
So you'd have to create your own Z-report making use of report RSRV_JOB_RUNNER (which are the actual RSRV tests) or the function module RSDRD_DIM_REMOVE_UNUSED.
Rgds,
Colum

ALV Grid in back ground

Hi friends, i got some problem in alv grid while i am running it in back ground.
my report contains some currency(amount) field in out put. when i am removing the amount field it is good result in back ground. but when it consist of amount field it is giving error. it indicating some string length problem. and error analysis as follows.
Error analysis
In statement
"STRLEN( obj )..."
the argument "obj" can only take a character-type data object.
In this case, the operand "obj" has the non-character type "P".
pls tell me can't we run amount field in back ground. if s how to solve my error. pls give me some ideas.
Kumar.

Hi
Many a times there is a requirement to display ALV Grid (not ALV List) in the background Job. I have checked the SDN Forum for the same and it has been mentioned that ALV Grid cannot be displayed in Background, but the list output of ALV is possible. So user wont have the actual Grid interface but the List interface.
There is a workaround to display ALV Grid in Background Job. The only restriction is you cant schedule the job through SM36. You need to execute the transaction of the report program, fill in the selection screen data and hit Execute.
The job would be executed in background. User will be able to see the Job Log and Job Status after executing the program. User doesnt have to go to SM37 to view the job status/log. Once the Job Status is changed to COMPLETED, user can click on DISPLAY SPOOL to view the ALV Grid.
/people/prashant.patil12/blog/2007/02/20/displaying-alv-grid-in-background-job

Running the alv report in background and sending it thro email

hi,
      i have to run the alv report in background and send the output through email

Hi
Many a times there is a requirement to display ALV Grid (not ALV List) in the background Job. I have checked the SDN Forum for the same and it has been mentioned that ALV Grid cannot be displayed in Background, but the list output of ALV is possible. So user wont have the actual Grid interface but the List interface.
There is a workaround to display ALV Grid in Background Job. The only restriction is you cant schedule the job through SM36. You need to execute the transaction of the report program, fill in the selection screen data and hit Execute.
The job would be executed in background. User will be able to see the Job Log and Job Status after executing the program. User doesnt have to go to SM37 to view the job status/log. Once the Job Status is changed to COMPLETED, user can click on DISPLAY SPOOL to view the ALV Grid.
Limitations:
Cant schedulea background job
The session should be active until the background job is completed. If the session is closed, then user wont be able to check the output in ALV Grid. User would be able to check the output through spool or SM37
Advantages:
If the spool width is greater than 255 characters, then the entire width could be seen in the output because the output is directed to an ALV Grid and not to spool
Interface of ALV Grid is available instead of ALV List even though its a background job.
Program wont give the TIME OUT error
Steps Required:
1. Once you execute the program, the following screen would be displayed
2. Click Display Job Status to check the Status of the Background Job
3. Click on Display the Job Log to check the Log
4. Click on Display Job Status to check the Job Status
5. Click on DISPLAY SPOOL to check the spool content once the Job Status is changed to COMPLETED. Output is displayed in ALV Grid
Programs:
1. Two different programs needs to be created
ZPROGRAM_ONE: This is the 1st program, where the selection screen and all the data validations would be done. Error handling for invalid data should be done in this program.
Once the data validation is done, this program would call the 2nd program ZPROGEAM_TWO. Build the logic to display ALV Grid in this program. The logic will only display ALV in foreground and it wont be reflected in the spool.
ZPROGRAM_TWO: This program would fetch all the data and do all the processing. If you want the spool output along with ALV Grid output, then build the logic in this program to display ALV Grid.
*& Report ZPROGRAM_ONE                                                *
REPORT zprogram_one                            .
PRASHANT PATIL
TABLES : mara,
         tsp01.
type-pools:slis.
TYPES : BEGIN OF t_mara,
          matnr   TYPE mara-matnr,
          ersda   TYPE mara-ersda,
          ernam   TYPE mara-ernam,
          laeda   TYPE mara-laeda,
        END OF t_mara.
DATA : i_mara       TYPE STANDARD TABLE OF t_mara,
       wa_mara      TYPE t_mara,
       wa_index     TYPE indx,        " For Index details
       wa_index_key TYPE indx-srtfd VALUE 'PRG_ONE',
       i_jobsteplist     TYPE STANDARD TABLE OF tbtcstep, " For spool number
       wa_params         TYPE pri_params, " To Get Print Parameters
       wa_jobhead        TYPE tbtcjob,     " To know the status of job
       wa_jobsteplist    TYPE tbtcstep,    " To know the spool
       w_jobname         TYPE tbtco-jobname, " Job name for bckgrnd job
       w_jobcount        TYPE tbtco-jobcount, " Unique id for bckgrd job
       w_path            TYPE string,         " Upload path
       w_lsind           TYPE sy-lsind,       " Index
       wa_seltab         TYPE rsparams,
       i_seltab          TYPE STANDARD TABLE OF rsparams,
       wa_index1         TYPE indx,        " For Index details
       wa_index_key1     TYPE indx-srtfd VALUE 'PRG_TWO',
       i_fieldcat        TYPE slis_t_fieldcat_alv,
       wa_fieldcat       LIKE LINE OF i_fieldcat.
        CONSTANTS DECLARATION                                        *
CONSTANTS :
         c_a(1) TYPE c VALUE 'A',
         c_m(1) TYPE c VALUE 'M',
         c_l(1) TYPE c VALUE 'L',
         c_c(1) TYPE c VALUE 'C',
         c_zfdr(4) TYPE c VALUE 'ZFDR',
         c_x(1)    TYPE c VALUE 'X',
         c_locl(4) TYPE c VALUE 'LOCL', " Destination is LOCAL
         c_f(1)    TYPE c VALUE 'F',   " Job Status - Failed
         c_s(1)    TYPE c VALUE 'S',
         c_p(1)    TYPE c VALUE 'P'.
SELECTION SCREEN PARAMETERS
SELECT-OPTIONS : s_matnr FOR mara-matnr.
START-OF-SELECTION.
Before the export, fill the data fields before CLUSTR
wa_index-aedat = sy-datum.
wa_index-usera = sy-uname.
EXPORT s_matnr
       TO DATABASE indx(st) FROM wa_index ID wa_index_key.
To Open the Job for background processing
PERFORM open_job.
To get the print parameters
PERFORM get_print_parameters.
Submit the job in background
PERFORM job_submit.
Close the background job
PERFORM job_close.
This is the output screen with the buttons ********
Create 3 buttons DISPLAY SPOOL, STATUS, JOBLOG
SET PF-STATUS 'ZS001'.
WRITE: / 'The program is submitted in Background'.
WRITE: / 'Press DISPLAY SPOOL to see the spool'.
WRITE: / 'Press STATUS to see the status of the background'.
AT USER-COMMAND.
If user presses the 'BACK' button
IF sy-ucomm = 'BAK'.
    IF wa_jobhead-status = c_f OR
        wa_jobhead-status = c_a.
      LEAVE TO SCREEN 0.
    ENDIF.
ENDIF.
If the user presses the 'DISPLAY SPOOL' Button
IF sy-ucomm = 'DISPLAY'.
    PERFORM display_spool.
ENDIF.
If the user presses the 'JOB STATUS' Button
IF sy-ucomm = 'STATUS'.
    PERFORM display_status.
ENDIF.
If the user presses the 'JOB LOG' Button
IF sy-ucomm = 'JOBLOG'.
    PERFORM display_job_log.
ENDIF.
*&      Form open_job
      text
--> p1        text
<-- p2        text
FORM open_job .
This is to Create a new job which is to be submitted in background to
process sales order/delivery/invoice
Here we would get a unique id ( Jobcount ) which identifies our job
along with the job name which we have assigned to our job
CONCATENATE sy-uname
              sy-datum
              sy-uzeit
                      INTO w_jobname . " Assign unique jobname
CALL FUNCTION 'JOB_OPEN'
   EXPORTING
DELANFREP              = ' '
JOBGROUP               = ' '
    jobname                = w_jobname
SDLSTRTDT              = NO_DATE
SDLSTRTTM              = NO_TIME
JOBCLASS               =
IMPORTING
   jobcount                = w_jobcount
CHANGING
RET                    =
EXCEPTIONS
   cant_create_job        = 1
   invalid_job_data       = 2
   jobname_missing        = 3
   OTHERS                 = 4
IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
            WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
ENDFORM.                    " open_job
*&      Form get_print_parameters
      text
--> p1        text
<-- p2        text
FORM get_print_parameters .
DATA : l_valid TYPE c.
This is to get the Print Parameters for the job which is to be
submitted in background to process sales order/delivery/invoice
CALL FUNCTION 'GET_PRINT_PARAMETERS'
   EXPORTING
ARCHIVE_ID                   = C_CHAR_UNKNOWN
ARCHIVE_INFO                 = C_CHAR_UNKNOWN
ARCHIVE_MODE                 = C_CHAR_UNKNOWN
ARCHIVE_TEXT                 = C_CHAR_UNKNOWN
AR_OBJECT                    = C_CHAR_UNKNOWN
ARCHIVE_REPORT               = C_CHAR_UNKNOWN
AUTHORITY                    = C_CHAR_UNKNOWN
COPIES                       = C_NUM3_UNKNOWN
COVER_PAGE                   = C_CHAR_UNKNOWN
DATA_SET                     = C_CHAR_UNKNOWN
DEPARTMENT                   = C_CHAR_UNKNOWN
      destination                  = c_locl " LOCL
EXPIRATION                   = C_NUM1_UNKNOWN
      immediately                  = space
IN_ARCHIVE_PARAMETERS        = ' '
IN_PARAMETERS                = ' '
LAYOUT                       = C_CHAR_UNKNOWN
LINE_COUNT                   = C_INT_UNKNOWN
LINE_SIZE                    = C_INT_UNKNOWN
LIST_NAME                    = C_CHAR_UNKNOWN
LIST_TEXT                    = C_CHAR_UNKNOWN
MODE                         = ' '
      new_list_id                  = c_x
PROTECT_LIST                 = C_CHAR_UNKNOWN
      no_dialog                    = c_x
RECEIVER                     = C_CHAR_UNKNOWN
RELEASE                      = C_CHAR_UNKNOWN
REPORT                       = C_CHAR_UNKNOWN
SAP_COVER_PAGE               = C_CHAR_UNKNOWN
HOST_COVER_PAGE              = C_CHAR_UNKNOWN
PRIORITY                     = C_NUM1_UNKNOWN
SAP_OBJECT                   = C_CHAR_UNKNOWN
TYPE                         = C_CHAR_UNKNOWN
      user                         = sy-uname
USE_OLD_LAYOUT               = ' '
UC_DISPLAY_MODE              = C_CHAR_UNKNOWN
DRAFT                        = C_CHAR_UNKNOWN
ABAP_LIST                    = ' '
USE_ARCHIVENAME_DEF          = ' '
DEFAULT_SPOOL_SIZE           = C_CHAR_UNKNOWN
PO_FAX_STORE                 = ' '
NO_FRAMES                    = C_CHAR_UNKNOWN
   IMPORTING
OUT_ARCHIVE_PARAMETERS       =
      out_parameters               = wa_params
   valid                        = l_valid
   EXCEPTIONS
     archive_info_not_found       = 1
     invalid_print_params         = 2
     invalid_archive_params       = 3
     OTHERS                       = 4
IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
            WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
ENDFORM.                    " get_print_parameters
*&      Form job_submit
      text
--> p1        text
<-- p2        text
FORM job_submit .
The job which we have created & the unique id ( jobcount ) which we
have got identifies our job. Hence those parameters are passed along
with the name of the background program "ZPROGRAM_TWO"
The job is submitted in background.
CALL FUNCTION 'JOB_SUBMIT'
    EXPORTING
ARCPARAMS                         =
    authcknam                         = sy-uname
COMMANDNAME                       = ' '
OPERATINGSYSTEM                   = ' '
EXTPGM_NAME                       = ' '
EXTPGM_PARAM                      = ' '
EXTPGM_SET_TRACE_ON               = ' '
EXTPGM_STDERR_IN_JOBLOG           = 'X'
EXTPGM_STDOUT_IN_JOBLOG           = 'X'
EXTPGM_SYSTEM                     = ' '
EXTPGM_RFCDEST                    = ' '
EXTPGM_WAIT_FOR_TERMINATION       = 'X'
    jobcount                          = w_jobcount
    jobname                           = w_jobname
LANGUAGE                          = SY-LANGU
    priparams                         = wa_params
    report                            = 'ZPROGRAM_TWO'
VARIANT                           = ' '
IMPORTING
STEP_NUMBER                       =
   EXCEPTIONS
     bad_priparams                     = 1
     bad_xpgflags                      = 2
     invalid_jobdata                   = 3
     jobname_missing                   = 4
     job_notex                         = 5
     job_submit_failed                 = 6
     lock_failed                       = 7
     program_missing                   = 8
     prog_abap_and_extpg_set           = 9
     OTHERS                            = 10
IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
            WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
ENDFORM.                    " job_submit
*&      Form job_close
      text
--> p1        text
<-- p2        text
FORM job_close .
Once the job is submitted in background then the job is closed
CALL FUNCTION 'JOB_CLOSE'
    EXPORTING
AT_OPMODE                         = ' '
AT_OPMODE_PERIODIC                = ' '
CALENDAR_ID                       = ' '
EVENT_ID                          = ' '
EVENT_PARAM                       = ' '
EVENT_PERIODIC                    = ' '
    jobcount                          = w_jobcount
    jobname                           = w_jobname
LASTSTRTDT                        = NO_DATE
LASTSTRTTM                        = NO_TIME
PRDDAYS                           = 0
PRDHOURS                          = 0
PRDMINS                           = 0
PRDMONTHS                         = 0
PRDWEEKS                          = 0
PREDJOB_CHECKSTAT                 = ' '
PRED_JOBCOUNT                     = ' '
PRED_JOBNAME                      = ' '
SDLSTRTDT                         = NO_DATE
SDLSTRTTM                         = NO_TIME
STARTDATE_RESTRICTION             = BTC_PROCESS_ALWAYS
    strtimmed                         = c_x
TARGETSYSTEM                      = ' '
START_ON_WORKDAY_NOT_BEFORE       = SY-DATUM
START_ON_WORKDAY_NR               = 0
WORKDAY_COUNT_DIRECTION           = 0
RECIPIENT_OBJ                     =
TARGETSERVER                      = ' '
DONT_RELEASE                      = ' '
TARGETGROUP                       = ' '
DIRECT_START                      =
IMPORTING
JOB_WAS_RELEASED                  =
CHANGING
RET                               =
   EXCEPTIONS
     cant_start_immediate              = 1
     invalid_startdate                 = 2
     jobname_missing                   = 3
     job_close_failed                  = 4
     job_nosteps                       = 5
     job_notex                         = 6
     lock_failed                       = 7
     invalid_target                    = 8
     OTHERS                            = 9
IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
            WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
ENDFORM.                    " job_close
*&      Form display_spool
      text
--> p1        text
<-- p2        text
FORM display_spool .
To Read the Job to get the spool details
DATA : l_rqident TYPE tsp01-rqident, " Spool Number
         l_spoolno TYPE tsp01_sp0r-rqid_char.
CLEAR : l_rqident,
          w_lsind,
          wa_jobsteplist.
REFRESH : i_jobsteplist.
SET PF-STATUS 'ZAR02'.
Get the Spool Number
CALL FUNCTION 'BP_JOB_READ'
    EXPORTING
      job_read_jobcount           = w_jobcount
      job_read_jobname            = w_jobname
      job_read_opcode             = '20'
    JOB_STEP_NUMBER             =
   IMPORTING
     job_read_jobhead            = wa_jobhead
   TABLES
     job_read_steplist           = i_jobsteplist
CHANGING
   RET                         =
   EXCEPTIONS
     invalid_opcode              = 1
     job_doesnt_exist            = 2
     job_doesnt_have_steps       = 3
     OTHERS                      = 4
IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
            WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
Read the Job Step list to get the spool number
READ TABLE i_jobsteplist INTO wa_jobsteplist INDEX 1.
CHECK wa_jobsteplist-listident <> space.
Spool Number
l_rqident = wa_jobsteplist-listident.
MOVE l_rqident TO l_spoolno.
Check the spool in TSP01
SELECT SINGLE * FROM tsp01 WHERE rqident = l_rqident.
IF sy-subrc = 0.
    LEAVE TO LIST-PROCESSING.
    CALL FUNCTION 'RSPO_R_RDELETE_SPOOLREQ'
      EXPORTING
        spoolid       = l_spoolno
    IMPORTING
      RC            =
      STATUS        =
    PERFORM show_alv.
ENDIF.
w_lsind = sy-lsind.
IF sy-lsind GE 19.
    sy-lsind = 1.
ENDIF.
ENDFORM.                    " display_spool
*&      Form show_alv
      text
--> p1        text
<-- p2        text
FORM show_alv .
Before the import, fill the data fields before CLUSTR.
wa_index1-aedat = sy-datum.
wa_index1-usera = sy-uname.
To Import the selection screen data from Calling Program
IMPORT i_mara
FROM DATABASE indx(st) ID wa_index_key1 TO wa_index1.
FREE MEMORY ID wa_index_key1.
This prepares the field-catalog for ALV.
PERFORM prepare_fieldcatalog.
This displays the output in ALV format .
PERFORM display_alv.
ENDFORM.                    " show_alv
*&      Form display_status
      text
--> p1        text
<-- p2        text
FORM display_status .
To Display the STATUS of the JOB which is exectued in background
CLEAR : wa_jobsteplist.
REFRESH : i_jobsteplist.
WRITE:/ 'DISPLAYING JOB STATUS'.
CALL FUNCTION 'BP_JOB_READ'
    EXPORTING
      job_read_jobcount           = w_jobcount
      job_read_jobname            = w_jobname
      job_read_opcode             = '20'
    JOB_STEP_NUMBER             =
   IMPORTING
     job_read_jobhead            = wa_jobhead
   TABLES
     job_read_steplist           = i_jobsteplist
CHANGING
   RET                         =
   EXCEPTIONS
     invalid_opcode              = 1
     job_doesnt_exist            = 2
     job_doesnt_have_steps       = 3
     OTHERS                      = 4
IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
            WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
To Display the status text as per the status type
CASE wa_jobhead-status.
    WHEN 'S'. WRITE: / 'Scheduled'.
    WHEN 'R'. WRITE: / 'Released'.
    WHEN 'F'. WRITE: / 'Completed'.
    WHEN 'A'. WRITE: / 'Cancelled'.
    WHEN OTHERS.
ENDCASE.
IF sy-lsind GE 19.
    sy-lsind = 1.
ENDIF.
ENDFORM.                    " display_status
*&      Form display_job_log
      text
--> p1        text
<-- p2        text
FORM display_job_log .
To display the log of the background program
LEAVE TO LIST-PROCESSING.
CALL FUNCTION 'BP_JOBLOG_SHOW_SM37B'
    EXPORTING
      client                    = sy-mandt
      jobcount                  = w_jobcount
      joblogid                  = ' '
      jobname                   = w_jobname
    EXCEPTIONS
      error_reading_jobdata     = 1
      error_reading_joblog_data = 2
      jobcount_missing          = 3
      joblog_does_not_exist     = 4
      joblog_is_empty           = 5
      joblog_show_canceled      = 6
      jobname_missing           = 7
      job_does_not_exist        = 8
      no_joblog_there_yet       = 9
      no_show_privilege_given   = 10
      OTHERS                    = 11.
IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
            WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
ENDFORM.                    " display_job_log
*&      Form prepare_fieldcatalog
      text
--> p1        text
<-- p2        text
FORM prepare_fieldcatalog .
CLEAR wa_fieldcat.
wa_fieldcat-fieldname    = 'MATNR'.
wa_fieldcat-tabname      = 'I_MARA'.
wa_fieldcat-reptext_ddic = 'Material no.'.
wa_fieldcat-outputlen    = '18'.
APPEND wa_fieldcat TO i_fieldcat.
CLEAR wa_fieldcat.
wa_fieldcat-fieldname    = 'ERSDA'.
wa_fieldcat-tabname      = 'I_MARA'.
wa_fieldcat-reptext_ddic = 'Creation date'.
wa_fieldcat-outputlen    = '10'.
APPEND wa_fieldcat TO i_fieldcat.
CLEAR wa_fieldcat.
wa_fieldcat-fieldname    = 'ERNAM'.
wa_fieldcat-tabname      = 'I_MARA'.
wa_fieldcat-reptext_ddic = 'Name of Person'.
wa_fieldcat-outputlen    = '10'.
APPEND wa_fieldcat TO i_fieldcat.
CLEAR wa_fieldcat.
wa_fieldcat-fieldname    = 'LAEDA'.
wa_fieldcat-tabname      = 'I_MARA'.
wa_fieldcat-reptext_ddic = ' Last Change'.
wa_fieldcat-outputlen    = '10'.
APPEND wa_fieldcat TO i_fieldcat.
ENDFORM.                    " prepare_fieldcatalog
*&      Form display_alv
      text
--> p1        text
<-- p2        text
FORM display_alv .
Call ABAP List Viewer (ALV)
call function 'REUSE_ALV_GRID_DISPLAY'
    exporting
      it_fieldcat = i_fieldcat
    tables
      t_outtab     = i_mara.
ENDFORM.                    " display_alv
     ZPROGRAM_TWO: This is the 2nd program which would be called from program ZPROGRAM_ONE.
*& Report ZPROGRAM_TWO                                                *
REPORT zprogram_two                            .
PRASHANT PATIL
TABLES : mara.
TYPE-POOLS:slis.
TYPES : BEGIN OF t_mara,
          matnr   TYPE mara-matnr,
          ersda   TYPE mara-ersda,
          ernam   TYPE mara-ernam,
          laeda   TYPE mara-laeda,
        END OF t_mara.
DATA : i_mara        TYPE STANDARD TABLE OF t_mara,
       wa_mara       TYPE t_mara,
       wa_index      TYPE indx,        " For Index details
       wa_index_key TYPE indx-srtfd VALUE 'PRG_ONE',
       wa_index1     TYPE indx,        " For Index details
       wa_index_key1 TYPE indx-srtfd VALUE 'PRG_TWO',
       i_fieldcat        TYPE slis_t_fieldcat_alv,
       wa_fieldcat       LIKE LINE OF i_fieldcat.
SELECT-OPTIONS : s_matnr FOR mara-matnr.
Before the import, fill the data fields before CLUSTR.
wa_index-aedat = sy-datum.
wa_index-usera = sy-uname.
To Import the selection screen data from Calling Program
IMPORT s_matnr
FROM DATABASE indx(st) ID wa_index_key TO wa_index.
FREE MEMORY ID wa_index_key.
SELECT matnr
       ersda
       ernam
       laeda
       FROM mara
       INTO TABLE i_mara
       WHERE matnr IN s_matnr.
PERFORM prepare_fieldcatalog.
PERFORM display_alv.
Before the export, fill the data fields before CLUSTR
wa_index1-aedat = sy-datum.
wa_index1-usera = sy-uname.
EXPORT i_mara
TO DATABASE indx(st) FROM wa_index1 ID wa_index_key1.
*&      Form prepare_fieldcatalog
      text
--> p1        text
<-- p2        text
FORM prepare_fieldcatalog .
CLEAR wa_fieldcat.
wa_fieldcat-fieldname    = 'MATNR'.
wa_fieldcat-tabname      = 'I_MARA'.
wa_fieldcat-outputlen    = '18'.
APPEND wa_fieldcat TO i_fieldcat.
CLEAR wa_fieldcat.
wa_fieldcat-fieldname    = 'ERSDA'.
wa_fieldcat-tabname      = 'I_MARA'.
wa_fieldcat-outputlen    = '10'.
APPEND wa_fieldcat TO i_fieldcat.
CLEAR wa_fieldcat.
wa_fieldcat-fieldname    = 'ERNAM'.
wa_fieldcat-tabname      = 'I_MARA'.
wa_fieldcat-outputlen    = '10'.
APPEND wa_fieldcat TO i_fieldcat.
CLEAR wa_fieldcat.
wa_fieldcat-fieldname    = 'LAEDA'.
wa_fieldcat-tabname      = 'I_MARA'.
wa_fieldcat-outputlen    = '10'.
APPEND wa_fieldcat TO i_fieldcat.
ENDFORM.                    " prepare_fieldcatalog
*&      Form display_alv
      text
--> p1        text
<-- p2        text
FORM display_alv .
Call ABAP List Viewer (ALV)
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
    EXPORTING
      it_fieldcat = i_fieldcat
    TABLES
      t_outtab    = i_mara.
ENDFORM.                    " display_alv
its possible to display ALV Grid using OO ALV. Following code can be used instead of FM.
In the PBO, add following code
SET PF-STATUS 'ZSTAT'.
If program is executed in background
CALL METHOD cl_gui_alv_grid=>offline
RECEIVING
e_offline = off.
IF off IS INITIAL.
IF container1 IS INITIAL.
CREATE OBJECT container1
EXPORTING
container_name = 'CC_ALV1' .
ENDIF.
ENDIF.
CREATE OBJECT g_grid1
EXPORTING
i_parent = container1.
CALL METHOD g_grid1->set_table_for_first_display
EXPORTING
I_BUFFER_ACTIVE =
I_BYPASSING_BUFFER =
I_CONSISTENCY_CHECK =
I_STRUCTURE_NAME =
IS_VARIANT =
i_save = 'A'
i_default = ' '
is_layout =
is_print =
IT_SPECIAL_GROUPS =
it_toolbar_excluding =
IT_HYPERLINK =
IT_ALV_GRAPHICS =
IT_EXCEPT_QINFO =
CHANGING
it_outtab = i_output
it_fieldcatalog = i_fieldcatalog
IT_SORT =
IT_FILTER =
EXCEPTIONS
invalid_parameter_combination = 1
program_error = 2
too_many_lines = 3
OTHERS = 4
IF sy-subrc <> 0.
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
Reward points if useful
Regards
Anji

ALV Grid without screens

Hello experts,
is it possible to implement ALV grid display (OO) without statements such as "call screen 100"?
I have an example, logically everything should work but, unfortunatelly, nothing displays. Code:
ZPROGRAM CODING ***
REPORT ZTESTPROG.
DATA: save_ok LIKE sy-ucomm,
      ok_code LIKE sy-ucomm,
      it_spfli TYPE TABLE OF spfli WITH HEADER LINE.
DATA: G_CUSTOM_CONTAINER1 TYPE REF TO CL_GUI_CUSTOM_CONTAINER,
      GRID1 TYPE REF TO CL_GUI_ALV_GRID,
      it_cat TYPE LVC_T_FCAT,
      wa_cat TYPE LVC_S_FCAT.
START-OF-SELECTION.
SELECT * FROM spfli
           INTO TABLE it_spfli.
perform INITIAL_GRID.
form INITIAL_GRID.
PERFORM create_field_catalog.
PERFORM create_grid_control.
endform.                 " INITIAL_GRID OUTPUT
FORM create_field_catalog .
IF it_cat[] is initial.
    clear wa_cat.
    wa_cat-col_pos   = 1.
    wa_cat-fieldname = 'CARRID'.
    wa_cat-datatype = 'CHAR'.
    wa_cat-inttype   = 'C'.
    wa_cat-intlen    = 3.
    wa_cat-reptext   = 'Airline Code'.
    wa_cat-coltext   = 'Airline Code'.
    append wa_cat to it_cat.
    clear wa_cat.
    wa_cat-col_pos   = 2.
    wa_cat-fieldname = 'CONNID'.
    wa_cat-datatype = 'NUMC'.
    wa_cat-inttype   = 'N'.
    wa_cat-intlen    = 4.
    wa_cat-reptext   = 'Flight Conn. No'.
    wa_cat-coltext   = 'Flight Conn. No'.
    append wa_cat to it_cat.
    clear wa_cat.
    wa_cat-col_pos   = 3.
    wa_cat-fieldname = 'CITYFROM'.
    wa_cat-datatype = 'CHAR'.
    wa_cat-inttype   = 'C'.
    wa_cat-intlen    = 20.
    wa_cat-reptext   = 'Dep. city'.
    wa_cat-coltext   = 'Dep. city'.
    append wa_cat to it_cat.
    clear wa_cat.
    wa_cat-col_pos   = 4.
    wa_cat-fieldname = 'AIRPFROM'.
    wa_cat-datatype = 'CHAR'.
    wa_cat-inttype   = 'C'.
    wa_cat-intlen    = 3.
    wa_cat-reptext   = 'Dep. airport'.
    wa_cat-coltext   = 'Dep. airport'.
    append wa_cat to it_cat.
    clear wa_cat.
    wa_cat-col_pos   = 5.
    wa_cat-fieldname = 'CITYTO'.
    wa_cat-datatype = 'CHAR'.
    wa_cat-inttype   = 'C'.
    wa_cat-intlen    = 20.
    wa_cat-reptext   = 'Arrival city'.
    wa_cat-coltext   = 'Arrival city'.
    append wa_cat to it_cat.
    clear wa_cat.
    wa_cat-col_pos   = 6.
    wa_cat-fieldname = 'AIRPTO'.
    wa_cat-datatype = 'CHAR'.
    wa_cat-inttype   = 'C'.
    wa_cat-intlen    = 3.
    wa_cat-reptext   = 'Dest. airport'.
    wa_cat-coltext   = 'Dest. airport'.
    append wa_cat to it_cat.
ENDIF.
ENDFORM.                    " create_field_catalog
*&      Form create_grid_control
      text
--> p1        text
<-- p2        text
FORM create_grid_control .
IF G_CUSTOM_CONTAINER1 is initial .
    CREATE OBJECT G_CUSTOM_CONTAINER1
           EXPORTING CONTAINER_NAME = 'CUSTOM1'.
    CREATE OBJECT GRID1
           EXPORTING I_PARENT = G_CUSTOM_CONTAINER1.
    CALL METHOD GRID1->SET_TABLE_FOR_FIRST_DISPLAY
     EXPORTING
       I_BUFFER_ACTIVE               =
       I_BYPASSING_BUFFER            =
       I_CONSISTENCY_CHECK           =
       I_STRUCTURE_NAME              =
       IS_VARIANT                    =
       I_SAVE                        =
       I_DEFAULT                     = 'X'
       IS_LAYOUT                     =
       IS_PRINT                      =
       IT_SPECIAL_GROUPS             =
       IT_TOOLBAR_EXCLUDING          =
       IT_HYPERLINK                  =
       IT_ALV_GRAPHICS               =
       IT_EXCEPT_QINFO               =
       IR_SALV_ADAPTER               =
      CHANGING
        IT_OUTTAB                     = it_spfli[]
        IT_FIELDCATALOG               = it_cat[]
       IT_SORT                       =
       IT_FILTER                     =
      EXCEPTIONS
        INVALID_PARAMETER_COMBINATION = 1
        PROGRAM_ERROR                 = 2
        TOO_MANY_LINES                = 3
        others                        = 4
    IF SY-SUBRC <> 0.
      MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
                 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
ENDIF.
ENDFORM.                    " create_grid_control
In contrast, if you use function "Reuse_Alv_List_Display" it works without any screens.

Hi
If you wish to go with OO approach to ALV Grid you can use the CL_SALV class.
Here you do not need to create the screen.
TYPES: BEGIN OF ty_kna1,
        kunnr TYPE kunnr,
        name1 TYPE name1_gp,
        land1 TYPE land1_gp,
       END OF ty_kna1,
       ty_t_kna1 TYPE TABLE OF ty_kna1.
DATA: t_kna1       TYPE TABLE OF ty_kna1,
      r_salv_table TYPE REF TO cl_salv_table,
      r_display    TYPE REF TO cl_salv_display_settings,
      r_columns    TYPE REF TO cl_salv_columns_table.
START-OF-SELECTION.
** Fetch Data
SELECT kunnr
         name1
         land1
    FROM kna1
    INTO TABLE t_kna1
    UP TO 25 ROWS.
CALL METHOD cl_salv_table=>factory
* EXPORTING
*    list_display   = if_salv_c_bool_sap=>true
*    r_container    =
*    container_name =
    IMPORTING
      r_salv_table   = r_salv_table
    CHANGING
      t_table        = t_kna1.
r_columns = r_salv_table->get_columns( ).
r_columns->set_optimize( ).
r_display = r_salv_table->get_display_settings( ).
r_display->set_striped_pattern( value = 'X' ).
r_salv_table->display( ).
Edited by: SAP LEARNER on Apr 6, 2011 4:56 PM

Is it possbile to create ALV Grid using Class & without using SE51

Is it possible to create a alv grid using Class, with out using the screen painter(SE51).

Hi Preethi,
It is possible to creat ALV grid using class, provided u have to create a custom control in the screen dialog.
Try with the foll code. This is an example for flight detail.
DATA: container TYPE REF TO cl_gui_custom_container,
      alv_con TYPE REF TO cl_gui_alv_grid.
data : it_sflight like table of wa with header line,
       g_fieldcat type lvc_t_fcat.
/* Paste the code the PBO
    CREATE OBJECT container
      EXPORTING
        container_name              = 'C_SPFLI'. "Specify the container name which u created in the dialog screen.
    CREATE OBJECT alv_con
      EXPORTING
        i_parent          = container.
/* Use the foll. to dislay the report
CALL METHOD cl_grid->set_table_for_first_display
        EXPORTING
         I_STRUCTURE_NAME              = 'SFLIGHT'
        CHANGING
          it_outtab                     = it_sflight[]
          IT_FIELDCATALOG               = g_fieldcat.
First create the container and then place the ALV in the container and for dislaying pass the necessary table.
Hope this will useful for u.
Get back if u r unable to do it.
Regards
Router

Is it possible to run alv grid in background

Similar Messages

Maybe you are looking for