Do you have any question about this error?
Message type: E = Error
Message class: SRT_CORE - Nachrichtenklasse für SOAP Runtime
Message number: 247
Message text: Monitor de mensajes WS - Descripción de campos
El sistema emite un mensaje de error y no le permitirá continuar con esta transacción hasta que se resuelva el error.
<ZH>Contents</>
<ZH>Fields description</>
<ZH>Status group and status code</>
<ZH>PAF status</>
<ZH>Message status</>
<ZH>Queue status</>
<ZH>Sequence status</>
<ZH>Task Watcher status</>
<ZH>Adapter type</>
<ZH>Restart, Retry and Maximum retry counter</>
Field name,,Description
ACTION_MSGID,,T100 Message ID for Recommended Action
ACTION_MSGNO,,T100 Message Number for Recommended Action
ADAPTER_TYPE,,Adapter type
ATTACHMENTS,,Indicator for message with attachments
CHANGED_BY,,User name of last change
CHANGED _TS,,UTC timestamp at last change
CHANGED _DATE,,Local date at last change
CHANGED _TIME,,Local time at last change
COMM_TYPE,,Communication type (Remote / Shortcut)
CREATED_BY,,User name of message creation
CREATED_TS,,UTC timestamp at message creation
CREATED_DATE,,Local date at message creation
CREATED_TIME,,Local time at message creation
CREATE_COMMIT_TIME,,Time between create and commit
DUMP_ERROR_ID,,ID of Runtime Error ("Terminated with dump"-selection
only)
DUMP_DATE,,Date of Runtime Error ("Terminated with dump"-selection only)
DUMP_TIME,,Time of Runtime Error ("Terminated with dump"-selection only)
ERROR_COUNTER,,Error count
ERROR_INDICATOR,,Application or system error
ERROR_TEXT,,Error information
ERROR_VERSION,,Last error version
EXPIRY_DATE,,Expiry date for finished, cancelled and isolated messages
HTTP_TIME,,Time for HTTP transport and protocol
IB_COMPONENT,,Receiver component
IB_IF_NAME,,Receiver interface name
IB_IF_NAMESPACE,,Receiver interface namespace
IB_IF_OPERATION,,Receiver interface operation
IB_PARTY,,Receiver party
IDOC_REQUEST_ID,,IDoc Request ID
IDOC_RESPONSE_ID,,IDoc Response ID
LAST_VERSION,,Last message version
LOCATION,,Location (Consumer / Provider)
LUW_SEQ_MESSAGES,,Number of sequence message in a Logical Unit of Work
(LUW)
MANDT,,Client identifier
MAX_RETRY_COUNTER,,Maximum retry counter (based on application
requirement)
MESSAGE_ID,,Message identifier
MESSAGE_SIZE,,Message size
MESSAGE_STATE,,Message status
MIGRATED,,Migrated from XI persistency
NEXT_RETRY_DATE,,Date of next retry
NEXT_RETRY_TIME,,Time of next retry
OB_COMPONENT,,Sender component
OB_IF_NAME,,Sender interface name
OB_IF_NAMESPACE,,Sender interface namespace
OB_IF_OPERATION,,Sender interface operation
OB_PARTY,,Sender party
OPERATION_TYPE,,Operation type (e.g. Compensate message)
PAF_STATE,,Process Agent Framework status
PARENT_ID,,Parent message identifier
PERSIST_ID,,Persistency identifier
PERSIST_TYPE,,Persistency type (XI/WS persistency)
PROD_VERSION,,Last productive message version
PROVIDER_TIME,,Provider system or application time
QUEUE_NAME,,Queue name
QUEUE_STATE,,Queue status
REF_ID_TYPE,,Reference identifier type (Update Task or bgRFC)
REF_ID_VALUE,,Identifier of update task or queue unit
RETENT_CATEGORY,,Retention category for finished, cancelled and isolated
messages
RETRY_COUNTER,,Retry counter (based on application requirement)
ROOT_CONTEXT_ID,,Root context identifier in Extended Passport
SCHEDULER_TIME,,Wait for bgRFC scheduler
SEQUENCE_ID,,Sequence identifier
SEQUENCE_STATE,,Sequence status
SRT_TIME,,Time of SOAP Runtime
STATE_CODE,,Processing status code
STATE_GROUP,,Processing status group
STATE_TEXT,,Text for processing status code
TOTAL_TIME,,Total processing time
TW_STATE,,Task Watcher status
TECHNICAL_SID,,Technical sequence identifier
TRANSACTION_ID,,Transaction identifier in Extended Passport
TW_TASK_ID,,Task Watcher identifier
WSRM_VERSION,,WSRM version
<ZH>Status group and status code</>
<ZH>Status group 'Application error'</>
Status code <ZH>'Application_Error'</>: Application error occurred
during message processing. See Error Log for more error details.
<ZH>Status group 'System error'</>
Status code <ZH>'Error_in_Compensate'</>: Compensate message failed.
Status code <ZH>'Error_in_Update_Task'</>: Message can't be processed
because an error in the Update Task..
Status code <ZH>'System_Error'</>: System error occurred during message
processing. See Error Log or bgRFC Monitor for more error details.
<ZH>Status group 'Wait for processing'</>
Status code <ZH>'Not_first_in_Queue'</>: Once all predecessors are
successfully finished, this message will be processed automatically.
Status code <ZH>'Not_first_in_WSRM'</>: Message processing has to wait
due to missing messages with lower message numbers.
Status code <ZH>'Processing'</>: Message is still processing.
Status code <ZH>'Queue_Lock'</>: The bgRFC queue is currently locked.
Status code <ZH>'Wait_for_Ack'</>: Wait for an acknowledgment from
application (Adapter Type GROUPWARE)
Status code <ZH>'Wait_for_Compensate'</>: Compensate message has to wait
for the Task Watcher (TU/C<(>&<)>C)
Status code <ZH>'Wait_for_Pull'</>: Wait for pulling from application
(for Adapter Type GROUPWARE)
Status code <ZH>'Wait_for_Retry'</>: Wait for retry
Status code <ZH>'Wait_for_Scheduler'</>: Message/Queue is waiting for
bgRFC scheduler to be processed.
Status code <ZH>'Wait_for_Update_Task'</>: Message processing has to
wait for the Update Task.
Status code <ZH>'Wait_for_Processing'</>: Message processing has to wait
for system resources.
<ZH>Status group 'Cancelled'</>
Status code <ZH>'Cancelled'</>: Message is manually cancelled.
Status code <ZH>'TUCC_Annulled'</>: Compensate message is annulled after
a TU/C<(>&<)>C scenario has been successfully finished.
<ZH>Status group 'Isolated'</>
Status code <ZH>'Isolated'</>: Based on the configuration, this message
is isolated and won't be transferred to provider system.
<ZH>Status group 'Finished'</>
Status code <ZH>'Delivered'</>: Message is successfully delivered to
provider system or to provider application.
Status code <ZH>'MP_Finished'</>: Message Mapping is successfully
finished (for Adapter Type MAPPING).
For a selection from within the message monitor (transaction SRT_MONI)
or Monitoring API (Interface IF_WSM_ACCESS_MONITOR) following additional
groups are available:
<ZH>Status group 'Errorneous'</>
contains status group <ZH>"Application error" </>and <ZH>"System error".
</>
<ZH>Status group 'Cancelled or isolated'</>
contains status group <ZH>"Cancelled" </>and <ZH>"Isolated".</>
<ZH>Status group 'Incomplete processing'</>
contains status group "<ZH>Application error", "System error" </>and<ZH>
"Wait for processing"</>.
<ZH>Status group 'Incomplete (no "pulling"-messages)'</>
same as <ZH>'Incomplete processing'</> but no "pulling"-messages (using
by Groupware).
<ZH>Status group 'Terminated with dump'</>
contains messages if the processing is terminated with a short dump
(Runtime error or RABAX).
<ZH>PAF status</>
<ZH>Processed,,</>Message is already processed by Process Agent
Framework.
<ZH>Reconciled,,</>Message is already reconciled by Process Agent
Framework.
<ZH>Reconcilable,,</>Reconciliation can be run for current message.
<ZH>Unknown,,</>Reconciliation is not always available and can lead to
exception because not all PAF Agents support reconciliation.
<ZH>Message status</>
<ZH>102 - Scheduled,,</>Message is scheduled and waiting for processing.
<ZH>103 - Finished,,</>Message is successfully delivered.
<ZH>110 - EV_Finish,,</>Event is successfully processed.
<ZH>111 - EV_Error,,</>Erroneous event processing
<ZH>112 - EV_Created,,</>Event is created.
<ZH>114 - Syst_Error,,</>System error.
<ZH>117 - Appl_Error,,</>Application error
<ZH>118 - Forwarded,,</>Error is forwarded due to Forwarded Error
Handling.
<ZH>119 - Changed,,</>Message payload was changed.
<ZH>121 - Cancelled,,</>Message is manually cancelled.
<ZH>122 - Annulled,,</>TU<(>&<)>C/C message is annulled.
<ZH>130 - Wait_Ack,,</>Wait for acknowledgment (Groupware scenario).
<ZH>131 - Wait_Pull,,</>Wait for pulling (Groupware scenario).
<ZH>132 - MP_Finish,,</>Mapping message is successfully processed.
<ZH>133 - Isolated,,</>Message is isolated due to configuration.
<ZH>134 - Cancel_Req,,</>Cancellation is requested for current message.
<ZH>Queue status (based on status of bgRFC Queue, Unit and Update Task)
</>
<ZH>Blocked,,</>Message is blocked due to predecessors.
<ZH>Comm_Error,,</>Communication error
<ZH>Empty,,</>Queue is empty.
<ZH>Executing,,</>Message is still processing.
<ZH>Execution_Error,,</>Execution error
<ZH>In_Other_Client,,</>Unit or queue was created in other SAP client
<ZH>Lock,,</>Queue is locked.
<ZH>Not_Found,,</>Queue not found
<ZH>Ready,,</>Queue/Unit is ready for processing.
<ZH>Server_Shutdown,,</>Application server is shutting down.
<ZH>Unknown,,</>Unknown queue or unit status
<ZH>Unit_Not_Found,,</>Unit not found
<ZH>UPD_Error,,</>Error in Update Task
<ZH>UPD_Not_Found,,</>Message not found in Update Task
<ZH>UPD_Wait,,</>Wait for processing in Update Task
<ZH>Wait_for_Retry</>,,Wait for retry
<ZH>Sequence status</>
<ZH>Closed,,</>Sequence is closed.
<ZH>Created,,</>Sequence is created but not used.
<ZH>Error,,</>Sequence is stopped due to error.
<ZH>Hard_Term_Req,,</>Hard termination is requested.
<ZH>In_Use,,</>Sequence is in use.
<ZH>Isolated,,</>Sequence is isolated due to configuration.
<ZH>Soft_Term_Req,,</>Soft termination is requested
<ZH>Task Watcher status</>
<ZH>Failed,,</>TW-Task processing failed.
<ZH>In_Process,,</>TW-Task is in process.
<ZH>Not_Found,,</>TW-Task is not found.
<ZH>Adapter type</>
<ZH>EVENT,,</>Event
<ZH>MAPPING,,</>Mapping
<ZH>PLAINSOAP,,</>Plain SOAP
<ZH>GROUPWARE,,</>Groupware scenario
<ZH>WS,,</>Standard Web Service
<ZH>XI,,</>XI peer-to-peer
<ZH>SHORTCUT,,</>Shortcut
<ZH>Retry, Maximum Retry Counter and Error Counter</>
After a message processing is terminated because of a system or
application error, you can restart the processing from within Message
Monitor. The error counter will be increased for each processing error.
In case the application has a temporary problem and can't process a
message, it can stop the processing by requiring the Web Service Runtime
to "retry" the processing of this message later. The default maximum
number of retry is 7.
The current error counter, current retry counter, max. retry counter and
also the local date and time of the next retry will be shown in the
message monitor in retry case (Processing status is "Wait_for_Retry").
Extracto de mensaje de error del sistema SAP. Copyright SAP SE.
Get instant SAP help. Start your 7-day free trial now.
Feature | Free Access | Free Trial |
---|---|---|
Basic SAP error explanation | ![]() |
![]() |
Step-by-Step Usage Guide | ![]() |
![]() |
Interactive SAP Coach Assistance | ![]() |
![]() |
AI Troubleshooting for T-Code Errors | ![]() |
![]() |
SRT_CORE246 Códigos de status de tarea BTM
¿Qué causa este problema? El sistema emite un mensaje de error y no le permit...
SRT_CORE245 Monitor de secuencias WS - Descripción de campos
¿Qué causa este problema? El sistema emite un mensaje de error y no le permit...
SRT_CORE248 Análisis de rendimiento
¿Qué causa este problema? El sistema emite un mensaje de error y no le permit...
SRT_CORE249 Códigos de status del Processing Agent Framework
¿Qué causa este problema? El sistema emite un mensaje de error y no le permit...
Los mensajes de SAP se dividen en 3 categorías diferentes:
mensajes de error (tipo de mensaje = E), mensajes de advertencia
(W) o informativos (I).
Un mensaje de error le impedirá continuar con su trabajo: es una parada difícil y debe corregir el error antes de poder continuar. Un mensaje de advertencia detendrá su trabajo, sin embargo, puede omitir la advertencia presionando la tecla Intro en su teclado. Dicho esto, sigue siendo una buena práctica investigar la causa del mensaje de advertencia y solucionarlo. Un mensaje de información no detendrá su trabajo y es realmente solo para fines informativos.
Haga clic en este enlace para buscar todos los mensajes de SAP.