Reg: Problem in Positing IDOC

[Former Member]

Hi,

I got below warning message in we02.

No resources, immed. processing not possible: Too few free dialog work

processes

Message no. B1999

Just i tried in WE19 it also showing Error Message "Interface for function ZTESTFUNC Is incorrect".

Can u give solution for this.

With Regards,

Raj

[Former Member]

Hi,

I got below warning message in we02.

No resources, immed. processing not possible: Too few free dialog work

processes

Message no. B1999

Just i tried in WE19 it also showing Error Message "Interface for function ZTESTFUNC Is incorrect".

Can u give solution for this.

With Regards,

Raj

[Former Member]

The first message means that at the time you tried to execute WE02 there were no free dialog processes available on the application server you logged on to SAP. You can check in SM50 to see how many processes there are and who is using them.

Regarding the interface error message, I assume you are using an Z function module to process your iDoc but the interface of your Z-function seems to have wrong/missing parameters.

If that is not the case please provide more details on what exactly you try to do.

Regards,

Michael

[Former Member]

Hi Michael,

I want transfer PO Details as Sales order.

I have configured Inbound settings and FM interface settings which i followed:-

Inbound IDoc Posting Function Module

In the receiving system, create a function module Z_IDOC_INPUT_ZRZSO_MT using SE37. Below, I have described the logic for the same.

Add Include MBDCONWF. This include contains predefined ALE constants.

Loop at EDIDC table

Check if the message type is ZRZORDER. Otherwise raise WRONG_FUNCTION_CALLED exception

Loop at EDIDD table

Append data from the segments to appropriate internal tables

For example: append data from ZRZSEG1 segment to the internal table of type ZCUSTOMERS

Update the DDic tables from internal tables

Depending on the result of the update, fill the IDoc status record (type BDIDOCSTAT) and append it to the corresponding table.

Status 53 => Success

Status 51 => Error

You can download the sample ABAP code for the above function module here.

Inbound Settings

Define Logical Systems u2013 Transaction SALE (Please refer to Outbound Settings discussed in previous part)

Assign Client to Logical System u2013 Transaction SALE (Please refer to Outbound Settings discussed in previous part)

Maintain RFC Destinations u2013 Transaction SM59 (Please refer to Outbound Settings discussed in previous part)

Define Ports u2013 Transaction WE21 (Please refer to Outbound Settings discussed in previous part)

Generate/Create Partner Profile u2013 Transactions BD82/WE20 (Please refer to Outbound Settings discussed in previous part)

Assign Function Module to Logical message u2013 Transaction WE57

Create a new entry

Specify name of the Function Module as Z_IDOC_INPUT_ZRZSO_MT

Also, specify Type as F, Basic IDoc type as ZRZORDER, Message type as ZRZSO_MT and Direction as 2 (Inbound)

Save the entry

Define Input method for Inbound Function Module u2013 Transaction BD51

Create a new entry

Provide Function Module name as Z_IDOC_INPUT_ZRZSO_MT

Specify the Input method as 2

Save the entry

Create a Process Code u2013 Transaction WE42

Create a new Process Code ZPCRZ

Select Processing with ALE Service

Choose Processing type as Processing by function module

Save the entry

On the next screen, select your function module from the list

Save the changes

Now you will be taken to the next screen

Double-click on Logical message

In the Assignment to logical message, specify the message type ZRZSO_MT

Save the changes

rgds,

raj

[nkr1shna]

Hi Raja,

Please check the SAP note 796631 which talks about error generated during IDOC generation.

Hope this note can help you to do analysis on this issue.

Let me know whether issue got resolved or still exists?

Regards

Krishna

[Former Member]

What I meant is that it looks like the interface for your function module is not correct. Please check, if the function module you are using to process your Idoc has the following interface:

*"*"Local Interface:
*"  IMPORTING
*"     REFERENCE(INPUT_METHOD) TYPE  INPUTMETHD
*"     REFERENCE(MASS_PROCESSING) TYPE  MASS_PROC
*"  EXPORTING
*"     REFERENCE(WORKFLOW_RESULT) TYPE  WF_RESULT
*"     REFERENCE(APPLICATION_VARIABLE) TYPE  APPL_VAR
*"     REFERENCE(IN_UPDATE_TASK) TYPE  UPDATETASK
*"     REFERENCE(CALL_TRANSACTION_DONE) TYPE  CALLTRANS2
*"  TABLES
*"      IDOC_CONTRL STRUCTURE  EDIDC
*"      IDOC_DATA STRUCTURE  EDIDD
*"      IDOC_STATUS STRUCTURE  BDIDOCSTAT
*"      RETURN_VARIABLES STRUCTURE  BDWFRETVAR
*"      SERIALIZATION_INFO STRUCTURE  BDI_SER
*"  EXCEPTIONS
*"      WRONG_FUNCTION_CALLED

That should do it,

Michael

[Former Member]

Hi Michael,

Thanks a lot Michael . It is working now.

Thanks and regards,

Raja

fd

[Former Member]

Hi!

Michael

Everything is correct as per interface you suggested and instead of that I am getting this error

"Immediately processing not possible: Incorrect parameter with CALL FUNCTION."

And when I double click on that to see the Performance Assistant it shows

"Immediately processing not possible: Incorrect parameter with CALL FUNCTION.

Message no. B1999"

Your response is appreciated.