SAP_CCMS_DT_SCHEDULER job cancelled in SM37

Hi,
I was doing a check in the background job and got the job SAP_CCMS_DT_SCHEDULER as cancelled.It is scheduled by user SAPSYS.the detail of the job log gives:"Logon of user SAPSYS failed in client 000 when starting a step" "message 560."
this job has been cancelling from 8th august.and is performed almost every ten minutes in the system and is getting cancelled.
please help what to do??
regards,
Priyanshu Srivastava

Hi Priyanshu,
Check if the user who scheduled the job is locked.Also check if the user exist or not?
tcode sm37
Regards
Ashok Dalai

Similar Messages

Job Cancelled in SM37

Hi all,
Job is cancelled in sm37 daily from 7th december onwards.
We have 4 process chains in our project and all the chains are ok when i am checking in RSPC,and the data is being loaded into the respective cubes and ods.
The error message is like
Job started
Step 001 started (program RSPROCESS, variant &0000000001639, user ID ALEREMOTE
Job or process BI_PROCESS_LOADING, waiting for event is unknown
Job cancelled after system exception ERROR_MESSAGE.
I have removed one processchain from scheduling 10 days before.
Is this is the reasong for the job failures?
Please help me
Sridath

Hi......
Look Job : BI_PROCESS_LOADING.........is actually the background job.............in a process chain.......when the trigger come to a load process...........first this job will run........and after completion of this job...........the actual IP will start...............we don't schedule this job.......but u r saying ur loads are fine.........if this job fails......then the IP will not start......so how ur IP s are running........As already suggested............u deschedule the chain........then again schedule it back.......
Now to check job that exactly fails at 12:00 a.m.....................
Go to SM37 ............give this job name...............date......and in the time field give the time.........
Regards,
Debjnai......

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 ".

Capture event from job cancelled in SM37 by workflow, is not posible.

Hi, i'm learning workflows and i want capture the event ABORT o CANCELLED form job in sm37 and send email to agent recipient but i dont know as to resolve this problem.
Please , i need help.
Thanks.

Hi......
Look Job : BI_PROCESS_LOADING.........is actually the background job.............in a process chain.......when the trigger come to a load process...........first this job will run........and after completion of this job...........the actual IP will start...............we don't schedule this job.......but u r saying ur loads are fine.........if this job fails......then the IP will not start......so how ur IP s are running........As already suggested............u deschedule the chain........then again schedule it back.......
Now to check job that exactly fails at 12:00 a.m.....................
Go to SM37 ............give this job name...............date......and in the time field give the time.........
Regards,
Debjnai......

In LO Cockpit, Job contol job is cancelled in SM37

Dear All
   I am facing one problem. Pl help me to resolve that issue.
When ever I am scheduling the delta job for 03 (Application Component), that is cancelled in SM37. Hence, I couldn't retrive those data from queued delta MCEX03 (smq1 or lbwq) to RSA7 because of job is cancelled. When I have seen that job log I got below Runtime Errors. Please hep me to resolve this issue
Runtime Errors         MESSAGE_TYPE_X
Date and Time          04.10.2007 23:46:22
Short text
The current application triggered a termination with a short dump.
What happened?
The current application program detected a situation which really
should not occur. Therefore, a termination with a short dump was
triggered on purpose by the key word MESSAGE (type X).
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
Short text of error message:
Structures have changed (sy-subrc=2)
Long text of error message:
Technical information about the message:
Message class....... "MCEX"
Number.............. 194
Variable 1.......... 2
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
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:
"MESSAGE_TYPE_X" " "
"SAPLMCEX" or "LMCEXU02"
"MCEX_UPDATE_03"
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.
Thanks in advance
Raja

LO EXTRACTION:
First Activate the Data Source from the Business Content using LBWE
For Customizing the Extract Structure LBWE
Maintaining the Extract Structure
Generating the Data Source
Once the Data Source is generated do necessary setting for
Selection
Hide
Inversion
Field Only Know in Exit
And the save the Data Source
Activate the Data Source
Using RSA6 transport the Data Source
Replicate the Data Source in SAP BW and Assign it to Info source and Activate
Running the Statistical setup to fill
the data into Set Up Tables
Go to SBIW and follow the path
We can cross check using RSA3
Go Back to SAP BW and Create the Info package and run the Initial Load
Once the Initial delta is successful before running delta load we need to set up V3 Job in SAP R/3 using LBWE.
Once the Delta is activated in SAP R/3 we can start running Delta loads in SAP BW.
Direct Delta:- In case of Direct delta LUWs are directly posted to Delta Queue (RSA7) and we extract the LUWs from Delta Queue to SAP BW by running Delta Loads. If we use Direct Delta it degrades the OLTP system performance because when LUWs are directly posted to Delta Queue (RSA7) the application is kept waiting until all the enhancement code is executed.
Queued Delta: - In case of Queued Delta LUWs are posted to Extractor queue (LBWQ), by scheduling the V3 job we move the documents from Extractor queue (LBWQ) to Delta Queue (RSA7) and we extract the LUWs from Delta Queue to SAP BW by running Delta Loads. Queued Delta is recommended by SAP it maintain the Extractor Log which us to handle the LUWs, which are missed.
V3 -> Asynchronous Background Update Method Here by seeing name itself we can understand this. I.e. it is Asynchronous Update Method with background job.
Update Methods,
a.1: (Serialized) V3 Update
b. Direct Delta
c. Queued Delta
d. Un-serialized V3 Update
Note: Before PI Release 2002.1 the only update method available was V3 Update. As of PI 2002.1 three new update methods are available because the V3 update could lead to inconsistencies under certain circumstances. As of PI 2003.1 the old V3 update will not be supported anymore.
a. Update methods: (serialized) V3
Transaction data is collected in the R/3 update tables
Data in the update tables is transferred through a periodic update process to BW Delta queue
Delta loads from BW retrieve the data from this BW Delta queue
Transaction postings lead to:
1. Records in transaction tables and in update tables
2. A periodically scheduled job transfers these postings into the BW delta queue
3. This BW Delta queue is read when a delta load is executed.
Issues:
Even though it says serialized , Correct sequence of extraction data cannot be guaranteed
V2 Update errors can lead to V3 updates never to be processed
Update methods: direct delta
Each document posting is directly transferred into the BW delta queue
Each document posting with delta extraction leads to exactly one LUW in the respective BW delta queues
Transaction postings lead to:
1. Records in transaction tables and in update tables
2. A periodically scheduled job transfers these postings into the BW delta queue
3. This BW Delta queue is read when a delta load is executed.
Pros:
Extraction is independent of V2 update
Less monitoring overhead of update data or extraction queue
Cons:
Not suitable for environments with high number of document changes
Setup and delta initialization have to be executed successfully before document postings are resumed
V1 is more heavily burdened
Update methods: queued delta
Extraction data is collected for the affected application in an extraction queue
Collective run as usual for transferring data into the BW delta queue
Transaction postings lead to:
1. Records in transaction tables and in extraction queue
2. A periodically scheduled job transfers these postings into the BW delta queue
3. This BW Delta queue is read when a delta load is executed.
Pros:
Extraction is independent of V2 update
Suitable for environments with high number of document changes
Writing to extraction queue is within V1-update: this ensures correct serialization
Downtime is reduced to running the setup
Cons:
V1 is more heavily burdened compared to V3
Administrative overhead of extraction queue
Update methods: Un-serialized V3
Extraction data for written as before into the update tables with a V3 update module
V3 collective run transfers the data to BW Delta queue
In contrast to serialized V3, the data in the updating collective run is without regard to sequence from the update tables
Transaction postings lead to:
1. Records in transaction tables and in update tables
2. A periodically scheduled job transfers these postings into the BW delta queue
3.This BW Delta queue is read when a delta load is executed.
Issues:
Only suitable for data target design for which correct sequence of changes is not important e.g. Material Movements
V2 update has to be successful
Direct Delta: With this update mode, the extraction data is transferred with each document posting directly into the BW delta queue. In doing so, each document posting with delta extraction is posted for exactly one LUW in the respective BW delta queues.
Queued Delta: With this update mode, the extraction data is collected for the affected application instead of being collected in an extraction queue, and can be transferred as usual with the V3 update by means of an updating collective run into the BW delta queue. In doing so, up to 10000 delta extractions of documents for an LUW are compressed for each Data Source into the BW delta queue, depending on the application.
Non-serialized V3 Update: With this update mode, the extraction data for the application considered is written as before into the update tables with the help of a V3 update module. They are kept there as long as the data is selected through an updating collective run and are processed. However, in contrast to the current default settings (serialized V3 update), the data in the updating collective run are thereby read without regard to sequence from the update tables and are transferred to the BW delta queue.
V1 - Synchronous update
V2 - Asynchronous update
V3 - Batch asynchronous update
These are different work processes on the application server that takes the update LUW (which may have various DB manipulation SQLs) from the running program and execute it. These are separated to optimize transaction processing capabilities.
Taking an example -
If you create/change a purchase order (me21n/me22n), when you press 'SAVE' and see a success message (PO.... changed...), the update to underlying tables EKKO/EKPO has happened (before you saw the message). This update was executed in the V1 work process.
There are some statistics collecting tables in the system which can capture data for reporting. For example, LIS table S012 stores purchasing data (it is the same data as EKKO/EKPO stored redundantly, but in a different structure to optimize reporting). Now, these tables are updated with the txn you just posted, in a V2 process. Depending on system load, this may happen a few seconds later (after you saw the success message). You can see V1/V2/V3 queues in SM12 or SM13.
V3 is specifically for BW extraction. The update LUW for these is sent to V3 but is not executed immediately. You have to schedule a job (e.g. in LBWE definitions) to process these. This is again to optimize performance.
V2 and V3 are separated from V1 as these are not as real time critical (updating statistical data). If all these updates were put together in one LUW, system performance (concurrency, locking etc) would be impacted.
Serialized V3 update is called after V2 has happened (this is how the code running these updates is written) so if you have both V2 and V3 updates from a txn, if V2 fails or is waiting, V3 will not happen yet.
hope it will helps you.....

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

Job Cancelled Problem

Hi Masters,
In SM37 I seen that 3 jobs were cancelled.
Pls see below:
======
Job started
Step 001 started (program RSSTAT1, variant &0000000002410, user name ALEREMOTE)
Log:Programm RSSTAT1; Request REQU_3ZAF2Q2IY0EE5RZCTYPE2FCAT; Status ; Action Start
Deleting/reconstructing indexes for InfoCube ZSRVPUR01 is not permitted
Deleting/reconstructing indexes for InfoCube ZSRVPUR01 is not permitted
Log:Programm RSSTAT1; Request REQU_3ZAF2Q2IY0EE5RZCTYPE2FCAT; Status @08@; Action Callback
Report RSSTAT1 completed with errors
Job cancelled after system exception ERROR_MESSAGE
How to investigate cancelled jobs under ALEREMOTE? How can i know this cancelled Job's request is assigned for what task.?
How to rerun a cancelled job? Pls tell steps.
Please suggest me.
Thanks,
BW26.

Hi,
it looks like you have an authority problem with aleremote. But anyway, did you check the syslog (sm21) or the dump overview (st22)? Are there any problems logged for the run time of the job?
regards
Siggi
PS: Have look here it might be of some help for you! /people/siegfried.szameitat/blog/2005/07/28/data-load-errors--basic-checks
Message was edited by: Siegfried Szameitat

Job Cancelled with an error "Data does not match the job def: Job terminat"

Dear Friends,
The following job is with respect to an inbound interface that transfers data into SAP.
The file mist.txt is picked from the /FI/in directory of the application server and is moved to the /FI/work directory of application server for processing. Once the program ends up without any error, the file is moved to /FI/archive directory.
The below are the steps listed in job log, no spool is generated for this job and it ended up with an error "Data does not match the job definition; job terminated".Please see below for more info.
1.Job   Started
2.Step 001 started (program Y_SAP_FI_POST, variant MIST, user ID K364646)
3.File mist.txt copied from /data/sap/ARD/interface/FI/in/ to /data/sap/ARD/interface/FI/work/.
4.File mist.txt deleted from /data/sap/ARD/interface/FI/in/.
5.File mist.txt read from /data/sap/ARD/interface/FI/work/.
6.PD-DKLY-Y_SAP_FI_POST: This job was started periodically or directly from SM36/SM37 (Message Class: BD, Message Number : 076)
7.Job PD-DKLY-Y_SAP_FI_POST: Data does not match the job definition; job terminated (Message Class : BD, Message No. 078)
8.Job cancelled after system exception
ERROR_MESSAGE
Could you please analyse and come up about under what circumstance the above error is reported.
As well I heard that because of the customization issues in T.Code BMV0, the above error has raised.
Also please note that we can define as well schedule jobs from the above transaction and the corresponding data is stored in the table TBICU
My Trials
1. Tested uplaoding an empty file
2. Tested uploading with wrong data
3. Tested uploading with improper data that has false file structue
But failed to simulate the above scenario.
Clarification Required
Assume that I have defined a job using BMV0. Is that mandatory to use the same job in SM37/SM36 for scheduling?
Is the above question valid?
Edited by: dharmendra gali on Jan 28, 2008 6:06 AM

Dear Friends,
_Urgent : Please work on this ASAP _
The following job is with respect to an inbound interface that transfers data into SAP.
The file mist.txt is picked from the /FI/in directory of the application server and is moved to the /FI/work directory of application server for processing. Once the program ends up without any error, the file is moved to /FI/archive directory.
The below are the steps listed in job log, no spool is generated for this job and it ended up with an error "Data does not match the job definition; job terminated".Please see below for more info.
1.Job Started
2.Step 001 started (program Y_SAP_FI_POST, variant MIST, user ID K364646)
3.File mist.txt copied from /data/sap/ARD/interface/FI/in/ to /data/sap/ARD/interface/FI/work/.
4.File mist.txt deleted from /data/sap/ARD/interface/FI/in/.
5.File mist.txt read from /data/sap/ARD/interface/FI/work/.
6.PD-DKLY-Y_SAP_FI_POST: This job was started periodically or directly from SM36/SM37 (Message Class: BD, Message Number : 076)
7.Job PD-DKLY-Y_SAP_FI_POST: Data does not match the job definition; job terminated (Message Class : BD, Message No. 078)
8.Job cancelled after system exception
ERROR_MESSAGE
Could you please analyse and come up about under what circumstance the above error is reported.
As well I heard that because of the customization issues in T.Code BMV0, the above error has raised.
Also please note that we can define as well schedule jobs from the above transaction and the corresponding data is stored in the table TBICU
My Trials
1. Tested uplaoding an empty file
2. Tested uploading with wrong data
3. Tested uploading with improper data that has false file structue
But failed to simulate the above scenario.
Clarification Required
Assume that I have defined a job using BMV0. Is that mandatory to use the same job in SM37/SM36 for scheduling?
Is the above question valid?

Job cancelled after system exception ERROR_MESSAGE in DB13

Hello All,
When i opened the t-code DB13 i saw that this job "Mark tables requiring statistics update" is cancelled.
JOB LOG:
12.02.2011 22:00:16 Job started
12.02.2011 22:00:16 Step 001 started (program RSDBAJOB, variant &0000000000085, user ID 80000415)
12.02.2011 22:00:18 Job finished
12.02.2011 22:00:18 Job started
12.02.2011 22:00:18 Step 001 started (program RSADAUP2, variant &0000000000081, user ID 80000415)
12.02.2011 22:01:26 Error when performing the action
12.02.2011 22:01:26 Job cancelled after system exception ERROR_MESSAGE
When check for the BGD Job in SM37 for this job i found the same error in the job log with the status cancelled.
Job log overview for job: DBA!PREPUPDSTAT_____@220000/6007 / 22001700
12.02.2011 22:00:18 Job started
12.02.2011 22:00:18 Step 001 started (program RSADAUP2, variant &0000000000081, user ID 80000415)
12.02.2011 22:01:26 Error when performing the action
12.02.2011 22:01:26 Job cancelled after system exception ERROR_MESSAGE
I couldn't find any logs in SM21 of that time also no dumps in ST22.
Possible reason for this error:
I have scheduled the job Check database structure (only tables) at some other time and deleted the earlier job which was scheduled during the bussiness hours which caused performance problem.
So to avoid performance issue i scheduled this job in the mid night by cancelling the old job which was scheduled during the bussiness hours.
And from the next day i could see this error in DB13.
Rest all the backups are running fine but the only job getting cancelled is for "Mark tables requiring statistics update"
Could anyone tell me what should i do to get rid of this error?
Can i schedule this "Mark tables requiring statistics update" again by deleting the old one?
Thanks.
Regards.
Mudassir Imtiaz

Hello Adrian,
Thanks for your response.
Every alternate day we used to have performance issue at 19:00hrs.
Then when i checked what is causing this problem, i discovered that there was a backup "Check Database Structure (tables only)" scheduled at this time and it was mentioned that this backup may cause performance issue.
Then i changed "Check Database Structure (tables only)" the time of this backup to 03:00hrs.
The next day when i checked DB13 i found that one of the backups failed.
i.e. "Mark Tables Requiring Statistics Update"
Then i checked the log which i posted earlier with the error: "Job cancelled after system exception ERROR_MESSAGE"
I posted this error here and then i tried to delete the jobs scheduled i.e. "Mark Tables Requiring Statistics Update" and then re-schedule it at the same time and interval.
And then it started working fine.
So i just got curious to know the cause of the failure of that job.
Thanks.
Regards,
Mudassir.Imtiaz
P.S There is one more thing which i would like to say which is not related to the above issue, and m sorry to discuss this in this thread.
I found a few Bottlenecks in ST04 with Medium and High priority.
Medium: Selects and fetches selectivity 0.53%: 122569 selects and fetches, 413376906 rows read, 2194738 rows qualified.
High: 108771 primary key range accesses, selectivity 0.19%: 402696322 rows read, 763935 rows qualified.
There are a lot these.
I would really appreciate if you tell me what is the cause for these Bottlenecks and how to resolve.
Thanks a lot.

Background job cancelled

Hi Experts
 I have defined and scheduled a background job using variant, but when i try to execute the job, but it is cancelled and gives the job log as follows.
Job started 00 516 S
Step 001 started (program ZCUT1, variant ZONE, user ID SAP01) 00 550 S
ABAP/4 processor: OBJECTS_OBJREF_NOT_ASSIGNED 00 671 A
Job cancelled 00 518 A
What could be the reason, pls help me solve it out.
Thanks in advance.
Regards
Rajaram

HI,
refer this once.
There are two ways for you to handle,
one manually setting up the job through SM36 which is better and convinient,
secondly through program using FM's JOB_OPEN, SUBMIT, JOB_CLOSE.
Find below steps in doing both:
Procedure 1:
1. Goto Trans -> SM36
2. Define a job with the program and variant if any
3. Click on start condition in application tool bar
4. In the pop-up window, click on Date/Time
5. Below you can see a check box "Periodic Job"
6. Next click on Period Values
7. Select "Other Period"
8. Now give '15' for Minutes
9. Save the job
In SM37 u can check the status of the jobs that u have assigned to background...
Here u mention the job name or the report name to check the status of the job...
After mentioning the job name or program name u just execute it.. ( without any name also u can execute then it gives u all the jobs set by your user name..
the status colud be released,active,finished etc..
Procedure 2 via Program:
Below is a sample code for the same. Note the ZTEMP2 is the program i am scheduling with 15mins frequency.
DATA: P_JOBCNT LIKE TBTCJOB-JOBCOUNT,
L_RELEASE(1) TYPE c.
CALL FUNCTION 'JOB_OPEN'
EXPORTING
JOBNAME = 'ZTEMP2'
IMPORTING
JOBCOUNT = P_JOBCNT
EXCEPTIONS
CANT_CREATE_JOB = 1
INVALID_JOB_DATA = 2
JOBNAME_MISSING = 3
OTHERS = 4.
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
SUBMIT ZTEMP2 VIA JOB 'ZTEMP2' NUMBER P_JOBCNT
TO SAP-SPOOL WITHOUT SPOOL DYNPRO
WITH DESTINATION = 'HPMISPRT'
WITH IMMEDIATELY = SPACE
WITH KEEP_IN_SPOOL = 'X' AND RETURN.
CALL FUNCTION 'JOB_CLOSE'
EXPORTING
JOBCOUNT = P_JOBCNT
JOBNAME = 'ZTEMP2'
STRTIMMED = 'X'
PRDMINS = 15
IMPORTING
JOB_WAS_RELEASED = L_RELEASE
EXCEPTIONS
CANT_START_IMMEDIATE = 1
INVALID_STARTDATE = 2
JOBNAME_MISSING = 3
JOB_CLOSE_FAILED = 4
JOB_NOSTEPS = 5
JOB_NOTEX = 6
LOCK_FAILED = 7
INVALID_TARGET = 8
OTHERS = 9.
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.

Message with IDOC number, created by LSMW, missing in job log in SM37

Hi gurus,
We have a temporary interface which uses LSMW to create IDOCs and update in SAP. It's used for materials, BOMs and document info records. In LSMW we have defined standard message types MATMAS_BAPI, BOMMAT and DOCUMENT_LOAD for the IDOCs. All these have the same problem.
A background job runs and starts LSMW. In the job log in SM37 I want to see which IDOCs were created. For some reason this is different in my development system and my test system, and as far as I know all settings should be the same. In the test system LSMW creates more message lines in the job log, than it does in the dev system. Message number E0-097 is "IDOC XXXX added", and this is missing in the dev system.
This is what it looks like in the dev system:
Data transfer started for object 'MATMAS' (project 'X', subobject 'Y')             /SAPDMC/LSMW   501    I
Import program executed successfully                                                             /SAPDMC/LSMW   509    I
File 'XXX.lsmw.read' exists                                                                               /SAPDMC/LSMW   502    I
Conversion program executed successfully                                                    /SAPDMC/LSMW   513    I
Data transfer terminated for object 'MATMAS' (project 'X', subproject 'Y')       /SAPDMC/LSMW 516    I
And this is what it looks like in the test system. More information, which is exactly what I want in dev system too:
Data transfer started for object 'MATMAS' (project 'X', subobject 'Y')             /SAPDMC/LSMW   501    I
Import program executed successfully                                                             /SAPDMC/LSMW 509    I
File 'XXX.lsmw.read' exists                                                                               /SAPDMC/LSMW 502    I
Conversion program executed successfully                                                    /SAPDMC/LSMW 513    I
File 'XXX.lsmw.conv' exists                                                                              /SAPDMC/LSMW   502   I
IDoc '0000000002489289' added                                                                      E0                         097   S
File 'XXX.lsmw.conv' transferred for IDoc generation                                      /SAPDMC/LSMW   812   I
Data transfer terminated for object 'MATMAS' (project 'X', subproject 'Y')      /SAPDMC/LSMW   516   I
In both cases the IDOC is created and update works fine.
My only issue is that I can't see the IDOC number in the dev system. I know I can get the IDOC number in WE02, but in this case we have program logic which reads the job log to be able to check IDOC status before sending OK message back to the other side of the interface.
I hope any of you can have an idea how I can update somewhere to get message E0-097 with IDOC number into the log.
Regards,
Lisbeth

Hi Arun,
If you want to show your messages in the job log you have to use the MESSAGE statement. In case you use WRITE statements an output list be created which can be found in the spool (there is an icon to go to the spool directly).
Regards,
John.

Job cancelled While loading data from DSO to CUBE using DTP

Hi All,
while i am loading data frm DSO to CUBE the job load is getting cancelled.
in the job overview i got the following messages
SYST: Date 00/01/0000 not expected.
Job cancelled after system exception ERROR_MESSAGE
wt can be the reason for this error as i have successfully loaded data into 2 layers of DSO before loading the data into the CUBE

hi,
Are u loading the flat file to DSO?
then check the data in the PSA in the date field and replace with the correct date.
i think u r using write optimised DSO which is similar to PSA it will take all the data from PSA to DSO.
so clear the data in PSA and then load to DSO and then to CUBE.
If u dont need a date field in CUBE then remove the mapping in transformation in cube and activate and make DTP activate and trigger it it will work.

Job cancelled after system exception ERROR_MESSAGE

Hello all
I am facing the following issue.
A custom report is schedulled and run as backround job. The report should create a txt file on server.
The report works fine in foreground, but as backround job ends up cancelled all the time.
The job log:
Job log overview for job:    VI5 / 13072800
Date       Time     Message text                                                                     Message class Message no. Message type
27.03.2009 13:09:28 Job started                                                                           00           516          S
27.03.2009 13:09:28 Step 001 started (program ZESSRIN110R, variant PR1_0000381, user ID METAPARTNER)      00           550          S
27.03.2009 13:09:28 File creation ERROR:                                                                  00           001          E
27.03.2009 13:09:28 Job cancelled after system exception ERROR_MESSAGE                                    00           564          A
There is no info in SM21 regarding the error.
Can anybody help with this?
Thanx in advance.
imi
Edited by: Imrich Vegh on Mar 27, 2009 2:27 PM

btw the part of my code looks like this:
server path check
    IF p_srv IS NOT INITIAL.
      OPEN DATASET gv_server FOR OUTPUT IN TEXT MODE ENCODING DEFAULT.
      IF sy-subrc EQ 0.     --- I keep receiving 8 here in BACKGROUND JOB
        WRITE : / text-077, gv_server.
      ELSE.
        MESSAGE text-069 TYPE 'E'.
      ENDIF.

Read the job Z_JOB from SM37 and re-schedule dynamically

Hi All,
I have one requirement where I need to schedule a job in background. The job Z_JOB has 10 steps in it and each step itu2019s calling different program with a variant. Now I need write a Z program to re-schedule the Z_JOB dynamically.
I know how to schedule the job with multiple steps through program. (JOB_OPEN, Submit Statement, JOB_CLOSE). But my question is there any other way to read the job Z_JOB from SM37 and re-schedule dynamically. So that I can avoid this 10 SUBMIT programu2026??
Thanks in Advance,
Raghu.

Hello Raghu ,
JOB_OPEN ( Opens a BG job )
JOB_SUBMIT ( Insert a background Task)
JOB_CLOSE (Closes a BG job)
Are the 3 function module by with you can create a have a bg job sheduled programatically...!
Hope it helps
Edited by: Anup Deshmukh on May 3, 2010 12:36 PM

Background job cancelled , where as working fine in foreground

Hi,
In selection screen , I have a to provide a file name and execute the program.
When I execute in foreground its working fine, but where are when I execute in background with variant it shows invalid file name and job cancelled in long text.
Please suggest me what would be the problem and possible solution.
Thanks,
Ameer

Hi Ameer,
Add the following condition for running the prgram in Background.
*****To upload file*********
IF sy-batch = 'X'. "-----> If backgroung execution option is selected.
OPEN DATASET p_filename FOR INPUT IN TEXT MODE ENCODING DEFAULT.
WHILE sy-subrc = 0.
      READ DATASET p_filename INTO wa_struc.
      APPEND wa_struc TO itab_struc.
ENDWHILE.
CLOSE DATASET p_filename .
ENDIF.
*****To download file*********
IF sy-batch = 'X'.
   OPEN DATASET p_filename1 IN TEXT MODE FOR OUTPUT ENCODING DEFAULT.
   IF sy-subrc = 0.
    LOOP AT itab_struc INTO wa_struc.
      TRANSFER wa_struc TO p_filename1.
    ENDLOOP.
    CLOSE DATASET p_filename1.
ENDIF.
ENDIF.
Hope this addresses your issue.
Regards,
Arnab

SAP_CCMS_DT_SCHEDULER job cancelled in SM37

Similar Messages

Maybe you are looking for