topic Re: Incorrect parameter with CALL FUNCTION - WE19 in Application Development and Automation Discussions

Incorrect parameter with CALL FUNCTION - WE19

Former Member — Wed, 17 Mar 2010 04:22:48 GMT

hi! All

while creating IDOC through WE19 - Start Inbound it creates IDOC with Status - 64."IDoc ready to be transferred to application" "No filters , No conversion , No version change ."

Incorrect parameter with CALL FUNCTION

This parameter was "MASSAVEINFOS".

but i have Included this parameter in my Function module.

INPUT_METHOD TYPE INPUTMETHD

MASS_PROCESSING TYPE MASS_PROC

NO_APPLICATION_LOG LIKE SY-DATAR

MASSAVEINFOS LIKE MASSSAVINF

whats the mistake i have done.

Regards

Re: Incorrect parameter with CALL FUNCTION - WE19

GauthamV — Wed, 17 Mar 2010 04:42:43 GMT

You can run BD20 transaction to change the status of idoc from 64.

Re: Incorrect parameter with CALL FUNCTION - WE19

Former Member — Wed, 17 Mar 2010 04:47:12 GMT

Hi,

In addition, check your partner profile settings if the IDOC mode is checked 'Trigger Immediately' or 'Collect IDOC'. If Collect IDOC is checked, the IDOCs will collected as a bunch and processed by a background job. Check 'Trigger Immediately' to see if the status changes.

Re: Incorrect parameter with CALL FUNCTION - WE19

Former Member — Wed, 17 Mar 2010 05:09:08 GMT

hi! Gautham

Tried to re send the IDOC there to i'm getting the same DUMP error Incorrect parameter with CALL FUNCTION

parameter was "MASSAVEINFOS"

whats the mistake i have done

Re: Incorrect parameter with CALL FUNCTION - WE19

Former Member — Wed, 17 Mar 2010 05:09:41 GMT

s trigger status is in - Trigger Immd.

Re: Incorrect parameter with CALL FUNCTION - WE19

Former Member — Wed, 17 Mar 2010 07:36:31 GMT

Hi,

Either the ref type for "MASSAVEINFOS" that is "MASSSAVINF", is incorrect or not expected in the importing parameters of your function module.

Regards,

Chen

Re: Incorrect parameter with CALL FUNCTION - WE19

Former Member — Thu, 18 Mar 2010 05:19:30 GMT

hi! Chen

Thanks for your reply

Since that parameter is not required that error came.

now i'm getting the Status - 51 Incorrect function module ZIDOC_INBOUND_KANBAN_MONITOR called up

as per the Diagnosis checked the Message Type and Idoc type assigned to the Functiona Module through the T.code WE57

Functional Module Function Type Basic Type Message Type

ZIDOC_INBOUND_KANBAN_MONITOR Function module ZSEG_KANBAN_MONITOR ZKANBANMESSAGE

were is the problem plz help me

Regards

Re: Incorrect parameter with CALL FUNCTION - WE19

Former Member — Thu, 18 Mar 2010 05:34:58 GMT

Also check if Proces code is assigned to ur Dunction Module in Transaction WE42.

Regards

Srikanth M

Re: Incorrect parameter with CALL FUNCTION - WE19

Former Member — Thu, 18 Mar 2010 05:56:54 GMT

Thanks for your reply.

checked in WE42; created Inbound process code exist.

where might be the problem.

since i'm new to this i cldnt guess were it may be.

kindly guide me

Regards

Re: Incorrect parameter with CALL FUNCTION - WE19

Former Member — Thu, 18 Mar 2010 06:20:43 GMT

Hi KV,

Have you created an entry in BD51?

Regards,

Chen

Re: Incorrect parameter with CALL FUNCTION - WE19

Former Member — Thu, 18 Mar 2010 06:35:52 GMT

hi! Chen

yes, created characteristics for the function module.

Function Module input dialog allowed

ZIDOC_INBOUND_KANBAN_MONITOR 1 un-check

regards

