Background jobs (how to manage)

Hello,
We recently had e-mail enabled in our system so we can send items directly to employees via outlook for workflow items. I'm trying to get some standard SAP programs to be able to run once a night and e-mail me the results, but I'm not sure the best way to handle this. I've been able to do this for 'Z' reports we've written ourselves.
An example would be to run transaction SM37 to pick up any jobs that are 'cancelled' or 'active' so I can monitor any issues with a nightly e-mail instead of running the program manually every day. Since this cannot be run in the background, is there a similar program that can be run to monitor this?
Another example is the workflow report 'Work Items Without Agents' (transaction SWI2_ADM1), but when I run it in the background, no data appears.
I know it's not that difficult to run SM37, but when I want to monitor several standard programs it adds up to time I just don't have right now since we just went live with an upgrade a couple of weeks ago.
Thanks in advance for any advice,
Jonathan

Hi Jonathan,
CCMS should be setup to report on any failed jobs. The only thing you might have to update are the settings to generate an email.
So CCMS is probably a better place to look for a solution than SM37.
Hope that helps.
J. Haynes
Denver, CO

Similar Messages

In background job how commit & rollback work works?

Hello Friends,
My requirement is, to fetch all sales order items based on some condition and load them into one table say OCC1 in job J1. Now the second requirement is to upload the job information J1 with job name, user name, end date in second table say OCC2 in job J2.
My question is if there is some error I found while processing job 2 I have to rollback entire work which means I have to remove all records those I have inserted in to table OCC1. Can any one suggest me how to handle such problem? Some how I am able to create two job and update the tables. However, what about rollback work? Whether there is an implicit commit work after every background job? I am working on SAP 4.6C version.
Thanks,
Amol C.

I think by using just ROLL BACK work it will not rollback your first job's data.
You need to make some mechanism which can delete the data from OCC1 if the J2 got error.
Regards,
Naimesh Patel

Background job , how we set report width

Hello,
when i run a report in background, 'Background Print Parameters' window appears. Here i see various values filled default. Like a name in Spool Request -- Name. Report page -65. Report width --450.
How is Report width set = 450.
Can you please explain this to me.
regards

ok SAMANAT one more query how do 'NAME' is filled under tab 'Spool Request'.
regards
Message was edited by: Surpreet Singh Bal

How to run the program in background job,program should run in 3 days.

Dear Gurus,
i have a program , that program should run approximately 3 days to get the result.
i scheduled this program as a background job.
how can i run sto5 t-code for this same program.
i that case how we can trace the output.
Experts please help me out.
Thank u very much.
Regards
sudheer

Hello Sudheer,
The trace can be set on background jobs by using ST12 transaction. Please make sure that the trace is activated for only few minutes in production environment.
Contact your basis team to activate trace on background job and the transaction used is ST12.
Thanks

CC Management Reports background job- no results

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

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

Background job not deleted

Hi Experts,
i want delete the "SM:SELFDIAGNOSIS" background job on solution manager system .
and i have deleted, go to next date and then delete the released job but after one day again its showing in released.
so how i can delete it properly .
Regards
jai kr.

Shiv,
First check the frequency of this job from SM37
Go to SM37 -> give your job name ->and select all the options like
delete the entries in start date and end date fileds. then execute.
If you find job in Released state ,simply go to menu Job -> click on release to schedule.
Now this job will in Schedule and won't run untill you release it.
Deleting the jobs is not good idea ,simply you can suspend it.
Regards,
Srinivas Chapa.

Schedule Background Jobs

Hi
Gurus
What is Schedule Background Jobs and whatu2019s the use of Schedule Background Jobs
How it will worku2019s
Please give me detail Information about Schedule Background Jobs
Many Thanks
Mahi

Hello Mahi,
The BackGround job - "Program" thats runs in SAP Server and not depend any user interface.
like Antivirus program on your local station that runs (scaning your computer all the time) without any user interface (becide tray Icon) and unless you going to Running Proccess on your computer you don't know that it working.
Schedule BackGround Job its any backGround Job that you schedule to run any time you want and you can make it run recursivly.
you can go to Transaction SM36 to schedule your Programs.
Good Luck
Eli Steklov
Please Reward Points if it Helped

I cannot cancel a background job

Hello,
I cannot cancel a background job which is running since the last Friday. I use the SM37 transacction but it doesn't stop.
Can anybody tell me how can I get to stop this job?
Thanks in advance.
Regards.

