Symptom
- Job RC_COLLECT_ANALYSIS_DATA fails with message error below.
Error occurs with Data Volume Management data collection job TMW_RC_DVM_DATA_COLL.
Job cancelled after system exception ERROR_MESSAGE
- Checking data collection job TMW_RC_DVM_DATA_COLL, the following message error appears
DVM dataset not complete. RC = 1
DVM Message : DVM dataset not complete. Missing table sizes.
Internal session terminated with a runtime error XSLT_BAD_SOURCE_CONTEXT (see ST22)
Job cancelled
- Dump below is generated
Category XSLT Runtime Error
Runtime Errors XSLT_BAD_SOURCE_CONTEXT
Except. CX_XSLT_RUNTIME_ERROR
----------------------------------------------------------------------------------------------------
|Short Text
| XSLT: No valid XML source
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|What happened?
| The transformation cannot be carried out because the XML source
| document cannot be parsed.
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|Error analysis
| An exception has occurred which is explained in more detail below. The exception is assigned to class 'CX_XSLT_RUNTIME_ERROR' and was not caught in procedure "TMW_RC_COLLECT_DVM_DATA" "(FUNCTION)", nor was it propagated by a RAISING clause.
| Since the caller of the procedure could not have anticipated this exception, the current program was terminated.
| The reason for the exception is: Either the source document contains invalid XML, or the ABAP program that called the transformation is handling it incorrectly.
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|How to correct the error
| The exception must either be prevented, caught in procedure "TMW_RC_COLLECT_DVM_DATA" "(FUNCTION)", or the possibility of it occurring must be declared in the RAISING clause in the procedure.
| To prevent the exception, note the following:
| The most common cause of this error is a conflict between the encoding specification in an encoding declaration in program <?xml version="1.0"encoding="..."?> and the actual encoding of the data.
| If the document is kept in an ABAP string, the actual encoding must be the system code page. If this does not correspond to the encoding declaration, a parsing error can occur.
| Encoding conflicts of this kind often occur when XML documents are produced in a system as a string and imported into a system with a different character set as a string.
| XML documents should therefore be kept as binary data (x string) if they leave the system or can be accessed from outside.
| If the error occurs in a non-modfied SAP program, you might be able to
Category XSLT Runtime Error
Runtime Errors XSLT_BAD_SOURCE_CONTEXT
Except. CX_XSLT_RUNTIME_ERROR
----------------------------------------------------------------------------------------------------
| find a solution in the SAP Notes system. If you have access to the SAP Notes system, check there first using the following keywords: |
| "XSLT_BAD_SOURCE_CONTEXT" CX_XSLT_RUNTIME_ERROR
| "SAPLTMW_CTS_SWITCHES" bzw. LTMW_CTS_SWITCHESU17
| "TMW_RC_COLLECT_DVM_DATA"
Read more...
Environment
- SAP ERP 6.0
- SAP S/4 HANA
Product
Keywords
XSLT_BAD_SOURCE_CONTEXT, CX_XSLT_RUNTIME_ERROR, SAPLTMW_CTS_SWITCHES, bzw, LTMW_CTS_SWITCHESU17, TMW_RC_COLLECT_DVM_DATA , KBA , SV-SMG-DVM , Data Volume Management , SV-SCS-S4R , SAP Readiness Check , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview