Symptom
You find that Job executing SBAL_DELETE fails due to CONNE_IMPORT_WRONG_COMP_TYPE dump.
Joblog shows:
dd.mm.yyyy hh:mm:ss Job started
dd.mm.yyyy hh:mm:ss Step 001 started (program SBAL_DELETE, variant &000000000000<nr>, user ID <username>)
dd.mm.yyyy hh:mm:ss Internal session terminated with a runtime error CONNE_IMPORT_WRONG_COMP_TYPE (see ST22)
dd.mm.yyyy hh:mm:ss Job canceled
If you directly go to SE38 transaction for SBAL_DELETE report, and try to display Variant &000000000000<nr>, you get same dump:
Category ABAP programming error
Runtime Errors CONNE_IMPORT_WRONG_COMP_TYPE
Except. CX_SY_IMPORT_MISMATCH_ERROR
ABAP Program SBAL_DELETE
Application Component BC-SRV-BAL
Date and Time dd.mm.yyyy hh:mm:ss
Short Text
Error during IMPORT of object "S_LOG_NM".
What happened?
Error in the ABAP application program.
The current ABAP program "SBAL_DELETE" had to be terminated because it found a
statement that could not be executed.
Error analysis
When importing object "S_LOG_NM", component number 3 in the dataset had a
different data type to the corresponding component of the target object
in program "SBAL_DELETE".
The data type is "N" in the dataset, but "C" in the program.
Read more...
Environment
SAP NetWeaver
Product
Keywords
CONNE_IMPORT_WRONG_COMP_TYPE, SBAL_DELETE, CX_SY_IMPORT_MISMATCH_ERROR, S_LOG_NM
The data type is "N" in the dataset, but "C" in the program , KBA , BC-SRV-BAL , Basis Application Log , How To
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.