Background Job " RDDVERSI" getting terminated

Hi gurus,
When we check in SM37, We are seeing a background job that is getting terminated. In the job log it says DATASET_NOT_OPEN, Job cancelled. It is trying to run "RDDVERSI" program.
It is creating a Dump in ST22 and when we check the Dump in ST22, it says "The file "/usr/sap/trans/tmp/D01V985854.P01" has not been opened".
I checked the log in the trans directory and it gives me following error. Path of the Log "usr/sap/trans/log/D01V985854.P01".
1AEPU320 See job log"RDDVERSI""07435800""P01"
1 ETP184 CREATE VERSIONS BEFORE IMPORT
1 ETP110 end date and time   : "20070912074448"
1 ETP111 exit code           : "12"
1 ETP199 ######################################
1 ETP199X######################################
1 ETP184 CREATE VERSIONS BEFORE IMPORT
1 ETP101 transport order     : "D01K985854"
1 ETP102 system              : "P01"
1 ETP108 tp path             : "tp"
1 ETP109 version and release : "340.16.24" "640"
1 ETP198
1AETR012XProgram terminated (job: "RDDVERSI", no.: "07460000")
1AEPU320 See job log"RDDVERSI""07460000""P01"
1 ETP184 CREATE VERSIONS BEFORE IMPORT
1 ETP110 end date and time   : "20070912074651"
1 ETP111 exit code           : "12"
1 ETP199 ######################################
I think when it is trying to import a transport request, it is trying to create a version of it and it is not able to create that.
Can anybody help me in solving this problem?
Any Help is appreciated
Regards,
Swaroop.

Can you run this program in the foreground with a user that has the same permissions. If you get an authorization error again, check with transaction se53 on which objects you are missing authorization.
For these objects you can create an additional authorization profile...
Kind regards,
Mark

Similar Messages

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.

Background Job cancelling with error Data does not match the job definition

Dear Team,
Background Job is getting cancelled when I run a Job on periodically but the same Job is executing perfectly when I run it manually(repeat scheduling) .
Let me describe the problem clearly.
We have a program which picks up files from an FTP server and posts the documents into SAP. We are scheduling this program as a background Job daily. This Job is running perfectly if the files contain no data. But if the file contains data the JOb is getting cancelled with the following messages.
And also the same Job is getting executed perfectly when repeat scheduling is done ( even for files with data).
Time     Message text                                                                       Message class Message no. Message type
03:46:08 Job PREPAID_OCT_APPS2_11: Data does not match the job definition; job terminated        BD           078          E
03:46:08 Job cancelled after system exception ERROR_MESSAGE                                      00           564          A
Please help me in resolving this issue.
Thanks in advance,
Sai.

hi,
If you have any GUI function modules used in the program of job
you cannot run it in background mode.

SAP job SAP_COLLECTOR_FOR_PERFMONITOR getting failed with abap dump LOAD_PROGRAM_NOT_FOUND

Dear Experts,
Background job SAP_COLLECTOR_FOR_PERFMONITOR getting failed with abap dump LOAD_PROGRAM_NOT_FOUND.
As it is hourly scheduled job and it gets finished 22 times in a day but other 2 times fails with abap dump.
Finished Job log
Job started
Step 001 started (program RSCOLL00, variant , user ID Bharath)
Clean_Plan:Cleanup of DB13 Plannings
Clean_Plan:started by RSDBPREV                       on server
Clean_Plan:Cleaning up jobs of system DEV
Clean_Plan:finished
Job finished
Failed Job Log
Job started
Step 001 started (program RSCOLL00, variant , user ID Bharath)
Internal session terminated with a runtime error (see ST22).
Kindly suggest on this..
Thanks,
Bharath.

Dear Divyanshu,
Our system in ERP 6.0 EHP5 with SP level 10. The ABAP Dump shows below error.
|Short text                                                                                        |
|    Program "RSORA811" not found.                                                                 |
|What happened?                                                                                    |
|    There are several possibilities:                                                              |
|                                                                                                  |
|    Error in the ABAP Application Program                                                         |
|                                                                                                  |
|    The current ABAP program "RSCOLL00" had to be terminated because it has                       |
|    come across a statement that unfortunately cannot be executed.                                |
|    or                                                                                            |
|    Error in the SAP kernel.                                                                      |
|                                                                                                  |
|    The current ABAP "RSCOLL00" program had to be terminated because the                          |
|    ABAP processor detected an internal system error.                                             |
|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                                                                                    |
|    On account of a branch in the program                                                         |
|    (CALL FUNCTION/DIALOG, external PERFORM, SUBMIT)                                              |
|    or a transaction call, another ABAP/4 program                                                 |
|    is to be loaded, namely "RSORA811".                                                           |
|                                                                                                  |
|    However, program "RSORA811" does not exist in the library.                                    |
|                                                                                                  |
|    Possible reasons:                                                                             |
|    a) Wrong program name specified in an external PERFORM or                                     |
|       SUBMIT or, when defining a new transaction, a new                                          |
|       dialog module or a new function module.                                                    |
|    b) Transport error                                                                            |
|Information on where terminated                                                                   |
|    Termination occurred in the ABAP program "RSCOLL00" - in                                      |
|     "LOOP_AT_SYSTEMS_AND_REPORTS".                                                               |
|    The main program was "RSCOLL00 ".                                                             |
|                                                                                                  |
|    In the source code you have the termination point in line 535                                 |
|    of the (Include) program "RSCOLL00".                                                          |
|    The program "RSCOLL00" was started as a background job.                                       |
|    Job Name....... "SAP_COLLECTOR_FOR_PERFMONITOR"                                               |
|    Job Initiator.. " bharath"                                                                       |
|    Job Number..... 18243400
Kindly check and suggest..
Thanks,
Bharath.

