Report layout - ME2N - Automatic background job

HI all
We are using the above report for Pending PO-RElease ie., dynamic selection - release indicator "B" thru automatic background programme schedueld thru SM36 (after setting the variant) for the relevant/concerned users.
The issue is, the report layout be default standard sap layout is taking, actually i have saved layout as PO no & date, but always, whenever background job is run, default sap report is taken in HTML.
request kindly help how i can ensure my our report layout for backgrounds jobs thru ME2N or is there any other report which can give the pending PO-Release report for my requirement.
thanks in advance
regards
srihari

I am doing same as suggested by you for all other reports, but i am not successful with ME2N, because after having your own default layout, but for background it is default taking sap report. even i have tried to delete the sap - std report format but not allowed.
if any one knows how to change the sap-default std report layout then also it's okay for us, as default report as 15 columns whereas we need only max 5 columns in report layout
thanx in advance
regards
srihari

Similar Messages

Job failure ( report RFFDKU00 scheduled for background job)

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

note 167301 might help.

Spool report line width in background jobs

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

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

Report to cancel released background jobs

Hi Folks,
Can anyone guide me whether there is any standard report/program where i can delete/cancel the background jobs already released/scheduled? We can cancel individual job using SM37, but i need to cancel "n" number of jobs at one slot.
Thanks in advance.
Regards,
Shiva

Siva,
can plz tell me how to change or reschedule the time on background job ?
Dilip

Emailing the report to external email - Background job

HI
We are creating background job for running the report in background...but i want the output(report) to send an email in Excel format after the job run successfully...
Here the email is External email not SAP inbox..
Do you have any idea how to achieve this? any user-exit or even handling will help this?
Please let me know
Thanks
Govi

Iam not using custom program to send the email...I know about the FM SO_DOCUMENT_SEND_API1...to send email.
My requirement is to send email to user the report in Excel after the background job runs.
we will define the job in SM36 with variant for the report with program name and variant.
after the job runs the spool request will be created and we can also setup the output of the report to be sent to SAP inbox.
my question is to how to send the output of this report in Excel format to external email i.e. Gmail, yahoo etc...
I hope u r clear now...
Please let me know if you know the answer.
Thanks

Automatic Background Jobs Monitoring

Hi,
I'd like to ask how to setup an alert to the background job if it fails to run. How is it done in K1P box?
What I'd like to happen is to have a message sent out to the jobs owner it encountered any problems. I work in the Support Team and I'd like my team be informed automatically (via email or anything) without contacting the K1P box Owner.
Hope someone can help me here.
Thanks,

Hi,
You can create a query using SQ1. Tables you need are /SAPAPO/LISMAP and /SAPAPO/LISLOG. The query can help you to sort or order the jobs based on the status message type and many other parameters.
Best Regards,
Ivo Stoyanov

How to pass layout variant in background job?

Dear Gurus,
I have set layout variant as PARAMETERS in my program.
The report will be executed successfully in front-end, but if I set it in background , it will pop up error msg: Program (IS_VARIANT-REPORT) not specified.
But the alv function I have check...
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
    EXPORTING
      I_BYPASSING_BUFFER       = 'X'
      I_CALLBACK_PROGRAM       = W_REPID
      I_GRID_TITLE             = V_GRID_TITLE
      I_CALLBACK_PF_STATUS_SET = 'SET_PF_STATUS'
*      I_CALLBACK_USER_COMMAND = 'FORM_USER_COMMAND'
*      I_STRUCTURE_NAME         = 'ZSDS0005'
      I_SAVE                   = 'A'
      IS_LAYOUT                = I_LAYOUT
*      IS_VARIANT               = STRU_DISVAR
      IS_VARIANT               = DEF_VARIANTE_F4
      IT_FIELDCAT              = I_FIELDCAT_ALV[]
      IT_SORT                  = XT_SORT[]
    TABLES
      T_OUTTAB                 = IT_OUT
    EXCEPTIONS
      PROGRAM_ERROR            = 1
      OTHERS                   = 2
Jamie

