WMS related background running job reports

Hi All,
Anyone could help to list all the WMS/Shipping/TMS related background jobs' reports?
such as:
1. create the TO -> RLAUTA10;
Thank you very much,

Hi,
Very easy, go to se38 and enter RL*. You will then see all WM related reports.
MdZ

Similar Messages

Problem of background running of report

Hello folks,
I have one report,which updates Z table(CUSTOM TABLE).when i run this program in foreground ztable(CUSTOM TABLE) updation takes place and output is correct.But when i run this program in BACKGROUND ,THAT Z TABLE(Custom table) can not be updated and all problem starts from there.I have used "COMMIT STATEMENT " TO UPDATE THE ZTABLE IMMEDIATLY.tHIS STATEMENT IS CAUSING ANY PROBLEM?PLEASE HELP ME.

Hi Nirad,
while updating to ensure that nobody are using the table you can lock the lock by using SAP locking mechanisam.
for this you create a lock object in ABAP Dictionary.A lock object contains the database table for which you want to specify a shared lock. When you activate the lock object obj , this generates two function modules with the names ENQUEUE obj and DEQUEUE obj. These function modules perform the explicit locking or releasing of SAP locks in an ABAP program.
call function ENQUEUE obj before updating the table and DEQUEUE obj before commit.To formulate a lock condition, you have to specify values for the primary key fields of the table contained in the lock object in the function modules.
Please reward points if you find this useful.

Run the Report as a Background job and Get the Output in Excel in Local PC

Hello Gurus,
I have one following requirement.
One should be able to run the report as a background job and it should be possible to get the report in Excel format, also when running the report in background. The excel report should have the same information and look as the current SAPreport.
Please provide some solution.
Any helpful answer get surely awarded.
Thanks a lot,
Varlanir

GUI_* WS_* Function In Background, CSV Upload
GUI_* and WS_* function modules do not work in background
When scheduling a job in the background the appropriate statement to read in your file is OPEN DATASET, and the file must be on the file system that the SAP server can see.
At anytime, a user can switch of the Personal Computers even though the job is still running in the background. Therefore GUI_* and WS_* function modules are not designed to work in that way, as they need to access your personal computer file.
To choose the correct download method to used, you can check the value of SY-BATCH in your code,
if it is 'X' use OPEN DATASET and if it is ' ' use WS_UPLOAD.
*-- Open dataset for reading
DATA:
dsn(20) VALUE '/usr/test.dat',
rec(80).
OPEN DATASET dsn FOR INPUT IN TEXT MODE.
IF sy-subrc = 0.
DO.
 READ DATASET dsn INTO rec.
 IF sy-subrc <> 0.
 EXIT.
 ELSE.
 WRITE / rec.
 ENDIF.
ENDDO.
ENDIF.
CLOSE DATASET dsn.
*-- Open dataset for writing
DATA rec(80).
OPEN DATASET dsn FOR OUTPUT IN TEXT MODE.
TRANSFER rec TO '/usr/test.dat'.
CLOSE DATASET dsn.
What is the difference when we use upload, ws_upload, gui_upload function modules?
UPLOAD, WS_UPLOAD, GUI_UPLOAD, are used in BDC concepts. ie., Batch Data Communication.
Batch Data Conversion is a concept where user can transfer the Data from non SAP to SAP R/3. So , in these various Function Modules are used.
UPLOAD--- upload a file to the presentation server (PC)
WS_UPLOAD---- Load Files from the Presentation Server to Internal ABAP Tables.
WS means Work Station.
This is used upto SAP 4.6 version.
GUI_UPLOAD------- Replaces WS_UPLOAD. Upoad file from presentation server to the app server. From 4.7 SAP version it is replaced.
How to Upload csv file to SAP?
Common File Download Upload Questions:
How you upload the data from text file to sap internal table? From my knowledge its by upload or gui_upload.
How you download the data from sap internal table to text file?
How you upload the data from xls (excel) file to sap internal table how you download the data from sap internal table to xls(excel) file.
You can upload data from presentation server to an internal table using gui_upload. Use gui_download to download from internal table to flat file.
Use fm ALSM_EXCEL_TO_INTERNAL_TABLE to upload data frm excel.
Use function module GUI_UPLOAD
The FILETYPE refer to the type of file format you need: For e.g 'WK1' - Excel format , 'ASC' - Text Format etc.
CALL FUNCTION 'GUI_UPLOAD'
EXPORTING
 FILENAME = 'C:\test.csv'
 FILETYPE = 'ASC'
