F110 job cancelled during an SAP restart

Our payment run transaction F110 was running its payment process batch program at the time when our SAP system was stopped and restarted today (to fix an unrelated issue).
A few postings were generated, but have many more to process. Payment run status states the run was cancelled and the number of postings generated.
We are unable to complete the process by printing what has been generated and re-process another payment run or complete the existing run.
We have tried to look in a few system transactions to see if we could release locks or process updates (SM12 and SM13, respectively). We can see the cancelled job in the job log, SM37.
Can anyone help as to how we can complete the payment run process?

HI -
Thank you for this information. Actually our job had already cancelled as a result of SAP coming down. As it turns out, our FI business analyst did some additional online digging for this answer as well, and together with the payroll client, they deleted the rest of the run somehow (it was stuck partially done). They were able to back out and then re-run the entire process from the beginning.
When I get the specific menu choices and actions they took from their documentation, I will post that as well to close this question. I just wanted to respond at this time to tell you it was resolved.
Thank you!
Jeremy

Similar Messages

Job cancelled during Business content Activation

Hello gurus,
When i tried to Install them ( BI 7)Info objects (DF before and DF after)(automatic collection) in the background,the job gets cancelled after sometime(sm37).But i could see them Info objects in RSA1 (but no context menu to view the hierarchies under specific info objects)(eg: MATERIAL,COSTCENTER..).But i can see them Hierarchy tables when in the IO definition.Infosources and Info cubes are present aswell,but no Datasources!!!!! Well can somebody take time to help me out here..
manythanks
arun
(note: Would assign points for sure)

Hi,
Try installing necessary objects. (use that option) and load the reequired infources, datsources ect. separately instaed of loading after and before option.
It will be more efficient.
*Hope it helps.

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

SAP Connect Job Cancelling

I keep having this same issue happening every couple of weeks where the scheduled workflow job SAPCONNECT ALL SEND will start canceling out with the error "Job canceled due to system shutdown". Usually when this happens there will be an RFC connection in SM51 that is stuck in a loop. The only way we can fix the issue is by doing a complete reboot of the server. Is this something that normally happens with this job?

Was able to fix the issue by updating to the latest SAPCCMSR.

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.

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 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 canceled in Solution Manager system

Dear all expert ,
Two background jobs canceled in solution manager system before some time.
details-
Background jobs :
                    1 - LANDSCAPE FETCH
    Program name : RSGET_SMSY
Job log : Job started
Step 001 started (program RSGET_SMSY, variant ,
The SLD server connection is inactive
Job cancelled after system exception ERROR_MESSAGE
                   2 - SEND_SYSTEM_RELATIONSHIP_TO_SUP
    Program name : AI_SC_SEND_SYSTEM_RELATIONSHIP
Job log :
                   Job started
Step 001 started (program AI_SC_SEND_SYSTEM_RELATIONSHIP, variant ,
SOL determined as monitoring Solution Manager system
SAP customer number unknown for installation number 0020606335
Job cancelled after system exception ERROR_MESSAGE
please help me , what should i do ?
I am waiting for your positive response.
Regards
Shubh

hi,
You can try following ....
For the job SEND_SYSTEM_RELATIONSHIP_TO_SUP
Program : AI_SC_SEND_SYSTEM_RELATIONSHIP
1. Up to Support Package 09:
a) Start transaction SMSY.
b) Choose Shft+F5.
c) Select the system named in the message.
d) Choose F6.
e) Select the "System Data in SAP Support Portal" tab.
f) Using the input help, fill the system number field with the correct system.
g) Save the data.
2. Up to and including Support Package 08:
a) Start transaction SOLMAN_CONNECT.
b) Select the system in question in the ID field and choose the filter pushbutton.
c) Select the system and select "Create configuration".
d) Fill the system number field using the input help with the correct system.
e) For example, select the "BW GUI Connection" service type.
f) Carry out all of the subsequent steps of the Configuration Assistant until you see the "Finish" pushbutton.
This establishes a unique relationship between your system in the Solution Manager and the system number in the SAP Support Portal. Problems no longer occur with this system when the SEND_SYSTEM_RELATIONSHIP_TO_SUPP job is next run. However, the problem may still exist for other systems (in these cases, you should follow the same steps).
Hope this will help to solve your issue..
Regards
Bhuban
RKFL

Error when executing APD-Job cancelled after system exception ERROR_MESSAGE

Hi,
We have a process chain which executes a APD using an ABAP program RSAN_PROCESS_EXECUTE.
It was executing successfully until few days back but now a days frequently once in 3 days roughly it is getting cancelled during execution of ABAP Program with the message 'Job cancelled after system exception ERROR_MESSAGE'
checked st22 and sm21 but didn't get any clue.But if we execute the same process chain manually(Immediate load) it is working fine all the times.
What may be the reason for the cancellation of the chain sometimes and the same chain working fine some other time and working very much fine when ran manually.
Regards,
Vishnu

Hi Vishnu,
Can you check if there are any other process which is triggering the abap program RSAN_PROCESS_EXECUTE at the same time as the execution of this process in the chain. You can check in which other chains this process is being used. You can compare the time when this failed in the chain you mentioned with the same being run in other chains at the same time.
Sasi

Back ground job cancelling

Hello Everyone,
Our scheduled background job cancel each time in job log log it gives this error message:
""ABAP/4 processor: TSV_TNEW_BLOCKS_NO_ROLL_MEMORY"".
This is a ABAP Memory Message.
I went into ST22 and saw the error message. System is not able to allocate memory to the data selected from the table( No roll storage space of length 3178504 available for internal storage.). Probably i need increase the roll memory of our server, i think this will done by basis people.or Alternatly i can process the data by small packets like 1000 records every time.
So i can i know how can i process the data by small packets like 1000 records every time.
Need your help.
Thanks,
Lasya.