MDMGX download to ports as background job without FTP?

Hello everybody,
is it possible to use MDMGX as a background job to download directly into the mdm ports without FTP?
If I try to download as a local download (in background job) I get the error message: "Cannot open dataset for batch download of file: No such file or directory. Message no. MDM_GX_MSG031"
Any advice?
Regards,
Axel

Hello Alex,
As said in the above post MDMGX is used to extract the reference data from ECC. This data can be extracted to the local system as well. You need to specify the FTP server and MDM Root of the system on which the MDM server is Installed, by doing so the data extracted will be placed in the respective folders created under the given root in MDM. PI is not required for this since the output is in the required XML format
Please go through the below link
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f0740b31-a934-2b10-2e95-af2252991baa?QuickLink=index&overridelayout=true&30296699350032
http://wiki.sdn.sap.com/wiki/display/SAPMDM/MDMGenericExtractor
Hope this helps
Rgds,
Prasad
Edited by: Prasad Tuttagunta on Feb 28, 2012 12:28 PM

Error in background job of downloading data to PC

Hi Gurus,
   I hv created a report for downloading data to PC using
GUI_DOWNLOAD FM when scheduling job in background
job is getting canceled...................
give me some solution....

thnaks friend.i hv used DATASET as u said...............
But I M getting dump
FILE IS NOT OPEN
this is my code
TYPES:BEGIN OF T_MARD,
        MATNR LIKE MARD-MATNR,
        WERKS LIKE MARD-WERKS,
        LGORT LIKE MARD-LGORT,
        LABST LIKE MARD-LABST,
        MAKTX LIKE MAKT-MAKTX,
     END OF T_MARD.
***********WORK AREAS**********
DATA: WA_MARD TYPE T_MARD,
      WA_MARD1 TYPE T_MARD.
DATA:BEGIN OF IT_MARD1 OCCURS 0,
        MATNR(18),
        WERKS(4),
        LGORT(4),
        LABST(13),
        MAKTX(40),
     END OF IT_MARD1.
TYPES : BEGIN OF TY_BAT,
          LINE(100) TYPE C,
        END OF TY_BAT.
*********INTERNAL TABLES*******
DATA:IT_MARD TYPE STANDARD TABLE OF T_MARD INITIAL SIZE 0 WITH HEADER LINE .
types: BEGIN OF ITAB1,
            FIELD(100),
      END   OF ITAB1.
DATA : IT_BAT TYPE TABLE OF TY_BAT,
       WA_BAT TYPE TY_BAT,
       wa_itab1 type itab1.
data : it_tab type table of ALSMEX_TABLINE with header line.
*DATA: FILENAME1 TYPE STRING valu.
*DATA: FILENAME1(500).
DATA: FILENAME1 TYPE RLGRAP-FILENAME .
LOOP AT IT_MARD1.
      CONCATENATE IT_MARD1-MATNR IT_MARD1-LABST IT_MARD1-MAKTX
                  INTO wa_ITAB1    SEPARATED BY ' '.
      APPEND wa_itab1 to IT_tab.
      CLEAR wa_ITAB1.
    CLEAR WA_MARD.
ENDLOOP.
CONCATENATE 'D:\STOCKINH\' SY-DATUM '.TXT' INTO FILENAME1.
open dataset filename1 for output in binary mode." ENCODING DEFAULT.
IF sy-subrc = 0.
EXIT.
ENDIF.
LOOP AT it_tab into wa_itab1.
TRANSFER wa_itab1 TO filename1.
CLEAR wa_itab1.
ENDLOOP.
close dataset filename1.
MESSAGE S001(38) WITH 'Files Generated'.
WA_BAT = 'ftp -s:d:\ftp\ftp_upload.txt'.
APPEND WA_BAT TO IT_BAT.
CLEAR FILENAME1.
   FILENAME1 = 'D:\STOCKINH\ftp_upload.BAT'.