TABLES
 DATA_TAB = itab
EXCEPTIONS
 FILE_OPEN_ERROR = 1
 FILE_READ_ERROR = 2
 NO_BATCH = 3
 GUI_REFUSE_FILETRANSFER = 4
 INVALID_TYPE = 5
 NO_AUTHORITY = 6
 UNKNOWN_ERROR = 7
 BAD_DATA_FORMAT = 8
 HEADER_NOT_ALLOWED = 9
 SEPARATOR_NOT_ALLOWED = 10
 HEADER_TOO_LONG = 11
 UNKNOWN_DP_ERROR = 12
 ACCESS_DENIED = 13
 DP_OUT_OF_MEMORY = 14
 DISK_FULL = 15
 DP_TIMEOUT = 16
 OTHERS = 17.

CNTL_ERROR while running a report in background mode

Hi,
I am running a report in background on daily basis. I am using cl_gui_custom_container class here and calling the constructor of this class. I am getting a CNTL_ERROR exception at this point. But if i run the same report directly, it is not throwing any exception. The problem is if i schedule it to background. I am not able to sort it out. So please if any body knows, answer this.
Thanks,
Kumar

Hi Nithin,
I was facing the similar issue in a custom report program. I did apply the logic that you'd mentioned.
I've implemented the code as below.
IF gr_container IS INITIAL.
*** Check whether the program is run in batch or foreground
    IF CL_GUI_ALV_GRID=>OFFLINE( ) IS INITIAL.
* Run in foreground
      CREATE OBJECT gr_container
        EXPORTING
          container_name = 'WORK_AREA_CONTAINER'.
      CREATE OBJECT lv_grid
        EXPORTING I_PARENT = gr_container.
    ELSE.
* Run in background
      CREATE OBJECT lv_grid
        EXPORTING
          I_PARENT = gr_dockcontainer.
      ENDIF.
      ENDIF.
i_parent_control = gr_dockcontainer.
        CREATE OBJECT m_base_splitter
        EXPORTING
          parent            = i_parent_control
          ROWS              = 1
          columns           = 2
        EXCEPTIONS
          cntl_error        = 1
          cntl_system_error = 2
          OTHERS            = 3.
        CALL METHOD m_base_splitter->get_container
        EXPORTING
          row       = 1
          column    = 2
          RECEIVING
          container = m_splitter_right_part
        EXCEPTIONS
          OTHERS    = 1.
After I've implemented the above code I'm getting the following error in the batch job:
Category               ABAP Programming Error
Runtime Errors         OBJECTS_OBJREF_NOT_ASSIGNED
Except.                CX_SY_REF_IS_INITIAL
You attempted to use a 'NULL' object reference (points to 'nothing')
access a component (variable: "M_BASE_SPLITTER").
An object reference must point to an object (an instance of a class)
before it can be used to access components.
Either the reference was never set or it was set to 'NULL' using the
CLEAR statement.
Would you be able to help me in the above issue?

How to run GR55 reports in background for cost center hierarchies