Thank you so much, but the sample code have one bug, and I have already modified the code.
The variant will be caught only after clicking F4 list, if there's already one default variant, system will ignore it.
AT SELECTION-SCREEN.
* Validating selection screen fields
PERFORM F_AT_SELECTION_SCREEN.
*&      Form f_at_selection_screen
*       text
* --> p1        text
* <-- p2        text
FORM F_AT_SELECTION_SCREEN .
* ALV Layout variant
IF NOT P_VARI IS INITIAL.
    MOVE GX_VARIANT TO G_VARIANT.
    MOVE P_VARI          TO G_VARIANT-VARIANT.
    CALL FUNCTION 'REUSE_ALV_VARIANT_EXISTENCE'
      EXPORTING
        I_SAVE     = 'A'
      CHANGING
        CS_VARIANT = G_VARIANT.
    GX_VARIANT = G_VARIANT.
ELSE.
    PERFORM F_INITIALIZE_VARIANT.
ENDIF.
ENDFORM.                    " f_at_selection_screen
*&      Form f_initialize_variant
*       text
* --> p1        text
* <-- p2        text
FORM F_INITIALIZE_VARIANT .
* CLEAR DEF_VARIANTE_F4.
* gv_save           = 'X'.
GX_VARIANT-REPORT = SY-REPID.
* DEF_VARIANTE      = DEF_VARIANTE_F4.
CALL FUNCTION 'REUSE_ALV_VARIANT_DEFAULT_GET'
    EXPORTING
      I_SAVE     = G_SAVE
    CHANGING
      CS_VARIANT = GX_VARIANT
    EXCEPTIONS
      NOT_FOUND = 2.
IF SY-SUBRC = 0.
    P_VARI = GX_VARIANT-VARIANT.
ENDIF.
ENDFORM.                    " f_initialize_variant

BAP Log/Error Report in case of Background Job

Hi Friends,
I have to develop one program where I am creating purchase orders using BAPI. This Program would be scheduled in background
hence the Error/log report can not be seen .I have been told to use SAP Application Log for getting the Error Report.
How this can be achieved using SAP Application log functionality. Any Help would be appreciated.
Thanks

>
TANGO18 wrote:
> I have to develop one program where I am creating purchase orders using BAPI. This Program would be scheduled in
> background hence the Error/log report can not be seen .
Incorrect. How are you displaying your error / log report ?
Even if you use simple WRITE statements to display the log, the details would be there in the corresponding spool generated.
BR,
Suhas

Download alv report using layout variant in background

Hi All,
I want to download an Alv report using layout varaint in background job.
can any one please help me.
i.e...
I am facing a problem in downloading a text file to the Application server.
My requirement is, when the user downloads a file with the layout variant, the file should have only the columns which was selected in the variant.
Will rewards to helpfull ans
regards
Chetan

hey seshu,
I am facing a problem in downloading a text file to the Application server.
My requirement is, when the user downloads a file with the layout variant, the file should have only the columns which was selected in the variant.

Is it possible to save a report to a file in background job?

Hi,
I want to save a report as a file every day, is it possible to do it by background job?
Thanks.

thanks all of you,
I don't went to save the file manually.
I only want to a function just like archiving function which can save file in background job.
I can develop a program to save a report as file in background job,but I have to develop a program for every report,I want to know is there any standard function for it, just like throwing the report to spool.

Background Job Scheduling

Hi,
I am scheduling a report to run in background.
In this report it is creating background jobs automatically for different company codes.
It submits the 1st background job and waits until it finishes.
Then 2nd job starts in background and continues with other jobs.
At end it finishes all the jobs and closes.
Now my problem is.
1.       Whether is it possible for us to submit all the jobs at 1 time. And execute at same time. Ie., 1st, 2nd job will start at same time.
2.       If possible how can we do that.
What I have written is
loop at companycode.
Create job name.
call fun 'Job_Open'.
submit xxxx user sy-uname via job job_name numer job_count
to sap-spool
spool parameters l_spool_parameter
without spool dynpro
with companycode
with ......
and return.
endloop.
Please help ASAP, urgent.

hi praveen,
Job Scheduling Explained
Definition
Before any background processing can actually begin, background jobs must be defined and scheduled. The scheduled time for when a job runs is one part of the jobs definition. There are several ways to schedule jobs:
From Transaction SM36 (Define Background Job)
With the "start program in the background" option of either Transaction SA38 (ABAP: Execute Program) or Transaction SE38 (the ABAP editor)
Through the background processing systems own programming interface. (Many SAP applications use the internal programming interface to schedule long-running reports for background processing.)
Through an external interface.
Scheduling Background Jobs
Use
You can define and schedule background jobs in two ways from the Job Overview:
·         Directly from Transaction SM36. This is best for users already familiar with background job scheduling.
·         The Job Scheduling Wizard. This is best for users unfamiliar with SAP background job scheduling. To use the Job Wizard, start from Transaction SM36, and either select Goto ® Wizard version or simply use the Job Wizard button.
Procedure
       1.      Call Transaction SM36 or choose CCMS ® Jobs ® Definition.
       2.      Assign a job name. Decide on a name for the job you are defining and enter it in the Job Name field.
       3.      Set the jobs priority, or Job Class:
