SM21 Log - Transaction Termination 01 540
Hi,
Lately, the below error has been creating in SM21 syslog multiple times a minute in our SAP system.
There is no user and txn detected in SM21 syslog.
I have deleted the CUA, its child systems, GUM data and BD64 but it still does not stop.
I have checked SM50/SM51, no suspicious activity going on. I have checked batch jobs across systems, nothing running.
I have checked SM04, no suspicious users/connection. No dumps at ST22.
I am running out of ideas. Does anyone has any clue what could be causing it?
We are running R/3 46C, Oracle 10.2.0.2, AIX 5.3. Kernel 46D_EXT, 2415.
SM21 Syslog
=============
"DIA 00 D01 Transaction termination 01 540 ( )"
Documentation for system log message D0 1 :
The transaction has been terminated. This may be caused by a
termination message from the application (MESSAGE Axxx) or by an
error detected by the SAP System due to which it makes no sense to
proceed with the transaction. The actual reason for the termination
is indicated by the T100 message and the parameters.
Additional documentation for message 01 540
You cannot log on (CUA system authorization missing)
No documentation exists for message 01540
Thanks in advance.
Check for error messages on the developer traces of the dialog instances dev_w*
Also check that the CUA user has proper rights specially S_RFC and that the CUA child is a trusted system
Regards
Juan
Similar Messages
-
Sm21 log (Transaction Canceled DB 61)
Hi,
Can u pls suggest for the below log, what action should be take to void this error, Iam getting toomany log daily.
08:02:01 BTC 021 300 WF-BATCH D0 1 Transaction Canceled DB 612 ( #0000000000001 RSWWDHEX )
Details
Recording at local and central time........................ 12.01.2010 08:02:01
Task...... Process User...... Terminal Session TCode Program Cl Problem
01478 Background Processor No. 021 WF-BATCH 1 RSWWDHEX K SAP Web
Module nam Loc T100................ Parameters
DB 612
Documentation for system log message D0 1 :
The transaction has been terminated. This may be caused by a
termination message from the application (MESSAGE Axxx) or by an
error detected by the SAP System due to which it makes no sense to
proceed with the transaction. The actual reason for the termination
is indicated by the T100 message and the parameters.
Thanks
SumanHi,
it looks like the job (program RSWWDHEX) for monitoring deadlines in workflow is failing to start. Have you applied support pack recently? You can try to reschedule that job using transaction SWWB. The problem is described in note 618656. There are also some other notes related to this job. So I would suggest to search for additional notes.
Cheers -
Transaction termination 00 158 ( )
Today in SM21 i found many of this error log (almost 200-250 logs)
08:04:27 DIA 01 D01 Transaction termination 00 158 ( )
08:04:27 DIA 01 R68 Perform rollback
08:04:27 DIA 01 R68 Perform rollback
Documentation for system log message D0 1 :
The transaction has been terminated. This may be caused by a
termination message from the application (MESSAGE Axxx) or by an
error detected by the SAP System due to which it makes no sense to
proceed with the transaction. The actual reason for the termination
is indicated by the T100 message and the parameters.
Additional documentation for message 00 158
User is locked. Please notify the person responsible
No documentation exists for message 00158
I checked SUIM but there are few and old locked user
Anyone knows what's the reason?Trace file opened at 20061213 124800 NFT, REL 46D,0,2113, VER 3
======> connection closed
Trace file opened at 20061213 124842 NFT, REL 46D,0,2113, VER 3
======> connection closed
Trace file opened at 20061213 125030 NFT, REL 46D,0,2113, VER 3
======> connection closed
Trace file opened at 20061213 125038 NFT, REL 46D,0,2113, VER 3
======> connection closed
Trace file opened at 20061213 125421 NFT, REL 46D,0,2113, VER 3
======> connection closed
Trace file opened at 20061213 185054 NFT, REL 46D,0,2113, VER 3
======> CPIC-CALL: 'ThSAPECMINIT'
Time out durante la realizzazione del collegamento (partner esistente?)
Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 1356
CPIC-CALL: 'ThSAPECMINIT'
Time out durante la realizzazione del collegamento (partner esistente?)
DEST =SAPOSCOL_CAPDB
HOST =10.200.255.119
PROG =rfcoscol
Trace file opened at 20061213 185120 NFT, REL 46D,0,2113, VER 3
======> CPIC-CALL: 'ThSAPECMINIT'
Time out durante la realizzazione del collegamento (partner esistente?)
Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 1356
CPIC-CALL: 'ThSAPECMINIT'
Time out durante la realizzazione del collegamento (partner esistente?)
DEST =SAPOSCOL_CAPDB
HOST =10.200.255.119
PROG =rfcoscol
Trace file opened at 20061213 190942 NFT, REL 46D,0,2113, VER 3
======> connection closed
Trace file opened at 20061213 205048 NFT, REL 46D,0,2113, VER 3
======> CPIC-CALL: 'ThSAPECMINIT'
Time out durante la realizzazione del collegamento (partner esistente?)
Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 1356
CPIC-CALL: 'ThSAPECMINIT'
Time out durante la realizzazione del collegamento (partner esistente?)
DEST =SAPOSCOL_CAPDB
HOST =10.200.255.119
PROG =rfcoscol
Trace file opened at 20061213 205111 NFT, REL 46D,0,2113, VER 3
======> CPIC-CALL: 'ThSAPECMINIT'
Time out durante la realizzazione del collegamento (partner esistente?)
Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 1356
CPIC-CALL: 'ThSAPECMINIT'
Time out durante la realizzazione del collegamento (partner esistente?)
DEST =SAPOSCOL_CAPDB
HOST =10.200.255.119
PROG =rfcoscol
Trace file opened at 20061213 205507 NFT, REL 46D,0,2113, VER 3
======> CPIC-CALL: 'ThSAPCMRCV'
Il Gateway locale non è attivo
Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 2943
CPIC-CALL: 'ThSAPCMRCV'
Il Gateway locale non è attivo
Trace file opened at 20061214 005047 NFT, REL 46D,0,2113, VER 3
======> CPIC-CALL: 'ThSAPECMINIT'
Time out durante la realizzazione del collegamento (partner esistente?)
Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 1356
CPIC-CALL: 'ThSAPECMINIT'
Time out durante la realizzazione del collegamento (partner esistente?)
DEST =SAPOSCOL_CAPDB
HOST =10.200.255.119
PROG =rfcoscol
Trace file opened at 20061214 005114 NFT, REL 46D,0,2113, VER 3
======> CPIC-CALL: 'ThSAPECMINIT'
Time out durante la realizzazione del collegamento (partner esistente?)
Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 1356
CPIC-CALL: 'ThSAPECMINIT'
Time out durante la realizzazione del collegamento (partner esistente?)
DEST =SAPOSCOL_CAPDB
HOST =10.200.255.119
PROG =rfcoscol
Trace file opened at 20061214 025054 NFT, REL 46D,0,2113, VER 3
======> CPIC-CALL: 'ThSAPECMINIT'
Time out durante la realizzazione del collegamento (partner esistente?)
Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 1356
CPIC-CALL: 'ThSAPECMINIT'
Time out durante la realizzazione del collegamento (partner esistente?)
DEST =SAPOSCOL_CAPDB
HOST =10.200.255.119
PROG =rfcoscol
Trace file opened at 20061214 025122 NFT, REL 46D,0,2113, VER 3
======> CPIC-CALL: 'ThSAPECMINIT'
Time out durante la realizzazione del collegamento (partner esistente?)
Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 1356
CPIC-CALL: 'ThSAPECMINIT'
Time out durante la realizzazione del collegamento (partner esistente?)
DEST =SAPOSCOL_CAPDB
HOST =10.200.255.119
PROG =rfcoscol
Trace file opened at 20061214 045052 NFT, REL 46D,0,2113, VER 3
======> CPIC-CALL: 'ThSAPECMINIT'
Time out durante la realizzazione del collegamento (partner esistente?)
Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 1356
CPIC-CALL: 'ThSAPECMINIT'
Time out durante la realizzazione del collegamento (partner esistente?)
DEST =SAPOSCOL_CAPDB
HOST =10.200.255.119
PROG =rfcoscol
Trace file opened at 20061214 045116 NFT, REL 46D,0,2113, VER 3
======> CPIC-CALL: 'ThSAPECMINIT'
Time out durante la realizzazione del collegamento (partner esistente?)
Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 1356
CPIC-CALL: 'ThSAPECMINIT'
Time out durante la realizzazione del collegamento (partner esistente?)
DEST =SAPOSCOL_CAPDB
HOST =10.200.255.119
PROG =rfcoscol
Trace file opened at 20061214 095956 NFT, REL 46D,0,2113, VER 3
======> connection closed
Trace file opened at 20061214 123854 NFT, REL 46D,0,2113, VER 3
======> connection closed
Trace file opened at 20061214 123904 NFT, REL 46D,0,2113, VER 3
======> connection closed
Trace file opened at 20061214 165052 NFT, REL 46D,0,2113, VER 3
======> CPIC-CALL: 'ThSAPECMINIT'
Time out durante la realizzazione del collegamento (partner esistente?)
Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 1356
CPIC-CALL: 'ThSAPECMINIT'
Time out durante la realizzazione del collegamento (partner esistente?)
DEST =SAPOSCOL_CAPDB
HOST =10.200.255.119
PROG =rfcoscol
Trace file opened at 20061214 165117 NFT, REL 46D,0,2113, VER 3
======> CPIC-CALL: 'ThSAPECMINIT'
Time out durante la realizzazione del collegamento (partner esistente?)
Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 1356
CPIC-CALL: 'ThSAPECMINIT'
Time out durante la realizzazione del collegamento (partner esistente?)
DEST =SAPOSCOL_CAPDB
HOST =10.200.255.119
PROG =rfcoscol
Trace file opened at 20061214 205054 NFT, REL 46D,0,2113, VER 3
======> CPIC-CALL: 'ThSAPECMINIT'
Time out durante la realizzazione del collegamento (partner esistente?)
Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 1356
CPIC-CALL: 'ThSAPECMINIT'
Time out durante la realizzazione del collegamento (partner esistente?)
DEST =SAPOSCOL_CAPDB
HOST =10.200.255.119
PROG =rfcoscol
Trace file opened at 20061214 205124 NFT, REL 46D,0,2113, VER 3
======> CPIC-CALL: 'ThSAPECMINIT'
Time out durante la realizzazione del collegamento (partner esistente?)
Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 1356
CPIC-CALL: 'ThSAPECMINIT'
Time out durante la realizzazione del collegamento (partner esistente?)
DEST =SAPOSCOL_CAPDB
HOST =10.200.255.119
PROG =rfcoscol
Trace file opened at 20061215 005057 NFT, REL 46D,0,2113, VER 3
======> CPIC-CALL: 'ThSAPECMINIT'
Time out durante la realizzazione del collegamento (partner esistente?)
Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 1356
CPIC-CALL: 'ThSAPECMINIT'
Time out durante la realizzazione del collegamento (partner esistente?)
DEST =SAPOSCOL_CAPDB
HOST =10.200.255.119
PROG =rfcoscol
Trace file opened at 20061215 005129 NFT, REL 46D,0,2113, VER 3
======> CPIC-CALL: 'ThSAPECMINIT'
Time out durante la realizzazione del collegamento (partner esistente?)
Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 1356
CPIC-CALL: 'ThSAPECMINIT'
Time out durante la realizzazione del collegamento (partner esistente?)
DEST =SAPOSCOL_CAPDB
HOST =10.200.255.119
PROG =rfcoscol
Trace file opened at 20061215 025102 NFT, REL 46D,0,2113, VER 3
======> CPIC-CALL: 'ThSAPECMINIT'
Time out durante la realizzazione del collegamento (partner esistente?)
Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 1356
CPIC-CALL: 'ThSAPECMINIT'
Time out durante la realizzazione del collegamento (partner esistente?)
DEST =SAPOSCOL_CAPDB
HOST =10.200.255.119
PROG =rfcoscol
Trace file opened at 20061215 025131 NFT, REL 46D,0,2113, VER 3
======> CPIC-CALL: 'ThSAPECMINIT'
Time out durante la realizzazione del collegamento (partner esistente?) -
Hi Folks,
I have noticed that some of the entries from the SM21 logs get deleted in few hours.
For example our team report the error "Transaction Canceled DB 645" in sm21 log at 26.05.2011 at 4:00 AM.
When we checked the SM21 logs at 10:00 AM on the same day, the entry was no longer present.
Request you to kindly help me in this.
Regards,
YasminMy Stderr file reads the below. Please help me understand the context and if there is any issue.
(22476) New Child Process created.
(22476) Starting local Command:
Command: dw.sapPRD_DVEBMGS00
pf=/usr/sap/PRD/SYS/profile/PRD_DVEBMGS00_ebdchux2
ICM up and operational (pid: 22480) ***
work process W3 died => ThSigHandler: signal
work process W1 died => ThSigHandler: signal
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
work process W1 died => ThSigHandler: signal
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
work process W4 died => ThSigHandler: signal
work process W2 died => ThSigHandler: signal
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
work process W1 died => ThSigHandler: signal
work process W4 died => ThSigHandler: signal
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
work process W1 died => ThSigHandler: signal
work process W2 died => ThSigHandler: signal -
Transaction termination KI 294
Hi,
We have a SAP system(R/3 release 4.6C) with Oracle (9.2.0.7.0) as Database. We have got number of errors in SM21 for the Background user. But i am not able to get any cancelled job at the particular time at SM37 for this user. The errors looks like
Transaction termination KI 294 ( 00000002 0000000133 )
Transaction termination KI 294 ( 00000033 0000000135 )
Transaction termination KI 294 ( 00000004 0000000133 ).
The description of this error in SM21 comes as such:
Additional documentation for message KI 294
System error: network activity with invalid internal number
&CAUSE&
A network activity has not been defined for the number &V1& &V2
internally.
&SYSTEM_RESPONSE&
&WHAT_TO_DO&
Inform your system administrator.
I have checked with the same error in SAP Market place where i have not got any detail. Iam not getting any clue how to proceed further. Please guide me on resolving this issue at the earliest.
Thanks in advance.
Regards,
Shahul Hameed MHi,
We have a SAP system(R/3 release 4.6C) with Oracle (9.2.0.7.0) as Database. We have got number of errors in SM21 for the Background user. But i am not able to get any cancelled job at the particular time at SM37 for this user. The errors looks like
Transaction termination KI 294 ( 00000002 0000000133 )
Transaction termination KI 294 ( 00000033 0000000135 )
Transaction termination KI 294 ( 00000004 0000000133 ).
The description of this error in SM21 comes as such:
Additional documentation for message KI 294
System error: network activity with invalid internal number
&CAUSE&
A network activity has not been defined for the number &V1& &V2
internally.
&SYSTEM_RESPONSE&
&WHAT_TO_DO&
Inform your system administrator.
I have checked with the same error in SAP Market place where i have not got any detail. Iam not getting any clue how to proceed further. Please guide me on resolving this issue at the earliest.
Thanks in advance.
Regards,
Shahul Hameed M -
Create RFx Response: An error occurred in the PD Layer transaction terminated
Hello Experts,
Currently we are in SRM 7.02 implemenation: we are facing below problem while creating RFx response with popup screen.
"An error occurred in the PD Layer transaction terminated"
For this we have checked below
1. http://scn.sap.com/thread/1912966 ----> it didn't help
2. We have assigned SAP_ALL role to bidder also ----> Facing same issue
3. Check Number ranges ---> everything is fine.
there is no clue from above points.
Thanks & Regards
Sandeep.Hello Sandeep,
I am facing the same problem while creating the RFx response in SUS side. Same error occurred while i am creating the Rfx response with bidder.
error: An error occurred in the PD Layer transaction terminated
Could you please let me know, did you find any solution for this issue?
Thanks in advance!!
Thanks,
Anil -
An error occurred in the PD layer; transaction terminated in SC
Hi experts,
I have an issue like this "An error occurred in the PD layer; transaction terminated". This error came when i save Shopping Cart.
Just for the information, I have maintained number range assignment for BUS2121 - Shopping Carts also.
And I am working on SRM 7.0
Do you have any idea to solve this issue?
Thanks,
Rhesa SyahrialHi Sam,
Thanks for your fast reply.
Below is the error analysis from st22.
An exception occurred which is explained in detail below.
The exception, which is assigned to class 'CX_BBP_PD_ABORT', was not caught and
therefore caused a runtime error.
The reason for the exception is:
Buffer table not up-to-date
I have checked in sapnote also about this issue. but still not resolved.
Regards,
Rhesa Syahrial -
How can i log transaction codes, programes and tables used by a user?
Hi everyone,
i need to log transaction codes, programes and tables a user has used in a certain time. how can i trace that and is it possible with timestamps?
i tried something with the badi workload_statistic but thats not what i need. is there a simple function which can do that or is this really much more complicated?In SE13 there is an option to log table changes for a table.
If you search for "SCU3" you will find plenty of information on this. Also search for "RECCLIENT" (without the "/") and you will find some more specialized threads.
Cheers,
Julius -
Inconsistency in classification data = transaction terminated
Hello Guys & Gals,
I am doing the transaction CORK for Partial Confirmation of Process Orders.At the end of the Transaction,after putting the Production date & when saving it,a mesage is showing that "ERROR IN GOODS MOVEMENTS".when i m going through the termination message,it shows the message text that
"Inconsistency in classification data => transaction terminated"
By double clicking over the same,the below details is shown:-
Inconsistency in classification data => transaction terminated
Message no. 12126
Diagnosis
An inconsistency resulted during initialization of the classification data in the batch master transaction. The transaction therefore had to be terminated.
If i am going to the change view of the Material Master & select Classification View(not plant specific)..ther shows nothing.
Could you plz help me out that,where exactly it stuck up.
Thanks
JPDear,
Please refer my reply from this thread and OSS note 555508
Re: Problems with confirmation production order
Hope it will also solve your problem.
Regards,
R.Brahmankar -
How to adjust SM21 logs retention Period
Hi,
My requirement it to get the system logs for minimum for 5 months,
i have set the parameter "rslg/max_diskspace/central"
but still i am getting the logs for 13 days only.
So please let me know the exact clean up job name for SM21 log,
so that i can adjust the retention period.
and also do i need to adjust the parameter "rslg/max_diskspace/local" too to get the required SM21 logs?
Regards,hi,
For the list of standard jobs please refer this sap note
16083 Standard jobs, reorganization jobs
1411877 New standard jobs
For the system log details please refer this points
1. The local system log file
a) File names
The local system log file that is written to each application server is determined by the profile parameter rslg/local/file.
The name of the file is usually SLOG<inr>, where <inr> is the instance number. Therefore, the name is SLOG77, for example.
In most systems, the profile parameter rslg/local/old_file is also set and points to a file SLOGO<inr>. This 'old' local system log file is not created by default. Instead, the current local system log file is written 'in a circle'.
b) File size
'Writing in a circle' means the following: If the file has reached the maximum size (profile parameter rslg/max_diskspace/local), the system overwrites the oldest entry with the latest entry and so on. The local system log file always has the same file size as of this moment. The profile parameter rslg/max_diskspace/local describes the maximum file size in bytes. If you switch from non-Unicode to Unicode, you must double the value of this profile parameter.
The central system log file
a) File names
The profile parameter rslg/central/file describes the name of the current central system log file, and the profile parameter
rslg/central/old_file describes the name of the 'old' central system log file.
b) Size of files
The profile parameter rslg/max_diskspace/central specifies a size in bytes. If the current system log file has reached half of this size, it is copied to rslg/central/old_file, and a new current central system log file is started.
Additionally refer this note
862 Reduce size of system log file
Regards,
Naveen.
Edited by: Naveen Kumar on Mar 5, 2012 2:18 PM -
Backup log is terminating abnormally
Hi Experts
I am unable to take the backup in tape, i am getting a error "sqlstate 42000" operation on device R3DUMP exceeded retry count backup log is terminating abnormally.
Thanks in advance
Regards
VenkatHi Experts
I am unable to take the backup in tape, i am getting a error "sqlstate 42000" operation on device R3DUMP exceeded retry count backup log is terminating abnormally.
Thanks in advance
Regards
Venkat -
When i see the SM21 logs for today and yesterday,
it is showing the log for yesterday for today and today's log for yesterday's date
I could find this from the time. Today 1 PM has not come untill now, but i have logs for today 1 PM
Please helpHello,
We have also noticed this at times. The results vary depending on what date you enter as the beginning date in the central log. For example, if the month has just changed and you enter the beginning date as 01/30/2010 thru 2/01/2010, the results show incorrectly. Our backup was done on 1/31/10 but shows as taking place on 2/1/10.
If I enter 1/30/2010 thru 1/31/2010 where the date range is all in one month, it appears correct, but if I enter a range that spans days in 2 months the central log isn't accurate.
We put in the rslgcoll patch this past week which fixed the incorrect year 2083 (per Note 1428174) and were hoping this would resolve the issue listed above as well. The year is now correct, but the other issue still is showing up if you enter a date range spanning days in 2 months.
Regards,
Cheryl -
Transaction termination error in SM21
HI All,
every day we are observing one error message in sm21 with one background user. The below is the error message description.
the transaction has been terminated. This may be caused by a
termination message from the application (MESSAGE Axxx) or by an
error detected by the SAP System due to which it makes no sense to
proceed with the transaction. The actual reason for the termination
is indicated by the T100 message and the parameters.
Can you please anybody help me out. why it is happening every day. one ore thing for this there is no dump in st22.
Thanks in advance for your valuable suggestions.
Regards,
Venkat.Hi,
Work around for you problem:
Could you please check whether user exists or not or user locked.
--Kishore -
Process Chain - Status Green but log says "Termination of chain "
Hello Friends,
One of the Steps in a Sub Chain of the Meta Chain shows the log as follows:
30.10.2009 05:20:28 Job started
30.10.2009 05:20:28 Step 001 started (program RSPROCESS, variant &0000000049485, user ID SCMREMOTE)
30.10.2009 05:20:35 Spool request (number 0000017553) created without immediate output
30.10.2009 05:20:35 Entire chain now has status 'G'
30.10.2009 05:20:35 Termination of chain has been reported to meta chain D6SBR9M64EV91ZX911UJI7K36
30.10.2009 05:20:35 Job finished
and the Step has changed to Green. So we normally assume that it has executed succesfully. Recently, there came this data issue. This step loads Open Sales Order data from a Cube to APO DP Planning area. Now few Open Sales Order Qty for a material are missing in planning area.
Does this step in the Process chain has executed Succefully or as the log says is it terminated? Though the step changes to green , were all the materials not loaded into planning area?
Please advice and suggest.
Thanks,
Chandra.Hii
This log shows that chain has been successfully terminated. This is a common log
The missing of Open Sales Order Qty for a material may be due to other reason .
Try to get into more details for which Orders this has happened and check in the source system.
Thanks
Sonal... -
Hi All,
I have been observing, there is a lot of below mentioned logs in sm21.
"Enqueue: Lock group 0D contains invalid lock mode /. Lock object ED"
Can u plz any one comment on this log meesage, why this is comming.
Thanks in advance..Hi Venkat,
You see locks when users are working, some tables will be locked by preventing other users changing the same table.
First check from how long these locks are and which user is responsible.If the locks are running for long then check the user is presently logged in and working or in any background job and you need to contact that user and confirm whether he is doing anything or not.After confirming with the user you can select and delete the locks after getting confirmed that it doesnt affect any current users work or background job or update request.
Regards,
Kalyan
Edited by: Kalyan Gupta on Mar 12, 2009 2:48 PM
Maybe you are looking for
-
I have restarted my computer numerous times and I get the message every time.
-
it is difficult to get refund, i have cancelled the product within 15 days, but I have not received my money back yet. Not sure how to claim the money
-
Financial Reporting Reports Formatted Differently in PDF
Hello all - I am working in a 11.1.2.1 environment. When I view Financial Reporting Studio reports in HTML, they appear formatted as I expect them to. When I view the same reports in PDF, it seems to drop any bolding or italicizing I do on the header
-
Hi Guys, I was just hoping to get your opinion on something. I have a procedure in Production that is taking longer and longer to finish and sticks on one certain section of code. The code is an INSERT into the main dimension table. This same procedu
-
Photoshop CC trotz Kündigung Geldeinzug
Ich habe die Software gekündigt, deaktiviert und vom Rechnung entfernt. Dennoch wurde mir einen Monat später wieder der Monatsbeitrag abgebucht. Der Kontakt mit Adobe ist nahezu unmöglich, da auf der Homepage nur vorgegeben Wege existieren, die nic