1. I have been asked by our users to create batch jobs to run in the background for some GR55 reports, that can then be sent directly to cost center managers via email.
I have figured out the process to do this as long as the cost center manager only needs to see a single cost center at a time. However, if they are in charge of multiple cost centers, we also want to send them a summarized report using the hierarchy we have set up. I can't seem to make this work, as the job only seem to recognize the last cost center in the group and the report is for that cost center.
Example. cost centers 100, 200 and 300 belong to hierarchy abc. If I run the job just for cost center 100 it is fine. But if I have a variant to run hierarchy abc, or even if I use the range 100 to 300, all I get is a report for cost center 300.
We cannot use BW because we only have revenue in BW. I am being asked to make this work from standard R/3 within the GR55 realm of reporting.
2. In addition, the report selection criteria includes two separate plan/forecast versions. They need to update these each month prior to running the reports and sending them out. I looked at the variables associated with the versions and tried to set them up with default values that I hoped would update automatically so that they don't have to manually change 50 or so variants each month. But I don't see any dynamic variables that I can use to have the system make that change without going into each variant individually.
3. There is another piece to this equation as well. There is another report they want sent out in batch, but it is several pages wide in SAP and several pages long. So when you run it in batch and either spool it or get it sent as an email, it is very ugly in the formatting due to all the page splits horizontally and vertically. If anyone knows how to get the report to stay together like it would if you had excel integration turned on, it would be very helpful. I have tried running it with that integration turned on, but the jobs are set up with user batch_mgr and not my id, so it isn't working well. The batch_mgr id is just a system id, not a dialog id. We also don't want the jobs set up with a regular user id because if people leave, then the jobs all need to be changed.

Kim,
I may have options for issues 1 and 2. In case of 3, what I can tell you is I understand the concern, but this is what typically happens in some standard CO reports that are not ALV compatible, I don't think there is not much there to do unless you add some custom code for the output.
In regards to point 1, yes, I have noticed that this happens in some standard and custom reporting, not sure what is going on. I came up with a work around that made the trick for my client in a similar scenario; which is editing the cost center groups. For instance, instead of having the group set as a range from 100 to 300, the groups are have listed the cost centers, 100, 200 and 300. Obviously, the disadvantage of this option is that it would require a bit of more cost center group maintenance.
In regards to point 2, I understand from your note that your users already have set up selection variants for the report. One option for you is to get the help from a developer to create a custom period variable and tiny program that runs in batch every month that would update that variable accordingly. Once that's done, you may have to update at least once, the selection variant attributes to change the period to a selection variable, so everytime from that point of time forward that the variable gets updated, it will be ready with the right value for every selection variant that uses it.
Hope this helps.
GG

Background job report printout

Hi all,
we are facing the spool issue with background scheduling and foreground.
If i run any report in foreground, the printout is coming in one page perfectly but if we scheduled the report in background, printouts are splitted into different pages.
i want the printout should be come in one page after completing the background job. please give your suggestions.
regards
Ramesh
Edited by: Ramesh Sammiti on Nov 5, 2009 8:09 AM

Hi Manoj
At present we are scheduling reports through background job. Every 65 lines(rows) the data like column names and headers are repeating in every page. i do not require this column names. The entire data should be displayed in single page without any names etc.,
my requirement
i want to print 1000 rows in a page without any page breaks. For this what are the steps i need to take care. please help me
regards
Ramesh
Edited by: Ramesh Sammiti on Dec 7, 2009 11:45 AM
Edited by: Ramesh Sammiti on Dec 7, 2009 11:46 AM
Edited by: Ramesh Sammiti on Dec 7, 2009 11:56 AM

Authorization object for running a report in background

Good day experts,
I tried running a report in background, I choose immediately so that it doesn't have to be scheduled. But when I checked it in my own jobs, It remains at scheduled status. When I tried it on my admin account, It works and with status finished. It seems to be an authorization problem. What object could I be missing with my user account? I tried S_TCODE SMX and SP02 but still not working.
Thanks in advance!

Hi karshbax,
What you're looking for is authorization object S_BTCH_JOB. You need authorization for field JOBACTION = RELE.
In future use transaction SU53. It shows last error authorization error, so if this is authorization problem then after try of manual releasing of job you'll find in SU53 precise info what went wrong.
Best Regards
Marcin Cholewczuk

