Hi Roman,
Please find following ST22 dump:
Short text
An exception occurred that was not caught.
What happened?
The exception 'CX_SOAP_CORE' was raised, but it was not caught anywhere along
the call hierarchy.
Since exceptions represent error situations and this error was not
adequately responded to, the running ABAP program
'CL_SRT_WSP_RT_CONFIG==========CP' has to be
terminated.
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
An exception occurred which is explained in detail below.
The exception, which is assigned to class 'CX_SOAP_CORE', was not caught and
therefore caused a runtime error.
The reason for the exception is:
Error when calling SOAP Runtime functions: <no error message available>:
("Operation "updateEMUsers{urn:ManagedSetupWSWsd/ManagedSetupWSVi/document}"
not supported (interface: "CO_DIAG_WILY_WS_MANAGED_SETUP" binding key:
"000C29DAC1181EE2B4B32CEBF62085F7"
Regards,
Nilutpal.