SLAW2 usage -> Hourly dump because of /BDL/SAPLBDL11_6X

[benoit-schmid]

Good morning,

I have sent the slaw2 consolidated informations on one of our system.

Since that I keep having the following dumps, each hour, in this system:

Category ABAP Programming Error
Runtime Errors CALL_FUNCTION_CONFLICT_TYPE
Except. CX_SY_DYN_CALL_ILLEGAL_TYPE
ABAP Program /BDL/SAPLBDL11_6X
Application Component SV-SMG-SDD
Date and Time 07.11.2018 03:55:37

Error analysis
An exception has occurred which is explained in more detail below. The
exception is assigned to class 'CX_SY_DYN_CALL_ILLEGAL_TYPE' and was not
caught in procedure
"/BDL/_TRANSFER_DATA_6X" "(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:
The call to the function module "LAW_SET_TRANSFER_OK" is incorrect:

The function module interface allows you to specify only
fields of a particular type under "BDLDATKEY".
The field "LS_CONTENT_KEY" specified here is a different
field type
.

Would you know how to fix this problem?

Not only do we waste time working for SAP by doing the yearly audit,

we also have to beta test their code 🙂

Thanks in advance for your answer.

[benoit-schmid · Accepted solution]

Good morning,

Thanks Yogel for your answer.

In our case this has been solved with the Note 579690.

Have a good day.

[patelyogesh]

Hello Benoît Schmid,

Please check SAP note :

2554666 - Dump CX_SY_DYN_CALL_ILLEGAL_TYPE in Function Module /BDL/_TRANSFER_DATA_6X

Thank you

Yogesh Patel