Symptom
It is not possible to download DVM data from ST14, or use ANALYSISBROWSER or DVM_SETUP via ST13, as the below dump is generated:
Category ABAP programming error
Runtime Errors CALL_FUNCTION_CONFLICT_LENG
Except. CX_SY_DYN_CALL_ILLEGAL_TYPE
ABAP Program /SSF/DLBROWSER
Application Component SV-SMG-MON-BPM
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
Short Text
Type conflict during a function module call (field length).
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
What happened?
Error in the ABAP application program.
The current ABAP program "/SSF/DLBROWSER" had to be terminated because it
found a
statement that could not be executed.
A function module was called incorrectly.
---------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------
Error analysis
An exception has occurred in class "CX_SY_DYN_CALL_ILLEGAL_TYPE". This
exception was not caught
in procedure "FILL_DEST_AUTO_SETTINGS" "(FORM)" or 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 occurring was:
The reason for the exception is:
The call to function module "/BDL/_GET_SDCC_CUSTOMIZING_NEW" is incorrect:
In the function module interface, it was stipulated that only fields of
a specific type and length can be specified under "RFCLIST". The currently
specified field )"LT_SDCC_RFCLIST_NEW") has the right type, but its length is
incorrect.
---------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------
Information on where terminated
The termination occurred in ABAP program or include "/SSF/DLBROWSER", in
"FILL_DEST_AUTO_SETTINGS". The
main program was "/SSF/DLBROWSER".
In the source code, the termination point is in line 2221 of include
"/SSF/DLBROWSER".
include "/SSF/DLBROWSER".
The termination is due to exception "CX_SY_DYN_CALL_ILLEGAL_TYPE" occurring in
procedure "FILL_DEST_AUTO_SETTINGS" "(FORM)",
but not being handled locally there or being declared in the RAISING
clause.
The procedure is in program "/SSF/DLBROWSER". Its source code begins in line
2106 of
include "/SSF/DLBROWSER".
---------------------------------------------------------------------------------------------------
Source Code Extract
---------------------------------------------------------------------------------------------------
2220| IF SY-SUBRC = 0.
>>>>>| CALL FUNCTION '/BDL/_GET_SDCC_CUSTOMIZING_NEW'
2222| EXPORTING
2223| GET_SDCC_CUST = 'X'
Read more...
Environment
ST-PI >= 740 SP21 and ST-A/PI <= 01V* SP03
Product
Keywords
DVM, ST13, ST14, ANALYSISBROWSER, DVM_SETUP, dump, CALL_FUNCTION_CONFLICT_LENG, /SSF/DLBROWSER, FILL_DEST_AUTO_SETTINGS, The call to function module /BDL/_GET_SDCC_CUSTOMIZING_NEW is incorrect, CALL FUNCTION '/BDL/_GET_SDCC_CUSTOMIZING_NEW', CUST_DMA_TAANA, , KBA , SV-SMG-DVM , Data Volume Management , 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.