Skip to Content
0
Former Member
Sep 30, 2013 at 06:12 AM

CALL_FUNCTION_PARM_UNKNOWN while running MIGO tcode

127 Views

Hi

While running MIGO tcode the following dump is appearing -

Can i resolve this error by applying any notes or do i have to take help from abaper for this.

Please tell me the note number to apply

Category ABAP Programming Error

Runtime Errors CALL_FUNCTION_PARM_UNKNOWN

  1. Except. CX_SY_DYN_CALL_PARAM_NOT_FOUND

ABAP Program CL_IM_WB2_MIGO_PROCESS========CP

Application Component LO-GT-TC

Date and Time 30.09.2013 07:44:08

Short text

Function parameter "I_DOC_TYPE" is unknown.

What happened?

Error in the ABAP Application Program

The current ABAP program "CL_IM_WB2_MIGO_PROCESS========CP" had to be

terminated because it has

come across a statement that unfortunately cannot be executed.

Function module "WB2_PROCESS_GO_SET_ITEM_DATA" was called

with the parameter "I_DOC_TYPE".

This parameter is not defined.

What can you do?

Note down which actions and inputs caused the error.

To process the problem further, contact you SAP system

administrator.

Using Transaction ST22 for ABAP Dump Analysis, you can look

at and manage termination messages, and you can also

keep them for a long time.

Error analysis

An exception occurred that is explained in detail below.

The exception, which is assigned to class 'CX_SY_DYN_CALL_PARAM_NOT_FOUND', was

not caught in

procedure "IF_EX_MB_MIGO_BADI~PBO_DETAIL" "(METHOD)", nor was it propagated by

a RAISING clause.

Since the caller of the procedure could not have anticipated that the

exception would occur, the current program is terminated.

The reason for the exception is:

Function module "WB2_PROCESS_GO_SET_ITEM_DATA" was called

with the parameter "I_DOC_TYPE".

This parameter is not defined.

How to correct the error

Probably the only way to eliminate the error is to correct the program.

If the error occures in a non-modified SAP program, you may be able to

find an interim solution in an SAP Note.

If you have access to SAP Notes, carry out a search with the following

keywords:

"CALL_FUNCTION_PARM_UNKNOWN" "CX_SY_DYN_CALL_PARAM_NOT_FOUND"

"CL_IM_WB2_MIGO_PROCESS========CP" or "CL_IM_WB2_MIGO_PROCESS========CM002"

"IF_EX_MB_MIGO_BADI~PBO_DETAIL"

If you cannot solve the problem yourself and want to send an error

notification to SAP, include the following information: