VF11 (cancel invoice) in background job

Hi,
Is there a way to schedule a job for x numbers of invoices we want to cancel? In VF11 (as far as I can see) there is no option to save a variant and then setup this job in SM36. Reason I want to run it as a job is that I don't want my name tag on all cancelled invoices. Any good suggestions?
Kind regards

Hi,
Check Note 1259505 - FAQ: New cancellation procedure in SD, surely it gives you some idea
Regards,
Eduardo

Similar Messages

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

Long Running VF11: Cancel Invoice

We have a table used for GL's that was converted from pooled to transaparent in 2003. There were tools and access keys used for creating this Z table related to the GL. The table has over 24,000,000 recs in it and causes VF11 to run for an hour to cancelk an invoice. I do not see any handy exits to put any code so certain bussineses can skip the logic. There are indexes but I do not think they are being utilized in the SAP R programs.
Bottom line: Either purge, or clean the table?
Anybody know any other ways to clean up this table or other suggestions?
Thank-You.

Use ST05 or ST04
ST05 has been explained earlier.
ST04 - You can find where the bottleneck is..whether its a connection problem or database problem etc. You will find data by Transaction.
Sri

Printing of Invoices during background Jobs

Hello,
We have an o/p type that is processed each time a billing document is created. The o/p type prints the billing document as soon as it is saved. When we have a billing due list program run in background the printouts are waiting in the Spool and are not printed. Is there any way we can print the documents when the billing due list program runs in background.
Any help would be appreciated.
Thanks,
Alam.

Hello Alam,
If your question was answered, please close this thread and assign the points to the person that give you the answer.
Regards,
Eric

Printing Invoices in Background Jobs

Hello,
We have an o/p type that is processed each time a billing document is created. The o/p type prints the billing document as soon as it is saved. When we have a billing due list program run in background the printouts are waiting in the Spool and are not printed. Is there any way we can print the documents when the billing due list program runs in background.
Any help would be appreciated.
Thanks,
Alam.

Hello Alam,
If your question was answered, please close this thread and assign the points to the person that give you the answer.
Regards,
Eric

How to cancel invoice documents in Background Jobs ?

Dear sd Gurus
i want to cancel invoice documents in Background Jobs .
I Have checked this link also VF11 (cancel invoice) in background job
But i did find Exact Way
Thanks a lot

Hi Madhuri,
I suggest you to use LSMW for this activity. Just do the recording, test it for one billing doc. If successful then run it for all billing doc which you want to cancel.
MT

BWREMOTE background job canceled in sap r/3 system

Hi my friends,
Thanks for your help ahead.
Today I checked the background job in SAP R/3 created by BWREMOTE via SM37. It showed me some jobs had been canceled.
I displayed its log, the detail message is:
==========================================
Step 001 started (program SBIE0001, variant &0000000083494, user name BWREMOTE)
DATASOURCE = ZQM_NOT_SHFGRP
Call up of customer enhancement BW_BTE_CALL_BW204010_E (BTE) with 1,593 records
Result of customer enhancement: 1,593 records
Call up of customer enhancement EXIT_SAPLRSAP_001 (CMOD) with 1,593 records
ABAP/4 processor: SAPSQL_INVALID_FIELDNAME
Job cancelled
==========================================
Then I displayed the "Long Text" of the job log. It is
One of the field names in the SELECT clause was not recognized.
Error analysis
The SELECT clause was specified in an internal table at runtime.
It contains the field name "TPR00", but this does not occur in any of
the database tables listed in the FROM clause.
Information on where termination occurred
The termination occurred in the ABAP/4 program "SAPLXRSA " in
"EXIT_SAPLRSAP_001".
The main program was "SBIE0001 ".
Source code extract
008840 concatenate 'TPR'
008850 day_temp+6(2)
008860 ' = '
008870 ' ''' zshift '''' into
008880 cond .
008890 append cond to itab .
008900 select schkz into i_not_shfgrp-zzschkz from t552a
008910 where zeity = '2'
008920 and mofid = 'CN'
008930 and mosid = '28'
008940 and ( schkz = 'SFTA' or
008950 schkz = 'SFTB' or
008960 schkz = 'SFTC' or
008970 schkz = 'SFTD' )
008980 and kjahr = day_temp+0(4)
008990 and monat = day_temp+4(2)
> and (itab) .
009010 endselect.
I guess that there is not a field named TPR00 in table t552a.
Next, I opened the 'project management of sap enhancement' via CMOD, entering the project name and chosing 'Display'.
Then Double click the Components 'EXIT_SAPLRSAP_001', we can see the function module 'EXIT_SAPLRSAP_001'. In the source codes, there is an include program, it is 'INCLUDE ZXRSAU01.'.
Then, I double clicked the Include program and find the position program terminated. The source codes are:
ZQM_NOT_SHFGRP *
when 'ZQM_NOT_SHFGRP'.
loop at c_t_data into i_not_shfgrp .
l_tabix = sy-tabix .
clear :mbatch ,zshift,cond ,zfield, zcharg, day_temp .
refresh itab.
if i_not_shfgrp-ausvn is initial.
else.
aa = '080000'.
bb = '160000'.
cc = '235959'.
day_temp = i_not_shfgrp-ausvn.
if i_not_shfgrp-auztv ge aa and
i_not_shfgrp-auztv lt bb .
zshift = 'MSHF' .
elseif i_not_shfgrp-auztv ge bb and
i_not_shfgrp-auztv le cc .
zshift = 'LSHF'.
else .
zshift = 'NSHF'.
day_temp = i_not_shfgrp-ausvn - 1.
endif.
concatenate 'TPR'
day_temp+6(2)
' = '
' ''' zshift '''' into
cond .
append cond to itab .
select schkz into i_not_shfgrp-zzschkz from t552a
where zeity = '2'
and mofid = 'CN'
and mosid = '28'
and ( schkz = 'SFTA' or
schkz = 'SFTB' or
schkz = 'SFTC' or
schkz = 'SFTD' )
and kjahr = day_temp+0(4)
and monat = day_temp+4(2)
and (itab) .
endselect.
endif.
I found that we got a TPR00 during concatenation. In other words, day_temp+6(2) = 00. But I think it is impossible. I can not explain this.
Any ideas, my friends. Many thanks.

select schkz into i_not_shfgrp-zzschkz from t552a
where zeity = '2'
and mofid = 'CN'
and mosid = '28'
and ( schkz = 'SFTA' or
schkz = 'SFTB' or
schkz = 'SFTC' or
schkz = 'SFTD' )
and kjahr = day_temp+0(4)
and monat = day_temp+4(2)
and (itab) . => doesn't make sense?!
endselect.
endif.
it seems something got deleted between 'and' and '(itab)'... so, you'll have to recheck the requirements for your select to fill the 'and' statement further.
so, it should look like
and monat = day_temp+4(2)
and <some kind of condition that needs to be fulfilled>.
endselect.
<some logic to fill a line in your internal table>.
append cond to itab.
endif.
obviously <some kind of condition that needs to be fulfilled> needs to be replaced by a real condition
and <some logic to fill a line in your internal table> needs to be replaced by some kind of formula
I assume something like (otherwise it would be really weird to select that field):
cond = i_not_shfgrp-zzschkz.
or a formula using the i_not_shfgrp-zzschkz field.
It would also be a lot better to replace your select ... endselect by a select single as you'll be selecting 1 record only anyways.
Message was edited by:
RafB

HRALXSYNC Background job is cancelled

Hi,
I scheduled HRALXSYNC report in background but it is executed for some time and then it is Canceled and the job type is execute immediately.
Here am pasting the details of scheduled job.
Date            Time           Message text
08/30/2011 07:09:52    Job started
08/30/2011 07:09:52    Step 001 started (program HRALXSYNC, variant SAP&DEFAULT, user ID SHAIKSJ)
08/30/2011 07:17:34    Enter at least one number for the business partner
08/30/2011 07:17:34    Job cancelled after system exception ERROR_MESSAGE
Note: Here this background job run as "changes since".
Can any suggest me how to solve this issue.
Thanks in advance
Saleem

Hi Saleem,
Not sure if you already solved your issue.
But I have one remark regarding the value of "Changes Since":
The program HRALXSYNC stores the date of last successful runtime in table T77ZZ (REPID=HRALXSYNC).
"01.01.1900" is the inital default date. Please start HRALXSYNC in dialog mode and select "Changes Since" and execute the program. Then select all lines of the result list and press on the 'Repair' button. Errors in the result need to be investigated.
I am actually as well 'fighting' in the area of HR data Integration into CRM.
Kind Regards,
Bjoern

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[].

How to cancel the background job processing in ABAP programming?

Hi,
I have a requirement where i need to cancel the job depending on some constraint. My code is something like this:
Select some data from the table.
if sy-subrc = 0.
Do nothing.
Else
Cancel the job
call function 'BP_JOB_ABORT'
exporting
 jobcount = number
 jobname = name
EXCEPTIONS
 CHECKING_OF_JOB_HAS_FAILED = 1
 JOB_ABORT_HAS_FAILED = 2
 JOB_DOES_NOT_EXIST = 3
 JOB_IS_NOT_ACTIVE = 4
 NO_ABORT_PRIVILEGE_GIVEN = 5
 OTHERS = 6
The above code is cancelling the job but it is throwing an exception called CX_SY_DYN_CALL_PARAM_MISSING because i dint pass job count. How can we find the job count of next job that is going to run? Or How to handle the exception which it is throwing. Even if i try to handle that exception something like this:
TRY
call function 'BP_JOB_ABORT'
exporting
 jobcount = number
 jobname = name
EXCEPTIONS
 CHECKING_OF_JOB_HAS_FAILED = 1
 JOB_ABORT_HAS_FAILED = 2
 JOB_DOES_NOT_EXIST = 3
 JOB_IS_NOT_ACTIVE = 4
 NO_ABORT_PRIVILEGE_GIVEN = 5
 OTHERS = 6
RAISE EXCEPTION TYPE CX_SY_DYN_CALL_PARAM_MISSING.
CATCH
CX_SY_DYN_CALL_PARAM_MISSING.
ENDTRY.
It avoids the exception but it doesnt cancel the job. I even tried with function modules like JOB_OPEN
JOB_SUBMIT,BP_JOB_SELECT,BP_JOB_ABORT and tried to build some logic using status overview table (TBTCO) and TBTCP (Jobstep overview table).
Can someone suggest me the right way to write this program ?
Thanks in advance.
Rashmi

Hi,
Problem is solved.
Create an background job with 2 steps. The first step in the background job calls the program ZBACKJOB_STEP1. In the variant we have a wrong material number
If the material number is not found in Mara, the next step in the job should not get executed and the job should get cancelled..
In the above posts i had asked how do I get the job count of the job that is currently triggering the program at the runtimeu2026..If u see the below code uu2019ll get to know.. We have to use the standard structure TBTCM which captures the properties/characteristics of the job.
REPORT ZBACKJOB_STEP1.
TABLES: MARA,TBTCM.
PARAMETERS : MATNR TYPE MATNR.
START-OF-SELECTION.
SELECT SINGLE * FROM MARA WHERE MATNR = MATNR.
IF SY-SUBRC IS INITIAL.
 WRITE / : 'This is the material selected on the selection-screen' , MARA-MATNR.
ELSE.
 CALL FUNCTION 'GET_JOB_RUNTIME_INFO'
 IMPORTING
 EVENTID = TBTCM-EVENTID
 EVENTPARM = TBTCM-EVENTPARM
 EXTERNAL_PROGRAM_ACTIVE = TBTCM-XPGACTIVE
 JOBCOUNT = TBTCM-JOBCOUNT
 JOBNAME = TBTCM-JOBNAME
 STEPCOUNT = TBTCM-STEPCOUNT
 EXCEPTIONS
 NO_RUNTIME_INFO = 1
 OTHERS = 2.
 IF SY-SUBRC = 0.
 CALL FUNCTION 'BP_JOB_ABORT'
 EXPORTING
 JOBCOUNT = TBTCM-JOBCOUNT
 JOBNAME = TBTCM-JOBNAME
 EXCEPTIONS
 CHECKING_OF_JOB_HAS_FAILED = 1
 JOB_ABORT_HAS_FAILED = 2
 JOB_DOES_NOT_EXIST = 3
 JOB_IS_NOT_ACTIVE = 4
 NO_ABORT_PRIVILEGE_GIVEN = 5
 OTHERS = 6.
 IF SY-SUBRC <> 0.
 ENDIF.
 ENDIF.
ENDIF.
Regards,
Rashmi

SAP_COLLECTOR_FOR_PERFMONITOR background job cancelled in SM37

Dear all ,
One of the scheduled background job has been cancelled .
Kindly check the below loga and Background job details .
Job name        SAP_COLLECTOR_FOR_PERFMONITOR
Job class       C
Status          Canceled
(ABAP Program
Name           RSCOLL00
Variant
Language       EN)
Job Log :
30.05.2010 06:20:32 Job started
30.05.2010 06:20:32 Step 001 started (program RSCOLL00, variant , user ID DDIC)
30.05.2010 06:20:37 Clean_Plan:Cleanup of DB13 Plannings
30.05.2010 06:20:37 Clean_Plan:started by RSDBPREV                       on server PRDCIXI
30.05.2010 06:20:38 Clean_Plan:Cleaning up jobs of system IRP
30.05.2010 06:20:39 Clean_Plan:finished
30.05.2010 06:20:43 ABAP/4 processor: DBIF_RTAB_SQL_ERROR
30.05.2010 06:20:43 Job cancelled
Kindly suggest

Dear all ,
Kindly check the ST22 error logs .
Short text SQL error occurred in the database when accessing a table. What happened? The database system detected a deadlock and avoided it by rolling back your transaction. What can you do? If possible (and necessary), repeat the last database transaction in the hope that locking the object will not result in another deadlock. Note which actions and input led to the error. For further help in handling the problem, contact your SAP administrator . You can use the ABAP dump analysis transaction ST22 to view and manage termination messages, in particular for long term reference. Error analysis The database system recognized that your last operation on the database would have led to a deadlock. Therefore, your transaction was rolled back to avoid this. ORACLE always terminates any transaction that would result in deadlock. The other transactions involved in this potential deadlock are not affected by the termination. Last error logged in SAP kernel Component............ "SAP-Gateway" Place................ "SAP-Gateway on host PRDCIXI / sapgw01" Version.............. 2 Error code........... 679 Error text........... "program prodoradb.sapccmsr.99 not registered" Description.......... "TP prodoradb.sapccmsr.99 not registered" How to correct the error Database error text........: "ORA-00060: deadlock detected while waiting for resource" Internal call code.........: "[RTAB/UPD /MONI ]" 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_RTAB_SQL_ERROR" " " "RSHOST3M" or "RSHOST3M" "PUT_LOGBOOK" 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 System call.......... " " Module............... "gwr3cpic.c" Line................. 1835 The error reported by the operating system is: Error number..... " " Error text....... " "
for detail log.
System environment
SAP-Release 700
Application server... "PRDCIXI"
Network address...... "10.54.145.32"
Operating system..... "AIX"
Release.............. "5.3"
Hardware type........ "000184CAD400"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 8
Shortdump setting.... "full"
Database server... "PRODORADB"
Database type..... "ORACLE"
Database name..... "IRP"
Database user ID.. "SAPSR3"
Terminal................. " "
Char.set.... "C"
SAP kernel....... 700
created (date)... "Mar 7 2010 21:00:49"
create on........ "AIX 2 5 005DD9CD4C00"
Database version. "OCI_102 (10.2.0.2.0) "
Patch level. 246
Patch text.. " "
Database............. "ORACLE 10.1.0.., ORACLE 10.2.0.., ORACLE 11.2...*"
SAP database version. 700
Operating system..... "AIX 1 5, AIX 2 5, AIX 3 5, AIX 1 6"
Memory consumption
Roll.... 1217248
EM...... 0
Heap.... 0
Page.... 32768
MM Used. 1050520
MM Free. 146024
and Transaction
Client.............. 000
User................ "DDIC"
Language key........ "E"
Transaction......... " "
Transactions ID..... "4BFF227871E00187E10080000A369120"
In the source code you have the termination point in line 521
of the (Include) program "RSHOST3M".
The program "RSHOST3M" was started as a background job.
Job Name....... "SAP_COLLECTOR_FOR_PERFMONITOR"
Job Initiator.. "DDIC"
Job Number..... 02033500
In the source code you have the termination point in line 521
of the (Include) program "RSHOST3M".
The program "RSHOST3M" was started as a background job.
Job Name....... "SAP_COLLECTOR_FOR_PERFMONITOR"
Job Initiator.. "DDIC"
Job Number..... 02033500
Program............. "RSHOST3M"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
rmation on where terminated
Termination occurred in the ABAP program "RSHOST3M" - in "PUT_LOGBOOK".
The main program was "RSHOST3M ".

Background job SAP_PERIODIC_ORACLE_SNAPSHOT got cancelled.

Hi All,
Background job SAP_PERIODIC_ORACLE_SNAPSHOT got cancelled.
Im SM37 the log shows that the job has been cancelled because 'No Vendor Specified'
Is that any variant needs to be specified.
Please help me on this.
Thanks & Regards,
Gopi L.

Hi,
Please check the SM21 log and the corresponding work process trace (dev_wX - X refers to the work process number used by the job, can be seen from SM21) for errors.
Best regards,
Warren

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.

Background job PLAAP5BULCOD_CONS_CHECK_CCR_MPOR cancelling

Hi,
Background job PLATA_CONS_CHECK_CC_EMPTOR canceling in my SCM 5 system.
Log from SAM is as below. Job is running around 2.5 hours.
In ST, found few time out errors while this job is running.
Didnt found errors related to this job (user, twp) in SAM.
Is function module /SAPPORO/COIF_DELTA_SE_FROM_R and /SAPPORO/DM_COPY_ORDERS_LCD_PACK related to the program /SAPPORO/COIF_DELFTWARE ?
how to fix this? is any other logs are available to check this (in SCM)?
Please suggest.
(AIX,Oracle,SCM)
SAM error: ____________________________________________________________________________________
21.03.2010 10:30:03 Job started
21.03.2010 10:30:03 Step 001 started (program /SAPPORO/COIF_DELFTWARE, variant PR_MANU_FORD, user ID BATCH_AM)
21.03.2010 11:13:04 Iteration executed
21.03.2010 11:13:05 Spool request (number 0000031813) created without immediate output
21.03.2010 11:13:05 Results saved successfully
21.03.2010 11:13:06 Step 002 started (program /SAPPORO/COIF_DELFTWARE, variant PR_PLAN_FORD, user ID BATCH_AM)
21.03.2010 12:00:18 Iteration executed
21.03.2010 12:00:24 Spool request (number 0000031833) created without immediate output
21.03.2010 12:00:25 Results saved successfully
21.03.2010 12:00:25 Step 003 started (program /SAPPORO/COIF_DELFTWARE, variant PR_MANU_FORD, user ID BATCH_AM)
21.03.2010 13:00:58
21.03.2010 13:00:58 Background job terminated due to communication error
21.03.2010 13:00:58 Job canceled after system exception ERROR_MESSAGE
ST22 Errors_______________________________________________________________________________
TIME_OUT ERRORS with the following details:
user ID: BATCH_AM
Function module: /SAPPORO/COIF_DELTA_SE_FROM_R (and /SAPPORO/DM_COPY_ORDERS_LCD_PACK also )
Thanks & Regards,
Nagendra.

Hi Nagendra,
it seems the problem is related to timed out issue in the work process
what is the present value of rdisp/max_wprun_time ? check in RZ11 , increase the value of atleast 3600 ( setting zero is maximum value , you can also try and revert back once bgd process completes)
Thanks and regards
Purna

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.

VF11 (cancel invoice) in background job

Similar Messages

Maybe you are looking for