Background job interaction

hi ,
is it possible to user interaction in background job . my requirement is after execution of program select some row and send the mail . and it should be daily basis . so if i schedule the program in background . how can user interact with program .

Hi
In case you would like to interact directly with a specific background job, you can adjust the program to wait for some parameters from SAP memory and then adjust the necessary behavior. So users can set parameters like flags during program execution and change the behavior
Best regards

Similar Messages

Background Job Processing Spool Retention period

Hi ,
In my program i am calling another ABAP program and sumitting the same as a background job(using Job_Submit,Close etc.)
In this case i can view the Spool generated by the called program(using sm37).
But this spool exists for a very less period in the system.Is it possible to specify a retention period,as 90 days in my case.?
Pls Help !!!
Answers will be rewarded.
Regards,
Rohan

hi Roahn,
You must set print parameters before the printing process starts.
When printing lists after creating them, the system uses the print format specified in the print parameters to split the completed list and fit it onto the print pages, truncating it if necessary.
When printing lists while creating them, the system uses the print format to actually format the list in the program.
Print parameters are set either interactively by the user or from within the program.
For each print process, the spool system needs a complete and consistent set of print parameters. In ABAP, the structure PRI_PARAMS (ABAP Dictionary) represent a set of print parameters.
When passing the print parameters interactively, the system displays a dialog box after starting the report, on which the user has to enter the most important print parameters.
It's shown below which input field of the Print List Output dialog window conform to which PRI_PARAMS component.
Input field----
Retention period
Component-------PEXPI
Meaning----
Number of days for which the system holds the spool request before deleting it. (Default value: 8).

Background Job RSPPFPROCESS Taking too long to execute.

