Error while testing Inbound Idoc

[Former Member]

The error message "Interface for function Z***** is incorrect*." is shown while trying to test an incoming IDOC in we19.

PL HELP!!!!!!!

The procedure followed by me was,

WE31 created custom segments,

WE30 Created custom basic type,

we81 Custom message type,

se37 function module,

we82,

we57,

bd51,

we42,

bd67,

we20,

Am not able to figure out why exactly is the error message being shown.

please tell me if a step was missed or what the possible error is, I think the parameters of function module are correct....

[Former Member]

Hi friend,

if it is help full please give max reward point.

Standard program, RBDMOIND is scheduled or executed online to determine whether the communication was successful. If IDoc is Dispatched to destination system, RBDMOIND updates the status of the IDoc to 12 (Dispatched OK), Otherwise remains in status 03.

Two programs enable cross-system reporting:

 RBDSTATE: It reports the status of the incoming IDocs to sending system, using ALEAUD message and ALEAUD01 IDoc

 RBDAUD01: It executed on sending system to analysis the audit log and display the output as a report

IDoc Status in Receiving System IDoc status in Sending System via ALEAUD

53 – Application docu posted => 41 – Application docu created in receiving sys

51 – Error: Application docu => 39 – IDoc in receiving sys. Status repeated

not posted each time RBDSTATE runs.

68 – Error: No further processing => 40 – Application docu not created

ALE Auditing

BDM7 => ALE Audit: Statistical Analysis

BDM8 => ALE Audit: Sending the Confirmations

RBDSTATE => Run on Receiving System to return Audit Message

[Former Member]

Hi Friend,

u can do from these t-code. if help full please give me max reward point.

Test

WE19 TEST TOOL FOR IDOC PROCESSING

WE15 SELECTION PROGRAM ISSUING OUTPUT

WE14 PROCESS ALL SELECTED IDOC (EDI)

WE18 GENERATE TEST STATUS FILE FOR OUTBOUND IDOC

WE17 PROCESS STATUS FILE (TRIGGER STATUS PROCESSING)

WE12 INBOUND PROCG OF MODIFIED OUTBOND FILE

WE16 INBOUND PROCG OF ORIG.INBOUND FILE

[Former Member]

You are trying to post an inbound idoc via a customer created function module?

Just make sure that your function has following interface:

*" IMPORTING

*" VALUE(INPUT_METHOD) LIKE BDWFAP_PAR-INPUTMETHD

*" VALUE(MASS_PROCESSING) LIKE BDWFAP_PAR-MASS_PROC

*" EXPORTING

*" VALUE(WORKFLOW_RESULT) LIKE BDWF_PARAM-RESULT

*" VALUE(APPLICATION_VARIABLE) LIKE BDWF_PARAM-APPL_VAR

*" VALUE(IN_UPDATE_TASK) LIKE BDWFAP_PAR-UPDATETASK

*" VALUE(CALL_TRANSACTION_DONE) LIKE BDWFAP_PAR-CALLTRANS

*" TABLES

*" IDOC_CONTRL STRUCTURE EDIDC

*" IDOC_DATA STRUCTURE EDIDD

*" IDOC_STATUS STRUCTURE BDIDOCSTAT

*" RETURN_VARIABLES STRUCTURE BDWFRETVAR

Just use a standard function module as reference, e.g. idoc_input_material

hope this helps

*" SERIALIZATION_INFO STRUCTURE BDI_SER

*" EXCEPTIONS

*" WRONG_FUNCTION_CALLED

[Former Member]

The parameters of the function module are correct......

I have to create a Custom function module, cannot use a standard function module.

Any other reasons as to why the error is being shown???

[Former Member]

Check your settings via program RBDMOINC

( fill in your message type in the selection screen)

[Former Member]

Hi Ajith,

I am also finding similar problem.

Please provide me the solution you got / found.

As per my R&D i found that the Program is finding the Old parameters of the funciton inprogram SAPMSED5 line number 346. Here it trying to compare with actual parameters of the ZFunction Module.

Eg:, Export Parameters (Old):PROCES_DATA_NEXT, RETURN_CODE.

Regards,

Manju