Hello friend,
I think these links will help you to stop the job running in back ground,
How to stop Active Background Jobs
http://stackoverflow.com/questions/1439033/sap-background-job-hows-it-running
If your problem still exists revert back to me i will help you.
Thanks,
Sri Hari

SM:SELFDIAGNOSIS background job getting failed in Solution manager

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

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

How to Cancel a ACTIVE background Job scheduled in SM37.

Hi Friends,
I have scheduled a Background job. The job is ACTIVE now. How can I cancel this job?
Regards,
Viji

There is a last ditch method for jobs that don't get canceled for some reason or the other
Go to SM50 - first try canceling the job from there
If that doesn't work, note down the Process ID (PID) of the job
Take direct OS access to your system (You would need your Basis person for this) and terminate the job
If the server is Windows based, you can end it using the task manager and end that process id

Background job failing - ECC 6.0, Solution Manager 7.0

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

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

Best practice - Manage background job users

Gate Keepers and Key Masters,
What is the best way to manage users who run background jobs?
For example currently we have a special system user with SAP_ALL that is only used to schedule jobs with. and we manage who has authorization to schedule jobs.
We are told that this is not the best way to go about it and that we have to remove SAP_ALL from that user. I don't see a very good way to eliminate SAP_ALL profile, short of analyzing every single batch job that is already scheduled, and creating or assigning existing roles for each job or step. Even that doesn't guarantee that authorizations given to my batch user would be enough to run any jobs that may be scheduled in the future.
Can you give me any pointers on how to address this problem.
Thanks
Matt

Hello,
as a matter of fact the cleanest way is giving to the backgroud job's user only the authorizations to perform programs and steps he have to.
Usually auditors allows keeping SAP_ALL for system users.
However, a work-aroud could be the creation of a special role, containing authorization to do "almost everything". You should run transaction PFCG, enter the name of the role, save, then go straightly to the tab "Authorizations" and press the button "Change authorization data". In the pop-up screen "Choose template" choose "Do not select templates"; then follow the scroll-down menu path "Edit --> Insert authorization(s) --> Full authorization". Then go to the push-button "Organizational levels" and press the push-button "Full authorization". If you want you can refine this role, removing some critical authorization object such as, for instance, S_USER_*, or others like that. Then you can assign this role to the background user.
Hope to be useful.
Best regards,
Andrea

How to find Spool number for a 2 steps background job.

Hi All,
How to find spool number (and also the background job name ) for a 2 steps background job.
in the table TBTCO i can see step numbers but i dont get the spool number. Is there any link between TBTCO and TSP01.
Also after getting the spool number i need to drill down on ALV report. I hard coded the spool number and was able to drill down using BDC and call transaction but when i press back button it is not returning to the ALV report.
Thanks,
Shiva.

Which one creates the spool? (first one I guess)
What kind of spool? (WRITE, sapscript, smartform, pdf...)
Do you use special statements like NEW-PAGE, or other things?
Are you sure that the spools are generated by these jobs? (did you compare the spool generation times and job run dates to be sure...)

How to avoid use of function module in case of background jobs?

Hi ,
I am working a file tranfer interface .Functionality is to extract file either apllication or presentation server , and process the file through bapi , send the result in their respective server. This program should run through batch jobs in background mode.
I am using following function module :
SUBST_GET_FILE_LIS : Get the file list from application server
TMP_GUI_DIRECTORY_LIST_FILES : Get the file list from presentation server
GUI_UPLOad : to extract file data from presentation server
GUI_downLOAD : to download data to presentation server
in case of background job these function modules will not work.... so how to resolve this issue...
what are the methods we can apply?
Thanks & Regards
Sandeep

Hi,
This FM is used to get list of files from Application server (will work in Background). This cannot be used to list files from presentation server. There is no way , by which you can process presentation server files in background mode.
Regards
Vinod

How to get data from the called program using SUBMIT in a background job?

Hi Experts,
I've a program which creates a background job using JOB_OPEN and JOB_CLOSE function modules.
Between the above function modules I need to call a program using SUBMIT VIA JOB statement.
My problem is, How do I fetch some data in an internal table in the called program to the calling program after the SUBMIT statement?
I tried to EXPORT and IMPORT the data, but they are giving a failed sy-subrc when using this background job.
Kindly let me know your inputs and valuable suggestions.

Kumar,
When we execute a program as a background job then the output will be sent to Spool which needs to be fetched again.I guess we need to use Submit via spool as mentioned by Rajat.
Check these threads to get some idea
submit report to spool & import spool id
Re: Generate Spool for a report
K.Kiran.

Background jobs (how to manage)

Similar Messages

Maybe you are looking for