topic Re: Problem with inbound idoc in Application Development and Automation Discussions

Problem with inbound idoc

Former Member — Mon, 11 Jan 2010 10:29:21 GMT

Hi all,

I am doing IDOC to transfer data from one ZTable of source client to another client in a ZTable.

My inbound IDOC is processed with status 64.So I am using RBDAPP01 report, giving IDOC no, my message type and executing.Then I am getting dump as follows:

What happened?

When calling a function module, one of the parmaeters was not

specified.

Error in the ABAP Application Program

The current ABAP program "SAPLBD20" had to be terminated because it has

come across a statement that unfortunately cannot be executed.

Error analysis

An exception occurred that is explained in detail below.

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

not caught in

procedure "IDOCS_PASS_TO_APPLICATION" "(FORM)", 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:

When calling the function module "ZFM_IDOC_STUDENT", one of the parameters

needed according to the interface description was not specified.

This parameter was "INPT_METHOD".

I maintained input method in BD51 in my receiver side.Even I am getting above dump.

Please suggest why input method value is taking as space here.

Re: Problem with inbound idoc

nirajgadre — Mon, 11 Jan 2010 10:43:12 GMT

Hi,

I guess you are not passed the one of the mandatory parameters to the function module ZFM_IDOC_STUDENT.

check all the parameters which are required for this function module.

Re: Problem with inbound idoc

former_member404244 — Mon, 11 Jan 2010 10:43:32 GMT

Hi,

Can you please give us the inbound side ALE configurations... also you can debug the function module... use we19 tcode and specify the idoc number whihc was in 64 status and then specify the funcation module and call in debug mode and debug the function module..

Regards,

Nagaraj

Re: Problem with inbound idoc

Former Member — Mon, 11 Jan 2010 10:45:44 GMT

Hi Jaya,

Have you specified the input method in the import parameters in your function module and have u defined the function module in inbound process code. please explain the configuration you did to receive and process the data in brief.

Re: Problem with inbound idoc

Former Member — Mon, 11 Jan 2010 11:09:44 GMT

Hi , my problem is solved. I made my importing parameters optional.Now it's working fine.

My importing parameters :

INPT_method

Mass_processing

I maintained INPT_method through BD51 tcode and I left maintaining value for mass processing.

I wonder why I am getting dump as Input method is missing...

Edited by: Jaya on Jan 11, 2010 12:12 PM

Re: Problem with inbound idoc

Balu483 — Tue, 23 Feb 2016 12:27:24 GMT

naming convention is considered in case of inbound function module creation.

one of the parameters needed according to the interface description was not specified

for this kind of run time errors in case of IDOCS will causes ,because of different parameters names for our custom inbound function module and standard function module