·         High priority:      Class A
·         Medium priority: Class B
·         Low priority: Class C
       4.      In the Target server field, indicate whether to use system load balancing.
·         For the system to use system load balancing to automatically select the most efficient application server to use at the moment, leave this field empty.
·         To use a particular application server to run the job, enter a specific target server.
       5.      If spool requests generated by this job are to be sent to someone as email, specify the email address. Choose the Spool list recipient button.
       6.      Define when the job is to start by choosing Start Condition and completing the appropriate selections. If the job is to repeat, or be periodic, check the box at the bottom of this screen.
       7.      Define the jobs steps by choosing Step, then specify the ABAP program, external command, or external program to be used for each step.
       8.      Save the fully defined job to submit it to the background processing system.
       9.      When you need to modify, reschedule, or otherwise manipulate a job after you've scheduled it the first time, you'll manage jobs from the Job Overview.
Note: Release the job so that it can run. No job, even those scheduled for immediate processing, can run without first being released.
Specifying Job Start Conditions
Use
When scheduling a background job (either from Transaction SM36, Define Background Job or CCMS ® Jobs ® Definition), you must specify conditions that will trigger the job to start.
Procedure
Choose the Start condition button at the top of the Define Background Job screen.
Choose the button at the top of the Start Time screen for the type of start condition you want to use (Immediate, Date/Time, After job, After event, or At operation mode) and complete the start time definition in the screen that appears.
For the job to repeat, check the Periodic job box at the bottom of the Start Time screen and choose the Period values button below it to define the frequency of repetition (hourly, daily, weekly, monthly, or another specific time-related period). Then choose the Save button in the Period values screen to accept the periodicity and return to the Start Time screen.
Once youve completed specifying the job start conditions, choose the Save button at the bottom of the Start Time screen to return to the Define Background Job screen.
No job can be started until it is released, including jobs scheduled to start immediately. Since releasing jobs can be done only by a system administrator from the job management screen (Transaction SM37) or by other users who have been granted the appropriate Authorizations for Background Processing, no unauthorized user can start a job without explicit permission
Managing Jobs from the Job Overview
Use
The Job Overview, or Job Maintenance, screen is the single, central area for completing a wide range of tasks related to monitoring and managing jobs, including defining jobs; scheduling, rescheduling, and copying existing jobs; rescheduling and editing jobs and job steps; repeating a job; debugging an active job; reviewing information about a job; canceling a job's release status; canceling and deleting jobs; comparing the specifications of several jobs; checking the status of jobs; reviewing job logs; and releasing a job so it can run.
Procedures
To display the Job Overview screen, choose CCMS ® Jobs ® Maintenance or call Transaction SM37. Before entering the Job Overview screen, the system first displays the Select Background Jobs screen. You'll need to complete this Job Selection screen to define the criteria for the jobs you want to manage. Once you've selected jobs to manage, you can choose from a wide range of management tasks:
To copy a single existing job, choose Job ® Copy.
To reschedule or edit job steps or attributes of a single job, choose Job ® Change. A job step is an independent unit of work within a background job. Each job step can execute an ABAP or external program. Other variants or authorizations may be used for each job step. The system allows you to display ABAP programs and variants. You can scan a program for syntax errors. You can also display the authorizations for an authorized user of an ABAP job step.
To repeat a single job, choose Job ® Repeat scheduling.
To debug an active job, choose Job ® Capture: active job. Only a single selection is allowed. If an active job seems to be running incorrectly (e.g., running for an excessively long time), you can interrupt and analyze it in debugging mode in a background process, and then either release it again or stop it altogether.
You will be able to capture a background job only if you are logged on to the SAP server on which the job is running. To find server information in the Job Overview, select and mark the job, then choose Job ® Job details.
To review information about a job, choose Job ® Job details. Details displayed can include:
current job status
periodicity, or the repetition interval
other jobs linked to the current job, either as previous or subsequent jobs
defined job steps
spool requests generated by the current job
To cancel a job's "Released" status, select the job or jobs from the Job Overview list and choose Job ® Release -> Scheduled.
To cancel a job from running but keep the job definition available, select the job or jobs from the Job Overview list and choose Job ® Cancel active job.
To delete a job entirely, select the job or jobs from the Job Overview list and choose Job ® Delete. Jobs with the status of Ready or Running cannot be deleted.
To compare the specifications of more than one job, select the jobs from the Job Overview list and choose Job ® Compare jobs.
To check the status of jobs, select the job or jobs from the Overview Job list and choose Job ® Check status. This allows you to either change the job status back to Planned or cancel the job altogether. This is especially useful when a job has malfunctioned.
To review job logs, select a job or jobs with the status Completed or Canceled from the Job Overview list and
regards
karthik
reward me points if helpfull

