Symptom
Users are unable to access the transaction code RSPLAN which triggers a dump in transaction ST22 as below:
Runtime Errors: CALL_METHOD_CONFLICT_TYPE
Exception: CX_SY_DYN_CALL_ILLEGAL_TYPE
ABAP Program: CL_RSR_TIME_RELATION_HDB======CP
Application Component: BW4-ME
......
1 CX_SY_DYN_CALL_ILLEGAL_TYPE
(Program) CL_RSR_TIME_RELATION_HDB======CP
(Include) CL_RSR_TIME_RELATION_HDB======CM008
(Row) 92
(Short Text) Call of the method GET_VALID_FISCPER of the class
CL_RSR_TIME_RELATION_HDB failed; wrong type for parameter
I_FISCYEAR
(Long Text) A type conflict occurred when the program tried to passan actual
parameter to the formal parameter 'I_FISCYEAR' of the method
'GET_VALID_FISCPER' of the class'CL_RSR_TIME_RELATION_HDB'.
CLASSNAME CL_RSR_TIME_RELATION_HDB
FORM
FUNCTION
IS_RESUMABLE
KERNEL_ERRID
METHODNAME GET_VALID_FISCPER
PARAMETER I_FISCYEAR
PARAM_NUMBER 0
PROGNAME
Read more...
Environment
- SAP BW/4 HANA
-
SAP NetWeaver
Product
Keywords
rsplan, bw4, call_method_conflict_type, cx_sy_dyn_call_illegal_type, cl_rsr_time_relation_hdb, planning functions, planning sequences, rsrhierarchyvirt. , KBA , BW-PLA-IP , Integrated Planning , EPM-BPC-BW4-PLA , BPC/4 - Planning Enginee , 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