Incorrect parameter with CALL FUNCTION - WE19

[Former Member]

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

Kv

[GauthamV]

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

[Former Member]

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

[Former Member]

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.

[Former Member]

s trigger status is in - Trigger Immd.

[Former Member]

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

[Former Member]

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

kv

[Former Member]

Hi

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

Regards

Srikanth M

[Former Member]

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

kv

[Former Member]

Hi KV,

Have you created an entry in BD51?

Regards,

Chen

[Former Member]

hi! Chen

yes, created characteristics for the function module.

Function Module input dialog allowed

ZIDOC_INBOUND_KANBAN_MONITOR 1 un-check

regards

Kv

[Former Member]

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

[Former Member]

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

[Former Member]

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

Kv

[Former Member]

Hi,

Try to debug Function Module ZIDOC_INBOUND_KANBAN_MONITOR from We19.

Regards

Srikanth

[Former Member]

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

[Former Member]

Thanks Chen for your kind reply.

Now the Status is in 62 - IDoc passed to application

why the document is not yet completed.

Regards

kv

[Former Member]

Hi KV,

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

Regards,

Chen

[Former Member]

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

[Former Member]

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

Kv

[Former Member]

Hi! Chen

Thanks for your Support. After appending IDOC Status I'm able to get IODC Status as 53.

i have followed the steps for o reach Outbound IDOC status - 03 & Inbound IDOC Status - 53,

but (Questioning is wrong at this end sorry to trouble you)

Sender Client - 300

Receiver Client - 984

Both the clients have Function Modules to Distribute the IODC and to Retrieve IODC

how come Client 984 will come to know IDOC have been sent to 984 from 300 how read it. Can you explain me regarding the integration.

Regards,

Kv

[Former Member]

Hi KV,

Though not an expert, below is my understanding of the IDOC communication between two systems.

IDOCs in SAP use TRFC as communication protocol.

Sender Client: 300, Receiving Client: 984.

Now when you send an IDOC from 300, you fill up the IDOC control record with sender and receiver info, based on which the corresponding partner profile is set up. In the partner profile you set up the PORT which is nothing but a RFC destination.

No when an IDOC is sent from 300, it makes a TRFC call to the 984 system, and here since you would have set up the process code in the partner profile(again picked up from control record of the IDOC), the system knows which posting FM to use.

Hope it was helpful

Regards,

Chen

[Former Member]

hi! Chen

Thanks for your full support.

yes its more useful.

the main thing to communicate is Partner Profile between clients.

now I'm not able to generate the Inbound parameter from the client 984. and also not able to distribute the model

sorry to trouble you more . . . where i have done the mistake

Regards

Kv

[Former Member]

Not Sure if i understand the issue, can you elaborate a little more.

Regards,

Chen

[Former Member]

hi! Chen

I'm generating the Partner profile using the T.code BD64

in that its generating :

Partner:

Sender

Receiver

Port

Reciver SAPSCD

Outbound Parm

Receiver Zmessage Zsegment

but not generating Inbound Parameter.

Where the problem is

Regards

Kv