Re: Incorrect parameter with CALL FUNCTION - WE19

Former Member — Thu, 18 Mar 2010 06:54:21 GMT

Hi KV,

Below are the three important steps that need to be performed for inbound IDOCs. Make sure you have completed the below steps.

WE57: Assign Idoc to function module(not the function group).

BD51: Create an entry for Inbound function module.

WE42: Create inbound process code, here you also need to make sure that the FM name is attached.

Also check if the details have been entered properly in the Partner profile we20.

Regards,

Chen

Re: Incorrect parameter with CALL FUNCTION - WE19

Former Member — Thu, 18 Mar 2010 07:00:33 GMT

Sorry missed out WE82, but i guess you have done this too...

In the Partner profile check if the IDOC Type, Message Type and Process code are assigned correctly.

Regards,

Chen

Re: Incorrect parameter with CALL FUNCTION - WE19

Former Member — Thu, 18 Mar 2010 07:11:47 GMT

yes chen

assigned Message type & Basic Type in WE82

assigned Function Module, Basic Type, Message Type in WE57

assigned Inbound Process code and Function Module in WE42

assigned Function Module and Input Type in BD51

all the parameters are also assigned correctly in WE20.

chen where might be the problem

Regards

Re: Incorrect parameter with CALL FUNCTION - WE19

Former Member — Thu, 18 Mar 2010 07:28:13 GMT

Hi,

Try to debug Function Module ZIDOC_INBOUND_KANBAN_MONITOR from We19.

Regards

Srikanth

Re: Incorrect parameter with CALL FUNCTION - WE19

Former Member — Thu, 18 Mar 2010 07:53:17 GMT

That will not be possible KV, as the call to the FM is not being made, as far as i see you have completed the needed settings.

As i do not have access to an SAP system, i suggest that you try below,

1) Go to WE19, enter the IDOC number and F8.

2) In this screen, click on Inbound function module.

3) In the field for inbound function module press F4, it should list your FM name here if all the necessary we42/82/57, BD51 and WE20 have been done correctly.

Another thing that you can try is, on WE19,

1) Idoc Number F8

2) /h - to start Debug

3) Now click on Standard inbound, in the debug mode press F5 once.

4) Now put a break point on all message statement

See where exactly the message of wrong FM is being thrown, it will most probably be after a select statement on one of the tables associated with WE42/82/57/BD51 etc. With this you will where you have missed out.

All the best !!!

Regards,

Chen

Edited by: Chen K V on Mar 18, 2010 8:55 AM

Re: Incorrect parameter with CALL FUNCTION - WE19

Former Member — Thu, 18 Mar 2010 08:24:43 GMT

Thanks Chen for your kind reply.

Now the Status is in 62 - IDoc passed to application

why the document is not yet completed.

Regards

Re: Incorrect parameter with CALL FUNCTION - WE19

Former Member — Thu, 18 Mar 2010 08:36:30 GMT

Hi KV,

Try running the program RBDAPP01, or change the partner profile to process immediately.

Regards,

Chen

Re: Incorrect parameter with CALL FUNCTION - WE19

Former Member — Thu, 18 Mar 2010 11:20:33 GMT

Hi KV,

Sorry man i thought the status was 64, my bad i just looked up the post to check on the status and i realized my mistake...

Run the program RBCHSTA(i guess that is the name of the program, if not try RCHST in SE38 and do a F4)

This program will change the status back to 64, and then run RBDAPP01 again , this should do.

Regards,

Chen

Re: Incorrect parameter with CALL FUNCTION - WE19

Former Member — Thu, 18 Mar 2010 12:46:18 GMT

hi! Chen

Thanks for your Support.

If i execute an IDOC from

1. WE19 - Inbound Function Module I'm able to retrieve the records from IDOC but IDOC status is at 62

IDoc passed to application

2. If i directly execute the IDOC by Start Inbound Its status is 51 - No status record was passed to ALE by the application

tried debugging, there i'm not able to retrieve the IODC status record. where might the problem

Regards