CALL_FUNCTION_ILLEGAL_P_TYPE is an ABAP runtime error which you may come across when using or developing within an SAP system. See below for the standard details explaining what it means and how you can avoid or fix this runtime error.
Short Dump Classification: A - ABAP Programming Error
You can view further information about a runtme error by using transaction code ST22 which will show you this and all runtime erros that have happen in your SAP system.
Also check out the Comments section below to view or add related contributions and example screen shots.
See SAP Note #611004
Parameter: <runtime parameter>
Wrong parameter type in an RFC call
Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.
Correct the interfaces between the caller and the function module
accordingly.
Also check whether the Remote Function Calls preceding the incorrect
call are correct.
See 'What happened?'
The error occurs if parameters are submitted incorrectly in a Remote
Function Call.
Example:
A table is submitted on the client as CHANGING, but is declared with
TABLE in the function module that is called on the server.
Client: Server:
CALL FUNCTION 'TEST' FUNCTION TEST. DESTINATION
'NONE'
CHANGING TABLES
TAB_CHG = E_TAB. TAB_CHG STRUCTURE RFCT
The following error message is triggered:
"Error PARAMETER CONVERSION ERROR occurred.
P1=CALL_FUNCTION_ILLEGAL_P_TYPE"
CALL_FUNCTION_ILLEGAL_P_TYPE - call function illegal p type CALL_FUNCTION_ILLEGAL_PARMLIST - call function illegal parmlist CALL_FUNCTION_ILLEGAL_LEAVE - call function illegal leave CALL_FUNCTION_ILLEGAL_INT_LEN - call function illegal int len CALL_FUNCTION_ILLEGAL_DATA_TYP - call function illegal data typ CALL_FUNCTION_ILLEGAL_CODE - call function illegal code