open dataset filename1 for output in binary mode." ENCODING DEFAULT.
IF sy-subrc = 0.
EXIT.
ENDIF.
LOOP AT it_bat INTO wa_bat.
TRANSFER wa_bat TO filename1.
CLEAR wa_bat.
ENDLOOP.
close dataset filename1.
CLEAR: IT_BAT.
REFRESH IT_BAT.
WA_BAT-LINE = 'open 10.100.103.199'.
APPEND WA_BAT TO IT_BAT.
CLEAR WA_BAT.
WA_BAT-LINE = 'epossync'.
APPEND WA_BAT TO IT_BAT.
CLEAR WA_BAT.
WA_BAT-LINE = 'sync@1234'.
APPEND WA_BAT TO IT_BAT.
CLEAR WA_BAT.
WA_BAT-LINE = 'lcd D:\STOCKINH\20080201.TXT'.
APPEND WA_BAT TO IT_BAT.
CLEAR WA_BAT.
WA_BAT-LINE = 'cd /home/epossync/AMIT'.
APPEND WA_BAT TO IT_BAT.
CLEAR WA_BAT.
WA_BAT-LINE = 'binary'.
APPEND WA_BAT TO IT_BAT.
CLEAR WA_BAT.
WA_BAT-LINE = 'hash'.
APPEND WA_BAT TO IT_BAT.
CLEAR WA_BAT.
WA_BAT-LINE = 'put D:\STOCKINH\20080201.txt'.
APPEND WA_BAT TO IT_BAT.
CLEAR WA_BAT.
WA_BAT-LINE = ' '.
APPEND WA_BAT TO IT_BAT.
CLEAR WA_BAT.
WA_BAT-LINE = 'bye'.
APPEND WA_BAT TO IT_BAT.
CLEAR WA_BAT.
CLEAR FILENAME1.
FILENAME1 = 'D:\STOCKINH\ftp_upload.txt'.
open dataset filename1 for output in binary mode." ENCODING DEFAULT.
IF sy-subrc = 0.
EXIT.
ENDIF.
LOOP AT it_bat INTO wa_bat.
TRANSFER wa_bat TO filename1.
CLEAR wa_bat.
ENDLOOP.
close dataset filename1.

Inbound IDoc creating background job even for trigger immediately setup

All,
I have a very serious problem in our production system.
Scenario:
Vendor is chagend in system A (Outbound) and the same is interfaced to System B (Inbound) and i am using trigger immediately option, but still I am seeing a background job is created for 'RBDAPP01' and creating the spool request. The issue is I am sending 1000 of idocs and the spool number is increasing daily in system B.
So, can any one explain me why the background job is getting triggered even though I set the partner profile settings as 'Trigger Immediately'.
The above issue is not happening in our quality system it simply updagtes vendor information in system B with out creating any background job. Please note that the same settings are maintained in both the systems.
Your immediate inputs are really valuable for me.
Regards,
Suman

This is an performance issue on the receiving system. In case the system does not have enough resources to process the IDoc immediately it will always schedule a background job to ensure the processing of data.
You need to check whether the system has enough work processes available during the time when 1000 of IDocs are received or send the IDocs in packages with some time in between.
Regards,
Kai

Background job error No appropriate entry found in table ADRT

Hi,
I have developed a report to sent mail in background. My background job is getting cancelled in background. but it runs in foreground.I have used leave to transaction statement in my report.
In my development server job cancellation occurs.but mails are being sent.whereas in production server job cancellation ocurrs but mails are not sent.
It shows the below error also...
27.12.2010 17:00:00 Job started
27.12.2010 17:00:00 Step 001 started (program YSD_OUTSANDING, variant &0000000000094, user ID ABAPER)
27.12.2010 17:00:01 No appropriate entry found in table ADRT
27.12.2010 17:00:01 Job cancelled after system exception ERROR_MESSAGE
please help me to overcome this error...
Thanks & Regards,
A. Jenifer

I don't see how either of those replies are helpful...
To the OP, you haven't given much information. That's a custom program but the failure is being triggered most likely by your attempt to generate the email by the standard code. You need to get the error message ID and number from the log and find the codepoint (from a where-used analysis or debug) and analyze the condition that's triggering the message. Most likely, it's a simple fix - there appears to be a missing remakrk entry but sometimes those messages are misleading and the message issued isn't actually the problem.

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

Background Job cancellation-Alert config in Solman

Team,
We would like to send an alert to the distribution list or the user whenever a particular background job is getting cancelled.
Could you please let me know the steps how it can be done in solution manager.
Regds,
Satyanarayana N