Hi Gurus,
I'm working with SAP CRM 2007 - Interaction Centre
We have configured first response date and to do by date in item category.
If agent fails to response within the first response date or if agent fails to complete
to close the ticket within the to do by date,An action is configured to trigger and an
escalation email(Smart Form) is sent to agent`s manager inbox.
We have scheduled background job for the program RSPPFPROCESS with variant in background
to trigger this actions( It is scheduled 4 times in a day ).
Previously this job used to take 6 hours to complete execution.
But now its taking 12 hours to complete the execution and there is no change in the
variant.
Can anyone please advice me reason for this behavior.
Kind Regards,
Vinod

Hi Manfred,
We are experiencing similar performance issue when running the RSPPFPROCESS Job. We opened a OSS message for quite some time but didn't get any useful help from SAP.
Can you please provide more information regarding your ZRSPPFPROCESS program on identifying the crtical performance steps to resolve the performance issue? We are also thinking of archiving the record in table PPFTTRIGG , we have over 73+ millions records in the table but there is no archiving object for PPF actions. We would like to focus on reducing the number of entries in the table PPFTTRIGG hopefully to improve the performance. Any thoughts on it?
Thanks in advance for your kind help!
Best Regards,
Madeline

How to Execute WebDynpro Applications as Background Job ?

Hi Gurus,
We have developed a lot of WDJ applications with component reusage; ie,
quite a lot of business logic are wrapped in WDJ Components which are
re-used by other WD UIs.
Now we'd like to automate some of the processes with background jobs
and faced with a few problems :
#1. How can we write a background WD application which can be
triggered by external mechanism and without presenting any UI?
#2. If we write the background program in a Java DC, how can we
invoke existing methods in WD components ?
Anyone got a clue ??
Ying-Jie Chen

Hello Amit,
> Well I can think of a workaround in this case.If you are aware
> of the suspend-resume functionality of the WD application then
> its possible to run the WD application virtually in background.
[ stuffs deleted ...]
It sounds like a possible alternative to our requirement, I'll
spend some time to investigate on the WD suspend-resume mechanism !
> Also let me know why are you preffering the WD if you dont
> require its UI
Our application requires the process to be performed with UI interaction;
with some instances it should be run as a background job. Either case involves
RFC calls to backend SAP R/3 and it's easy for RFC access with WD
Component. Though it's also possible to use CAF application service for
RFC access; due to some technical constrains, we did not use CAF
framework. Therefore it ends up where we are now ...
Thanks for your tip!
Ying-Jie Chen

GETWA_NOT_ASSIGNED in RMVKON00 (background job)

Hello everyone
We're having the following recurring problem:
There's a job running the first of every month, it uses an ALV GRID with this statement: REUSE_ALV_GRID_DISPLAY.
When it's run normally (not scheduled) it works perfectly, but when it is scheduled we get a GETWA_NOT_ASSIGNED shortdump.
We have adjusted RMVKON00 (to ZRMVKON00) to add 2 columns to the ALV display by following the strategy of creating a work area and adding it to the ALV's internal table structure.
Function call Code
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
 EXPORTING
 i_buffer_active = space
 i_callback_program = c_repid
 i_callback_pf_status_set = c_pf_status_set
 i_callback_user_command = c_user_command
 i_structure_name = 'I_TAB'
 it_fieldcat = tab_fieldcat[]
 it_sort = tab_sort[]
 is_layout = s_layout
 i_save = c_save
 is_variant = s_variant
 it_events = tab_events[]
 TABLES
 t_outtab = i_tab.
I_TAB setup
TYPES: BEGIN OF watype,
 mandt LIKE rkwa-mandt,
 mblnr LIKE rkwa-mblnr,
 mjahr LIKE rkwa-mjahr,
 zeile LIKE rkwa-zeile,
 status LIKE rkwa-status,
 bldat LIKE rkwa-bldat,
 budat LIKE rkwa-budat,
 bukrs LIKE rkwa-bukrs,
 sobkz LIKE rkwa-sobkz,
 lifnr LIKE rkwa-lifnr,
 werks LIKE rkwa-werks,
 matnr LIKE rkwa-matnr,
 shkzg LIKE rkwa-shkzg,
 gsber LIKE rkwa-gsber,
 bwaer LIKE rkwa-bwaer,
 wrbtr LIKE rkwa-wrbtr,
 bstme LIKE rkwa-bstme,
 bstmg LIKE rkwa-bstmg,
 hkont LIKE rkwa-hkont,
 mwskz LIKE rkwa-mwskz,
 belnr LIKE rkwa-belnr,
 gjahr LIKE rkwa-gjahr,
 buzei LIKE rkwa-buzei,
 navnw LIKE rkwa-navnw,
 prctr LIKE rkwa-prctr,
 text LIKE zconalv-text,
 name1 LIKE lfa1-name1,
 maktx LIKE makt-maktx,
 END OF watype.
DATA: alv_itab TYPE watype.
I_TAB fill in FORM alv_list
Fill itab with current rkwa table, and add corresponding
Vendor name & Material Desc.
DATA: i_tab TYPE TABLE OF watype,
 i_tabRow TYPE watype.
LOOP AT t_alv_list.
MOVE-CORRESPONDING t_alv_list TO i_tabRow.
SELECT SINGLE name1 INTO i_tabRow-name1
FROM LFA1
WHERE lifnr = t_alv_list-lifnr.
SELECT SINGLE maktx INTO i_tabRow-maktx
FROM MAKT
WHERE matnr = t_alv_list-matnr.
INSERT i_tabRow INTO TABLE i_tab.
This is an extract of the shortdump:
Transaction......... " "
Program............. "SAPLKKBL "
Screen.............. "SAPLKKBL 0500"
Screen line......... 3
Information on where termination occurred
The termination occurred in the ABAP/4 program "SAPLKKBL " in
"CHECKBOX_OUT".
The main program was "ZRMVKON00 ".
The termination occurred in line 1148
of the source code of program "LKKBLF01 " (when calling the editor 11480).
The program "SAPLKKBL " was started as a background job.
Any help is much appreciated.
Edit: shortdump extract added
Message was edited by: Tim Schraepen

I have found the thing that was causing the error!
If you look at the short dump it says something about program LKKBLF01 on line 1148.
I went to take a look at that line.
 if not r_sum is initial or <box> = '-'.
That <box> statement got me thinking that the layout could be the cause, so I commented out the layout parameter line like this:
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
 EXPORTING
 i_buffer_active = space
 i_callback_program = c_repid
 i_callback_pf_status_set = c_pf_status_set
 i_callback_user_command = c_user_command
 i_structure_name = 'ZRKWA'
 i_structure_name = 'T_ALV_LIST'
 it_fieldcat = tab_fieldcat[]
 it_sort = tab_sort[]
* is_layout = s_layout i_save = c_save
 is_variant = s_variant
 it_events = tab_events[]
 TABLES
 t_outtab = i_tab.
 t_outtab = t_alv_list.
And it worked!
Here's an important note I found in the documentation about that parameter:
Interaction
box_fieldname
Value range: SPACE, field name of the internal output table
If the list should have checkboxes at the beginning of each list row (to allow the user to select multiple rows at once), you must fill this parameter with the field name of the internal output table that represents the selection column for selecting rows with the help of checkboxes.
The field is always displayed as a checkbox at the beginning of each list row without a list heading.
I don't know why this has something to do with it, but my problem is solved. I will look into it further and update when I've found a better solution.
Thank you for all your help Christian.
I really appreciate it.

Call Function Destination in a background job

I am having a problem using:
CALL FUNCTION 'TABLE_ENTRIES_GET_VIA_RFC'
DESTINATION p_dest
in a background job.
I am working on a program that would compare the same table in 2 different systems and write the differences. It works when I run it in the foreground. However, I want to run this in a nightly background job. However, it is failing and I beleive that it is the result of the program needing a user to interactively logon to the remote system.
How can I bypass the logon screen or enter information into the logon screen using a background job?
Thanks.
Jon

Hi Jonathan,
Would you like to reward some points to the poster to thank them as a part of SDN Contributor Recognition Program?
You can click on the yellow star on the right of each post header to reward points.
For more information:
https://www.sdn.sap.com/sdn/index.sdn?page=crp_help.htm
John.

Background job not automatically poopulating Dependant Demand

Hi Users,
We've recently set up a POS & PA using the DP-BOM selection and characteristics, manually created PPM's and generated CVC's using the BOMS. All of this is set up fine in our SCM 7.0.
The background job has created the forecasts for the ouptput products but NOT the input product.
Now if I call up the parent material, and then choose to show the input products the dependant demand is generated. If I now return to the material with the dependant demand, it now shows the demand from the parent.
Or, if the forecast is genereated interactively, then the dependant demand is poopulated.
Is there an automated method to populate the dependant demand when using background jobs? I would like to think that we don't have to query every sales BOM parent in DP and drill into the input products to load the dependant demand?
Please let me know if there is an easier way to do this as part of the background processing.
Thanks
Edited by: Paul_111 on Mar 31, 2011 4:20 PM

Hi Andand,
Thanks for your reply and sorry if my post is confusing.
As far as the PPM with imputs A & B, output C - I have this relationship working and calcuclating demand in DP no problems.
If I now add a new PPM combination inpput X, Y and output Z. Create the BOM CVC and TSO so its all set to go. Add to selection profiles and background jobs.
Now, if I run the background job to create the forecast and this runs successfully. Now I check my products.
Z has the forecast generated, X & Z have no dependant demand showing.
The only way I've found that pushes the demand to X & Z is:
- open product Z in demand planning and then choose the option to show input products from the header
OR - from demand planning, select the univariate forecast to run interactively.
My issue:
The background job (if run alone) does not push the forecast on Z to X & Y.
And if I show the input products or create forecast (as bove) the dependat demand is shown on X & Y.
This is going to be a slow process if we have to do this everytime we run the backgound job.
What am I missing when running the background job?

Hi any one please explain background job scheduling

Hi any one please explain background job scheduling . Good answer can be rewarded.
Thanks

Background jobs are pgms that are scheduled to be run in the Background without user interaction. So this can be done only for Type 1(executable) Program and not for Module-Pool Programs. Typically, a variant is defined and the pgm is run using the same.
The transaction code is sm36 -Define Background job. Using the Start Condition tab you can define when you want the job to run (specific time or if it has to follow after a particular job is done etc.,) Using the Step tab you can assign the pgm name and variant.
After the job is scheduled, you can check the status in sm37, along with the Job log and Spool.
For more info:
http://help.sap.com/saphelp_bw30b/helpdata/en/c4/3a7f87505211d189550000e829fbbd/content.htm

How to delete Background job

hi all,
i am working on ECC6.0.
i am not able to find the path to delete background job completly.
can any body give me the navigation for the same in ECC6.0
Thanks in advance

hi
hopen ths wll help
To delete a background job explicitly, use:
BP_JOB_SELECT to obtain the jobname and job number of the job that you wish to delete.
You can select jobs according to all of the criteria available in the interactive background processing management system:
Jobname: Using a well-planned naming convention for your jobs will help you to select them precisely.
Job number
Name of the user who scheduled a job
Specifications for the start-time window/no start time scheduled
Start dependent upon predecessor jobs
Start dependent upon an event and event argument
Job status (preliminary, scheduled, ready, running, finished, aborted).
BP_JOB_DELETE to delete the job. The job log is deleted as well, if the job has already been run.
A job cannot delete itself. Also, a job that is currently running cannot be deleted. However, you can have it deleted automatically if it is completed successfully. See the DELANFREP parameter of JOB_OPEN.
Sample Program: Deleting a Background Job
Data declarations: BP_JOB_SELECT
DATA JSELECT LIKE BTCSELECT.
DATA SEL_JOBLIST LIKE TBTCJOB OCCURS 100 WITH HEADER LINE.
Sample selection criteria
JSELECT-JOBNAME = 'Name of job'.
JSELECT-USERNAME = SY-UNAME.
CALL FUNCTION 'BP_JOB_SELECT'
EXPORTING
JOBSELECT_DIALOG = BTC_NO
JOBSEL_PARAM_IN = JSELECT
IMPORTING
JOBSEL_PARAM_OUT = JSELECT
TABLES
JOBSELECT_JOBLIST = SEL_JOBLIST
EXCEPTIONS NO_JOBS_FOUND = 1
SELECTION_CANCELED = 2
OTHERS = 99.
In this example, the program loops over the internal table
SEL_JOBLIST and deletes each of the jobs that was selected.
Alternative: Have the user select the job to be deleted
with BP_JOBLIST_PROCESSOR. For an example, please see
Sample Program: Wait for Predecessor Job with JOB_CLOSE.
LOOP AT SEL_JOBLIST.
CALL FUNCTION 'BP_JOB_DELETE'
EXPORTING
FORCEDMODE = 'X'
JOBNAME = SEL_JOBLIST-JOBNAME
JOBCOUNT = SEL_JOBLIST-JOBCOUNT
EXCEPTIONS
OTHERS = 99.
ENDLOOP. *
FORCEDMODE deletes the job header even if other portions of the
job cannot be deleted from the TemSe facility, where they are
held.
FORCEDMODE can be used without fear of causing problems in the
System. Any TemSe problem that affects background jobs can be
resolved directly in the TemSe system and does not require the
job header.
regards
navjot
reward if helpfull

DP background jobs in local time zone

We are using APO DP in an international environment (SCM 4.1). We have setup up the system, that is using the local time zone (personal user settings), which is working fine in interactive planning (data views & macros). But when executing the macros
in background (APO background jobs triggered immediately by a process chain), the macro is run based on the server time and not in the local time zone. The ALEREMOTE user is set up in the same way online users regarding time zone settings.
Can someone explain, why the local time zone isn't used in the macros when executing in background, and tell me which setting we have missed.
Many thanks in advance
Marco

HI,
I understand the issue, the issue is the Australia gets days very first from the world.. it almost GMT+11 hrs. will almost a day difference to US.
I am not sure whether my proposal will make sense, but let me try
As the month completes we will copy the sales history for the closed month. where technically the the month is current month as per the system time.
Why can not change the macro to copy current period and run at system time? i am not sure aobut the otherconstriantes.
But looking at your question, it could be possible where your client has the local time zone defined. you can check the same from any APO screen, from menu > systems->status. you can see both time zone ( local) system time.
I suggest you check with basis if we can use the local time zone, we can use the localtimezone but agian everyone has to use our local time.. NO SENSE i guess..
Yarala

EXSQL_DSQL_NOROLL-DP Background job not working as part of chain

Hi,
While running a background job as part of process chain, I am getting the error message which says:
ABAP/4 PROCESSOR: EXSQL_DSQL_NOROLL
Job Cancelled.
When run in the foreground in the interactive planning, it is running fine. Please let me know the way to bypass this error.
Regards,
Guru Charan.

Dont know why it has come that time, but now, it is running fine.

Aggregation Level & Selection ID in Demand Planing Background job

Folks
Whle creating a Demand Planning job in the background, we need to make few selection such as
            1. Choosing a Selection ID(One, Several & Select All) and
            2. Choosing an Aggregation level.
My question is : Doesn't the selection ID already have the aggregation level defined with in as selection ID is basically something defined or shown as Product by Location and then by Sales Org etc. Isn't this the same as the aggregation level ???
Why do we need to have Selection Id as well as Aggregation level in Background job ?
In the interactive planning do we need the aggregation Level ? If so where do we specify the same ?
TIA

The aggregation level can make a big difference to the forecast results. If you run the forecast on a high level (for example, at division level), the system aggregates the historical data (for example, the historical data of all products in a division) before it carries out the forecast. However, if you run the forecast on a low level (for example, for just one product), the system creates the forecast based on the historical data at this level, and then aggregates the forecast results in the planning screen at runtime.
The default level is the most detailed level.Here values will be disaggregated to the lowest detailed level and forecast will be executed in that level for each CVC.
say
PRD LOC     PRD_GRP
A       A1           PG1
B       A1           PG1
C       A1           PG1
A       B1           PG1
B       B1           PG1
C       B1           PG1
here forecast wil be carried out for 6 CVCs
However, in real time, as you have many CVCs, we dont follow this.
Say we specify the aggregation level as PRD_GRP and LOC.. Then system aggregates values at product group and location level..executes forecast and then disaggregates.
in this case forecst will be carried out for
PRD LOC     PRD_GRP
      A1           PG1
      B1           PG1.
Selection ID on the other hand will be used for specific selections.
Suppose if u want to execute one profile for PRDGRP PG1 at LOC A1 , you create a selection ID with this selection like in interactive planning..
How ever, if your selection is
PRD         *
PRDGRP *
LOC          *,
then , here ur aggregation level helps how to disaggregate values before running the forecast

Differences in Background jobs and Dialog jobs

Hi everyone,
I am new to SAP and would like a little clarification regarding what is meant by Background jobs and Dialog jobs/processes. We had a situation at our client location where the system got completely bogged down to the point that it almost froze and many of the process chains were failing in BI. As per the basis team, the jobs were triggered as "dialog jobs" instead of "background" jobs which caused a heavy load on the system.
What is the difference? What happens when the jobs are run in the background or as dialog? Can both be checked in SM37?
Points will be awarded
Thanks.

**Dialog Work process:** The Dialog work process fulfill all requests for the execution of dialog steps triggered by an active user. The dialog work process are not used for request which take long time and which use more cpu. Every dispatcher requires at least two dialog work processes. The dialog work process default time is 300 secs. If the dialog work process does not respond in this time, it will be terminated. Also dialog work process are multiplexed to handle large no of user request.
**Background Work process:** The background work processes execute programs that run without user interaction. At least two background work processes are required per SAP system. More than one background work processes can be configured per dispatcher. Usually the background work process are used for carrying jobs that take long time to finish, like client copy, client transport etc.., . There are two types of background work process. They are A type and B type. A type background work process are used for mission critical jobs. Background jobs of priority a have high priority than B type back ground jobs.
you can check your job using tcode SM50.
Thanks
Dhiraj

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

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

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

Batch job and background job

Hi
what is the difference between a batch job and backgroun job ??
thanks
kumar

hi kumar,
As far as I know
Batch job are the jobs created with sessions. You can process those sessions in SM35. These are not direct update methods.
Where as the background jobs are the jobs running in the background with out user interaction. Once you schedule the job for the background job it will run with out user interaction according to the given schedule.
You can run the batch jobs also in background.

Background job interaction

Similar Messages

Maybe you are looking for