Do you have any question about this error?
Message type: E = Error
Message class: SRT_CORE - Nachrichtenklasse für SOAP Runtime
Message number: 206
Message text: Unequal number of messages and bgRFC units
In some releases without a necessary Support Package there was no
relation between a Web Service message and the bgRFC unit ID. Therefore,
it is not available to determine which message is belonging to which
bgRFC unit.
For these "old" messages only a check of number of bgRFC units and
according messages stored as incomplete in XI persistency is necessary.
This kind of checks can only be doen on the provider side because on
consumer side a bgRFC unit can contain more than one Web Service
message.
This check is now failed for the current message.
This might happen if the bgRFC queue is deleted manually from within the
bgRFC Monitor. Therefore, never delete a bgRFC unit or queue from within
bgRFC Monitor.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
All messages of the current sequence and bgRFC queue are now in an
inconsistent state and it is not clear whether some of them are already
delivered.
Following steps are necessary to clean up this situation:
Look at the message payload by clicking the "Message State" to run the
XI Message Monitor.
Based on the payload contact the responsible Web Service application and
ask for checking whether you can terminate the whole sequence and if
necessary delete all units of the affected bgRFC queue by using the
Sequence Monitor and the bgRFC Monitor.
Error message extract from SAP system. Copyright SAP SE.
SRT_CORE206
- Unequal number of messages and bgRFC units ?Get instant SAP help. Start your 7-day free trial now.
SRT_CORE205
Wait for Update Task
What causes this issue? The Web Service Reliable Messaging (WS RM) couldn't process the current message within the Update Task because the Updat...
SRT_CORE204
bgRFC Unit is not found
What causes this issue? The unit of a bgRFC queue using in Web Service Reliable Messaging (WS RM) is no longer valid even if there are still messages...
SRT_CORE207
Compensate message still in process
What causes this issue? The compensate message is still waiting for processing by the Task Watcher (TW) which is used for Tentative Update and Compen...
SRT_CORE208
Invalid compensate message in Task Watcher
What causes this issue? This compensate message is no longer valid within the Task Watcher (TW) which is used for Tentative Update and Compensate or ...
Click on this link to search all SAP messages.