To run a report in background in selection screen using a new button

hi friends iam new member to this site
nice to meet u all
i want to run a report in background using the selection screen of the same report and i want to keep a button in application tool bar.
after enter the values in the selection screen by clicking that button it should move to the screen which we get generally by menu option
program-->execute in background
and by entering the output device and start condition it should be scheduled in the background.
with job_open,job_submit and job_close we need variants.
for this i tried through bp_jobvariant_schedule and
bp_jobvariant_overview but with this we can run with variants only
but the user wants to enter the values in selection screen and need a button to run background
ok friends i think u understood me
please inform soon ok bye have a nice time

Hi Jagadish
There are two ways for you to handle the situation.
1. Train the users to enter the values in selection screen and manually go for backgroung scheduling.
2. Use At user command and within that basing on the option selection selected, use FM:JOB_OPEN with sy-repid get the job number, submit the program with the values on the selection screen and lastly executing FM: JOB_CLOSE with the job number from JOB_OPEN and SY-REPID.
Note that you have to set 'X' for export parameter something like startimmed while calling FM: JOB_CLOSE for immediate execution. Am not on SAP to give you the exact parameter.
Hope the above info helps you.
Kind Regards
Eswar

How to Run a Report automatically in Background for every night

Hi,
How to run a report program in Background automatically for every nigh.
Thanks
Ramesh

Hi Ramesh,
You can use SM36 and use the "Job Wizard" to define a background job in simple step by step procedure
Or
Goto SM37 and specify a job name.
Next specify the ABAP Program Name of the report you want to execute under Job Step.
Then click on "Extended Job Selection" and goto the Period Tab.
There select "Only Periodic Jobs" and then specify the frequency of execution based on Months, Weeks, Days, Hours or Minutes.
Hope this helps,
Regards,
Madhur
Message was edited by: Madhur Chopra

[REPORT][How to run a report in background?]

Hi there!
I'm with a problem here. How do I make a report run background always, without the interaction of the user to select this type of execution?
Thanks in advance.

Hi
U can create a new report to run it in background mode:
- Open the job
CALL FUNCTION 'JOB_OPEN'
 EXPORTING
 JOBNAME = VA_JOBNAME
 IMPORTING
 JOBCOUNT = VN_JOBCOUNT
 EXCEPTIONS
 CANT_CREATE_JOB = 1
 INVALID_JOB_DATA = 2
 JOBNAME_MISSING = 3
 OTHERS = 4.
- Run the report
 SUBMIT <REPORT> USER SY-UNAME
 VIA JOB VA_JOBNAME NUMBER VN_JOBCOUNT
 WITH ....... = .......
 WITH ....... = ........ AND RETURN.
- Close the job
CALL FUNCTION 'JOB_CLOSE'
 EXPORTING
 JOBCOUNT = VN_JOBCOUNT
 JOBNAME = VA_JOBNAME
 STRTIMMED = 'X' " start immediatly
 EXCEPTIONS
 CANT_START_IMMEDIATE = 1
 INVALID_STARTDATE = 2
 JOBNAME_MISSING = 3
 JOB_CLOSE_FAILED = 4
 JOB_NOSTEPS = 5
 JOB_NOTEX = 6
 LOCK_FAILED = 7
 OTHERS = 8.
Or you create a periodic job by SM36
Max

How run a report in background process ?

Hi Experts,
I wrote a code in which I am have multiple selection screens....means in first screen there will 3 radio buttons.
So, depending upon the radio button selected, the other selction screen will be displayed...
So, here i want to run a report in background process...But in menubar im not able to find 'program'.
So, please help me this to run my report in background process.. with any simple code...
Thanks,
Rocky.

