topic Re: Idoc Inbound Interface in Application Development and Automation Discussions

Idoc Inbound Interface

Former Member — Thu, 10 Nov 2005 23:11:12 GMT

I have a process where my freight rating PC, using MQSeries, triggers an inbound Idoc in SAP. This calls an SAP function which in turn prints a Packing Slip.

The output type for the packing slip is ZPL1 and always appeared as the 3rd output type on a packing slip. The function was coded by another person to always look for the packing slip in the 3rd position.

Now I have created a new output type ZBOL which means ZPL1 is now in the 4th position. I removed the hard coding and dynamically determine ZPL1 position.

I tested in Development/Test and it works.

But in production, when the PC triggers the Idoc, it still selects the 3rd output type to print.

The intesting thing is, I see the new code and when I walk through the code using debugger (WE19 / Inbound function module) in foreground mode it works by selecting the output type in 4th position.

Its like its still remembering the old program, but how?

What is going on?

Re: Idoc Inbound Interface

Former Member — Thu, 10 Nov 2005 23:17:02 GMT

This typically happens when your RFC connections are always logged on. Whenever you make changes to such functions, you need to restart your external RFC connection.

Restart your MQSeries connection with SAP (are you using business connector to connect the two?) and everything should be fine.

Srinivas

Re: Idoc Inbound Interface

Former Member — Thu, 10 Nov 2005 23:18:44 GMT

Jim,

Try to generate the function module which you changed. May be that will solve the problem.

Hope this helps.

Bipin