Hi
If you can divide the data into two internal tables and later collect into the one internal table, this could solve yuor problem.
Also you need to make sure that enough memory is available in the system. Check DB6cockpit for that.
Also there are a lot of correction notes available with SAP for the error"TSV_TNEW_BLOCKS_NO_ROLL_MEMORY"
Check what the job exactly does, and search for the relevant notes, as there are different notes for different application areas...
if its a loading job(Infopackage) you can reduce the data packet size of the IP, but that might hamper the loading performance.
Hope this helps
Regards
Shilpa

SAP_WP_CACHE_RELOAD_FULL - JOB CANCELLED

Dear All,
This job is running daily "SAP_WP_CACHE_RELOAD_FULL" & its getting cancelled. I am sending the job logs .
Job started
Step 001 started (program RWP_RUNTIME_CACHE_RELOAD, variant SAP&RELOAD_ALL, user ID SA
No component system chosen
Job cancelled after system exception ERROR_MESSAGE
Kindly help on this issue.
Thanks
S SURESH

As far as I know that job should be removed,
Read Note 16083 - Standard jobs, reorganization jobs
Regards
Juan

All my B/G job canceling due to dump: TSV_TNEW_PAGE_ALLOC_FAILED

Hi SAP Gurus,
Production system SAP R/3 Enterprice. 4.7
OS:AIX 5.3
DB:DB2
memory Parameters are already set properly, there was no issues from past 3 years, We din't change any parameter recently.
All my Pay run B/G job canceling due to dump: TSV_TNEW_PAGE_ALLOC_FAILED
B/G job log
================
11/26/2007 03:01:22 Job started
11/26/2007 03:01:22 Step 001 started (program RBDSER01, variant YBD40_01, user ID BC-BATCH)
11/26/2007 03:01:22 0 master IDocs set up for message type CHRMAS
11/26/2007 03:01:22 0 communication IDoc(s) generated for message type CHRMAS
11/26/2007 03:01:23 0 master IDocs set up for message type CLSMAS
11/26/2007 03:01:23 0 communication IDoc(s) generated for message type CLSMAS
11/26/2007 03:01:23 0 master IDocs set up for message type CLFMAS
11/26/2007 03:01:23 0 communication IDoc(s) generated for message type CLFMAS
11/26/2007 03:05:53 ABAP/4 processor: TSV_TNEW_PAGE_ALLOC_FAILED
11/26/2007 03:05:54 Job cancelled
Please let me know ASAP,
Thanks & Regards,
Kishore.
null

Hi,
If you did'nt change anything in the system, you'd better open a SAP support call urgently as it is a production problem...
>>>Production system SAP R/3 Enterprice. 4.7
Nice and well choosen typo !
Regards,
Olivier

Bacground job cancelled in Solman system.

Hi experts,
Two bacground job cancelled in Solman system.
1. SM:SELFDIAGNOSIS
Job started
Step 001 started (program RDSWP_SELF_DIAGNOSIS, variant &0000000001018, user ID SAP*)
ABAP/4 processor: MOVE_TO_LIT_NOTALLOWED_NODATA
Job cancelled
2.SM:SYNC SAP SESSIONS
Job started
Step 001 started (program RDSWPCISERVICEPLAN, variant &0000000001018, user ID SAP*)
Your user has no SAP Support Portal user assigned
Job cancelled after system exception ERROR_MESSAGE
Please give me the soltuin to fix it.
Regards,

Hi Vivek,
1). Adobe forms (TCode SFP) offers a feature where you can pass the value of the table instead of table iteself. For this yuo have to go to SFP > INTERFACE > Interface (Tab) >(Click on) Import
Here, you should see all the parameters listed. On the parameter that you want to meddle with, tick the "Pass Value" checkbox. This solved the issue and prevented the dump.
Exception MOVE_TO_LIT_NOTALLOWED_NODATA
Refer to the Note 834318 ...
2). please maintain the your S - user id in AISUSER t-code. Refer to below link for screenshots.
http://wiki.sdn.sap.com/wiki/display/SM/HowtomaintainthetransactionAISUSERforstandardandVARscenarios
Regards,
Arjun
Edited by: Arjun Venkateswarlu. on Jan 12, 2012 9:35 PM

SM:EXEC SERVICES JOB CANCELLED with MESSAGE_TYPE_X dump

In SAP solution manager server SM:EXEC SERVICES job is Cancelling
Hence we are unbale to get the EWA reports...
Error:
Job started
Step 001 started (program RDSMOPBACK_AUTOSESSIONS, variant
&0000000001009, user ID RAOP)
Solution OC Application Monitoring is being edited (Operations)
Trying to perform session 5000000003618
ABAP/4 processor: MESSAGE_TYPE_X
Job cancelled
Applied note 727998 but no use... please help me .
Regards
Prabhakar
Version details:
ST-SER 620-2006_2
PI_ BASIS 2005_1_620

Hi Prabhakar,
Which SP of Solman are you using? If you are using Solman SP12 then the ST-SER has to be upgraded to higher version. Also update the PI_BASIS component.
ST-SER 700_2007_1
PI_BASIS 2006_1_700.
Regards,
Raghavendra.

F110 job cancelled during an SAP restart

Similar Messages

Maybe you are looking for