Hi,
Try to see this example and adapt it for your case:
constants :   c_jobname like tbtcjob-jobname value 'ZRFC_CM_38',
              c_jobclass like tbtcjob-jobclass value 'A',
              c_x        type c                value 'X',
              c_msgclass type arbgb            value 'ZXXXSD',
              c_error    type bapi_mtype       value 'E',
              c_status   type bapi_mtype       value 'S',
              c_msg1     type msgnr            value '177',
              c_msg2     type msgnr            value '178'.
data : v_jobcount like tbtcjob-jobcount.
ranges:
r_auart    for vbak-auart,
r_wbstk    for vbuk-wbstk,
r_mtart    for mara-mtart,
r_reswk    for ekko-reswk,
r_vtweg    for vbak-vtweg.
call function 'JOB_OPEN'
    exporting
      jobname          = c_jobname
    importing
      jobcount         = v_jobcount
    exceptions
      cant_create_job = 1
      invalid_job_data = 2
      jobname_missing = 3
      others           = 4.
if sy-subrc = 0.
Assignment of Ranges
    append lines of:
       distribution_channel to r_vtweg,
       order_type_range     to r_auart,
       status_range         to r_wbstk,
       material_type_range to r_mtart,
       plant_range          to r_reswk.
Submit program in background
    submit z_beve_salesorder_list
      with p_spart   = division
      with p_file    = file_name
      with p_land1   = country
      with s_vtweg   in r_vtweg
      with s_auart   in r_auart
      with s_wbstk   in r_wbstk
      with s_mtart   in r_mtart
      with s_reswk   in r_reswk
       via job c_jobname
    number v_jobcount
       and return.
Close the Job
    call function 'JOB_CLOSE'
      exporting
        jobcount             = v_jobcount
        jobname              = c_jobname
        strtimmed            = c_x
      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.
    Status Message
      return-type = c_status.
      message id c_msgclass
         type c_status
       number c_msg1
         into return-message
         with c_jobname
              sy-datum
              sy-uzeit.
    else.
    Error Message
      return-type = c_error.
      message id c_msgclass
         type c_error
       number c_msg2
         into return-message
         with c_jobname.
    endif.
endif.
Regards.

Running ABAP Report in background

Hello,
I am getting timed out error when I execute my report program.
I believd running the report can do it for now.
Can you please tell me detils on how I should proceed on dev, qa and production environment.
Regards,
Sameer.

Hello Sameer,
You need to schedule the ABAP program in SM36 transaction.
Following are the steps:
1. Fill general data like Job Name, Job class and click on step button from application menu
2. Fill ABAP program details on this screen like ABAP Report Name, Variant Name (If any) and save it.
3. Go to SM37 transaction (Background Job monitor)
4. On initial screen newly created job will be filtered by user name or using job name.
5. it will be listed in job queue with Scheduled status.
6. Select the Job from listing and click on Release button from application toolbar
7. depending on your requirement you can release job immediately and it will start running as an when background wp is allocated to this job.
8. Or else you can schedule it with some frequency using other options like Date/Time, or using other events to trigger it.
Check if this can help.
Thanks,
Augustin.

How to run Various Reports in background.

I want ro run the various MM MIS reports in Background.

Hi,
In the Selection Criteria of the report, Press F9 to run the reports in the background.
Set the Parameters for the Background job (Print Options & Time) and save.
To view the output of the reports executed in the background, Select from the SAP Easy Access System --> Own Spool Requests
To view the details of one of these report, simple click in the check box on the left hand side of the report you wish to view, and click on the icon in the type column.
Hope it helps.
Regards,
Bijoy Kumar

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

How to Save Background job report out put in local / Network Drive?

Hello Techies,
How to Save Background job report out put in local / Network Drive.
Actually we have option to send mail aftr complete but i need to save in local drive or network drive .

Hi ,
Background job runs in application server , and your local /network drive is basically presentation server. So you cant save it in local /network drive from the job itself. But to download files, you can write the files to the application server using DATASET, in the background and then use the transaction CG3Y in the foreground to download the file.

WMS related background running job reports

Similar Messages

Maybe you are looking for