Hello,
I recommend to setup the Job Monitoring of Business Process Montoring from a Job Documentation. The alerts can either generate notifications (E-Mail, SMS) or workflow documents (messages in Support Desk).
This is demonstrated in a RKT tutorial:
http://service.sap.com/~sapidb/011000358700001911422008E.sim
The process is also documented:
http://help.sap.com/saphelp_smehp1/helpdata/en/8e/3ad6f807e147669036d2a6aed597aa/frameset.htm
Please also visit our Service Markteplace representation: http://service.sap.com/jsm
Kind regards,
Martin

Jobs not getting Scheduled when it is called from RFC

Hi Everyone,
I have Functional module in system1 which in turn creates a background Job, but when i call this Function module from System2 using RFC then the background job is not created. THought i debugged and the Function module on system1 is called successfully with right input parameters. M i missing anything ? Please advice
Regards,
Nikesh Kumar

Hi Chen,
Thanks for the reply. Actually the main problem is not with how the Background job is getting executed. Actually my function module schedules are job in system1 , but if the same func module is called via RFC from other system, it gets called successfully with same inputs (checked in debugging), but the background job does not get created.
Regards,
Nikesh Kumar

Background job getting CANCELLED

hello,
i have a background job scheduled for a report program.it is getting cancelled and giving the following error:
"TABLE_ILLEGAL_STATEMENT"
You attempted to change, delete or create a line in the
internal table "???", but no valid cursor exists
for the table.
Possible reasons:
1. The relevent ABAP/4 statement does not include the addition
   "...INDEX...", although the statement is not
   inside a "LOOP...ENDLOOP" loop processing this table.
2. The relevent ABAP/4 statement was called from within a
   "LOOP...ENDLOOP" loop after a DELETE "???".
what could be the reason?

it is also giving following error message:
Caution: Program has changed
Caution: At time of termination, Active source code no longer available and after above two statements its giving sign "?" before every statement in below manner:
024300 ?     lit_ekpo_dummy1[] = it_ekpo[].
024310 ?     DELETE lit_ekpo_dummy1 WHERE ebeln NE tab1-ebeln.
024320 ?     DESCRIBE TABLE lit_ekpo_dummy1 LINES count01.
024330 ?
024340 ?     REFRESH lit_ematn_dummy[].
024350 ?     lit_ematn_dummy[] = lit_ematn[].

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

Background job BI_ODSA_ASD is getting cancelled, set privilege at db level

Hi,
Background job BI_ODSA_ASD is getting cancelled,
i have increased the tablespace, still no luck,
last time i faced the same problem at that time , i gave some permission at oracle level which worked fine, i dont not remember now,
it was something like GRANT PRIVILEGE SAPSYS SAPCON...... (not sure)
if anyone knows please let me know.
Regards,
SM

Runtime Errors         UNCAUGHT_EXCEPTION
Exception              CX_SDB_ORA_PROGRAM_ERROR
Date and Time          20.09.2007 15:46:44
Short text
An exception occurred that was not caught.
What happened?
The exception 'CX_SDB_ORA_PROGRAM_ERROR' was raised, but it was not caught
anywhere along
the call hierarchy.
Since exceptions represent error situations and this error was not
adequately responded to, the running ABAP program
'CL_SDB_ORA_UPDATE_STATS=======CP' has to be
terminated.
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 exception occurred which is explained in detail below.
The exception, which is assigned to class 'CX_SDB_ORA_PROGRAM_ERROR', was not
caught and
therefore caused a runtime error.
The reason for the exception is:
ـbernehmen
The occurrence of the exception is closely related to the occurrence of
a previous exception "CX_SQL_EXCEPTION", which was raised in the program
"CL_SQL_STATEMENT==============CP",
specifically in line 31 of the (include) program
"CL_SQL_STATEMENT==============CM002".
The cause of the exception was:
ORA-20000: Insufficient privileges
ORA-06512: at "SYS.DBMS_STATS", line
2150
ORA-06512: at "SYS.DBMS_STATS", line 14112
ORA-06512: at line 1
How to correct the error
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:
"UNCAUGHT_EXCEPTION" "CX_SDB_ORA_PROGRAM_ERROR"
"CL_SDB_ORA_UPDATE_STATS=======CP" or "CL_SDB_ORA_UPDATE_STATS=======CM00I"
"UPDATE_STATS"
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.

VL10B is terminating in background job, no deliveries are generated

VL10B is terminating when running in a background job then no deliveries get generated for STO, is there a way to make the program skip to the next record instead of terminating so some deliveries will be generate?

Hi mohan,
check in material master whether there is any saftey stock / minimum stock is there.. if so. please correct it.
Ramki

Background Job " RDDVERSI" getting terminated

Similar Messages

Maybe you are looking for