Class (Priority) change in the background job

Hi,
We have a program which will pick up the file from application server and will submit to one more background job by using JOB_SUBMIT. Whenever the automatic background job has submitted from another program, by default it will take the class (priority) as 'C'. Is there any way to change the priority level from C to A throuhg JOB_SUBMIT i.e changing to higher level.
Please let me know.
regards,
Chandra
null

(1) Keep in memory that class "A" job must be reserved for system
(2) Nevertheless
The class is hard-coded in JOB_OPEN:
* Jobklasse setzen / NEWFLAG auf 'O'(Open) setzen
* (der Workflow-Job 'SWWDHEX_' bekommt immer Jobklasse A).
* Weiterhin bekommt ein spezieller Einplaner immer Jobklasse A
* wg. der Archivierung auf Datenbankhosts (->F.Hoffmann).
IF ( JOBNAME EQ 'SWWDHEX' ) OR ( CALLING_ABAP EQ CENTRAL_ADK_ABAP ).
GLOBAL_JOB-JOBCLASS = BTC_JOBCLASS_A.
ELSE.
GLOBAL_JOB-JOBCLASS = BTC_JOBCLASS_C.
ENDIF.
You may look at function modules BAPI_XBP_JOB_OPEN, BAPI_XBP_JOB_ADD_ABAP_STEP and BAPI_XBP_JOB_CLOSE.
(documentation at <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/edab9790-0201-0010-479a-98fcc7ebc7bd">External Interface for Background</a>)
Regards

Background job scheduling in idocs

Hi can u plz tell me like for a customized function module inorder to post and idoc .
variant should be created for function module or how does it go becoz we process the idoc through transaction we19?

In the receiving system, set inbound processing to Processing in background in the partner profiles with transaction WE20.
Schedule Report RBDAPP01 as a Background Job to process the IDocs (see also SAP Note 399271).
The report passes all inbound IDocs to the application for processing, if they meet the selection criteria, and have the following status:
Status 64, IDoc is ready for transfer to the application
Status 66, IDoc is waiting for preceding IDoc (Serialization).
http://help.sap.com/saphelp_sm32/helpdata/en/5f/45f93b4139b478e10000000a11402f/content.htm
Thanks

Schedule a report to run in background

Hi all,
I have a report that has a selection screen .
When i schedule this report as a background job , it is cancelled : "cannot perform frontend function in batch input mode " ??
I created a variant and in the job step specified the variant name ...!! would appreciate if anyone can tell how to schedule the report to run as background job ?

Hi,
Ok in this case there can be too options.
1) either take file from the shared network and put it in your presentation server and then take it into application server ( this is manual by using CG3z)and then execute your program in background
2) or you will have to code using FTP commands
First connect using FM FTP_COMMAND. you will ahve to use commands like mget etc
Once connected then pass command using FM
FTP_COMMAND
Then get the files Data into Internal table via FTP server which can be done using
FM FTP_SERVER_TO_R3
once done use the back ground processing
Make sure that there is R/3 connection mainained using SM59.

Get background job detail

Hi All,
I have created a report and created a background job for this. In another program I want to check whether an active/scheduled job of the first report exist or not?
How to solve this problem??
Regards,
Jeetu

Hi,
Use the Function module
BP_FIND_JOBS_WITH_PROGRAM
Check the output table
JOBLIST (Structure TBTCJOB)
It will have all the job details
Just pass the program name
Regards
Edited by: Rajvansh Ravi on Dec 9, 2008 7:11 AM

Report layout - ME2N - Automatic background job

Similar Messages

Maybe you are looking for