topic Re: How to trigger inbound custom function module? in Application Development and Automation Discussions

How to trigger inbound custom function module?

Former Member — Thu, 12 Oct 2006 15:22:17 GMT

Hello Experts,

Could someone help me with my dilemma?

I have created a custom process code which is linked to a custom function module for processing inbound IDocs. I have tested the function module successfully and I have set up the partner profile accordingly. The IDocs are coming in but get stuck at status "64". My function module never gets triggered even though in the partner profile it is set up to be triggered immediately. Any idea what I am missing?

Thanks,

Marlin

Re: How to trigger inbound custom function module?

Former Member — Thu, 12 Oct 2006 15:38:32 GMT

Hi Marlin,

It seems the issue is to due to lacking resources within a very short time in the system. Another reason could be that released locks are not available in time.

Please check OSS Notes 734576 and 555229 for more information.

Other solution, perhaps you change the partner profile to trigger by background job. In this case, you can schedule a job to run program RBDAPP01. Do you process a large number of IDocs?

Hope this will help.

Regards,

Ferry Lianto

Re: How to trigger inbound custom function module?

Former Member — Thu, 12 Oct 2006 15:42:36 GMT

Collect the IDOCs which are in the status of 64 and then pass those as input to the RBDAPP01 program. It will process the IDOCS through your inbound function module.

Thanks'Eswar

Re: How to trigger inbound custom function module?

Former Member — Thu, 12 Oct 2006 15:44:57 GMT

I would also check if you have any short dumps in the system since IDOC may be passed to FM immediately, but if it causes short dump -> IDOC remains in 64.

Re: How to trigger inbound custom function module?

Former Member — Thu, 12 Oct 2006 15:53:46 GMT

Hello Ferry,

Thank you for your prompt reply.

I thought about changing the partner profile and using RBDAPP01 to process the IDocs; however, that is my last resort. But I will definitely look into the OSS notes that you suggested.

Just a quick question: I don't need to generate anything anywhere (except for the function module, of course) or link an event to something, somewhere, do I?

Thanks,

Marlin

Re: How to trigger inbound custom function module?

Former Member — Thu, 12 Oct 2006 16:02:55 GMT

Hi marlin ,

just go for these checks and let us know the status ..

1.Check here .

Bd51 – assignment of Inbound function module. Present or not

Check here .

2.Bd67 –assignment of process code to inbound function module /present or not.

Check here.

In the object for the message type u need to give the BUS object as the application object.

like bus2032

Now place a break-point in ur function module and run it in debugging mode ..

Now check whether this one is getting into ur function module , next check the status record of the document number .

regards,

vijay.

take an idoc , populate it from we19 and then there call the function module in debugging mode in back ground ..

we'll see if this is actually picking the Fm or not.

Message was edited by: Vijay

Re: How to trigger inbound custom function module?

Former Member — Thu, 12 Oct 2006 17:04:59 GMT

Hi Marlin,

Please ensure you have maintained the message/application object (WE57) to link your custom FM to message type and IDoc type. Also the inbound process code (WE42) as well.

Regards,

Ferry Lianto

Re: How to trigger inbound custom function module?

Former Member — Thu, 12 Oct 2006 18:23:21 GMT

Hello,

Thank you all for replying so quickly.

--Vijay and Ferry, yes, I have checked all of your suggestions and everything was correctly in place. However, I have to say that this inbound process is a little different and the problem that I am having may be due to this fact that the IDoc is coming in as message type DELINS (830) and IDoc type DELFOR01, but the application object is BUS3027 which is for Planned Independent Requirement. It is a long story but I had to take the data in the inbound IDoc and load it to transaction MD61. There is no IDoc type for Planned Independent Requirement and all the data is already in the inbound IDoc. Therefore, I created my own process code and function module to load the data. Now, in WE57, I have linked the function module to BUS3027 even though DELINS is coming in! Do you think this is causing the problem? I don't see why it should but I must admit that I am at my wits end!!

Thanks,

Marlin

Re: How to trigger inbound custom function module?

Former Member — Thu, 12 Oct 2006 19:00:05 GMT

Hello Siarhei,

You were right! I did get a short dump due to the DYNPRO being passed in the background.

Thank you for your help.

Thanks,

Marlin